Live data from Hacker News

Having non-x86 machines makes your life harder

utcc.utoronto.ca

21–30 of 100 posts

Re: Having non-x86 machines makes your life harder

#21
post #4

Implied in this: The expectation to copy binaries between machines and having them work. Less of an issue if you compile from source.

My Chromium compile and test is still running... 2 days later...

chromium is also an abomination, its pretty much the single biggest thing one could possibly build. the sheer level of insanity in that codebase boggles the mind, >1GB highly compressed source is just not legitimate

Re: Having non-x86 machines makes your life harder

#22
post #4

Implied in this: The expectation to copy binaries between machines and having them work. Less of an issue if you compile from source.

My Chromium compile and test is still running... 2 days later...

Having never built it myself, I wonder why the hell is it so slow to compile? I've built Firefox many times, including multi-stage builds with PGO, and it takes maybe 30 minutes tops on my 2015 era desktop. Is it because they use a lot of vendored code?

Re: Having non-x86 machines makes your life harder

#23

Earlier quoted context omitted.

My Chromium compile and test is still running... 2 days later...

chromium is also an abomination, its pretty much the single biggest thing one could possibly build. the sheer level of insanity in that codebase boggles the mind, >1GB highly compressed source is just not legitimate

You haven't seen Office...

Re: Having non-x86 machines makes your life harder

#24
post #16
post #4

Implied in this: The expectation to copy binaries between machines and having them work. Less of an issue if you compile from source.

Reminds me of installing gentoo...

Watching text scroll by for hours made me the Linux expert I am.

Re: Having non-x86 machines makes your life harder

#25
post #6

Lots of people it's using OpenBSD on macppc with light usage. Even playing some games such as OpenTTD. Also, software like Luakit has been working fine, and on videoconferencing... once you have USB 2.0 UVC webcams, FFMPEG and drivers working, FLOSS conferencing software (lots of them) will work the same.

It's not that it doesn't work at all, but it is more effort. Even though I spent more time tinkering with lots of stuff than most (and probably still do), at least having the "Just Works™" option is nice.

Re: Having non-x86 machines makes your life harder

#26
The difference is not mainly about CPU architecture, it’s about the standardized PC architecture vs ARM computers where you need to build a new distribution for every model.

You can easily build a kernel that will run on any PC built in the last decade and any PC that will be built in the next decade. But if you are using an ARM computer you have to run the patched kernel provided by the manufacturer.

Re: Having non-x86 machines makes your life harder

#27
post #5

Earlier quoted context omitted.

Compiling from source is easier said than done for many big open source projects. In practice, they compile only with specific versions of GCC, CMake and libc.

Robustness of the build process should be part of the quality assessment.

You don't always have 6 different projects to choose from because there just aren't that many projects that solve $problem according to your specific $requirements.

And it's also just a hassle even with good build systems, and I say this as someone who has a bunch of custom build scripts to compile stuff from source.

Re: Having non-x86 machines makes your life harder

#28
post #4

Implied in this: The expectation to copy binaries between machines and having them work. Less of an issue if you compile from source.

I've never put much thought into this but given a "linux x86" binary package, on what range of machines is it supposed to work? for instance, what's x86 mean exactly? I suppose all x86 processors have slightly different sets of instruction. Also, different linux kernels may have different sets of syscalls?

Re: Having non-x86 machines makes your life harder

#29
"Picking the right binary for the right architecture", isn't your OS package manager supposed to take care of that? Cross-compiling is often pretty easy if you have custom binaries.

There is a big advantage to using different OSes/architectures with the same programs (compiled to target the right combination of hardware and OS) : it often helps detect subtle bugs, that may not manifest on one platform but be obvious on the next.

Re: Having non-x86 machines makes your life harder

#30
post #5

Earlier quoted context omitted.

Compiling from source is easier said than done for many big open source projects. In practice, they compile only with specific versions of GCC, CMake and libc.

Robustness of the build process should be part of the quality assessment.

quite often, this is a major indicator of how quality is valued in an organisation.

Whether we are talking about open-source or not, there has to be a commitment to excellence at all levels of the product, as would be expected in any other real-world manufacturing.

Post reply on HN