6 ms·

It's an utter waste of time for developers, business, everyone. Millions of lines of Go code have been written without generics. Libraries have been written. Su

It's an utter waste of time for developers, business, everyone. Millions of lines of Go code have been written without generics. Libraries have been written. Support, maintenance, cost, etc. This is why one shouldn't pick languages that regress in features from the get go. Now developers will waste time migrating the code to stdlib. This is not solving problems. This is doing tech for the sake of doing tech. Wasting everyone's time. Remember that code is not the deliverable.

pstuart 2mo ago
I'm confused by what language regression you are referring to. > Now developers will waste time migrating the code to stdlib Why? If it works now it works. Refactoring tools exist, and LLMs make this trivial. You just seem to hate the language and everything about it, and that's your right but I think your arguments are specious and ignore that most language that go mainstream evolve and that comes with tradeoffs (python2 -> python3, rust in general, etc). And as far as deliverables go, the code is absolutely foundational to that and Go was made to be maintainable by codemonkeys such as myself. Anyway, the language and the changes noted in the OP apparently aren't for you and that's ok -- there's plenty of languages out there for everyone's taste.
- deleted 2mo ago
  [deleted]
jppittma 2mo ago
Claude will migrate your whole repo in an hour.
- kokada 2mo ago
  I assume they will eventually add those to `go fix` too, so you don't even need Claude for the most basic refactors (the more complex ones, sure).
  - pstuart 2mo ago
    Likely but it may be asking too much to condense copypasta into generics -- but the tooling does improve on each release.
wbl 2mo ago
Nothing was broken in the change: there is no need to migrate.