I agree with this, I've been less and less happy with Windows since Windows 7 for the most part. I don't want telemetry, ads, and certainly not react native start menus. I just want an OS that works well.

I found the episode very enlightening, and learned a lot as well as unlearned a few things that I thought I had known.

I never realized how much of azure was him early on.' I didn't realize the tension between him and Bill, always assumed those two were thick as thieves, all the time. I super respect him for stepping down so that the company can change in the way it needs to, and also so wall street would realize a change has happened (which was around spending discipline vs. investments, and giving forward guidance, etc)

I left this episode with a lot more respect for him as a person and saw him much more introspective and up front that I would have imagined based on what I thought I knew before.

Also, a formerly favorite phrase of saying "we're in the Ballmer era at X company" is struck from my vocabularly, since in most places I've used it, it's meant to be an insult to the company, however it's really just an insult to Ballmer. He was way more intuned than many others.

Generalized a bit: everything can be a database if you use it wrongly enough.

I've been a registered user of ST for long long time, and I thought if anything hurt them in the marketplace, it was taking several years off from the end of 2013 until late 2017 with hardly anything being released that opened the door to Atom and other editors to catch up.

Many of they are all based on code OSS.

Windsurf started out as just extensions, as did continue.dev.

I wonder what is the delta in the API support needed to use vscode + paid extension vs. code OSS + bundled extensions.

This is like the Kiro team read one of Corey Quinn's many pieces on Cloud NAT pricing and was like "Hold my beer".

I know he thought it was "not terrible" at first, I'm excited to see his take on the pricing now :)

honestly until UV I thought this was the only sane way to package a python app, now it's still the only sane way and I'll use uv in the dockerfile which is honestly more complicated than their docs or reason would expect.

like what?

The problem is you can do whatever you want in it, and then have no way of reproducing that.

pyproject.toml tries to fix it, poetry kept wanting to use their own wonky names for the tags, I'm not sure why.

Once that is standardized, venvs should be cattle and not pets. That is all that is needed. UV makes that fast by hardlinking in the libraries and telling you the obvoius (that venvs should be cattle and not pets)

This fight was poetry's to loose.

I think poetry “lost” because they had to build ahead of the PEPs that standardized their way of doing things. I don’t think uv could exist without the work the poetry people put in, it served as a pretty powerful demonstration of the fact that better python packaging was possible.

No, the JS bundling changes are almost monthly and it's impossible to know which one should I use and what will be broken because of my choice.

Other than a brief stint with yarn (v1) I've never had any of these troubles with node+npm