

I have. Go is verbose


I have. Go is verbose


Haven’t python reintroduced the infix notation? That’s incredibly exhausting and lame. A simple fuck you would look much fancier


Hey, here’s my downvote.
I placed it not because I’m angry or disagree with your original statement, but because you have already acquired several downvotes and I just feel peer pressure to downvote you to hell


I remember her as a sip of fresh air. No other OS was this appealing


Well, you can’t “exterminate” a movement, idea, or people. You can only make it boring or not worthy of attention


Windows Vista walked away as the fastest.
My girl
He did. In 2014 with Crimea
That’s one way to lift Buendia family curse
Haha, the same. Was doing great, supported customer calls, onboarding new engineers, along with ongoing incoming tickets and got 3/5, wrote a few good and a dozen bad RFCs.
Then the manager had the audacity to ask why I am changing the company with a 40% raise. I could’ve asked for promotion, he said.
Yeah, Go is nice sometimes. It shines in codebases that are not quite large and not very small. Also it’s great to write a cli tool in it, though I prefer Rust because I hate myself. What I personally missed in Go (maybe skill issue, idk):
Metaprogramming. For big projects it’s inevitable. You need to have SPOT which generates documentation and headers (e.g. xml document, openapi spec). Otherwise you die. The fact that the source should be a git repo is cancer, as in this case artifacts are added in git, which results in merge conflicts.
DI. In JVM world it is a must. If you don’t have it, you fucking should have a reason for that! If your logic spans across multiple layers of factories, onboarding of a new developer creates friction.
For small web services that are not constrained by memory I would choose spring + openapi, as it really requires only model description and the endpoint, yielding you a client in any language you want.
If err != nill. Don’t let me started on importance of result and either monads.
Aspects and (usable) reflection. I want a codebase that has actual decoupling. I want a security code to be in a completely different place, away from the business logic, just as I want traces with serialization to be pluggable I don’t want to have a single place in code that has a sequence
auth -> validate inputs -> trace -> business logic -> validate output. I strongly believe that it’s faulty, untestable and prone to errors.