Michigan TypeScriptYep. We got the Doom engine running purely in TypeScript types. Like. For real. We’ve prepared two more videos, one answering “why we did this” (storytime format) and another answering “how we did this” (technical deep-dive). What would you like to hear about for those?
If you’d like to contact us for any reason, please email doom@michigantypescript.com or reach out on the #doom channel on the MiTS Discord (link below)
If you'd like a version of this video without background music or a moving animation, you can find it here: youtu.be/s4UE_CUn2N0
Michigan TypeScript has never and will never have any sponsored content. All videos have always and will always have all possible ads or monetization turned off. If you wanna support what we do, the best thing you can do is take what you learn here back to your job and make software that puts smiles on your user’s faces. And if you REALLY like what we do, then you’ll love SquiggleConf (cross-language devtools conference, squiggleconf.com, CFP open now for this year's conf, September 18-19 2025 in Boston).
TypeScript types can run DOOMMichigan TypeScript2025-02-26 | Yep. We got the Doom engine running purely in TypeScript types. Like. For real. We’ve prepared two more videos, one answering “why we did this” (storytime format) and another answering “how we did this” (technical deep-dive). What would you like to hear about for those?
If you’d like to contact us for any reason, please email doom@michigantypescript.com or reach out on the #doom channel on the MiTS Discord (link below)
If you'd like a version of this video without background music or a moving animation, you can find it here: youtu.be/s4UE_CUn2N0
Michigan TypeScript has never and will never have any sponsored content. All videos have always and will always have all possible ads or monetization turned off. If you wanna support what we do, the best thing you can do is take what you learn here back to your job and make software that puts smiles on your user’s faces. And if you REALLY like what we do, then you’ll love SquiggleConf (cross-language devtools conference, squiggleconf.com, CFP open now for this year's conf, September 18-19 2025 in Boston).
For those asking about the shirt, you can get it here: https://shop.squiggle.toolsTypeScript is being ported to Go | interview with Anders HejlsbergMichigan TypeScript2025-03-11 | You're about to see concurrent 10x performance on your type checking with half the memory and much faster editor startup. The TypeScript team has been porting the project to Go for the past 8 months.
In this interview with Anders Hejlsberg, co-creator and lead architect of TypeScript, we tried to ask questions that would be valuable to library authors, power users, and compiler contributors.
If you have any questions, you should join the AMA on the TypeScript Community Discord 10 AM PDT | 5 PM UTC on March 13th.
00:00 in this episode... 02:23 Introducing Anders 03:14 codename Strada and Corsa 04:29 whose idea was Corsa? 05:20 regarding other attempts (e.g. stc by DongYoon Kang) 06:07 discussions within the team about performance and scalability 07:46 it started in August 2024 08:58 "we realized, we can get to 10x with this!" 09:36 what was the general feeling on the team? 10:31 unprecedented move to "eject" from being self-hosted 11:25 there may always be some parts written JavaScript 13:16 why not Rust? 15:05 rational for why it has to be a garbage collected language 15:37 re: Rust's constraints: borrow checker, cyclic data structures 16:29 adding it all up: Go makes a lot of sense 17:59 JavaScript has a lot more in common with Go than Rust 19:14 why not C#? 20:11 the current codebase is written in a functional style 21:26 Strada's extensive use of flag packing with TypeScript Enums 23:44 typescript-go's memory consumption is HALF (!!) (while also being 10 times faster) 24:37 has spending so much time writing Go had any influce on TypeScript? 26:31 JavaScript is a very strange language to write a compiler in in the first place 27:37 ensuring a smooth transition (in absence of a language spec) 28:33 the AST will not change 29:19 library authors will not have to maintain two versions of their types 30:13 all 20,000 conformance tests already run without crashing 30:46 what do you foresee being the toughest challenges ahead? 31:19 challenge: deterministic ordering of type union members in a multi-core environment 33:09 largest challenge is providing a modern API to the existing codebase 34:44 what about the cross-language connection points for the API? WebAssembly? Rust bindings? 35:22 strengthening the Language Server Protocol 36:53 how long will the existing codebase be maintained after typescript-go is GA? 37:35 typescript-go is expected to be ready to use by the end of 2025, if not much sooner 38:32 will the Go and TypeScript codebases be merged, or stay separate? 39:10 what will happen to existing PRs? 40:25 will type-aware tooling also get a 10x speed up? 42:02 how hard was it to add concurrency to the type checker? 42:30 the current codebase make heavy use of immutability and structural sharing 44:37 why shared memory concurrency is so important to this codebase (something Go is excellent at) 46:43 adding concurrency in typescript-go was like 10 lines of code (!!!) 47:58 but type checking is harder to make concurrent (and how they solved it) 50:45 looking forward to the _next_ dozen years 51:32 does this open the door to any features that previously would have been infeasible? 52:28 scalability and performance are the top needs in the community 52:42 re: language features, TypeScript will _always_ keep up with ECMA 53:04 implications for AI and agentic programming of a 10x-faster type checker 54:39 does typescript-go open the door to a pure TypeScript runtime? 57:12 what about important 3rd party contributors that don't want to write Go? 58:36 the transition from JavaScript to Go is actually pretty gentle (compared to Rust) 59:53 this is a very exciting next chapter 1:01:10 Jake Bailey from the TypeScript team will present on typescript-go at SquiggleConf
-------
Michigan TypeScript has never and will never have any sponsored content. All videos have always and will always have all possible ads or monetization turned off. If you wanna support what we do, the best thing you can do is take what you learn here back to your job and make software that puts smiles on your user’s faces. And if you REALLY like what we do, then you’ll love SquiggleConf (cross-language devtools conference, squiggleconf.com, CFP open now for this year's conf, September 18-19 2025 in Boston).
For those asking about the Doom shirt, you can get it here: https://shop.squiggle.toolsshowing TypeScripts creator DOOM | Anders Hejlsberg | TypeScript Showcase #11Michigan TypeScript2025-03-09 | Anders Hejlsberg is a technical fellow at Microsoft and the lead architect on the TypeScript project. Anders was a co-creator of the TypeScript language, as well as C#, and has done groundbreaking work on Delphi and Turbo Pascal. So imagine our excitement when the opportunity arose to show him the DOOM-in-TypeScript-types project!
This was part of a longer conversation we had with Anders about TypeScript topics that will be launching next week.
Michigan TypeScript has never and will never have any sponsored content. All videos have always and will always have all possible ads or monetization turned off. If you wanna support what we do, the best thing you can do is take what you learn here back to your job and make software that puts smiles on your user’s faces. And if you REALLY like what we do, then you’ll love SquiggleConf (cross-language devtools conference, squiggleconf.com, CFP open now for this year's conf, September 18-19 2025 in Boston).
For those asking about the Doom shirt, you can get it here: https://shop.squiggle.toolsthe hardest challenge in the whole project [bonus technical content]Michigan TypeScript2025-03-06 | While working on finishing the deep-dive videos about this project, I came across this "journal entry" that was recorded immediately after conquering the hardest individual programming challenge of my career, and certainly the hardest single challenge of this whole project. Of course with something like this, you never know how close you are to accomplishing the goal, but it turned out that this was basically the very last hurdle to overcome before completing the project.
If nothing else, perhaps this will give you some insight into what it was like to work on a project like this.
Thanks to Mark Erikson for encouraging me to capture this moment as it was fresh. Looking back, I would never have been able to explain this again, even a day later, haha.
-------
Michigan TypeScript has never and will never have any sponsored content. All videos have always and will always have all possible ads or monetization turned off. If you wanna support what we do, the best thing you can do is take what you learn here back to your job and make software that puts smiles on your user’s faces. And if you REALLY like what we do, then you’ll love SquiggleConf (cross-language devtools conference, squiggleconf.com, CFP open now for this year's conf, September 18-19 2025 in Boston).
For those asking about the Doom shirt, you can get it here: https://shop.squiggle.toolsWe started a devtools conference! Heres what we did wrong.Michigan TypeScript2025-02-25 | We’re very passionate about devtools around here - are you surprised!? :) We channeled that passion into SquiggleConf, a cross-language conference focused on devtools. The first edition of the conference happened back in October, so now that we’ve had time to reflect we thought it’d be fun to share some of the screw-ups. We did a lot right, but we also made plenty of mistakes. This isn’t a typical video you’ll find on this channel, but we thought it could still be a good temporary home while we get SquiggleConf’s own YouTube channel up and running.
00:00 we had a conference! 00:58 the call for papers 01:26 know what you're asking for 03:04 the CFP acceptance process takes a lot of time 04:08 be very clear about deadlines 04:39 ask for submitters to provide context 05:21 but not questions you can ask later 06:01 talk dry-run prerequisite 07:00 a conference is a business 08:19 speaker experience gateway 09:03 more stuff on the website 09:48 be more clear that there isn't paid speaking slots 10:48 sell the city experience more 12:03 copious travel information 12:37 sponsors 15:29 partnering with local meetups 16:51 having a team 17:18 Boston's only software conference 17:46 super active use of the Discord 18:49 personal aspirations 20:50 do everything in advance that you possibly can 21:10 TOP LEARNING: run of show 23:43 small logistics details 24:23 the hotel 25:15 surprise expenses 29:13 going overboard on vegan food 31:00 no catastrophe 31:41 cultural differences 32:45 audio / video equipment 37:18 what went well 38:06 MCs 38:35 vibes 39:15 volunteers 40:04 volunteers 40:34 sponsors view booths as work 41:17 finding appropriate sponsors 41:47 after-conference event 43:58 special speaker events 45:38 on having repeat speakers 46:07 SquiggleConf almost never happened 48:35 being a match as founders 50:05 repeating what worked
You can always find us on the SquiggleConf Discord: discord.squiggleconf.com (@joshuakgoldberg and @dimitropoulos)🚦 Signals 🚦 JavaScripts Stage 1 TC39 ProposalMichigan TypeScript2024-12-09 | Signals is a Stage 1 Proposal to the TC39. To develop a complicated user interface (UI), JavaScript application developers need to store, compute, invalidate, sync, and push state to the application's view layer in an efficient way. UIs commonly involve more than just managing simple values, but often involve rendering computed state which is dependent on a complex tree of other values or state that is also computed itself. The goal of Signals is to provide infrastructure for managing such application state so developers can focus on business logic rather than these repetitive details.
Welcome Chandler Prall back on the channel in this live talk, given May 7th 2024 in Ann Arbor, Michigan. Check Vena (what's demoed in this talk) as well as more of Chandler's open source work on his GitHub: github.com/chandlerprall.
00:00 in this episode... 01:56 about Chandler and this talk 03:20 what are Signals? here's some examples 07:07 let's build our own Signals 10:41 The TC39 Signals proposal 12:21 audience questions: who is this for? 15:19 how extending Signals would work 16:46 so then is useEffect actually a Signal? 18:26 why does this have to be a top-level class? 19:53 how Signals improves developer tools 20:32 Web Components: Benefits and Downsides 23:28 Web Components examples 26:09 about "slots" 28:18 Vena: Signaling Web Components 31:05 goals for Vena 32:25 how events work 34:25 context, state, and live reload 36:26 JSX 39:46 Demos!
Twitter: twitter.com/MiTypeScript BlueSky: https://bsky.app/profile/michigantypescript.com Mastodon: fosstodon.org/@MichiganTypeScript Threads: threads.net/@michigantypescript Instagram: instagram.com/michigantypescript TikTok: tiktok.com/@michigantypescript Discord: discord.michigantypescript.com GitHub: github.com/MichiganTypeScript SoundCloud: soundcloud.com/michigan-typescripteven JavaScript programmers dont want to write JavaScriptMichigan TypeScript2024-07-09 | ...dont use semver. calculate the version number. we have the technology.Michigan TypeScript2024-06-24 | Click the related video on this short to see the full video (as well as links to join the Discord). YouTube no longer allows links of any kind anywhere in Shorts (otherwise, we'd link it here just like the old days...).we already compile to JavaScript anywayMichigan TypeScript2024-06-18 | ...Inferred Type Predicates - TypeScript 5.5s top new featureMichigan TypeScript2024-06-12 | This has has been a top wishlist features for so many people for so many years. Dan tells the story of how he cracked it, then we do a deep dive on the code itself. Although this was a pretty technical conversation there ended up also being quite a lot of great conversation on staying motivated and thinking through all the aspects of the problem from side-effects to performance implications.
Dan Vanderkam is an independent software developer, formerly at Google and Sidewalk Labs. He is the author of numerous open source JavaScript/TypeScript libraries, including the dygraphs charting library, source-map-explorer, literate-ts, pg-to-ts and crosswalk. He is the author of "Effective TypeScript: 83 Specific Ways to Improve Your TypeScript" (O'Reilly 2024) and has spoken at numerous TS conferences. When he's not writing about TypeScript, Dan enjoys hiking, rock climbing and birding.
Also, Effective TypeScript is one of the most practical and useful books on TypeScript in existence. A lot of us at MiTS have a copy and you'll be seeing Dan again in the future to talk about it. Between now and then you can order a copy here: amzn.to/3UjPrsK.
00:00:00 in this episode 00:02:06 the Recurse Center (deciding to tackle this issue) 00:03:53 first issue: numeric literal separators in ES2021 00:07:36 rediscovering this old issue 00:08:28 explaining the fundamentals of the feature 00:13:43 the idea for the first approach to solving the issue 00:16:24 wrong assumptions about how the compiler handles inference 00:17:59 what is a "Flow Node" in the compiler 00:21:46 about the TypeScript AST Viewer 00:22:18 second attempt: using Flow Nodes 00:23:26 digging into the code for the actual implementation 00:28:03 what most people don't understand about how type predicates actually work 00:30:21 are MiTS viewers interested in blog post readings (WITH the author)? 00:31:33 looking deeper than a type predicate goes 00:33:23 working with TypeScript's exhaustive test suite 00:36:03 dealing with outlier falsey types (like empty string, NaN, etc.) 00:38:27 what about `[].filter(Boolean)` (array filter with the Boolean constructor) 00:39:14 type guards now flow between functions 00:40:35 sage-tier advice from Anders Hejlsberg 00:41:20 building the courage to submit the PR 00:43:59 a scary moment where it looked like the solution might not actually work 00:46:37 a solution to the setback after going for a walk 00:50:29 a totally unique approach within the TypeScript compiler codebase 00:53:12 the process for getting it reviewed and approved and merged 00:54:36 performance optimization work 00:56:42 playing around with the end result 00:57:24 playing with truthiness checks 00:59:15 revisiting: why you shouldn't use .filter(Boolean) 01:01:57 about teaching these concepts 01:02:52 how ts-reset handles filter(Boolean) 01:05:51 wrapping up 01:07:49 after it all: it turns out this could have been done years ago
If you’re using a compiler and build step, you aren’t writing the code your users are running in the browser. If you need to “build” your web application, writing JavaScript is a choice. ReScript’s syntax allows developers to write type-sound, expressive, and readable code that still compiles to performant JavaScript, without the need for additional runtime libraries like Immer, ts-pattern, or rambda. If you’ve been keeping an eye on tc39 proposals, ReScript has features that have been stuck in tc39 proposals for years: do expressions, pattern matching, the Pipe Operator, and Record & Tuple values.
Rob Meyer is a Staff Software Engineer at Autobooks, working on enabling small and medium businesses to get paid. He's been attempting to squash TypeErrors using functional programming since 2015. In his spare time, he likes to play games and collect O'Reilly books that won't be read.
00:00:00 in this episode 00:02:26 a tour of ReScript 00:08:44 we all compile to JavaScript anyway 00:10:09 criticisms of TypeScript 00:13:47 about ReScript 00:20:19 variants 00:24:26 nominal types 00:29:22 immutable by default 00:30:35 everything is an expression 00:32:16 JSX is built in 00:34:21 pattern matching (the best feature) 00:39:15 the pipeline operator (!!!) 00:41:11 what was the learning curve like for your team? 00:44:34 incrementally adoptable 00:46:26 how do you decide which things to convert first? 00:50:35 an alternative to throwing in promises (a Result type) 00:54:00 what's a raw? 00:55:51 any issues using NPM packages? 00:59:10 why is it so fast? (compared to TypeScript) 01:00:57 looking at the compiled output 01:01:51 how do tests look? 01:03:04 what's ReasonML as compared to ReScript? 01:04:18 what's the interop with TypeScript like? 01:08:42 how does this interact with other assets like CSS/images/etc 01:10:48 what about formatting (like prettier/biome/etc)
Twitter: twitter.com/MiTypeScript Mastodon: fosstodon.org/@MichiganTypeScript BlueSky: https://bsky.app/profile/michigantypescript.com Threads: threads.net/@michigantypescript Instagram: instagram.com/michigantypescript TikTok: tiktok.com/@michigantypescript Discord: discord.michigantypescript.com GitHub: github.com/MichiganTypeScript SoundCloud: soundcloud.com/michigan-typescriptRust is not a barrier for TypeScript dev contributionsMichigan TypeScript2024-03-22 | Click the related video on this short to see the full video (as well as links to join the Discord). YouTube no longer allows links of any kind anywhere in Shorts (otherwise, we'd link it here just like the old days...).backlash about exception handlingMichigan TypeScript2024-03-15 | ...evolving schemas over timeMichigan TypeScript2024-03-08 | Click the related video on this short to see the full video (as well as links to join the Discord). YouTube no longer allows links of any kind anywhere in Shorts (otherwise, we'd link it here just like the old days...).jQuery datepicker is the height of the artformMichigan TypeScript2024-03-06 | ...how sound is sound enough?Michigan TypeScript2024-02-16 | Click the related video on this short to see the full video (as well as links to join the Discord). YouTube no longer allows links of any kind anywhere in Shorts (otherwise, we'd link it here just like the old days...).how Andarist time-travel debugs the TypeScript compiler with ReplayMichigan TypeScript2024-02-15 | Andarist loves fixing bugs - that's how he became a maintainer of several popular JS OSS projects and a contributor to the TypeScript compiler. In this video we look at how he uses Replay to debug the TypeScript compiler while he's doing all his cutting-edge advanced TypeScript work.
*note:* This is (sortof) part 2 of a video with Mark (Erikson, of Replay.io) and Andarist. In Part 1 (youtu.be/jtQjov140-8) we got a quick overview of what Replay is and how it works.
00:00 in this episode 04:35 the idea to use Replay with the TypeScript playground 06:05 thousands of Replay recordings 10:06 committing a change to TypeScript for Replay 11:30 starting the first recording 13:16 on handling displayment for massive files 15:42 looking at a previous recording 18:02 debugging 21:19 the risk presented by side effects 24:04 Replay knows everything from all time 25:19 how it all works up in the cloud 27:27 the caching layer has a memory! 29:45 filtering by your test run 33:18 on putting breakpoints in TypeScript types 35:56 on rewriting the TypeScript compiler in Rust 39:31 use case: using two Replay recordings side-by-side 40:40 there's a lot more Replay can do in the future 43:00 what's the coolest thing you've found in the TypeScript codebase? 46:01 applying learnings to XState
-------
Andarist loves fixing bugs - that's how he became a maintainer of several popular JS OSS projects and a contributor to TypeScript.
After all, if our whole goal at MiTS is to provide resources for passionate TypeScript engineers.. running a meetup is a pretty common thing for such people to do, so it makes sense to talk about the technical side of these things.
It's mentioned in the video, but just to say it here again: yes, we understand that this is significantly more equipment than technical conferences with thousands of attendees (not exaggerating). It's a whole other story on how this equipment came to be in our hands (and other non MiTS stuff it's used for), but we'll save that for another day.
We made this video in the hope that you'll find something useful if you're running a meetup (or aspiring to). There are plenty of things mentioned in the video that don't cost any extra money to do (e.g. printing out the WiFi information with a big QR code, remembering to get a regional favorite drink, playing a board game with everyone afterwards, finding a cozy and calm place for people to go afterwards to hang out more if they want, inviting local companies to leave a small supply of stickers, etc.). And, on that note: if there are ideas you have _for us_ then we'd love to hear them!
00:00 this ain't your normal MiTS video 01:51 the audio rack 02:50 social weirdness recording meetup talks 05:36 looking at the back of the video rack 08:07 even power is redundant 09:09 the front of the video rack: ATEM Mini Extreme ISO and HyperDeck Studio 4k Pro 10:19 synching all the video inputs (and not running out of space) 11:31 oh yeah! the audio rack drawers 12:13 we play a quick board game every month! 13:05 using supersource from the ATEM during the show 15:20 the "just walked in" experience 17:01 it's important to think about safety 20:20 why we need an audience camera 21:30 on the podium 22:36 a disaster story 24:18 the backdrop 27:34 Vernors Ginger Soda! (local things are good) 28:25 this seems like extreme overkill.. 31:10 Michigan TypeScript doesn't have sponsors 31:45 wrapping up
00:00 in this episode 02:24 introductions 05:52 what is Replay? 08:31 a demo of Replay 16:29 it can step backwards! 17:47 it can jump to react handlers! 19:13 collaboration capabilities 21:08 inspecting React props on raw DOM nodes 24:33 how Replay works under the hood 29:05 primary use-cases for Replay 30:34 could this be used to capture user error logs?
_______
Mark Erikson is a Senior Front-End Engineer at Replay, and lives in southwest Ohio, USA. Mark is a Redux maintainer, creator of Redux Toolkit, and general keeper of the Redux docs. He tweets at @acemarke, and blogs at blog.isquaredsoftware.com/. He spends much of his time answering questions about React and Redux anywhere there's a comment box on the internet, and usually hangs out in the Reactiflux chat channels. Mark is also disturbed at the number of third-person references he has written in this bio.
0:00 what are distributive conditionals in TypeScript's type system? 1:32 factoring out DistributiveConditional 4:08 factoring out NonDistributiveConditional 6:25 conclusion 7:43 we're doing more of these! let us know what you want!
Twitter: twitter.com/MiTypeScript Mastodon: fosstodon.org/@MichiganTypeScript BlueSky: https://bsky.app/profile/michigantypescript.bsky.social Threads: threads.net/@michigantypescript Instagram: instagram.com/michigantypescript TikTok: tiktok.com/@michigantypescript Discord: discord.michigantypescript.com GitHub: github.com/MichiganTypeScript SoundCloud: soundcloud.com/michigan-typescriptwrite software, but without that sinking feelingMichigan TypeScript2024-02-05 | Click the related video on this short to see the full video (as well as links to join the Discord). YouTube no longer allows links of any kind anywhere in Shorts (otherwise, we'd link it here just like the old days...).the biggest mistake people make when dual bundling [part 4]Michigan TypeScript2024-02-03 | Click the related video on this short to see the full video (as well as links to join the Discord). YouTube no longer allows links of any kind anywhere in Shorts (otherwise, we'd link it here just like the old days...).the biggest mistake people make when dual bundling [part 3]Michigan TypeScript2024-02-01 | Click the related video on this short to see the full video (as well as links to join the Discord). YouTube no longer allows links of any kind anywhere in Shorts (otherwise, we'd link it here just like the old days...).the biggest mistake people make when dual bundling [part 2]Michigan TypeScript2024-01-30 | Click the related video on this short to see the full video (as well as links to join the Discord). YouTube no longer allows links of any kind anywhere in Shorts (otherwise, we'd link it here just like the old days...).the biggest mistake people make when dual bundling [part 1]Michigan TypeScript2024-01-29 | ...Glide Data Grid with Jason Smith | TypeScript Showcase #9Michigan TypeScript2024-01-22 | This canvas-based grid handles 100 million rows at 120fps all while keeping up with accessibility, flexible styling, supporting server side rendering, and having great TypeScript support. It even runs Doom! Check it out: grid.glideapps.com
00:00 in this episode 01:21 Introduction 03:16 how did it all begin? 05:49 a quick tour 07:14 are the feature requests mostly community driven? 08:52 IT RUNS DOOM!!! 12:23 using canvas is the "special sauce" 13:13 how are you measuring the grid's performance? 16:57 isn't canvas bad for accessibility? 23:44 cross-browser support 27:19 the main draw function 31:15 how did you learn about Safari's inner workings? 32:46 struggles with types 35:53 handling subpixel zooming 38:50 how does styling work? 40:49 supporting theming 42:04 what happens for theme variables you didn't think to expose? 46:43 where do you think this is going in the future? 48:14 server side rendering 51:43 demo: uneven rows 54:03 what conference would you like to visit? 56:24 question for the survey of TypeScript 59:39 closing thoughts re: doing hard things
So then when this topic came up in our theorycrafting video on T[number], we thought "who better to do a short theorycraft video on assertUnreachable than Ryan himself?!". So.. here you go! Enjoy!
0:00 what `assertUnreachable` does 0:41 where'd the idea come from? 1:29 the problem it solves 1:56 how `assertUnreachable` works 2:20 thinking about `noImplicitReturns` being in the mix 3:31 interesting subtleties 4:30 should unreachable code even be allowed? 6:02 other variations on `assertUnreachable` 7:20 variations on adding a message or not throwing
00:00 accessing an array's values as a type 00:50 problem 1: consumers can pass bad values 01:01 problem 2: typos in the cases aren't caught 01:12 problem 3: missing cases (a not "exhaustive" switch) 01:41 attempt 1: copy/pasta string literals 03:34 attempt 2: typeof 03:59 attempt 3: `as const` 04:35 attempt 4: direct access typeof union 05:27 attempt 5: moving the union to within the index access 06:02 attempt 6: indexing with `number` 06:18 why this solution works 06:44 reviewing all the things TypeScript now catches for us 08:01 what is `T`?
Roman (goes by "Function" online) works as a fullstack software engineer at a logistics company where he develops in-house applications for financial controlling, HR, or training purposes. He's also working on a handful of gaming and DJ related software projects in his spare time using TypeScript wherever he can, sometimes leading him to weird-typed places because of his preference of precise and derived types.
His current main FOSS endeavor is a web-based strategy multiplayer inspired by "Advance Wars By Web": github.com/WarsWorld/Warsworld
Twitter: twitter.com/MiTypeScript Mastodon: fosstodon.org/@MichiganTypeScript BlueSky: https://bsky.app/profile/michigantypescript.bsky.social Threads: threads.net/@michigantypescript Instagram: instagram.com/michigantypescript TikTok: tiktok.com/@michigantypescript Discord: discord.michigantypescript.com GitHub: github.com/MichiganTypeScript SoundCloud: soundcloud.com/michigan-typescriptdoes your language silently add code?Michigan TypeScript2023-12-28 | Click the related video on this short to see the full video (as well as links to join the Discord). YouTube no longer allows links of any kind anywhere in Shorts (otherwise, we'd link it here just like the old days...).what are type only imports?Michigan TypeScript2023-12-27 | Click the related video on this short to see the full video (as well as links to join the Discord). YouTube no longer allows links of any kind anywhere in Shorts (otherwise, we'd link it here just like the old days...).is it christmas?Michigan TypeScript2023-12-24 | Click the related video on this short to see the full video (as well as links to join the Discord). YouTube no longer allows links of any kind anywhere in Shorts (otherwise, we'd link it here just like the old days...).Rust is much faster than TSCMichigan TypeScript2023-12-21 | Click the related video on this short to see the full video (as well as links to join the Discord). YouTube no longer allows links of any kind anywhere in Shorts (otherwise, we'd link it here just like the old days...).BuT tHaTs NoT wHaT thAt WorD MeAnSMichigan TypeScript2023-12-19 | ...Apollo Client with Lenz Weber-Tronic and Jerel Miller | TypeScript Showcase #8Michigan TypeScript2023-12-13 | Apollo is well known for having great tools (and documentation) and in this talk it is really clear how much care and attention they put into their products. Library authors have so much to learn and gather from this team, and we are very lucky to have them candidly sharing what they've learned along the way. Apollo Client is a GraphQL client that has so much history and complexity behind it yet the team manages to stay current new challenges like React Suspense. It's really incredible. Check it out!
00:00:00 in this episode 00:02:11 introductions 00:04:16 what is Apollo Client? 00:06:36 about optimistic updates? 00:08:00 what kinds of developers want Apollo Client? 00:09:19 what about Relay? 00:10:46 getting a look at using the library? 00:12:47 Apollo Client gives direct access to the query AST 00:20:48 does GraphQL introspection mean the client doesn't need the schema? 00:22:32 difficulties resulting from not knowing type inheritance ahead of time 00:24:25 key design choices (good _and_ bad) 00:27:16 state of affirs re: JSDoc, TSDoc TypeDoc, and more! 00:31:17 how do you identify and respond to user needs? 00:37:06 on: staying on top of GitHub issues and pull requests 00:41:04 feedback from users about repo metrics 00:42:42 how do you manage the open source workload? 00:44:03 implementing React Suspense 00:51:09 dealing with shifts in community preference 00:58:05 testing the types 01:00:22 tests in user-land 01:05:48 a novel approach to testing the library 01:15:09 what's next for Apollo Client? 01:20:22 question for the next guest 01:20:56 State of TypeScript survey question 01:22:46 wrapping up
_______
Lenz Weber-Tronic works as Senior Staff Software Engineer at Apollo GraphQL, where he is part of the team maintaining the Apollo TypeScript Client. He is also a maintainer of Redux Toolkit and if he’s not currently trying to summon elder gods with weird TypeScript incantations he can usually be found on StackOverflow answering questions on Apollo and Redux usage or opening random PRs on GitHub.
Jerel is a Principal Software Engineer at Apollo GraphQL maintaining the Apollo TypeScript Client living in beautiful Colorado, USA. He loves the art of software development and finding creative solutions to challenging problems.
Twitter: twitter.com/MiTypeScript Mastodon: fosstodon.org/@MichiganTypeScript BlueSky: https://bsky.app/profile/michigantypescript.bsky.social Threads: threads.net/@michigantypescript Instagram: instagram.com/michigantypescript TikTok: tiktok.com/@michigantypescript Discord: discord.michigantypescript.com GitHub: github.com/MichiganTypeScript SoundCloud: soundcloud.com/michigan-typescriptwhat are named imports?Michigan TypeScript2023-12-12 | Click the related video on this short to see the full video (as well as links to join the Discord). YouTube no longer allows links of any kind anywhere in Shorts (otherwise, we'd link it here just like the old days...).Biome does it allMichigan TypeScript2023-12-11 | Click the related video on this short to see the full video (as well as links to join the Discord). YouTube no longer allows links of any kind anywhere in Shorts (otherwise, we'd link it here just like the old days...).effection with Charles Lowell | TypeScript Showcase #7Michigan TypeScript2023-12-08 | Effection gives you some core primitives to write concurrent code. It's got some super well-thought out core primitives that enable you to do some pretty amazing things! In this showcase we'll see lots of code but also talk lots of theory on how all this stuff works. Really hope you enjoy this one! Let us know what you think.
00:00 in this episode 02:39 what is effection 05:12 concurrency vs parallelism 06:24 what are the guarantees of structed concurrency? 10:28 starting to build up the demo 11:44 shout out to Deno 14:10 effection operations always return 16:03 what yield* does 19:29 inspirations from Rust and Haskell 20:47 on exceptions and error handling 22:48 areas for improvement in TypeScript 24:19 would be nice to have overloaded exception handlers like Java 26:43 building up the demo 34:53 extracting all the complexity 41:37 what it's like to type generics 45:42 testing the types 47:41 runtime testing story 51:27 example: grabbing playwright console messages 53:03 what is a signal? 54:12 how to get things in-and-out of delimited continuations 55:12 any weird edge-cases 57:59 getting "buy-in" from colleagues 1:03:33 comparing/contrasting a promise gotcha 1:09:03 what's the effection equivalent of awaiting a promise? 1:11:39 effection has a very small surface area 1:12:03 API surface area for affection is like 5 functions 1:13:12 using an AbortController 1:14:34 what does the future hold for the effection library? 1:16:33 calculation provenance (!!) 1:18:11 questions for the "State of TypeScript" report 1:20:46 a question to pass to the next guest 1:22:23 demo: file watcher 1:27:31 thoughts on the "using" keyword and Disposables _______
More than 25 years ago, Charles torched a promising career in biochemistry and joined the dot-com revolution. After coding daily on systems big and small, he founded Frontside in 2005 based on the belief that good software development patterns are universal. Charles currently researches testing platforms and structured concurrency to power up every developer’s daily coding life.
Eric Bower is a software engineer working out of Ann Arbor, Michigan. When he's not running/longboarding/building keyboards/spending time with family, he likes to push the boundaries of TypeScript, particularly when it comes to utilizing generators. He's worked on redux-saga and is the creator of starfx. You might know him for his project neovimcraft.com, or maybe you've seen his blog (https://bower.sh ) come up on Hacker News. Check out his GitHub (github.com/neurosnap ) to see more of his open-source projects. _______
Twitter: twitter.com/MiTypeScript Mastodon: fosstodon.org/@MichiganTypeScript Threads: threads.net/@michigantypescript Instagram: instagram.com/michigantypescript TikTok: tiktok.com/@michigantypescript Discord: discord.michigantypescript.comyou need a type checker to dual package safely [part 2]Michigan TypeScript2023-11-29 | Click the related video on this short to see the full video (as well as links to join the Discord). YouTube no longer allows links of any kind anywhere in Shorts (otherwise, we'd link it here just like the old days...).how the redux maintainers metMichigan TypeScript2023-11-28 | Click the related video on this short to see the full video (as well as links to join the Discord). YouTube no longer allows links of any kind anywhere in Shorts (otherwise, we'd link it here just like the old days...).never thought wed have to bleep something out. lol.Michigan TypeScript2023-11-27 | Click the related video on this short to see the full video (as well as links to join the Discord). YouTube no longer allows links of any kind anywhere in Shorts (otherwise, we'd link it here just like the old days...).can you use a type only top import with an inline type import?Michigan TypeScript2023-11-22 | Click the related video on this short to see the full video (as well as links to join the Discord). YouTube no longer allows links of any kind anywhere in Shorts (otherwise, we'd link it here just like the old days...).Rices Theorem and the Halting ProblemMichigan TypeScript2023-11-21 | Click the related video on this short to see the full video (as well as links to join the Discord). YouTube no longer allows links of any kind anywhere in Shorts (otherwise, we'd link it here just like the old days...).Redux, RTK-Query, Reselect with Lenz Weber-Tronic and Mark Erikson | TypeScript Showcase #6Michigan TypeScript2023-11-17 | If you're a library author, this is the showcase of your dreams! It's quite a treat to have two authors with so much experience to come and share their experiences. We cover quite a lot of territory in just an hour and a half. Enjoy!
00:00:00 in this episode 00:02:23 introductions 00:03:15 where does the story begin? 00:05:18 the birth of redux-toolkit 00:06:07 the "redux brand" 00:10:12 redux-toolkit hits 1.0 00:11:46 tackling async actions 00:12:25 a demo of "legacy" redux 00:16:31 about action creators 00:19:25 the most complex types in the codebase 00:24:14 "application TypeScript" vs "library TypeScript" 00:27:32 the beginnings of RTK-query 00:28:21 handling thunks 00:33:18 enter "the query libraries" 00:36:21 introducing hooks 00:37:43 the compliance reason for redux-toolkit not being separate 00:38:47 was rtk-query named after react-query? 00:40:34 demo: creating rtk-query from scratch 00:43:47 exploring createApi 00:50:03 incredible type inferencing via import path 00:56:09 UnionToIntersection in the wild! 00:59:15 discussion on reselect 01:10:13 the desire for TypeScript debugging tools 01:11:24 TypeScript type performance benchmarking 01:13:49 the saga of improving performance 01:19:07 arethetypeswrong 01:20:46 Andrew Branch has done an amazing job 01:21:49 running code examples in docs! 01:23:48 strategies for injecting code in markdown 01:28:33 wrapping up
_______
Lenz Weber-Tronic works as Senior Staff Software Engineer at Apollo GraphQL, where he is part of the team maintaining the Apollo TypeScript Client. He is also a maintainer of Redux Toolkit and if he’s not currently trying to summon elder gods with weird TypeScript incantations he can usually be found on StackOverflow answering questions on Apollo and Redux usage or opening random PRs on GitHub.
Mark Erikson is a Senior Front-End Engineer at Replay, and lives in southwest Ohio, USA. Mark is a Redux maintainer, creator of Redux Toolkit, and general keeper of the Redux docs. He tweets at @acemarke, and blogs at blog.isquaredsoftware.com/. He spends much of his time answering questions about React and Redux anywhere there's a comment box on the internet, and usually hangs out in the Reactiflux chat channels. Mark is also disturbed at the number of third-person references he has written in this bio.
Eric Bower is a software engineer working out of Ann Arbor, Michigan. When he's not running/longboarding/building keyboards/spending time with family, he likes to push the boundaries of TypeScript, particularly when it comes to utilizing generators. He's worked on redux-saga and is the creator of saga-query. You might know him for his project neovimcraft.com, or maybe you've seen his blog (https://bower.sh ) come up on Hacker News. Check out his GitHub (github.com/neurosnap ) to see more of his open-source projects. _______
This video was recorded on October 3rd 2023 at a Michigan TypeScript in-person event (in Ann Arbor). There were 13 total lightning talks given that night on various recent updates in TypeScript, so if you hear a speaker referencing another talk: that's why! Check out the Release Report playlist on YouTube to see the rest :).