Live data from Hacker News

So Long, Macbook. Hello Again, Linux

richardmavis.info

421–430 of 531 posts

Re: So Long, Macbook. Hello Again, Linux

#422

End-user Linux has definitely improved in the last few years. It offers a lot of attractive features for what I imagine to be the typical HN demographic. That being said, it's still got rough spots that OSX doesn't. It works great when it works, but when it doesn't.... Font rendering, display/compositor fragmentation etc... Inb4 the anecdotal "well it works for me I just had to download the xf86 font library and comp…

I agreed with everything you said except this: > but there are still things that just going to be less painful on Apple. Of course OSX is more user friendly now , but Linux desktop has improved by leaps and bounds. 4 years ago you needed to be a developer or extremely savvy to run the average desktop distro, now I would say you just need to be tech sdavvy. I would argue that for the ho hum business cases (not extreme…

People have been saying that ever since, uhm, the first Mandrake release? It’s so much easier now, soon it will all be so smooth! except every year there is something else to rewrite/rejig.

As soon as auto-configuring XFree was kinda figured out, out goes XFree and in comes x.org. Xorg getting to the point where having 3d animations doesn’t require kernel-module-config expertise? Out goes Xorg, in comes Wayland. Gnome 2 worked out the kinks? Time for Unity! Kde 4 finally getting snappy? time to break it up! Init systems figured out? Systemd! ALSA getting adoption? Pulseaudio! Pulseaudio finally working? Let’s rip it out! And so on and so forth, in an endless churn.

Now, this sort of churn also happens in commercial alternatives; but stuff gets shipped when it’s 99.9% working, left running for years (or decades, if from Microsoft), then maybe gets rewritten with something that must be better (no regressions) or it won’t even ship. In the Linux world, it’s all just thrown over the wall; maybe you’ll be lucky and it will work on your machine, and maybe it won’t. By the time it gets fixed, it will be time to replace it. And so the experience is a perennial struggle against half-finished, unpolished software.

Re: So Long, Macbook. Hello Again, Linux

#423

End-user Linux has definitely improved in the last few years. It offers a lot of attractive features for what I imagine to be the typical HN demographic. That being said, it's still got rough spots that OSX doesn't. It works great when it works, but when it doesn't.... Font rendering, display/compositor fragmentation etc... Inb4 the anecdotal "well it works for me I just had to download the xf86 font library and comp…

That's true: some things are easier on Mac. In particular, I'd say that using software that hasn't been packaged for your distribution is much easier on Mac. However, your example of fonts is definitely not one of those areas, anymore. Font rendering on Linux is as advanced and capable as any other OS including in the areas of kerning and hinting. It should just work without any user intervention and look great. I ag…

Eh, I've been running xmonad within Gnome since (checks git blame) 2011 and I don't think I'm changing things anytime soon. Well, for the first 2 years I fiddled a lot and made sure I could just configure a computer the way I liked with a script. Occasionally I'll have an issue like Ubuntu switching to Gnome 3 but even that, the biggest disruption in years, just took an evening of fiddling to fix.

Re: So Long, Macbook. Hello Again, Linux

#425

I've used both Linux and OSX for a long time, and what I've found is that while Linux breaks a little more often, I stand a much better chance of being able to fix it. When I google for a Linux problem, there's much more likely to be an answer that works on StackOverflow, while on OSX it often just leads me to the Apple support forums with dozens of people asking the same question and no real answer. Similarly, while…

I find that when I google Linux problems I'm much more likely to get dozens of answers, all of them wrong. They're for a different distro, or a different arrangement of the software stack, or out of date, or not actually answers (why would you want to do that?), or just plain wrong.

Theoretically it could be a lot better, if the documentation was better, the stack wasn't so maddeningly complicated, and there wasn't so much needless fragmentation.

Re: So Long, Macbook. Hello Again, Linux

#426

Anecdotal like other comments but I and a few others from my workplace have switched to Dell XPS machines and run Linux now, and it's because we're working with Docker, even with 16GB RAM and solid-state drives, the performance of Docker on MacOS is pathetic, and entirely unusable for our work. The XPS machines we have are ugly, they're flimsy, they have a grotesque carbon-fibre pattern on them, the keys leave imprin…

> back-pain

What Mac were you using previously? 13 inch macbook pro is heavier than the 2.67 pound 13 inch XPS

Re: So Long, Macbook. Hello Again, Linux

#427

Earlier quoted context omitted.

>Almost all my colleagues struggled with setting up python 2 und 3 correctly at some point, whereas this just worked for me on Linux. This is one area where I'd have to concede the Apple experience is objectively suboptimal. However, the Python ecosystem isn't doing anyone any favors here.

> However, the Python ecosystem isn't doing anyone any favors here. Apple isn't, either. They ship a version of Python by default that is woefully out of date and conflicts with any other Python that you install, and what's more, some of their tools (notably, LLDB) freak out if you have a newer Python on your $PATH.

Sounds like RHEL 7...Unless you enable Software Collections.

Re: So Long, Macbook. Hello Again, Linux

#430

Earlier quoted context omitted.

I spend somewhere around 30% of the time in a terminal, and the remainder outside of it. I am a former mac user, and after a year and a half the Ctrl+Shift+C thing still drives me mad. Shortcuts are just better on the OSX side of the fence (not perfect, but way better). IMHO, global actions (copy, paste, select all, cut, undo, redo, etc.) should be mapped to one modifier (say AltGr) and local actions to another (say…

> the Ctrl+Shift+C thing I don't know about others, but with terminator[0] I'm able to map Ctrl+C to copy - but if nothing is selected, then ^C works as normal. Is that what you're looking for? 0: https://gnometerminator.blogspot.com/p/introduction.html

In GNOME Terminal you can go to the keyboard shortcut settings and rebind ctrl+C to copy and ctrl+V to paste. If you do so, then you can use Ctrl+Shift+C and Ctrl+Shift+V to do ^C and ^V. Not quite that "selection aware" behavior, but close enough.

From the terminal's point of view, Ctrl+C and Ctrl+Shift+C do the same thing. The only reason you can't usually use Ctrl+Shift+C is that by default that combination is intercepted by gnome-terminal to mean "copy".

(I wouldn't be surprised if other emulators with configurable keyboard shortcuts let you do a similar thing).

Post reply on HN