Live data from Hacker News

BSD vs. Linux (2005)

over-yonder.net

331–340 of 371 posts

Re: BSD vs. Linux (2005)

#331

Earlier quoted context omitted.

Why not try Apple? Mac OS X is an awesome UNIX that makes for great desktop use. Of course there are all the hipsters and idiots that use it, but put that aside and give it a solid try.

If Apple were to release MacOS for non-Apple hardware I would upgrade to that in a heartbeat. If the Ubuntu 'shell' for the Windows kernel works out I might switch to that as well.

Why not just do a hackintosh?

Re: BSD vs. Linux (2005)

#332
post #329

Earlier quoted context omitted.

> the "FreeBSD Desktop" is even more so. The funny thing is that there's a reason for that: up until recently, the focus of FreeBSD has been on being a server OS. There's a push recently on improving the graphics situation, but it's only relatively recent, and is mainly focussed on getting integrated graphics on more modern hardware working. There are also some efforts to expand the driver compatibility layer so that…

The containerisation approach on Linux isn't because of insularity or NIH - it's because the Linux kernel development process does not accept large, far-reaching "big bang" code drops. Instead, changes that have wide impact across the core kernel are expected to be made in a series of smaller incremental improvements, each of which is more limited in impact and more easily reviewed.

Such as systemd? :-)

Re: BSD vs. Linux (2005)

#333
post #329

Earlier quoted context omitted.

The containerisation approach on Linux isn't because of insularity or NIH - it's because the Linux kernel development process does not accept large, far-reaching "big bang" code drops. Instead, changes that have wide impact across the core kernel are expected to be made in a series of smaller incremental improvements, each of which is more limited in impact and more easily reviewed.

Such as systemd? :-)

systemd isn't part of the kernel at all.

Re: BSD vs. Linux (2005)

#334

Earlier quoted context omitted.

You can always dual-license the software. The GPL version of your software can always be a basic version, customers could pay for features they want to have.

Yes, but we're at the start again: Only when you don't depend on other GPL software at compile time (and even runtime bindings can be tricky AFAIK). So it only works if all people do is write a bunch of siloes and don't work as a community at all. So, looking at Linux system software as an example, it only works as long as you stay far away from the kernel.

If you depend on software, the authors of the dependencies have done a part of your job for you. GPL basically says the authors only agree to help you on the condition that you also help others. You can always choose not to be a part of such a community, then you will not get help. What is the problem?

Re: BSD vs. Linux (2005)

#335

Earlier quoted context omitted.

1. zfs runs well on a lot of systems. You might have to change a setting or two but it's not as you say. 2. pkg install and the related pkg utilities have existed for awhile. 5. systemd isn't and shouldn't be a requirement for applications going forward. Any application that requires it is limiting its portability for unknown reasons. The joy of trying a new system is the little things you learn that you weren't even…

> systemd isn't and shouldn't be a requirement for applications going forward. Any application that requires it is limiting its portability for unknown reasons. How should one do it instead? Treat each alternative system specifically? Or is there a way to cover them all at once, including unknown and future ones?

How about this: don't write applications that depend on the init system.

Seriously, who ever thought such a dependency was a good idea? Who even thought it would be a good idea to make an init system that was possible for an application to be dependent on? This is exceedingly poor engineering, and I'm dumbfounded at its acceptance and spread.

Re: BSD vs. Linux (2005)

#336
post #287
post #185

Earlier quoted context omitted.

I understand the rationale for this (performance), but it scares me a bit to have something as complex as a TLS stack running in kernel-space, which I assume it will do.

The sendfile/TLS work from Netflix does _not_ rely on the TLS stack running in kernel space. TLS session management, negotiation, and data framing is dealt with at the application layer, via nginx/openssl. Once the TLS handshake is completed and session keys are derived, you bind your session key to a socket. The FreeBSD kernel then sees this, and when you call `sendfile` to push static data out of the socket through…

Sometimes I let my biases get the better of me. Thanks for the reference.

Re: BSD vs. Linux (2005)

#337
post #92

Earlier quoted context omitted.

I've never heard the opposite. I've switched to OsX 4 years ago after being completely unhappy and irritated with Windows for over 12 years. Now after months of using Ubuntu (unity, xfce) and Mint (Cinnamon) I'm convinced that OsX is best for average (and power) desktop user by a huge margin. Although I would be much more happy with something Open Source.

You can hear the opposite from me then. I have an OS X laptop and a desktop running Gnome (Fedora) and I find Gnome far better. Originally, I didn't like Gnome 3, but after I used it a lot, I got used to it; I added some extensions, and now I prefer it. In my opinion: * Finder is garbage (alt tab is broken and non configurable. I can't figure out how to convince it that the built in display is always the primary disp…

> Finder is garbage

Try PathFinder: http://www.cocoatech.com/pathfinder/

It can be used for free until you decide to buy it.

> alt tab is broken and non configurable

Cmd+Tab? What exactly do you find annoying?

Try Missing Control (F3, or set a mouse hot corner in System Preferences -> Mission Control) to quickly see all windows (for all process, or Ctrl+F3 for current app, Cmd+F3 for desktop) and just raise the one you want.

Also try TinkerTool: https://www.bresink.com/osx/TinkerTool.html

> brew, compared to dnf or apt, is not good.

Try nix: https://nixos.org/nix/

> The programs from Apple are all terrible.

Which ones, and how, exactly?

Re: BSD vs. Linux (2005)

#339
post #255

Earlier quoted context omitted.

There is a VM that supports seamless mode for Linux? Tell me more. Which one?

Virtualbox has so-called 'seamless' mode, in which the X11 windows from VM running on Windows host appear as separate windows in the Windows desktop. However, they only appear separate; they don't have separate panel button and they are not directly reachable via alt+tab. One needs to switch to VM first, then use keyboard shortcut set up in VM to access them.

If you alt-tab it to the vm, you have to alt tab again to switch between linux programs.

Usually that's not a problem, because I only have emacs and/or a terminal session running. With the control key on the right, you switch back to your host os.

To switch to a windows program from linux you simply press RCtrl+Alt+Tab.

Virtual desktops in Win 10 are very handy while using a VM. Ctrl+Win+d opens a new virtual desktop. Ctrl+Win+Arrow Keys switches between them.

Re: BSD vs. Linux (2005)

#340
post #308

Earlier quoted context omitted.

Windows 7, desktop machine, and windows update don't really work without a functioning network connection. But if you don't believe me, and choose to believe those reporting issues with Linux, just do a google search on windows install and network issues. There is plenty of people reporting the same issue. to cite windows own support page: "If Windows can’t find a new driver for your network adapter, visit the PC man…

At this point, Windows 7 is 7 years old. Do an apples to apples comparison here, and try getting your same hardware working on a copy of Ubuntu 9.04 or RHEL 5.3. How hard is it?

Why should I only look at the exact date which windows 7 was released, rather than the date when a major release of debian got out, say 2011 with Debian 6.0? No network issue, occasional problems with x-server, problems with sound (as said above). Network works out of the box. On windows, issue with network, issue with graphics (until driver was installed), no problem with sound.

A few months ago I bought a gaming laptop on release date. Guess what, network worked without issue. X-server did not start until proprietary drivers were installed. Sound worked.

Windows release schedule do not match Debian's release schedule. Each year after a release, the default drivers will get worse, but the general experience can still be obtained by people who experience the install process. The experience I have endured with windows is issue with new motherboards and especially network drivers (and built-in raid cards for the installer... good grief, that was a wasted afternoon trying to get the installer to accept the raid drivers). Second to that, the fall back graphic drivers look crappy and is bad in every way except that its slightly better than a basic command prompt.

Post reply on HN