Lombok had a bunch of great things that should've been part of the java language to begin with. They've slowly been folded in (so now you have to work out which @NotNull annotation you want) but the language does still improve.
The issue here is that the author of that post, and potentially the fictional author of the thing being lampooned, are not drawing a distinction between a tutorial (or an explanation) and a how-to.
Either you want to get a task done, or you want to spend a lot longer learning how to work that out for yourself.
(Many tutorials will include small set of how-to-like instructions because emulating the actions of a master will improve one's vocabulary of what can be done as well as how it is achieved.)
Unsolicited "good morning message" - is that what it's called now?
I use "are you calling me a liar?" which is probably more effective in the UK than the US.
570 recorded homicides between March 2023 and 2024.
Data on "hundreds of thousands" of people can't provide the distinguishing markers to even have a stab at this.
It can reliably predict when people are black, though.
Grimes is on 4chan?!
More like because you're eating broccoli.
"I love life on Earth... but I love capitalism more."
It does rather sound like proposing an immediate 25k hike in house prices, yeah.
Incidentally, this kind of passive-aggressive pressure is the kind of thing that might be considered a legitimate security threat, post xz. If you need to vent, vent in private. If "it works for you" but the maintainer is asking legitimate questions about the implementation, consider engaging with that in good faith and evaluating their questions with an open mind.
Casey's video is interesting, but his example is framed as moving from 35 cycles/object to 24 cycles/object being a 1.5x speedup.
Another way to look at this is, it's a 12-cycle speedup per object.
If you're writing a shader or a physics sim this is a massive difference.
If you're building typical business software, it isn't; that 10,000-line monster method does crop up, and it's a maintenance disaster.
I think extracting "clean code principles lead to a 50% cost increase" is a message that needs taking with a degree of context.
view more: next ›
gedhrel
joined 2 years ago
That's a good point. You can get away with that with a new language, but adding nullability as a non-default option would break existing code much like making things const by default in C++ would, I suppose.