Live data from Hacker News

FreeBSD 13.2

freebsd.org

61–70 of 108 posts

Re: FreeBSD 13.2

#61
post #49

Does anyone here run FreeBSD on the desktop? If so, can you explain why you prefer it to Linux?

A coherent userland (not without occasional warts, but without stuff being deliberately, maliciously ignored, broken or replaced to foster someone's agenda). ZFS as a first class citizen, without wondering if Oracle will show up and take the ball away. Jails, although that's not super relevant to the desktop experience. I won't mention systemd, although I truly dislike it (though I have no particular attachment to in…

> ZFS as a first class citizen, without wondering if Oracle will show up and take the ball away.

Is this still true now that FreeBSD is using the ZoL/OpenZFS tree?

Re: FreeBSD 13.2

#62

I tried FreeBSD on ARM64. I couldn't get the browsers, like Firefox or Epiphany, to load without crashing. I'm not sure if it was something I was doing wrong or if the ARM ecosystem just isn't well supported yet. I was also running in a VM with QEMU. On the surface, FreeBSD sounds cool. I liked that I could boot directly to a console and then run the GUI only if I wanted to. Everything felt more modular. It reminded…

If you're going to run it in a VM, why ARM?

Re: FreeBSD 13.2

#63

Earlier quoted context omitted.

Canonical adopting systemd is what made it a standard, community went from being very divided on systemd to resigned and accepting it almost overnight after Canonical announced they were going systemd. This is a fairly common trend, they have a fair amount of influence although that seems to be waning after their push for snap.

Canonical only settled on systemd when Debian decided to adopt it, though.

That is nice historical revisionism, considering Canonical was all in on upstart.

Re: FreeBSD 13.2

#65
post #49

Does anyone here run FreeBSD on the desktop? If so, can you explain why you prefer it to Linux?

A coherent userland (not without occasional warts, but without stuff being deliberately, maliciously ignored, broken or replaced to foster someone's agenda). ZFS as a first class citizen, without wondering if Oracle will show up and take the ball away. Jails, although that's not super relevant to the desktop experience. I won't mention systemd, although I truly dislike it (though I have no particular attachment to in…

> The absence of snap and whatever horrors Canonical keeps pushing is another plus

Amen, brother.. Ubuntu 22 was my breaking point.

Re: FreeBSD 13.2

#66
post #49

Does anyone here run FreeBSD on the desktop? If so, can you explain why you prefer it to Linux?

A coherent userland (not without occasional warts, but without stuff being deliberately, maliciously ignored, broken or replaced to foster someone's agenda). ZFS as a first class citizen, without wondering if Oracle will show up and take the ball away. Jails, although that's not super relevant to the desktop experience. I won't mention systemd, although I truly dislike it (though I have no particular attachment to in…

For me, jails aren’t only technically better, but also have better ergonomics. With Docker:

- I always end up running out of disk space, because of Docker’s love of immutable layers for everything — my jails just live in a normal directory in the filesystem, no need to overthink it;

- I have no idea how to restrict /dev in Docker containers — I’m sure you can, but it’s a mystery to me;

- copying/moving files between host and container requires setting up volumes/ssh/whatever special ceremony; copying/moving files to/from jails is trivial, it’s the same as copying/moving files between any other directories;

- updating jails is easy; I use pkg and freebsd-update, just like with a normal system update, no need to update the host system one way, and the jails another way, like with Docker;

- jails don’t mess with my firewall rules, unlike Docker.

Overall, jails give me a much more cohesive experience.

Re: FreeBSD 13.2

#67
post #27

Earlier quoted context omitted.

Not Linux: Linux feels clunky like a bunch of third party cogs all mashed together. Some with teeth missing some with too many. If it's not SystemMd taking over the whole startup of system services and needing its own DHCP server, it's then down to package manager's. Apt being replaced with snap, snap replaced by flat images. Its divided and with no formality. Someone will create some new thing, I'll get popular, get…

Linux adoption at scale was only possible because of getting in bed with corporate. By the way, FreeBSD also enjoys a bit of corporated love, with the difference that love only goes into one direction.

Untrue on the one-way. Quite a few corporate entities have contributed back to FreeBSD over the years. Netapp, Netflix, Juniper, etc.

Re: FreeBSD 13.2

#68
post #41

Earlier quoted context omitted.

I'm aware. If I had to choose one it would be Slackware.

Posting this off Slackware 14.2/xfce4 on an old Thinkpad X220. All good. (Must get round to upgrading to 15.0 sometime)

When I first starting out using Linux, Slackware was my saving grace. A Linux distribution that was well organized, consistent, and just worked. It saved me from the disillusionment caused by RedHat and RPM hell.

Re: FreeBSD 13.2

#69

I tried FreeBSD on ARM64. I couldn't get the browsers, like Firefox or Epiphany, to load without crashing. I'm not sure if it was something I was doing wrong or if the ARM ecosystem just isn't well supported yet. I was also running in a VM with QEMU. On the surface, FreeBSD sounds cool. I liked that I could boot directly to a console and then run the GUI only if I wanted to. Everything felt more modular. It reminded…

Same experience with Browsers. Only Surf never dies.

https://surf.suckless.org/

ah, the memories

this + dwn https://dwm.suckless.org/

then I said to myself "why am I wasting so much time tinkering with stuff that gains me nothing" and moved on in my life

Re: FreeBSD 13.2

#70

Earlier quoted context omitted.

Canonical only settled on systemd when Debian decided to adopt it, though.

That is nice historical revisionism, considering Canonical was all in on upstart.

No, the parent you are replying to meant that Canonical only gave up on upstart and accepted defeat (and thus went with systemd) when Debian made that decision.
Post reply on HN