Right now Intel and AMD have less to fear from Apple than they do from Qualcomm – the people who can do what they need to do with a Mac and want to are already doing that, it’s businesses that are locked into the Windows ecosystem that drive the bulk of their laptop sales right now, and ARM laptops running Windows are the main threat in the short term.

If going wider and integrating more coprocessors gets them closer to matching Apple Silicon in performance per watt, that’s great, but Apple snatching up their traditional PC market sector is a fairly distant threat in comparison.

The problem is that the private sector faces the same pressures about the appearance of failure. Imagine if Boeing adopted the SpaceX approach now and started blowing up Starliner prototypes on a monthly basis to see what they could learn. How badly would that play in the press? How quickly would their stock price tank? How long would the people responsible for that direction be able to hold on to their jobs before the board forced them out in favor of somebody who’d take them back to the conservative approach?

Heck, even SpaceX got suddenly cagey about their first stage return attempts failing the moment they started offering stakes to outside investors, whereas previously they’d celebrated those attempts that didn’t quite work. Look as well at how the press has reacted to Starship’s failures, even though the program has been making progress from launch to launch at a much greater pace than Falcon did initially. The fact of the matter is that SpaceX’s initial success-though-informative-failure approach only worked because it was bankrolled entirely by one weird dude with cubic dollars to burn and a personal willingness to accept those failures. That’s not the case for many others.

NASA in-house projects were historically expensive because they took the approach that they were building single-digit numbers of everything – very nearly every vehicle was bespoke, essentially – and because failure was a death sentence politically, they couldn’t blow things up and iterate quickly. Everything had to be studied and reviewed and re-reviewed and then non-destructively tested and retested and integration tested and dry rehearsed and wet rehearsed and debriefed and revised and retested and etc. ad infinitum. That’s arguably what you want in something like a billion dollar space telescope that you only need one of and has to work right the first time, but the lesson of SpaceX is that as long as you aren’t afraid of failure you can start cheap and cheerful, make mistakes, and learn more from those mistakes than you would from packing a dozen layers of bureaucracy into a QC program and have them all spitball hypothetical failure modes for months.

Boeing, ULA and the rest of the old space crew are so used to doing things the old way that they struggle culturally to make the adaptations needed to compete with SpaceX on price, and then in Boeing’s case the MBAs also decided that if they stopped doing all that pesky engineering analysis and QA/QC work they could spend all that labor cost on stock buybacks instead.

Another perovskite hype piece. You’ll know that they’ve got something that’s commercially viable once they’re making these sorts of efficiency claims and not omitting information about cell degradation.

Given that the first perovskites studied had lifespans that could be measured in minutes, this is great progress, but the fundamental problem is that as a class of materials they just don’t want to exist outside of an inert atmosphere. Without significant progress in stability and encapsulation materials, they’re more of a research curiosity than a viable real-world PV tech.

A combination of resting on their laurels during AMD’s lost decade, and failure to retain competitive process technology during the extended gestation and ultimate failure of their non-EUV 10nm node. The arrogance of taking their foot off the gas and assuming nobody would ever catch back up to them backfired hard.

Problem is that if you’re looking for FOSS software outside of the absolute most mainstream use cases, that type of software is the only available option. GIMP and Inkscape have been mentioned but throw FreeCAD into the ring as well. Shotcut and Kdenlive are passable, but don’t quite measure up to the commercial alternatives.

My particular hobby horse is CFD code. OpenFOAM is fantastic from a technical standpoint, but until recently, to actually use it you either had to buy a commercial front-end, or literally write C++ header files to set up your cases. There’s a heroic Korean developer who’s put together a basic but very functional front-end GUI in the last year to change that, but it only covers relatively straightforward cases at the moment.

My first attempt to switch to Linux for my primary desktop was in 2007, and ended when my attempt to run WoW via WINE mostly worked, but had a weird an completely unfixable audio delay.

Proton (and Valve’s efforts on SteamOS and the Steam Deck more generally) have been an absolute godsend for Linux as a usable daily-driver.

I was a longtime Debian/apt diehard but I’m coming down on the same side of late. My homelab runs Proxmox (Debian based) with Ubuntu 22.04 LTS containers for more up-to-date packages, but my attempt to use KDE Neon (Ubuntu-based) for my desktop PC was a disaster. I’ve switched to Nobara (Fedora-based), and other than having to switch from Wayland back X11 because Wayland on NVidia breaks a bunch of things I need for work it’s been relatively smooth sailing.

The server I set up for my friends is named “Portable Creatures: Exhalation of the Wilderness” for a reason.

I installed KDE Neon on Friday evening and things were going great, everything was testing well, and Saturday game night with the gang went flawlessly, but this morning the VMWare Horizon Linux client spontaneously decided that it didn’t want to accept mouse input anymore, so after ten minutes of troubleshooting I gave up and booted back into Windows so that I can be productive today.

A battle lost, but the war is not over yet.

On the other hand, Fraunhofer is obnoxious enough about licensing and enforcement that companies like Google invested similar money and effort into developing open-source codecs just to avoid dealing with them.