Your burger opinions are valid. Mostly. Prove it in a short survey. $5 reward for eligible participants who complete it.

@bunjavascript @jarredsumner why a runtime behavior change over a compile time error when assertions can't be verified? I mean it's explicit but imo Number(raw) is more explicit and an easy change. Also what does it do to structural types?

@bunjavascript this feel worse than making a new language because now you need to know which runtime behavior it is. LLMs will get tripped up by this.

@bunjavascript how do you check `val as ComplextGenericTypeVar` ?

@bunjavascript this is remarkably close to Swift

@bunjavascriptespect.

That’s all cool and really improves the logic, but then call it BunScript and use the .bs extension💁‍♂️

By changing how TypeScript works - almost everywhere - you are taking on a lot and only increasing development chaos.

If you want to fix the TS, go through its committee.

@bunjavascript Rename to BunScript because it isn’t isomorphic.

@bunjavascript I am all for types, but "`as` converts" is a mistake.

The right conversation starts with the right rep. Let Cal make the intro.

@bunjavascript as a standalone idea, this is fine, but this isn't TypeScript - you've invented a language that looks identical but works entirely differently

@bunjavascript This is all pretty cool, but I think using `as` for converting types is a mistake, it should just be used for type assertions, like assignments do in this implementation

@bunjavascript Mostly agree, but not with "as converts".
`as` should assert a value's type, not change it.
Coercing invalid values can hide bad input.
Type mismatches should throw; conversions should be explicit, e.g. `Number()`. Thoughts, @jarredsumner?

@bunjavascript looks pretty cool but are we still calling it TypeScript or is it BunScript now? 🤔

@bunjavascript Impressive, but at this point it's just not TypeScript anymore and this will likely cause chaos and incompatibility issues. Having the same code behave differently on the backend Vs the browser feels like a really big problem to me.

@bunjavascript Seems so obvious now, the types are already there, fuck yes they should be real.

@bunjavascript time to leave node

The next generation of AI won't be won by model selection alone. It will be won by the teams that can build, manage, and scale proprietary multimodal datasets efficiently.

@bunjavascript So, bun is turning TypeScript into a real language. What a world we live in.

@bunjavascript Call it TypedScript

@bunjavascript what breaks when you turn it on

@bunjavascript Please enable it for SQL as well!

Inspiration: github.com/ilbertt/bun-sq…

@bunjavascript I don't think it's necessary to alter the TypeScript semantics.. I believe it's better to use the types to guide the AoT.

@bunjavascript all the checks are great, but as should never convert, it should check

@bunjavascript Oh come guys, this isn't that hard. You could still show the source of a function e.g.

It just blows up your binary.

Researchers are conducting a study to understand how to prevent suicide among Black LGBTQ young people. If you qualify, you will be invited to take a 45-minute online survey every 3 months over 18 months. Eligible participants receive $30 gift card for each survey completed.

@bunjavascript just call it BunScript with .bs instead of ts anymore

@bunjavascript Like the idea behind this in principle, but co-opting TypeScript for this feels wrong when it is entirely new behavior, and I fear it will cause confusion/fragmentation in the ecosystem. Treat it as your own, new language: BunScript, or something.

@bunjavascript This isn't TypeScript anymore, call it something else

@bunjavascript So it’s not TS anymore then…

@bunjavascript How does it work with discriminated unions, does it throw if a runtime value isn’t one of them? & does it allow branded types?

@bunjavascript @cirospaciari Awesome! Next... zod like validator built-in 😎

@bunjavascript failing ahead-of-the-time is good, but changing javascript specification is questionable

@bunjavascript would be nice a few references on this kind of post

@bunjavascript The `as any` case is the migration edge: runtime checks catch bad data, but existing TS can start throwing where it used to run. Is there an opt-out?

@bunjavascript I think it'll be better to have "converts" be called "casts"? It's a more familiar term.

@bunjavascript `as` should never convert, there are existing functions to parse numbers.

Which ones are built time vs runtime errors?

TypeScript is primarily structurally typed so these nominal errors go against that.

@bunjavascript It feels like rust here 😂