259 karma · joined June 12, 2022
Of course, the same issue exist in any compile language, say C, but you don’t expect to see C in a disassembly. Here you are working at the assembly level.
Pangea chose WorldGroup over FirstClass because it had QWK. https://github.com/l3nz/pangea-2023/blob/main/Storia_en.md
They should have compared natural and ultra processed food matching the same glycemic indexes to understand if there is some kind of procedure in manufacturing that changes it significantly even the same amount of sugar and fiber
And this is the best of cases. I fear many times in a smaller projects it was “it compiles at last, let’s see if anybody complains”. That’s why LLM’s are so damn effective today.
(been there, done that – I’m not pointing fingers, but we are human, we get tired, and we don’t have the NASA budget to complete things and ship them)
Traditionally SQL uses a lot of lines because you put one thing per line, but so what?
Well kinda. I found it very annoying every time you want to print a sorted map which keys are strings that you could not abstract the operation. It felt like paying a stupidity tax. (And I quite like go. It’s the only language where write once run everywhere actually works. Cross compiling for all targets is as easy as creating a local binary)
While you are at it, I humbly suggest to add composable streams too, that we had in 2014, and that make working with collections way more pleasant.
(Jokes aside, in Java it is very nice that you can start with a generic ArrayList and turn it into a linked list with one single keyword change and no code needs changing, or that you can turn any collection into a synchtonized or readonly doppelganger with one line of code. Collections are nice and I miss them in Golang)
Who ever thought a the semantycs of a pipe was a good idea after 30 years of everything else becoming HTTP?