gf000

iphone 18 pro max is also non-folding

> There's no way to create a class that prevents callers from reading the object before the constructor runs

That can only happen if you leak the reference (given we are talking about java language level semantics and not byte code), which I give you is unfortunately not that hard to do.

As for exceptions, I think they would pair beautifully with software transactional memory, which would work well with effects. In that case (and no side effects) it would not matter what code path we took, we could just go back to a known safe point.

Because ergonomy-wise I still think exceptions win (even though I do like Maybe types, and Rust's ? macro is plenty good): - they let one focus on the actual happy path code - no error is ever swallowed, unless explicitly written so (looking at you go with useless if errs that fail to properly handle the error), they are always handled somewhere - they automatically "unwrap" the Ok result, and automatically bubble up the Err side. - bubbling up is especially useful because most errors can't be handled at their source (e.g. IO error is meaningless, how you handle it depends on what you want to do in the first place, which is done several layers higher) - they automatically attach a stackframe/source, while with result types you may get a list of Ok Ok Ok Err and have no idea how that Err got there.

No, it's absolutely not defensible.

You are looking at it from the wrong direction.

The problem is not that you can write bad stuff in rust, the problem is that this particular usage pattern can't be sanely coded in C. This is a public API that should inform users and enforce certain properties. A Results type does exactly that, you would have to go way out of your way to force invalid stuff through that type alone.

0.001% of all Linux installs (including containers, CI workers, embedded, etc) is still a huge huge number. It should be taken seriously until proven otherwise

It would be interesting if you could just have all the motors hidden on the sides and have even the "cut" functionality driven by a cable getting pulled.

"Give me a fixed point and I will move the whole world"

It has like 4 fixed points, and it could just build a gun and shoot you!

I guess via the camera?

Why not just robo-dog? They can go pretty much everywhere a human can. You just add a strange neck/arm thingy as head and it can do pretty much everything. It's not accident that that became one of the best known robots.

How to properly secure it?

If you put it in a sandbox than herdr can no longer see it, can it?

Are they working together with interdependencies or not?

E.g. explorer.exe is not replaceable on windows so the display server and that is one software. (The kernel is NOT though, because it can surely run in a headless way). It's not that hard of a concept..

Well, does the way spreadsheet cells are handled has any relevance to presentations? If not, then they don't increase each other's complexity budget.

systemd-init has nothing to do with network resolution.

How does go even enter this discussion? It's closer to JS than to zig/rust.

> if you understand how the CPU, memory, network, and disk are processing

I don't think it's possible in the general case, it's way too complex for that. Sure for trivial examples it's trivial to claim one program is faster than the other, but can you really claim that your special allocator used in one place plus the extra argument used in calling that function is worth it without writing both options and measuring it? Like even measuring it is non-trivial, will it be inlined at the use site, how is it called, etc.

Well, my only gripe with it is that it's C. Otherwise it's very modular.

Sysvinit is not 1000 lines if you add all the scripts you have to write to get feature parity with systemd. And now you have written that in the worst programming language ever created, bash, that is basically impossible to not be chock full of errors.

Frankly the amount of crying I have seen about systemd... and it's basically the most stable part of my Linux installs. Even though I really have seen everything else "catch on fire".

Why not go with something like graalpy first? That's much less risk in terms of "we end up slightly changing behavior"

Even better are the bank websites that refuse to work on multiple tabs, logging you completely out after detecting that..

Just simply ask for that, and they usually know what to do.

They should write a test and stash the fix they just wrote. In this state it should fail. Once they re-apply the patch, it should become green and this gave use enough information to deduce that the test does test something.

Well, banking is digitalized for a long time (such a long time that they actually are using mainframes and cobol), and it's definitely not the epitome of good software, so I think it was always important, maybe we were just less directly reliant on it.

From another comment:

> 10^87 variables, a point where the proposed new method surpasses the already existing sat solvers

Yeah, it's not efficient in the ordinary sense.

Ask for red-green tests. Without that they are often indeed useless.

"hey Claude, rewrite it in rust"

I'm semi-sarcastic here, but this is actually possible now, while it was an often futile and very expensive roundtrip before AI resulting in two versions of your software that you have to simultaneously maintain.

Yeah shit like this is/was always extremely common on any kind of app created in the last 30 years. It's not related to vibe coding.

Bit didn't it also feel bad back then, you just forgot about it and has a rose-tinted view of the past?

Like software used to crash, were single-threaded and constantly frozen. How many times did you have to issue Ctrl+alt+del vs today? Even UIs were constantly out of sync with the underlying data, I would even go as far to claim that reactive frameworks like react cut down a big category of software bugs.

You seem to give too much credit for these companies and too less credit for governments.

First of all, most companies just want to make money, with minimal risk. It's significantly easier to make money when you are at worst doing grey area stuff and stay mostly legal (or even "better" is to lobby your thing into being legal). And any info known by more than 2 people is no longer a secret, and you ain't paying enough to your employees to lie under oath for their employer. So no, I don't believe it's happening all too often, and even if it does happen it's mostly out of ignorance, not a deliberate attempt to go against the law.

Though at this time it produces pretty bad text which is hardly useful for anything.

You can check what data is getting collected (e.g. decompile their distributed app at different versions), and you can - as a government - actually just go to their servers and check what they are doing (with necessary permits and lawful action), or even mandate them to show the source code.

Standing for an evil heinous party doesn't get offset by this, though, were it the case.

DNA is so many layers below human cognition, it's a bit like explaining the Moon landing's technology by a stick burning.

There is absolutely no DNA recombination during a thought process.