It may be even easier to not even leave a vm in off. Using either the fly command or their api, you can kick off a one-off machine that runs an arbitrary script on boot and dies when that script ends.

yanked from my script:

    cmd = [
      "fly", "machine", "run", latest_image,
      "--app", APP_NAME,
      "--region", options[:region],
      '--vm-size', 'performance-1x',
      '--memory', options[:memory] || '2048m',
      "--entrypoint", "/rails/bin/docker-entrypoint bundle exec rake #{rake_task}",
      "--rm"
    ]
    
    system(cmd)

or a 1-1 transliteration to their api. You can of course run many of these at once.

I found it not just to lead to embellishment, but (1) the problems it did flag mostly would be caught by minimal testing; whereas (2) it regularly missed deeper problems. For an example of the latter: using TanStack (React Query) api caching, you have different data shapes for infinite scroll vs non infinite scroll. There were circumstances were an app confused them. Typescript had nothing to say. Nominal typing easily handles these cases and, ime, caught more actual problems.

> the problems it did flag mostly would be caught by minimal testing

Yeah, I agree, and the thing is, you're going to write automated tests whether you're developing in JavaScript or TypeScript so the extra cruft of TypeScript seems even less worthwhile.

The argument I've heard people put forward is that JS is fine for small projects or a couple of developers but doesn't scale to large projects or teams. I don't know how large large is, but I've worked on a project with around 30 devs where the front-end was all JavaScript and everyone was touching it and, sure, that project had some problems, but the root cause of those problems wasn't using JavaScript.

> the problems it did flag mostly would be caught by minimal testing

Testing is more expensive up front and in maintenance than type annotations. A test suite comprehensive enough to replace type annotations would have an ass load of assertions that just asserted variable type; if you were involved in early pre-TS Node, you remember those test suites and how they basically made code immutable.

> (2) it regularly missed deeper problems

This is a skill issue. If your types do not match runtime behavior and you choose to blame the programming language rather than your usage of it, that's on you. There are a lot of unsafe edges to TS, but a diligent and disciplined engineer can keep them isolated and wrapped in safe blocks. Turn off `any`, turn on all the maximal strictness checks, and see if your code still passes, because if what you said about infinite scroll is true, it won't.

> here are a lot of unsafe edges to TS

And one of its many problems is that it tries quite hard to pass itself off as not having those unsafe edges which, ironically, makes it easier to get tripped up by them.

It's just... immensely self-aggrandizing nonsense. The subhed

> “Preface to the highest stakes negotiations in history.”

Like come on. The cuban missile crisis, for starters? Bro needs to calm tf down.

And for their kids sick and tired of trying to help them fix Window's incompetence. You're into Dell for at least $800 for anything approaching an actually usable laptop. This is definitely my mom's next laptop.

I also got the attractive asian women definitely not wearing construction clothing demonstrating automated pipe welding machines.

The worst is when you accidentally click one of the manosphere/incel videos, then get a stream of them afterwards.

Now I'm getting Asian archery videos, which are really ads for elaborate compound bows with pulleys. I've been trying to tell whether they're really hitting the target or just faking it.

most websites, particularly those behind cloudflare, are very restrictive even to crawlers that obey robots. Proof: a ton of my time over the last year, and my crawlers very carefully obey robots.

It's hard to see how this isn't extorting folks by offering a working solution that, oh, cloudflare doesn't block. As long as you pay Cloudflare.

Perhaps I'm overly cynical, but I'd be quite surprised if cloudflare subjected their own headless browsing to the same rules the rest of the internet gets.

>most websites, particularly those behind cloudflare, are very restrictive even to crawlers that obey robots. Proof: a ton of my time over the last year, and my crawlers very carefully obey robots.

The docs are pretty equivocal though:

>If you use Cloudflare products that control or restrict bot traffic such as Bot Management, Web Application Firewall (WAF), or Turnstile, the same rules will apply to the Browser Rendering crawler.

It's not just robots.txt. Most (all?) restrictions that apply to outside bots apply to cloudflare's bot as well, at least that's what they're claiming. If they're being this explicit about it, I'm willing to give them the benefit of the doubt until there's evidence to the contrary, rather than being a cynic and assuming the worst.

Sounds like a firing / soft firing / come to jesus moment about the viability of the business...

They could have launched paid subscriptions, they even said they were looking into it, crickets...

Pretty much. It's fun seeing idealists get slapped by reality. If you want to protect your ideals you better know how to fight for them using the same tactics as your competitors.

Learning how to build a board that is in your favor, making alliances with less than pure players if needed, and being ruthlessly competitive allows an ideal to become reality.

You are wrong about pretty much all of that, including your assumed reasoning for why this is happening. Jay chose to change her role so she could do deeper work on the technology. That's it.

The issue is that no one really believes the corporate speak any more. Bluesky does not get a pass on this, re: VC funding

I have concerns about one piece of messaging I've seen lately, working on a writeup, stay tuned

What's fun about it?

It's like seeing your kid learn how to walk. They'll fail a couple of times, but they'll get toughen up and finally learn.

Additionally, it's not like this necessarily got posted out of the blue. There's another Huy Fong sriracha shortage due to a Mexican crop failure driven by climate change. So anyone wondering why they can't buy it will naturally encounter this story.

https://lacabaarodriguez.shop/news/127/2026-03-06-huy-fong-f...

And as you mentioned, that lawsuit has pretty convincing evidence of a multi-year plan to really screw the supplier in order to get even more fantastically wealthy. Amazing greed combined with profound stupidity about the difficulty of reliably sourcing 2 _thousand_ acres of ripe chilies. There's been a decade of rolling shortages.

That's not what's happening as far as I can tell.

These users have agreed to a monthly contract or, if there is no money paid, a contract with no finite end date but with provisions to change terms, essentially terminating and restarting. So the service provider has decided to amend the contract at the end of the current (one month) contract in the first case, or on some date arbitrary date in the second (unpaid). The users are free not to accept the new contracts.

So nobody is just changing a contract mid stream. Use of a service month-to-month implicitly agrees to this: your ability to stop using and paying them on the 1st of the next month is their ability to change the terms on which the service is offered next month.

And btw, everyone on here hates this, but I don't know how else it could work. The idea that if I sell a customer one month of a paid saas on a monthly plan I'm somehow obligated to never change my terms or price forever as long as he or she keeps paying is beyond absurd. If people want stable terms, they need to find software that will sell them annual or multiyear contracts.

I think the way it would normally work is that you present them with the price offer and ask whether they accept, and if they do you render the service.

This is exactly the same. The company has changed the terms under which they will offer the service starting next contract renewal.

I'd like to agree, but I don't. If companies didn't want to be involved, they would aggressively be pushing governments to provide ways to confirm age w/o transmitting any other data. Primarily because you can't leak data you never had in the first place. I don't see that happening.