Ryan Cavanaugh 👉 searyanc.dev on bsky

Trying out Twitter 2: The Twittening. Follow @ bsky.app/profile/searya…

@KentonVarda @loganb @GrantSlatton Everyone says they'd be okay with the limited version of a feature right up until they hit a single limitation of it, at which point they say it shouldn't have existed in the first place because it added complexity to the language for no reason

@SeaRyanC @loganb @GrantSlatton Nah that's fine. It can just handle common cases and error on anything too complex, still would be incredibly useful.

No offense to the Zod devs but I don't understand why Zod has to exist. Why can't we just use the schema format we already have, that is, TypeScript? Why is there no way to construct a schema validator from a TypeScript type? This seems like such an obvious thing.

@loganb @GrantSlatton @KentonVarda There are things you can trivially check at runtime that can't be represented by the type system, and vice versa, so you'd always have a fairly awkward impedance mismatch

@GrantSlatton @KentonVarda Cc: @SeaRyanC this comes up a lot.

@Boenau This is why I drive a cement mixer for all my trips

Important reminder: It is difficult to use an e-bike when moving your family into a new home, which is why your household vehicle fleet should not include an e-bike.

@colinhacks I'm like 80% of the way there. Takes FAQ markdown as an input, tailors the FAQ output to the user's issue.

someone please make an AI for responding to GitHub issues, preferably w/ RAG against docs & previous issues there's a HUGE market for this (several dozen broke OSS maintainers)

@sclsoftware @typescript That's an odd result; no codebase we've looked so far at has sped up by that little. Do you have a repo we can try building to get a profile with?

@SeaRyanC @typescript I am geting a performance increase of ~15% (0.8s vs 0.68s). I was expecting something radical. What can we expect when it is ready?

Today we're announcing previews of the native port of TypeScript! These nightly previews will be available on npm and the VS Code marketplace! npm install -D @​typescript/native-preview npx tsgo --version Read up more on our blog! devblogs.microsoft.com/typescript/ann…

@sclsoftware @typescript Not supported yet. Soon!

@typescript tsconfig.json "references": [...] is not supported yet? It seems to ignore it. With tsc works fine.

@TheLarkInn Don't put your feet on the dash like this! It's extremely dangerous in the event of a crash

Never having to drive on trips because people with motion sickness are magically cured by driving. Forever passenger Prince. 😴

@iamkunalarya The naming *is* the set theory naming stackoverflow.com/questions/3885…

TypeScript's union and intersection types behave differently than set theory in math. Can someone explain the design decisions behind this? Why the shift from combining sets to combining types? #typescript

LIVE NOW with @ahejlsberg:

@lazytype @drosenwasser @andhaveaniceday We could serialize ASTs, but I'm not sure where that cache would even go (maybe tsbuildinfo?). Validating up-to-dateness implies I/O cost would be unchanged. Serializing types is pretty gnarly due to the type representation having references to the global symbol table

@SeaRyanC @drosenwasser @andhaveaniceday

So many people hung up on the new TS being written in Go. Problem solving is not forcing the usage of your favorite solution.

@tmikov @pawan_k_sharma_ There are JIT-side optimizations that could help here (e.g. identify "common prefix" object layouts and treat them as monomorphic) but they likely wouldn't pay for themselves in any scenario except this specific one

@tmikov @pawan_k_sharma_ But if you're accessing highly polymorphic data (e.g. as you would when reading off an AST node, or one type-kind of many), you go megamorphic, and now property access is on par with a hash table lookup

My brief thoughts on the TypeScript compiler rewritten in Go. It objectively makes sense. Besides Go, there is currently no other language that satisfies the following criteria: - Mainstream. - Multi-platform. - Garbage collected. - Performant. - Safe-ish (*). - Shared memory multi-threaded. - Natively compiled. I am being objective here, even though Go does not appeal to me. You can see what I wrote about that 10 years ago 😅: tmikov.blogspot.com/2015/02/you-do…. When ready, Static Hermes will satisfy all the above requirements, except for shared memory multi-threading. The JavaScript object model simply isn't really suitable for that. Brilliant attempts have been made: webkit.org/blog/7846/conc…, but IMO, the complexity is unjustifiably high. Static Hermes will eventually support github.com/tc39/proposal-…, or something like it, which is a useful and safe middle ground. *AFAIK, Go isn't completely safe because interfaces can be updated non-atomically, potentially causing a crash.

@acdlite Yeah, the code is basically line-for-line the same

I’m being told this is a genuine line-by-line port (most “ports” aren’t) and the perf gains are almost entirely attributable to parallelization, and if that’s true then that’s about as fair of a comparison you can make

This is exciting, but whenever you see perf stats attributed to rewriting in a new language (or framework etc), consider: if they had rewritten it in the exact same language it still would have been somewhat faster because they’d know how to do it less shitty the second time

@theo idk man, I had no problems falling asleep last night. Falling asleep at 10 PM, 1 AM, 3 AM, 3:30 AM, 5 AM, ...

I blame TypeScript

Several of you asked me why TypeScript chose Go instead of C#, and what that decision implies about Microsoft's commitment to C# and .NET. See #discussioncomment-12466988" target="_blank" rel="nofollow noopener">github.com/microsoft/type… by @ahejlsberg TL;DR nothing has changed. #dotnet #csharp

@jessfraz Elixir and Smalltalk were RIGHT THERE smh

everyone out here like "wHy NoT zIG" "WhY nOt RuSt" for rewriting typescript, as go has officially surpassed the "boring" chasm, blessing and a curse

@skydotcs "I wonder if the original author agrees" someone get this man a wikipedia

imagine writing TypeScript with your Go compiler and this guy shows up

The new TypeScript is *really* fast