Why is that preferable to just pivoting?

Because Sourcegraph is a viable business in its own right. Small companies find it challenging to do multiple things well, and it's normally better for them to spin off promising ideas that aren't directly part of their main product.

Presumably they wanted to continue working on sourcegraph? Or maybe they want to have something left if amp flops?

CDs skip very easily so they're not good for portability. So that limits their use to in the house, and they're you're competing with vinyl. Cassette fill a niche in the nostalgia world being something you can more easily use on the go.

I had lots of CD and mp3-CD players with good anti-skip. Some would even buffer enough or the song to stop the CD for several seconds at a time, especially so on my later mp3/ATRAC CD players. The crappier ones added crappy audio compression to fit it's tiny memory, but better ones could do the raw data and had no (at least to me) loss in quality and later the mp3/ATRAC ones would just buffer the actual file data.

I don't think I've ever experienced a car CD player skipping due to shock. I'm sure it could happen, but I don't do much trail driving at high speeds personally.

I listened to my CD players while biking, hiking, and more. No reason to leave the CDs at home unless you already upgraded to one of those fancy hard drive mp3 players.

Yeah it was probably around 2003 I listened to all my music on MP3 CDs I made and it had like 30 seconds solid of buffering that I never managed to hit unless I sat their purposefully shaking my player in my hands to watch the buffer meter go down.

There were many portable CD players with enough buffering that they'd never skip. Panasonic Shockwave (IIRC) for example. And car heatunits.

You had to get a very old or seriously cheap portable player to get skipping.

Cassettes get distorted too when moving (.e.g running). There’s very cool tech in some models that prevent this distortion but they are more expensive.

I don't understand how people use these tools without a subscription. Unless you are using it very infrequently paying per token gets costly very fast.

Work pays for it. I don't work for stingy companies that don't provide the tools required to do the job. (our team spends > $1000/m EACH on Amp alone)

Could you please share a little on why it's noticeably better than Claude Code on a sub (or 5? I mean, sometimes you can brute force a solution with agents)?

So the point of this is to clean the cap table, right? Current investors aren't getting a stake in the new company?

One great thing about Forejo is that you can have a FreeBSD builder and on GH you cannot, have to spin up a slow VM.

Also framework laptops work (mostly): https://github.com/FrameworkComputer/freebsd-on-framework

Even if true, not having great support for laptops doesn't mean "no one uses FreeBSD". Obviously it's supported by essentially all server hardware and is used there, as well as many routers and the Playstation.

I use it on the desktop as daily driver. It's great.

It's a desktop (a NUC) though so I don't use WiFi. I really hate laptops.

I feel like the existence of LuaJIT made is seemed like standard Lua was slow, but that's far from the case.

I spent a few nights trying to implement a Lua interpreter myself and it was still like 10x slower than PUC Lua, even before adding a GC. I'm not sure how they do it, it looks like regular C code

The fact that you're familiar with the Coke controversy proves the point. Before they were rare and memorable. Now it happens ever other week. Bots are intentionally driving division.

Why would they need to delete storage, they could just not accept past the cap.

Storage billing is partly time-based.

EBS is billed by the second (with a one minute minimum, I think).

Once a customer hits their billing cap, either AWS has to give away that storage, have the bill continue to increase, or destroy user data.

I think most of the "horror stories" aren't related to cases like this. So we can at least agree most such stories could be easily avoided, before we looked at solutions to these more nuanced problems (one of which would be clearly communicating the mechanism of a limit and what would be the daily cost of maintaining the maxed storage - and for a free account the settings could be adjusted for these "costs" to be within free quota)