Live data from Hacker News

From Mac to Linux: Web Development with Linux

medium.com

91–100 of 106 posts

Re: From Mac to Linux: Web Development with Linux

#91

Earlier quoted context omitted.

https://galliumos.org/ has done a lot for this space. They're doing a great job at normalizing a *buntu distro across the various chromebook hardware.

Interesting. Support looks patchy, only about 50% of listed devices are fully supported. https://wiki.galliumos.org/Hardware_Compatibility I searched for fully functional 2016 models and found only Acer Chromebook 11. Closer inspection revealed their information was inconsistent and that only 2014-2015 models work - 2016 models apparently don't and use the unsupported NVIDIA Tegra K1 processor. http://www.acer.com/ac…

The hardware list should be correct. The ARM machines you linked are Acer Chromebooks 13s (CB5-311), not Chromebook 11s. The 2016 11s are Intel Bay Trail, and supported.

GalliumOS has good-to-very-good support for almost all Intel Chromebooks, but does not support any ARM models yet.

GalliumOS works very well on the 2015 Pixels. It was a lot of work to get there.

And as with all Linux laptops throughout history, you should definitely check the hardware compatibility list first.

Re: From Mac to Linux: Web Development with Linux

#92

This kind of crap on HN? Srsly? The problem with desktop Linux is poor hardware support. I have Ubuntu on a desktop and on a relatively recent HP laptop. Here's a short list of problems I've experienced - incorrect Nvidia drivers installed by default, random crashes after screen lock, brightness controls don't work out-of-the-box, Wi-Fi dies after waking up, fingerprint scanner doesn't work and never will. I never ha…

Apple has a predefined and very limited line of hardware, so it's obvious that Mac OS is well integrated with Apple devices.

[deleted]

Re: From Mac to Linux: Web Development with Linux

#93

This kind of crap on HN? Srsly? The problem with desktop Linux is poor hardware support. I have Ubuntu on a desktop and on a relatively recent HP laptop. Here's a short list of problems I've experienced - incorrect Nvidia drivers installed by default, random crashes after screen lock, brightness controls don't work out-of-the-box, Wi-Fi dies after waking up, fingerprint scanner doesn't work and never will. I never ha…

Apple has a predefined and very limited line of hardware, so it's obvious that Mac OS is well integrated with Apple devices.

I'm talking about end result here, developing on Linux requires delving into stuff I don't really care about.

Re: From Mac to Linux: Web Development with Linux

#94

This kind of crap on HN? Srsly? The problem with desktop Linux is poor hardware support. I have Ubuntu on a desktop and on a relatively recent HP laptop. Here's a short list of problems I've experienced - incorrect Nvidia drivers installed by default, random crashes after screen lock, brightness controls don't work out-of-the-box, Wi-Fi dies after waking up, fingerprint scanner doesn't work and never will. I never ha…

Apple has a predefined and very limited line of hardware, so it's obvious that Mac OS is well integrated with Apple devices.

... Which makes macOS on Apple hardware a great choice for developers who prefer to focus their efforts on their projects instead of their tools.

... Which is not the only valid approach, of course, but it is compelling to many.

... And the counterargument is that having homogeneous dev and deploy environments has great value. And I agree, but I deploy on FreeBSD, Solaris, and Linux; self-hosted, AWS, and colocated. So I have lots of RAM, virtual machines, staging environments, and a strong preference for low levels of dogma.

Re: From Mac to Linux: Web Development with Linux

#95
post #67

Earlier quoted context omitted.

And your point is? spending the premium for a mac for this use case is a waste of your or the share holders money

not really actually. the 2 systems on offer were similar price range, and there was other factors that pushed towards a mac.

For the same performance/$ I doubt that

Re: From Mac to Linux: Web Development with Linux

#96
post #14
post #8

Earlier quoted context omitted.

The user interface. The package manager that handles everything. Not being locked to Apple's ecosystem, e.g. needing to install Xcode to get your CLI ecosystem working. Not having yearly updates that change everything. Using an open source operating system and not being bound to Apple hardware.

>Not having yearly updates that change everything Yeah, right. >not being bound to Apple hardware. Not an issue for years already, unless we are talking about some very specific hardware. PS: not trying to advocate for either of systems, worked on both linux (ubuntu, arch, centos) and macOS. Both have their share of pros and cons.

> >Not having yearly updates that change everything

>Yeah, right.

Minimal Arch Linux with a minimal desktop and rolling updates.

> >not being bound to Apple hardware.

>Not an issue for years already, unless we are talking about some very specific hardware.

It is an issue, if you have a budget and you want a fast computer for compiling and so on. Right now I'm having a modern 4GHz i7 with 32 gigabytes of ram, a m.2 SSD and two monitors where the other is a 30" IPS. Having the fastest computer in the office is pretty nice, with a price of a macbook and monitor.

Re: From Mac to Linux: Web Development with Linux

#97

Earlier quoted context omitted.

Apple has a predefined and very limited line of hardware, so it's obvious that Mac OS is well integrated with Apple devices.

I'm talking about end result here, developing on Linux requires delving into stuff I don't really care about.

All new dev tools do come from the Linux first, I think it has a reason. I'm personally fine do software development using Linux based laptop. I confirm Linux has some issues with hardware support, but nonetheless I'm still not ready to switch to the glossy Macbook screens.

Re: From Mac to Linux: Web Development with Linux

#98
post #11

The apt-get install for damn near anything is a big one (for Debian based distros obviously) in my opinion. I think the access to build tools and packages is big too. I had case recently where I needed to make a one line change to an Apache module; wget the source, make the change, configure, make, make install, exactly the same as on the prod server. Unfortunately the author delves into text editors, which can be fl…

Homebrew comes pretty close to apt-get on Mac. Of course the whole OS being open source & community driven (sans driver blobs) is nice thing, althought benefits are mostly idealogical than practical. The argument "dev env == production env" is overrated IMO, because you typically want more conservative/controlled production environment anyway and/or you may prefer different distro for workstation use. For serious use…

I ran a Macbook Pro for a while and found Homebrew to be a really poor imitation. I had a lot of issues with it (broken packages, manual intervention required, etc...), things didn't seem as up to date as I'd expect, and the range of packages was poor. It was also only usable for a small subset of the software I'd want.

Re: From Mac to Linux: Web Development with Linux

#99

This kind of crap on HN? Srsly? The problem with desktop Linux is poor hardware support. I have Ubuntu on a desktop and on a relatively recent HP laptop. Here's a short list of problems I've experienced - incorrect Nvidia drivers installed by default, random crashes after screen lock, brightness controls don't work out-of-the-box, Wi-Fi dies after waking up, fingerprint scanner doesn't work and never will. I never ha…

Is that an issue again? It definitely used to be with wifi cards and graphics cards, but back when I was running a laptop (3 years ago), that had all been sorted. I would buy a laptop and use it without any special effort.

Re: From Mac to Linux: Web Development with Linux

#100

The problem with most apt-based distributions is I've found that a lot of packages are out of date. Try out a pacman-based distribution some time. The idea of a rolling distro is great in my mind and most of the packages in the repo are up to date. If something is missing there is usually an AUR. If you use zsh with oh-my-zsh then you're going to have a much easier time finding whatever you need to install. Pacman ha…

There are upsides and downsides. I love Arch and run it myself, but I'd never recommend an 'easy Arch' variant, because I imagine it'd suck.

Arch with it's rolling release setup works, in my experience, because I know my system - all except the most core of the core components I'm never going to touch were installed by me and I know they are there and how I configured them, because I did it manually. No magic. When something goes wrong, I know why, and where to look to fix it. Rolling release adds a small amount of instability (although far less than you'd think), and I imagine that combined with the 'magic' in a more pre-built distro would be really annoying.

Post reply on HN