I will always, always love and respect it. I love that they are still committed to the OG device. I want to pull mine out and see if the spinning hard drive still works after all these years, might even try to update it!

Yes, there are way more options to get sub $500 Android phones, but pretending like an iPhone is too expensive for most Americans when carrier deals are often as good or better for iPhone options (to say nothing of the older phones being sold by Total Wireless and the like) and when more people in the United States use iPhone vs Android is a little bit silly.

We just got $1130 from Verizon for my husband's old iPhone 14 Plus towards his new iPhone 17 Pro (I get a new phone every year so I’m just on the Apple Upgrade plan or I buy it outright each year, whereas he gets a new phone every 3 years or so), making it essentially free (we had to change the plan he was on but it cost the same as the old plan) and if he’d wanted a regular iPhone 17, he could’ve dropped down to a cheaper phone plan too. A 16e would’ve been even less than that.

I’ve written before about how I think the Steam Deck is one of the best v1 products in recent memory, in large part because Valve learned so much (and so well) from the failures of the Steam Machines.

I don’t know if I would call it a misstep, but it was absolutely a failure. And a brutal one. Valve should be lauded for taking the right lessons from that failure and investing in Proton and doing the compatibility work themselves rather than expecting devs to do it (Apple is the only company that consistently gets developers to rebuild for their platform, and even game developers won’t do that), but we shouldn’t let the fact that it wound up on the right path years later diminish the fact that the original strategy —- if not the devices or idea itself —- was hugely flawed.

Handbrake and Losslssscut are great too. But in addition to donating to FFmpeg, I pay for ffWorks because it really does offer a lot of value to me. I don’t think there is anything close to its polish on other platforms, unfortunately.

[1]: https://www.ffworks.net/index.html

The official guidance from Microsoft since probably 2019 has been to encourage all greenfield projects to GitHub, as opposed to ADO.

Cursor, Windsurf, etc. are building multi-billion dollar businesses off the backs of the work that the VS Code team has done. And that’s totally fine! What’s not fine, is trying to have access to the whole ecosystem of first party extensions that aren’t MIT licensed.

I agree there should be more resilient extension repos, but this is one of the problems Eclipse Theia [0] has tried to take on, but most projects just fork the core VS Code experience and slot in OpenVSX rather than doing the hard, expensive work of building their own extension marketplaces or LSPs. And you know what, for a community or OSS fork, I think that’s fair. I think when you raise hundreds of millions in funding, you can build your own LSPs and start to maintain your own infra for extensions. And if you’ve got enough buy-in, you can probably convince developers to submit directly to your marketplace too.

And it isn’t even a rug pull, per se. The first changes to the license on some of the 1P VS Code extensions probably happened in late 2018 or early 2019, with remote share. The LSPs may have changed later. If anything, the Code team was probably too lax about letting the commercial forks use their resources wholesale against the license terms for as long as they did.

Disclaimer: I used to work at Microsoft and then at GitHub with things that touched VS Code. I now work at Google, who uses VS Code (well Monaco) inside some of our editors/products, but I don’t work on any of those.

[0]: https://theia-ide.org/

I fully agree that (A)GPLv3 code effectively stops code from being used by many large companies (every place I’ve worked in the last decade has a near blanket policy on refusing to use code licensed that way except in very specific and exigent circumstances), but it isn’t necessarily true that app developers can’t use (or can’t choose to license) (A)GPL code in their iOS apps, provided they abide by the terms of the license.

Most developers won’t — or can’t — but the advent of dynamic linking of libraries in iOS, as well as the EU-mandated third-party app stores (which aren’t available outside the EU, but still), make the situation a lot more grey from the black and white stands the FSF attempted to take in the early 2010s. And to my knowledge there have been no legal challenges about the use of GPL code in iOS apps, so the issue is essentially unsettled.

That said, in most of the cases where I have seen iOS apps use GPL code, the full app source was available (and that may or may not fulfill the redistribution requirements but I’m not a lawyer and I’m not going to cosplay as one).

On Android, where full Google Play alternatives like F-Droid are available, plenty of GPLv3 apps exist, even if they aren’t available on Google Play.

But yes, when it comes to incorporating GPL code into a non-GPL app, that is much more difficult in the realm of mobile than it is for other types of applications.

A WASM solution might not be the most performant but it will be an option.

As for the web not being a good application platform, that ship sailed 20+ years ago and at this point, it’s hard to find any “native” apps that don’t share at least some similarities or core components as web apps, even if it’s just for UI. Although I personally would rather have a good native Mac app than a mediocre web app, I’d rather have a well-written web app than a mediocre Mac Catalyst app, and in many cases, than running an iOS app on the Mac. And I often prefer a web app or app built with web technologies to “native” apps built with GTK or Qt.

[1]: https://liberapay.com/about/global