OvervCW

4 ms·

1. 31.▲
   by OvervCW 1y ago

   No need to talk about generics when we can talk about something simple like the inability to implement type safe enums in Go.
2. 32.▲
   by OvervCW 1y ago

   They are similar in the sense that there are very few abstractions, relying on the programmer to reimplement common patterns and avoid logical mistakes. You have to put thought into such things as: - Did I add explicit checks for all the er
3. 33.▲
   by OvervCW 1y ago

   In this specific blog post I suppose only "Ranging Directly over Integers" counts, but I was more generally referring to the introduction of features like generics.
4. 34.▲
   by OvervCW 1y ago

   I'm amused by posts like this because it shows that Go is finally slowly moving away from being an unergonomically simplistic language (its original USP?) to adopt features a modern language should have had all along. My experience dev
5. 35.▲
   by OvervCW 1y ago

   What does DO mean in this context?
6. 36.▲
   by OvervCW 1y ago

   Serverless only makes sense if the lifetime doesn't matter to your application, so if you find that you need to think about your lifetime then serverless is simply not the right technology for your use case.
7. 37.▲
   by OvervCW 1y ago

   Agree, it seems like they decided to use Cloudflare Workers and then fought them every step of the way instead of going back and evaluating if it actually fit the use case properly. It reminds me of the companies that start building their a