Recent submissions

Comment · 7 years ago
Yes, that must be it. As I understand it, the deconstruction was included in the working copy of his book before Chapter 1, and then later removed, correct?

Edit: Ah, incorrect. He actually intended it to be a chapter-by-chapter deconstruction but never completed it.

Comment · 7 years ago
Are you using cwm on OpenBSD or on something else? (Just curious.)
Comment · 7 years ago
Comment · 7 years ago
Comment · 7 years ago
This might have seemed as a superficial witticism, but it's not meant as one (honestly!).

There's a fundamental difference in approach towards hardware and software that's cultivated slowly, gently, and steadily by Apple. The objective is to shell out money to the company and its ecosystem, and starts with vendor lock-in with proprietary tech and cheap but paid apps in a closed-off app store, to reach to the point of an annual budget for Apple expenditures that follows the latest iterations of their products, which are buffed up with New! Shiny! Features! that aren't much thought out, but are nominally innovative.

Now, if you go the Linux/BSD open source/free software path, you'll be hard pressed to find software to throw money at. Best you could do is donate to support your favourite projects, but that's optional rather than mandatory. After settling down with a nice system configuration, you'll similarly be hard pressed to find reasons to waste money on continued "upgrades", instead opting for something that works, and returning to it. People buying couples (or even stockpiles) of, say, x203's is a good example here. They're not buying the marketed "cutting edge", they're rather opting for something that supports their workflow, at a fraction of a price.

This demonstrates a fundamental difference of attitudes, on the one hand people subscribing to an open-ended channel of (fashionable?) updates in hardware and software, and on the other people maintaining and updating a workflow. Perhaps obviously, I'm viewing this from the slightly biased dev angle (and not necessarily webdev either).

Understandably, video and graphics people may come from different tech cultures and have different expectations, where the Apple way is more or less the only (apparent) way.

TL;DR, I see the Apple mentality as bombastic value inflation with more varnish than wood, while the FOSS camp as gradual value increase albeit with the occasional splinters.

Disclaimer: I do make daily use of my MBA 11" 2013, but I'd be hard-pressed to change it. Yet if I'm forced to, I'd probably not go for lustre, but for something equally functional. (Think of a "My other laptop runs OpenBSD" bumper sticker.) When I need to offload a build cycle that'd take too long on the MBA, I do so on a Fujitsu rather than a Mac Pro.

There you go. Downvote a guy to assure a better explanation.

Comment · 7 years ago
Haven't tried that, but it really sounds it would be terrible to the wrists after prolonged use (in which case "prolonged" would mean longer than 10-15 minutes).
Comment · 7 years ago
Might you mean the "nipple"?
Comment · 7 years ago
Not really surprising. Old MBA 2013 has an awesome keyboard for coding (and is overall a great terminal device), and the Apple Wireless is identical to some MBA/MBP keyboards. The effective distance between the keys and the overall general width of the keyboard are pretty much en par with "proper" desktop keyboards, with excellent responsiveness and key travel. The MBP 2018 is another deal altogether, obviously. Sad, sad story.
Comment · 7 years ago
The primary difference is whether you think it's alright to spend £35 on a single simple cable or not. Many things that follow simply hinge on that.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton