Traister101

Isn’t it also like opt in? If you don’t annotate a type it just defaults to Any, which is just unchecked like standard JS

Nah Ryuko generally just looks different but the easiest one is her hair, she’s got just a red “strand”. Also notable is the outfit, Ryuko wouldn’t wear anything with that neck thing going on

What about the borrow checker needs an overhaul? Seems to do it’s job quite well. If you want to remove it then you should use like C++ or Zig or something since the borrow checker is fairly fundemenal to the design of the language

Here. Read this https://flowchainsensei.wordpress.com/2026/02/04/the-software-quality-and-productivity-crisis-executives-wont-address/

Executives aren’t ignorant. They have the data. They commission the surveys. They attend the conferences where CTOs present their concerns. They know that:

• 91% of CTOs cite technical debt as the biggest challenge
• 75% of projects are expected to fail
• 69% of developers lose significant time to inefficiencies
• Only 39% of projects meet success criteria
• The recommended 15–20% investment in technical debt management yields better long-term returns than crisis spending

Yet they choose:

• Not to allocate recommended budgets for technical debt management
• Not to make quality a strategic priority despite CTOs’ and developers’ concerns
• Not to mention these challenges in public communications to shareholders
• To celebrate AI productivity gains whilst developers report record inefficiency
• To focus on the next hype cycle (AI) rather than address fundamental problems

This isn’t a failure of knowledge. It looks to me like a failure of courage and integrity. A failure of the very concept of leadership.

That’s on the dev end of things but yes. Part of the build pipeline was re-obfuscation of your code so it’d actually work. Forge the mod loader just loaded the mods and provided code for modders to use. Forge Gradle was what handled the obfuscation stuff in dev

Congratulations you’ve discovered that Mojang used to ship the game after it was obfuscated! Java has nothing to do with the fact it’s obfuscated that’s on Mojangs end, for goofy “This’ll allow us to sue people who copy our game” logic. NeoForge came out the gate with official mappings at runtime (non obfuscated using the offical names Mojang provides. Yes Mojang obfuscated the game and then gives us the names of stuff anyway…) and recently Mojang announced they are finally dropping obfuscation all together.

Edit. To make sure this is totally clear the obfuscated names such as class_5699.method_65313 is the actual class name and method name. The jar has a class named class_5699 which Java loads and treats like any other class. Very goofy and annoying for modders since if you wanted a useful name you have to first decompile Minecraft, then change all the names, and then when you compile change all references to said names in your code back to their actual obfuscated nonsense.

Neither did Log4j in basically all cases, some maniac just put arbitrary code callbacks into their logger, undocumented and enabled by default. The insane part isn’t the feature itself it’s the fact it’s enabled by default in a logger of all things.

People in my experience are actually very serious about the standard out to debug log which is… baffling. Same people generally outright refuse to learn how to use a debugger in languages where those are pleasant

A logger? Console prints are shitty in general but especially when you have an actual logger already

FUCK goddamnit Bitwarden

They got their jimmies russled.

Couldn’t help but look through their history, seems they aren’t too pleased with life saying they like Ai more than people. Real depressing shit tbh, no wonder they are acting out like this

Clay seems really neat but I don’t write C

It can. It depends on what changed. If both of you touch the same file in a conflicting way you’ll have to merge the commit with the conflict. If you don’t then it just auto magically works.

For example if you have commits A - B - C with a branch A - D with D adding a brand new file you can trivially rebase (IE no need to merge) D onto C for a history of A - B - C - D

The best part about rebasing imo is that you get to merge commit by commit. Using the previous example if there’s a conflict in commit B but nothing in C all you have to do is fix commit D to handle the changes B made, nothing else

I mean should const not be the default? I do want to mutate objects sometimes but usually I just need a view of it’s state and not write access. It also makes mutable data a lot more obvious if whoever wrote the code your reading wasn’t putting const on stuff they should have been. Seems like something all languages with const semantics should have done

For now, they are dirt cheap for now and extremely unprofitable. We’re looking at more than a doubling of subscription price before they even approach profitability

LLMs making you code faster means your slow not LLMs fast

Very true the last ones weren’t going around spewing as many Nazi talking points

Douno off the top of my head. To take a wild guess they might just wrap a file handle and give it s nice api? If that’s what they do then moving from the file zeros out he handle for basically the same reason smart pointers set their internal pointer to nullptr, so they don’t delete it (or close the file in this case) underneath the new object.

Depends on the object what happens when they are moved from. Some objects are put into a valid moved from state (usually depends on if doing so is free or required anyway. For example to satisfy the invariant of the moved to unique pointer the moved from pointer needs to be set to nullptr in order to prevent the moved tos unique pointer being deleted from underneath it)

Because it sounds like English words which is “cool”