

Interesting. But can’t you do basically the same thing with @nonnull annotations? I remember using something like that a decade ago when I last wrote Java.


Interesting. But can’t you do basically the same thing with @nonnull annotations? I remember using something like that a decade ago when I last wrote Java.


IMO automated changelogs like these are not especially useful. Better than no changelog I guess, but nowhere near as good as a proper changelog. But proper changelogs take actual effort.
IDEs tend to work out of the box while the likes of vim or emacs need configuration and have an initially steep learning curve.
Not in my experience. It’s very easy to design systems that break IDE support. People love adding all sorts of ad hoc build scripts that mean you can’t just press F5 or whatever. It takes discipline and caring about IDEs to not do that.
And while people might love tweaking Emacs and Vim, it isn’t required.
There’s definitely an element of snobbery, and also of being lazy about tooling. Do you think once you become a talented dev you lose all human vices?
Some of the smartest people in the world believe in an imaginary dad who lives in the sky and grants imperceptible wishes. Everyone is human.
I completely agree. Also almost all of the fancy editing you can do with Vim can be done just with multiple cursors, and it’s less annoying because you do it incrementally (rather than typing a long sequence of commands and then seeing the result), and you much less to memorise.


It’s not actually incremental yet.


I agree. C2 continuity does matter for aesthetics sometimes, but not for a button.


Even KISS. Sometimes things just have to be complex. Of course you should aim for simplicity where possible, but I’ve seen people fight against better and more capable options just because they weren’t as simple and thus violated the KISS “rule”.


One example is creating an interface for every goddamn class I make because of “loose coupling” when in reality none of these classes are ever going to have an alternative implementation.
Sounds like you’ve learned the answer!
Virtual all programming principles like that should never be applied blindly in all situations. You basically need to develop taste through experience… and caring about code quality (lots of people have experience but don’t give a shit what they’re excreting).
Stuff like DRY and SOLID are guidelines not rules.


It must be python3 then.
Except on Windows! Actually it depends on if you installed Python from the Microsoft store or the official download. What a mess.
They don’t want to fix it because it might be confusing temporarily, so instead they’re going to leave it broken forever.


IMO it’s completely insane that they’re doing this. Same with Python packages.


Thanks for highlighting your username - made me notice that you post a lot of nonsense here so I can easily block it!
Yes that’s true, but the point is you should have to opt in to surprising or risky behaviour.
The non-strict versions also panic by default, but only in debug mode. So if you were willing to use abs() you should be willing to use strict_abs().
Arguably a bit of a mistake to have the “obvious” function names be surprisingly unsafe, but I guess it’s too late to fix that.
They’re released on a schedule so they are often quite boring.


AI AI blah blah AI.
Also why is HCL supposedly the 9th most popular “programming language” (which it isn’t anyway)?


There are some examples in the very first list I found googling for “cancel culture examples”.
Not all of them are political (e.g. cancelling someone for sexual assault is clearly not, and that Heineken one… how??), but a decent number are, e.g. number 6 is about as partisan as you can get.


It’s a fairly inevitable reaction to cancel culture. This was predicted and warned against when left-wing cancel culture was at its height, but people didn’t listen. Now we have right-wing cancel culture instead.


I wouldn’t recommend the Gang of Four book. Many of the design patterns they espouse are way over complicated from the days of peak OOP. You know, FactoryFactoryVisitor stuff. Usually best avoided.
I’m not sure that’s a factor here because Google doesn’t use CMake or Cargo (at least not the way we all use it).