35kb is the size of a lot of entire JS frameworks.

I should also mention that that 35 kB is uncompressed—gzipped, it’s 13 kB, and with brotli it’s 11.3 kB.

Meanwhile, an empty React project seems to be up to 190 kB now, 61 kB gzipped.

For startup performance, it’s fairly well understood that image bytes are cheap while JavaScript bytes are expensive. WebAssembly bytes cost similar to images.

Stick around any corporation (especially one that is heavily regulated and has a revolving door with the government) and you'll hear all kinds of stories.

I'd put this into that bucket of "someone I trust told me they heard the story from someone they trust". It means the story may not be true and they don't have any hard evidence, but they found it believable enough to repeat.

> It's hard to believe that "Priority Delivery" does literally nothing.

That's not exactly what they said. They said normal orders get artificially delayed and priority deliver orders get sent right away. They were clear that the real issue is that priority only exists because they actively made normal orders worse (I'd guess they actually took a few months of slowly backing off normal order time to get customers accustomed to the extra wait).

I've signed NDAs at a few companies. Implied confidentiality has more limitations and gray areas than an NDA and requires trials when businesses tend to prefer arbitrators (those supposedly neutral parties that know their future business depends on "making the right decision" which is why companies win nearly 95% of arbitrations).

Where did AIs learn those em dashes from?

JS has required proper tail calls (PTC) for a decade now. Safari's JavascriptCore and almost every implementation except v8/spidermonkey (and the now defunct chakra) have PTC.

v8 had PTC, but removed it because they insisted it MUST have a new tail call keyword. When they were shot down, they threw a childish fit and removed the PTC from their JIT.

There have been many demonstrations that F150, cybertruck, and others have short ranges when loaded and even shorter ranges when towing (I saw sub 40 miles on a full charge claimed by some people).

If you use your truck as a truck, that’s simply not feasible. If you just use it as expensive transportation, you probably still try to convince yourself by thinking about how you might use it as a truck sometimes and won’t buy an electric truck either.

There’s not much of a market, so leaving makes sense.

> I saw sub 40 miles on a full charge claimed by some people

I've seen some people claim the earth is flat, too! That 40 miles figure had 0 connection to reality

> sub 40 miles on a full charge claimed by some people

See, that's what you get for believing whatever you read on the internet that confirms what you already wanted to believe.

Back in reality, towing does demolish the range, you end up around 1.0 to 1.2 miles per kWh if you put a travel trailer behind a Lightning. Normal 70-75 mph driving is about 2.0 miles/kWh. Around town, depending on your habits, it's 3.5-4 mi/kWh. The battery is 131 kWh. So range can very quite a lot based on your current activity, but someone who told you sub-40 miles was jerking your chain (or had their own motivation for lying).

> There’s not much of a market, so leaving makes sense.

Let's be honest, most people who have trucks don't use them for work and towing

Only if you change TS to have actually sound types and it enables good performance instead of enabling you to craft extraordinarily convoluted types for stuff that you should have never written in the first place.

Put another way, I'm fine with the TS syntax (and use TS because there aren't other choices), but the TS semantics aren't a good long-term solution.

Nobody would consider Chrome or Firefox to be immature or lacking polish because they have replaced entire compilers several times over the past few years? I don't have an exact count, but they probably do this every 3-5 years which puts them way ahead of Racket.

I'd also note that Chez Scheme was a commercial implementation bought and open-sourced by Cisco. It wasn't something they threw together. Because it is a complete scheme v6 implementation they are building on instead of rolling their own implementation in C. Coding against a stable Scheme API has to be easier and less buggy than what they had before (not to mention Chez being much faster at a lot of stuff).