I’m guessing, they meant to write “that the language has no default way”.

I don’t know, man, far too many people seem to think that “easy to learn” means they’ll know all they need to know in relatively short time.

Like, you talk to our data scientists and they’ll tell you doing anything in Python, no problem. But you talk to our seasoned software engineers and you see the war flashbacks in their eyes, because it racks up in complexity so fucking quickly, it’s insane.

https://en.wikipedia.org/wiki/Satanic_nightjar

Yeah, same. The game where that screenshot is from (DCSS) also has an ASCII mode, where that skeleton dragon would probably look like this: D

The text log would say that a skeleton dragon appeared, and I could even imagine a skeleton dragon by itself quite easily, but when it comes to a whole room full of monsters, then it’s just a lot of info to keep track of. The small textures are almost like icons, in that they’re a compact way of telling me where which monster is.

Yeah, man, I’ve got this chronic fatigue thingamabob and if you’re asking me when I’m most energetic, the answer is never…

I’ve been telling all the juniors we have, that they’re free to use a GUI tool, but they do not get around learning the CLI. If you fuck up or Git breaks, you’ll need to look up how to unfuck it and that’s where the only help you find is for the CLI.

In particular, it’s also been my experience that you rapidly come into a situation where suddenly you’re the Git expert and need to help others. If you only know one specific GUI, you can only help others who use that GUI. If you know the CLI, you can help anyone.

It also happens that you need to interact with Git repos on a server where you simply won’t have a GUI.

And yeah, given that whole opinion, personally I seriously do not care to learn a GUI in addition to the CLI.

But that’s what I mentioned regarding Java there. Java calls them “exceptions”, but generally forces the caller to either handle them or explicitly bubble them upwards…

That sure is one of the possible jokes I couldn’t decide between. 🙃

As I see it, the difference is that we now have capable game engines freely available. Indie studios can, for the most part, offer the same quality of gameplay. AAA studios can only really differentiate themselves by how much content they shove into a game.

In particular, this also somewhat limits creativity of AAA games. In order to shove tons of content into there, the player character has to be a human, the gameplay has to involve an open world, there has to be a quest system etc…

KDE’s Dolphin runs on Windows and has that integrated. I don’t know for sure, though, that FTP support works on Windows…

<Insert joke about microplastic>

On the flipside, you give real intelligence 32 pixels and it infers photorealistic images:

(The textures are 32x32 pixels. Yes, that’s technically 1024 pixels, but shhh. 🙃)

It talks about the experience black people with autism have. In particular, it talks about someone with a hyperfixation on deejaying and how the video author relates to those experiences. The video author has a hyperfixation on writing.

Two notable points that stuck with me:

• Black autists may not get diagnosed, because they’re less likely to visit psychologists for depression and such. As apparently the family of his put it: Mental health issues are for white people.
• Autistic behavior quirks themselves got interpreted as white people behavior.

I wouldn’t get my hopes up. Them announcing something like this looks good PR-wise, so they’ll do it, even if they don’t actually expect this effort to lead to anything.

But even if they do implement such an API, companies won’t start adopting this API until its capabilities are roughly comparable to the kernel-level solution AND it’s available on most Windows systems in the wild. So, we’re likely talking more than a decade before this sees sufficient adoption…

The guy keeps on picking on Go, which is infamous for having terrible error handling, and then he has the nerve to even pick on the UNIX process return convention, which was designed in the 70s.
The few times he mentions Rust, for whatever reason he keeps on assuming that .unwrap() is the only choice, which’s use is decidedly discouraged in production code.

I do think there is room for debate here. But error handling is a hellishly complex topic, with different needs between among others:

• short- vs. long-running processes
• API vs. user-facing
• small vs. big codebase
• library vs. application code
• prototyping vs. production phase

And even if you pick out a specific field, the two concepts are not clearly separated.
Error values in Rust usually have backtraces these days, for example (unless you’re doing embedded where this isn’t possible).
Or Java makes you list exceptions in your function signature (except for unchecked exceptions), so you actually can’t just start throwing new exceptions in your little corner without the rest of the codebase knowing.
I find it quite difficult to properly define the differences between the two.

I guess, they swapped it, because people might misread it as both ‘legs’ and ‘house’ being negated…

Many people grew up playing Flash games and may want to revisit those. I doubt, there’s many websites out there, which still require Flash…

Welp, I guess that’s that then…

I mean, the flipside could be just as true. I would be surprised, if there’s not some right-wing twats, who felt attacked in their manliness by the concept of veganism, and then started gaming the system by deploying tons of downvote bots. If you regularly downvoted posts without commenting, you might’ve looked like such a bot.