Yeah that’s a fair point, although it’s still a bit… well, funny (not “funny ha ha”) that they even temporarily blocked those extensions. Not sure what Roskomnadzor could have done if Mozilla had refused even a temporary block, at least assuming the foundation doesn’t have any legal entities in Russia which they may well have

Browser maker decided not to follow Putin’s orders. Well done

Only after it caused a PR flap for them, though

Yeah, was the C++ dev just “pre-empting” the PHP devs by ordering all their beers for them so they don’t do it one by one and sing the rest of the song?

I, uh… I don’t get it. Somebody help an idiot out? I haven’t had my morning cuppa yet so it might just be a lack of caffeine.

Programming is also for nerds.

Therefore, tests are for programmers.

◼

Management said that writing tests takes too much time and eats into the time that could be used to write features for the app, so they decided that we’re not writing tests. They were always green anyhow

unzip && strip && touch && finger && grep && mount && fsck && more && yes && fsck && fsck && umount && clean && sleep

Edit: and yes, this joke is older than the gods as evidenced by the presence of finger, and I’m not sure clean is a thing in modern UN*X distros. Not in FreeBSD at any rate

And the devs hate the real fans of the game and implement features only to spite them

You’re surprised that gAmErS are complaining about something?

If you want to be able to eg. (de)serialize non-public fields of a type for any reason, you’ll need some way to get around the access restriction. Mocking is another use case – although it’s a philosophical discussion whether you should be mocking non-public fields.

And this isn’t just a Java thing, the comment you’re responding to has an example in C#, and you can do something similar in a lot of languages that support runtime reflection. Barring runtime reflection support you can do pointer math if the language supports it. Access restrictions on fields are there to stop casual misuse of private fields, but sometimes you actually may want to be able to step over those restrictions if you really know what you’re doing.

Frankly it’s been a while since I wrote either one. I just assumed Java because of the naming convention, and I didn’t see anything I took as obviously un-Java in the class definition

Where are your gods now?

public static Joke getTheJoke(Meme yourMeme) {
  Field jokeField = Meme.class.getDeclaredField("joke");
  jokeField.setAccessible(true);
  return (Joke) jokeField.get(yourMeme);
}

Ha yeah, just about anything is better than the current status quo

I think having null is great in some cases where you need to represent missing value.

Option types or sum types would probably be a much less terrible choice for this, although I guess some sort of nullable keyword counts as a sum type

That’s $6400 per hour

Great article, thanks for the link! It makes good points that I hadn’t really considered; I’ve probably just been cranky about it because I’ve preferred heterogenous translations

Oh yeah how did I forget the billion dollar mistake, definitely one of the worst misfeatures of Java

Java was such a fractal of stupid design choices in its early years, and a lot of it is still there. OOP except when it’s not (int vs Integer, [] arrays but also List et al), no unsigned number types, initially no way to do closures or pass methods around so everything had to be wrapped in super verbose bullshit, initially absolutely dogshit multiparadigm support and very noun-oriented, initally no generics either meaning everything’s an Object, when it did get generics they had to do type erasure for backwards compatibility, etc etc etc

She was an asshole who wanted me to redo work for free because she believed her son over someone who actually knew what they were doing, and after tens of minutes of wrangling I just went “fuck it” and obliged her request to sanitize the peripherals. The sum wasn’t all that big to begin with, so it’s not like she was on the hook for hundreds of euros – probably got a 50€ bill instead of a 20€ one. Not knowing any better obviously wasn’t the problem here, but if that’s your takeaway then I really don’t know what to tell you.

So yes, I did it.
No, I’m not sorry.
Yes, I’d do it again.