That's their point. The software they want to use often assumes its being run on a platform with systemd, so running that software on Alpine which makes a point to not use systemd causes challenges for them compared to using a different distro.
Nah I’ve a pretty sizeable long position that I’ve pretty much just sat on for a decade - I expect serious compression and then serious backlash over the next year though, as I don’t think their sales are going to slow down as the market seems to assume - we are still just in the foothills, the Newcomen engine. We ain’t seen nothing yet, and Nvidia is positioned to own a serious fraction of the future global economy.
That's the e-ink monopoly for you. Though you could probably use a slightly smaller b&w eink display with a second hand raspberry 4 to shave a lot from that number.
"It's possible to just connect two computers together with Ethernet" - on the front page of hackernews. Incredible. Ethernet over USB4 interdomain protocol at least had some novelty, but this...
It does seem to be a surprisingly common blindspot of programmers in general. I strongly recommend programmers learn it, it can save a lot of headaches in system architecture.
Especially since most machines will just WORK with auto-assigned magic weird IPs and you'll actually be able to share files directly via the OS if you do this, no need for Linux netcat tricks at all.
Now I still remember when target disk mode over ethernet was being talked about.
Programmers have very little understanding of computers, in general.
They'll think hard about a beautiful unrealistic idealisation of the problem, and/or treat a software abstraction as if it's the underlying reality, e.g. (of the latter) thinking networking starts with HTTP and languages start with JavaScript.
Just read the contract from the other side! If focusing on idealistic software abstractions instead of the problem is bad, the implication is that focusing on the problem is good. If treating a software abstraction as the underlying reality is bad, the implication is that looking below it to the actual underlying reality is good.
Not full precision. I've only benchmarked 27B across Q3-6 quants using lm-eval. I lack the hardware to bench 27B at BF16 but I might be able to do Q8_0. I haven't gotten around to doing 35B. I really should upload my collection of results to Github or somewhere.
Here's a summary of what I have for 27B. I used unsloth's UD-Q{3-6}_K_XL quants across 11 evals. The values are pretty linear between Q3 and Q6.
reply