Live data from Hacker News

So Long, Macbook. Hello Again, Linux

richardmavis.info

151–160 of 531 posts

Re: So Long, Macbook. Hello Again, Linux

#151
I recently 'downgraded' from a 2017 MBP nonTB to a 2015 X1 Carbon Thinkpad with Manjaro Linux installed and i'm loving it. Only cost me 330 euros second hand.

Apple are dead to me after I spent thousands on a machine that has a broken keyboard.

In hindsight I wish I switched to Linux years ago for my professional computing. swdevs, sysadmins & security people who know the ins and outs of computing should switch.

I call it conscious computing.

Re: So Long, Macbook. Hello Again, Linux

#152

I find the fetish for terminal-based music players a bit odd. I associate terminals with doing work , so the idea of having one whose sole purpose is playing music (presumably in the background while you do other stuff) to feel like a waste of screen real-estate and something I'm likely to accidentally pull up while trying to cycle between my other terminal windows where I'm doing stuff. I much prefer something that…

I usually run 2 konsole windows with several tabs in them. One is for git, building, packaging, etc, and the other is for random tasks on the side, and in a second tab there is mplayer playing some internet radio.

It's less clutter IMHO. But i don't use tiling wm.

Re: So Long, Macbook. Hello Again, Linux

#154

Hooking up three monitors, 2 of which are 4k onto Ubuntu is the most frustrating thing I've done with that OS. It just works on OSX though. Rough spots is a good way to describe it. Overall it works... But not without effort and competence.

That doesn't "Just work" on Windows 7 or 10, though, so not sure it's a failure on the part of Linux as much as a success on the part of macOS.

Anecdata incoming, multi-monitor on Win 10 works just fine for me. I've got 2 screens attached to my laptop and they're just fine, even with different scaling on each one.

Re: So Long, Macbook. Hello Again, Linux

#155
post #139

Earlier quoted context omitted.

I'm using xorg but very interested in Wayland. My main "fear" with wayland is that my scripts to properly handle things like a uniform copy/paste will stop working Would you have some links? I am especially interested in ways to handle shortcuts like with autohotkey on Windows: a context dependent remap (ex: pressing a given physical key may send ctrl-tab in an application, but ctrl-pagedown in another if said other…

Handling shortcuts would be compositor specific. Unlike X, the display server part with Wayland is implemented by the compositors. Wayland itself is just the protocol. KWin for example allows setting various global shortcuts: https://docs.kde.org/trunk5/en/kde-workspace/kcontrol/keys/i... For wl-copy / wl-paste, see: https://github.com/bugaevc/wl-clipboard

Would you recommend a given compositor to have something close to LXDE or any other minimal window manager in xorg?

I'm thinking about starting with weston and moving to sway if it doesn't do the job

Re: So Long, Macbook. Hello Again, Linux

#156

Earlier quoted context omitted.

> What does "display/compositor fragmentation" mean to end-user? My 1Password FireFox extension (ubuntu 18.04 LTS) doesn't work on X unless I log in through the website but it works just fine on Wayland.

What is your X session? Gnome/KDE or plain window manager? It might be, that your wm is not launching some service that wayland session is and 1password needs.

This was a clean install so Gnome shell - worked just fine on Ubuntu 17.10 and 18.10 with X and Wayland.

After I login through the 1password website, the extension window opens just fine so it might be some input security service, but how would a Firefox extension even have access to a system service like that except through Firefox's built in APIs?

Re: So Long, Macbook. Hello Again, Linux

#157
I've been developing fulltime on Linux since 2014. I can't speak for the default distros/DEs, since I've been using i3 and sway the entire time. But it's been a fantastic development environment for me.

I recently watched one of my colleagues run a build on their macbook. Not a complicated build. A go binary compile and a docker image build. But it really struck me how slow it was. What takes 15 seconds on my underpowered linux workstation took 60+ seconds on their $2000 macbook. That's unacceptable to me.

Re: So Long, Macbook. Hello Again, Linux

#158
post #85

There are different issues with OSX though, that colleagues of mine had, that never occur with Linux. E.g. the chore of somehow managing different software versions such as the outdated default one and a second one installed with homebrew. Almost all my colleagues struggled with setting up python 2 und 3 correctly at some point, whereas this just worked for me on Linux. Some struggled with font rendering between a 10…

>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 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).

Re: So Long, Macbook. Hello Again, Linux

#159

I guess the author actually meant to say “So long, OSX” as Macbooks (older than 2016 versions) actually are good hosts for running Linux. I myself run have two Macbooks (Air 13 and Pro 15) with dual boot setup, so I get the best of two worlds: perfect programming setup (i3) on Linux, perfect multimedia (I use Lightroom / Premiere sometimes) setup on OSX.

> I guess the author actually meant to say “So long, OSX”

It's called macOS, if you're going to be pedantic about something someone else wrote. It's not been called OSX (actually OS X) for years.

Re: So Long, Macbook. Hello Again, Linux

#160
I'm currently on Ubuntu 18.04 and I love it but:

- Firefox takes literally 10 seconds to start unless I disable eth0

- Chromium isn't able to resolve DNS for local intranet sites

- Have not tried chrome as installing it means fiddling with apt repos, wget or gdebi

These issues are unresolved as of January 2019. I can't say that I ever had such issues on macOS. I have had DNS issues because of my specific ISP router after a major macOS upgrade but my ISP patched it within a week.

Post reply on HN