You are essentially one executable just an editor so why don't you link statically ? Apart from the c runtime?

Still need to handle automatic upgrades. That's my plan. I was wondering if there's a better way...

100% of the user space programs were from gnu. Compiler was from gnu

The initial filesystem was minix

The kernel was Linux.

So I would say Linus had 100s of man years of ecosystem he could benefit from and that is the oss spirit.

But yeah he did not write a shell or an editor or Compiler etc and the kernel was of course oriented towards an unix like os.imagine you would have had to start from scratch, if you had just had a PC and a bios.

This is all true. It’s also all in a thread about GNU Hurd, which also builds on all of that GNU software plus a Mach-based kernel.

Were. How many are now? 1%? GNU's Not Vim, GNU's Not IntelliJ, GNU's Not Google Chrome.

> imagine you would have had to start from scratch, if you had just had a PC and a bios.

Like templeOS I guess

TempleOS blows my mind, honestly.

"AI is a jet engine "

and rust just wants to ensure you are a capable pilot that can actually steer a plane before stealing everyone else's attention

Porting perfectly working C code that has been in production for decades (and has a great track record wrt to security fixes) to rust is more or less an obfuscation challenge.

An academic exercise for sure. The Postgres team won't use this and take it forward, hence it will go stale and rot within months.

Or someone who likes it could run codex-get -y upgrade on it once every two weeks and it'll be fine for as long as you can afford the tokens.

Yet nobody is going to use it in production.

So what's the point?

As I said, it's an academic purpose I guess. Unless the Postgres team takes this and "owns" it accountability-wise, it's dead.

Chuckled at the anti-climactic sentence ending! lol

Same ,I switched to cursor. I told it how to invoke msbuild and it can edit away without needing a native Visual studio plugin.. no problems at all. Target language c++

What a dumb comment. It's almost like a low-level language having a different feature set is expected.

Also, there is no exact analogue, C++ is just wholly different where you can specify copy/move/destruct semantics on a gradual basis.

try reducing the heap size as it seems that's what's eating half of those 700mb

This time, 30mb.

You go to the gym to lift. Not to talk. You may talk shortly if it is related to something you need to continue your workout. Apart from that you do not talk. End of story.

I used to authoritatively state rules that existed in my own head. I no longer do this.

I always liked busting through the little social candy shell in the gym. Offering to let people work in on a scarce piece of equipment could lead to chit-chatting about whatever. It's nice! When you have about 3 minutes to rest in between sets there's time to let someone else work and talk a bit.

Varies wildly. Some people are there with this attitude. For others it's more of a social time with occasional breaks to do a workout set.

Yes! Looking back there were lots of people who chatted in between sets. I just never realized

Used this kind of font for output on the 320x200 screen all of the time in the late 80s while coding 68k asm on the Atari St

In the early 1990s, C++ had not yet been standardized by ISO, so your argument doesn’t apply to that period.

Let's see how this unwrap()s in production scnr

Oh come on, that was funny. It also highlights a problem with the way people write rust. If your app panics it has a bug. People throw panics in cases that can absolutely happen, a file isn't there or fails to parse, some set of inputs is mutually inconsistent these are things for error checking. Even if the correct way to handle an error you detect is to stop the app, do that instead of panicking. Panics are for things that should be impossible. Ideally they even get optimized out.