Earlier quoted context omitted.
Windows10 is already recording every keystroke/data of yours - what's the difference here? Also, Canonical's snappy packages can kinda solve this problem.
This great argument again...
BSD vs. Linux (2005)
361–370 of 371 posts
Re: BSD vs. Linux (2005)
#362Earlier quoted context omitted.
Enlighten me - what's the problem with the linux desktops?
They're Linux. How are you supposed to run Adobe inDesign on a Linux desktop? Or any other useful application, really. Linux should just kill off its desktop. Mac OS X won the Unix desktop wars, and has the expected use models of a desktop, with a proper modern GUI API as well, instead of the ancient X hacks.
With wine...
> Or any other useful application, really.
You search in the software center or in your menu and start the app. Simple. FUD elsewhere, apple-noob.
Re: BSD vs. Linux (2005)
#363When I say "Linux", I mean Red Hat. I mean Slackware. I mean Mandrake. I mean Debian. I mean SuSe. I mean Gentoo. I mean every one of the 2 kadzillion distributions out there, based around a Linux kernel with substantially similar userlands, mostly based on GNU tools, that are floating around the ether. So... do you include Android? It's worth asking, because though it uses a Linux kernel, it's a heavily modified one…
> little chance of Binder ever being accepted into Mainline I hate to break it to you, but... https://git.kernel.org/cgit/linux/kernel/git/stable/linux-st... Looks like it's in 4.1+.
I really haven't been paying attention O_O
Re: BSD vs. Linux (2005)
#364Earlier quoted context omitted.
On OpenBSD, just do `pkg_add -Uu`.
That's packages only, and with ports you're on your own, right?
Re: BSD vs. Linux (2005)
#365Earlier quoted context omitted.
They're Linux. How are you supposed to run Adobe inDesign on a Linux desktop? Or any other useful application, really. Linux should just kill off its desktop. Mac OS X won the Unix desktop wars, and has the expected use models of a desktop, with a proper modern GUI API as well, instead of the ancient X hacks.
> How are you supposed to run Adobe inDesign on a Linux desktop? With wine... > Or any other useful application, really. You search in the software center or in your menu and start the app. Simple. FUD elsewhere, apple-noob.
Re: BSD vs. Linux (2005)
#366Earlier quoted context omitted.
> How are you supposed to run Adobe inDesign on a Linux desktop? With wine... > Or any other useful application, really. You search in the software center or in your menu and start the app. Simple. FUD elsewhere, apple-noob.
We've banned this account for repeatedly violating the HN guidelines. If you don't want it to be banned, you're welcome to email hn@ycombinator.com. We're happy to unban people when there's reason to believe that they'll only post civil and substantive comments in the future.
Re: BSD vs. Linux (2005)
#367Earlier 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? :-)
Re: BSD vs. Linux (2005)
#368Earlier quoted context omitted.
Ah crap. The advice I got was just about the opposite - I wanted an L2ARC device in my system for performance. Atom C2758, 32GB ECC RAM, 4x4TB in RAIDZ2 (losing that much storage was painful , and the $1200AUD upgrade path to 4x8TB even more so) with a 128GB SSD as L2ARC. I found out some time later that I probably wanted an SLOG device instead but I'm really too afraid to touch my config. FWIW it's pretty stable on…
Your L2ARC shouldn't be bigger than 5x your system memory, ZFS has to keep mapping tables in-memory to determine where data on the L2ARC is stored, the bigger it gets the more memory you take away from your in-memory ARC, which can lead to worse performance than before since more data is having to come from your much higher-latency and lower bandwidth L2ARC or straight from spinning disks. RAIDZ is a performance kill…
Re: BSD vs. Linux (2005)
#369Earlier quoted context omitted.
> 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)
#370Earlier quoted context omitted.
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.
Hint: Programming is not engineering.