Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Why Oxide Chose Illumos

rfd.shared.oxide.computer

Post reply on HN
Print view View original

171–177 of 177 posts

Re: Why Oxide Chose Illumos

#171

Post by anonfordays »

anonfordays wrote: post #170
sophacles wrote: post #133

Earlier quoted context omitted.

> Cargo is widely recognized as low quality. Can you point me to both of: * why it's considered low quality * evidence of this "wide regard" Other than random weirdos who think allowing dependencies is a bad practice because you could hurt yourself, while extolling the virtues of undefined behavior - I've never heard much serious criticism of it.

>Can you point me to both of: >* why it's considered low quality >* evidence of this "wide regard" https://www.youtube.com/watch?v=OdMQwDtumJ8

Cargo/Rust is brought to you by a lot of the same minds that brought you the train wreck known as Node and npm.

Re: Why Oxide Chose Illumos

#172

Post by anonfordays »

dijit wrote: post #155
anonfordays wrote: post #148

Earlier quoted context omitted.

>Honestly, SMF is superior to SystemD Maybe 15 years ago, not by a mile now. systemd surpassed SMF years ago and it's not even close now. No one in their right mind would pick SMF over systemd in 2024.

The fact that its less opinionated about logging and networking and doesnt ever force any reload of itself are all reasonable reasons to prefer it. You don’t lose socket activation or supervison. SMF is designed to help work in the event of hardware failure too, which systemd definitely cant handle.

>The fact that its less opinionated about logging

It's simple and straightforward to use any other logging or network configuration system you wish.

>doesnt ever force any reload of itself are all reasonable reasons to prefer it.

It doesn't force reload it self.

>You don’t lose socket activation or supervison.

You don't lose that in systemd either.

>SMF is designed to help work in the event of hardware failure too

So is systemd.

>which systemd definitely cant handle.

It definitely can handle that. One of systemd's core functions is handling hardware events.

Re: Why Oxide Chose Illumos

#173

Post by dijit »

anonfordays wrote: post #172
dijit wrote: post #155

Earlier quoted context omitted.

The fact that its less opinionated about logging and networking and doesnt ever force any reload of itself are all reasonable reasons to prefer it. You don’t lose socket activation or supervison. SMF is designed to help work in the event of hardware failure too, which systemd definitely cant handle.

>The fact that its less opinionated about logging It's simple and straightforward to use any other logging or network configuration system you wish. >doesnt ever force any reload of itself are all reasonable reasons to prefer it. It doesn't force reload it self. >You don’t lose socket activation or supervison. You don't lose that in systemd either. >SMF is designed to help work in the event of hardware failure too So…

The confidence here is breathtaking.

Did AI write this? its completely incorrect.

Re: Why Oxide Chose Illumos

#174

Post by anonfordays »

dijit wrote: post #173
anonfordays wrote: post #172

Earlier quoted context omitted.

>The fact that its less opinionated about logging It's simple and straightforward to use any other logging or network configuration system you wish. >doesnt ever force any reload of itself are all reasonable reasons to prefer it. It doesn't force reload it self. >You don’t lose socket activation or supervison. You don't lose that in systemd either. >SMF is designed to help work in the event of hardware failure too So…

The confidence here is breathtaking. Did AI write this? its completely incorrect.

>The confidence here is breathtaking

Tends to happen when facts are on your side.

>Did AI write this?

"Everything I dislike is AI."

>its completely incorrect.

No it's not.

Re: Why Oxide Chose Illumos

#175

Post by dijit »

anonfordays wrote: post #174
dijit wrote: post #173

Earlier quoted context omitted.

The confidence here is breathtaking. Did AI write this? its completely incorrect.

>The confidence here is breathtaking Tends to happen when facts are on your side. >Did AI write this? "Everything I dislike is AI." >its completely incorrect. No it's not.

Yeah, it is. Systemctl reload, journald binary logging being forced on (is an opinion) and so on.

Blisteringly fucking moronic that you double down.

“not losing socket activation” was a reference to the fact that systemd actually gives you that.

Re: Why Oxide Chose Illumos

#176

Post by anonfordays »

dijit wrote: post #175
anonfordays wrote: post #174

Earlier quoted context omitted.

>The confidence here is breathtaking Tends to happen when facts are on your side. >Did AI write this? "Everything I dislike is AI." >its completely incorrect. No it's not.

Yeah, it is. Systemctl reload, journald binary logging being forced on (is an opinion) and so on. Blisteringly fucking moronic that you double down. “not losing socket activation” was a reference to the fact that systemd actually gives you that.

>Yeah, it is.

No, it isn't

>Systemctl reload

Yes, that is a feature.

>journald binary logging being forced on

Again, no one is forcing you to use that, this is old FUD.

>Blisteringly fucking moronic

Ad hominem means I'm right and you can't handle it.

>that you double down.

Yes, the facts haven't changed, I double down on the facts.

>“not losing socket activation” was a reference to the fact that systemd actually gives you that.

Good feature.

Re: Why Oxide Chose Illumos

#177

Post by anonfordays »

cthalupa wrote: post #149
anonfordays wrote: post #138

Earlier quoted context omitted.

>This isn't true - Azure uses Hyper-V I thought Azure was moving/moved to KVM for Linux, but I was wrong. >AWS uses an in-house hypervisor called Nitro Nitro uses KVM under the hood.

Nitro does not use QEMU or many other parts traditionally used with KVM, however. https://www.brendangregg.com/blog/2017-11-29/aws-ec2-virtual...

Still KVM, that is the core of the hypervisor.
Post reply on HN