Live data from Hacker News

So Long, Macbook. Hello Again, Linux

richardmavis.info

361–370 of 531 posts

Re: So Long, Macbook. Hello Again, Linux

#361
I just recently (a couple months ago) updated my Linux desktop experience at home. I had been running an Ubuntu 14.04 LTS install, that was getting long-in-the-tooth, as well as being unstable.

Part of the instability had to do with various hacks and patches I had put in place, including a big one where I updated gcc to the latest version to support C11; this broke my update process horribly - so much so that when I went to update the NVidia drivers, my system became ultra-b0rked. I had been meaning to do an upgrade - now I was forced to.

What saved me a great amount of trouble was the fact that I had partitioned my system; that is, when I had installed Ubuntu, I had put it on an SSD (/tmp and a few others were on a RAM disk), and /home was on a separate drive. So all I had to do was pull the SSD, drop in a new one, and re-install something else.

Actually, I also used a different drive for my /home directory, because my old drive was getting old - plus my /home directory itself had a lot of old baggage. To that end, I migrated it to a new drive, created a new user with the new OS install, then migrated the files I needed across (moving from Chrome to Chromium wasn't as easy as it should have been, but it was doable). For the most part, it was painless.

I ended up sticking with Ubuntu - but this time I went with Ubuntu Budgie. What I had done was check several other live distros first (regular Ubuntu, BunsenLabs, Solus, Mint, and a few others) to see what was out there again. See, my old system I had built from 14.04 LTS - but I had started with "minimal" and built it up to look and work almost identical to CrunchBang (#!), because I liked it so much (and #! had died, but its descendents hadn't been in a finished state - which is why I looked at BunsenLabs).

I ultimately wanted something like the MBP setup I used for work; I thought I had found it with Solus. It seemed almost perfect - except for its package manager. While it had a lot of offerings, I worried about the ease of whether I could install third-party stuff. One thing I had "vowed" to never again do was to "compile and install from source" (that was part of what got my into this mess); if I ever needed to do that, it would be better for me to run it in a container, on a VM, or in some other manner - just not mangled into my main system with no "accountability" as to what was done and where.

Solus' package management was a custom system, that leaned heavily on app images; I liked that, it was something I had recently looked into (like a week before all this happened), so I wanted that option. But their library wasn't as extensive as the Ubuntu ecosystem, and I also wasn't sure what to do about third-party .deb files and the like - how would I install those. So I looked around for a viable alternative.

I found it with Ubuntu Budgie. I could be on the latest version of Ubuntu (I actually chose stability over latest - so I went with 18.04 LTS), but still have the Budgie desktop (with Plank and other goodness). I've found the best of both worlds, and I have a system now that I believe is as close to my MBP (well, OSX) as I can get with Linux; honestly, I consider it a bit superior.

I've decided, as alluded before, not to install anything from source, as tempting as it may be, and instead only stick within the confines of what is available via apt and (trusted) third-party PPAs. Otherwise, I'll consider using one of the various app image systems, a VirtualBox VM, or something similar - or look for something else. I just don't want to end up in the same boat down the line.

Is it perfect? No. But it certainly beats the pants off of what I had to do with Linux 10 years before, or 10 years before that.

I've been using Linux in one form or another since 1995 (my first "install" was MonkeyLinux, which runs on a DOS filesystem; my first "real" Linux distro was TurboLinux 2.0); back then it was a "nightmare" - a fun nightmare, to be honest. Nothing like recompiling your kernel to get the latest PCMCIA drivers working, among other things. But I'm pretty past that kind of thing today.

Not completely, of course, as b0rking my system with a custom manglement to get gcc/C11 working (took me a while to get all the dependencies just right, but I had it up and running - but the update system for 14.04 LTS did not like it at all).

Re: So Long, Macbook. Hello Again, Linux

#362

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.

I have struggled occasionally with the various Linux package managers not being able to resolve Python library conflicts/dependency conflicts. Like, really, things where you wonder how possibly could there be a conflict, such as scipy not being able to update because matplotlib ver whatever being needed by some other lib that interoperates with scipy but itself is updatable something something something. I'm still no…

[deleted]

Re: So Long, Macbook. Hello Again, Linux

#363
post #182
post #130

Earlier quoted context omitted.

> Font rendering the Apple way is a style choice at best. Given how much of a hacker's usage of a computer is working with text (reading pages, writing code and documentation, taking notes) it's a style choice that actually has a significant impact. (By the way, macOS Mojave deprecates subpixel antialiasing — a poor decision when there are many non-hidpi displays still being used)

I've used both macbooks and linux and have never noticed a difference, so I have no clue what sort of impact I'm supposed to be noticing.

I remember a decade ago when there was more discussion about it the rought situation was: OS X fonts were "blurry" because the font rendering was optimized for stay true to the font shape. Microsoft was "crisp but kerning broken" because the font rendering optimized for pixel alignment, so less grey pixels but shapes moved slightly to fit pixel borders. Linux was somewhere in between however you configured it.

That was the time of sub-100dpi screens though. With 300dpi (Retina) screens these days it does not matter much anymore.

Re: So Long, Macbook. Hello Again, Linux

#364

Earlier quoted context omitted.

> On a Mac, you can cut/copy/paste using predictable keystrokes in any application, anywhere Interesting, because Linux is my daily driver, and when I borrow my spouse's MacBook one of the things I get tripped up on is some programs seem to use Ctrl+C/V and other programs use Command+C/V for copying/pasting

All Mac apps use the Command (⌘) key for copy/paste. I've never encountered an app that uses Ctrl. A developer would really have to go out of their way to accomplish this in their app, since the copy/paste menus are provided by Cocoa; the keyboard shortcuts are essentially built into the OS.

Actually I was misremembering. I was thinking of the Terminal app and having to use Ctrl+A/E to go to beginning/end of line. But jumping words uses Alt+arrow keys. And copy/paste is Cmd+C/V. I find the mixing of the modifier keys really unintuitive as a Mac noob.

Re: So Long, Macbook. Hello Again, Linux

#365
post #310

Earlier quoted context omitted.

There's also complication that there's more than one standard. It's the same reason that emacs doesn't use conventional shortcuts even when it's running in a GUI: it's been using its current conventions since before the invention of the conventions that are now more popular. Similarly, if we just want to go by "preexisting standards" then really it's those newfangled applications that have hijacked ctrl-z to do anyth…

> it's those newfangled applications that have hijacked ctrl-z Yes. Windows botched this by hijacking the Control key, and the desktop-Linux crowd are unable to do anything but imitate Windows. Pre-Linux GUIs didn't have this problem, and MacOS doesn't have this problem.

How hard would it be to adapt a linux distro to have separate keys for control/command (a la MacOS). This is my single biggest blocker against using Linux as my daily driver - not having consistent keybaord shortcuts that avoid collision with terminal interrupts.

Re: So Long, Macbook. Hello Again, Linux

#366
post #228
post #175

Earlier quoted context omitted.

Languages and platforms generally are best supported on linux. Clojure, haskell, python, anything except the platform provided by the Apple/Microsoft is easier to configure on linux. C++ ecosystem sucks a lot when you have to build 5 libraries using 5 different building systems. Linux package managers do that for you.

Yet VC++ offers much better tooling, including pre-compiled headers, incremental compilation and linking, experimental support for modules, C++ friendly OS APIs, and a package manager actually written in C++.

And then you want to use that library that isn't a msvc project.

Or, God forbid, you want to use clang or gcc. Or intel's whatever.

Re: So Long, Macbook. Hello Again, Linux

#367
post #301

Earlier quoted context omitted.

I might be unlucky but Linux had been a nightmare on the few laptops I've tried it on. It is not that I have not tried. I did. Some of the problems I had: Very slow UI, not recognizing my Wifi Card, Chrome stopping support for CentOS, Problems with the Graphic Card and multiple monitors, problems with most printers I try, problem with my Bluetooth mouse... Linux and the multiple variants have been horrible. Also, you…

Your experience running Linux on a laptop is highly dependent on how well it supports the hardware that happens to be in your device. If you're able to research the driver support ahead of time, you may find that Linux runs flawlessly on the laptop you bought. If you install Linux on a random laptop, then getting wifi, audio, etc working can be hit or miss, depending on the drivers. As far as installing apps, I guess…

> Your experience running Linux on a laptop is highly dependent on how well it supports the hardware that happens to be in your device.

My second mainline Linux install was a copy of RedHat on a laptop.

Mind you, this was RedHat 5.1 on an old 486 laptop with 8 meg of RAM, PCMCIA, etc. Sometime in 1995 or 96, I forget.

Several re-compiles later, I had that entire system working - all drivers for all the hardware, including the built-in modem (plus sound and PCMCIA ethernet).

I got lucky there.

Re: So Long, Macbook. Hello Again, Linux

#368
I've come to terms with the idea that different environments offer different things.

With Mac and OSX, you get a beautiful and thoughtful presentation, terminal access, and great with media. You can code, you can look sexy, you can edit your media projects with serious ease.

With Windows, you have brute power, great compatibility, and it's a better option for the market (i.e. cheap and expensive options). Windows is still King of mass market and gaming . (Withholding mobile)

With Linux, you have the option to have many kinds of environments at the lowest cost, with the understanding that you might have to work to get where you actually want to be. But when you get there, the satisfaction is 100x anything you'll get from the other platforms. (Withholding bsd, plan9, etc.)

I've been using Linux for about 7 years, mostly because I realized much of my CS homework can be done on Linux, and it was cool at the time. Also, Macs were/are way out of my budget, and Windows machines are a dime a dozen, just pick your price point. Then I realized the real magic of Linux: it's a free product of the world, for the world. Long after the business behind Windows and Mac leave the planet, Linux will stand as the people's platform. And I figured I should start learning it.

Re: So Long, Macbook. Hello Again, Linux

#369
post #205

Earlier quoted context omitted.

Unless they're X11 apps, those use whatever they feel like.

Of course — the same can be said for terminal programs or Windows apps run via virtualization. Those are not "Mac apps".

But at this point the situation is the same as on linux. I've never encountered anything on linux that didn't use ctrl-c for copy other than terminal apps.

Re: So Long, Macbook. Hello Again, Linux

#370
post #174

Earlier quoted context omitted.

I just use nix on OS X, better package manager than most linux distros have. I have my own copies of py2/3 and the system one, not a huge deal to be honest (outside of the pain of linux side nixos updates breaking derivations for macOS, but thats generally not a fault of the os).

The issue I have with Nix, vs a combined MacPorts+Homebrew is that Nix is a pain to get working. The time investment required for Nix is too high.

Last time I tried Nix I eventually got the Nix environment working, but ran into MacOS-specific issues trying to install relatively common development-related packages like Ruby and PostgreSQL.
Post reply on HN