TypeScript, Branded Types, Streaming vs Polling + More

Show Notes

00:00 Welcome to Syntax!
00:50 Catching up.
02:56 What are the limitations of SvelteKit?
06:41 Svelte 5 updates.
07:53 Branded types in TypeScript.
11:56 Queue applications and a ‘poor man’s queue’.
17:20 The real value of a functional QA team.
21:34 Invoker commands.
26:29 Growing security and permissions concerns.
33:03 Stripe vs PayPal in 2024.
38:24 Christmas gift guide.
38:39 Websockets vs streams vs polling.
41:04 Storing access and refresh tokens in a cookie.
45:41 Shipping with TypeScript errors.
49:34 Sick Picks + Shameless Plugs.

------------------------------------------------------------------------------
Hit us up on Socials!

#webdevelopment #webdeveloper #javascript

[gyros]

Was listening you on podcasts apps usually. Nice to watch you now, guys!

[everythingisfine]

My company is locked into some pretty poorly typed 3rd party libraries. Contractually we have to use. So needing to cast types is a necessity. It's a computer scientist purest vs business time is money situation. The business always wins

[fille.imgnry]

So now with Invokers, html WILL become the most popular ”programming language” 😅

[Lemmy]

I created my Branded types by using the intersaction & with an object with a property of type never and i don't have to do any crazy stuff to make it works with prmitives

type Longitude = number & { __whatever?: never }

const x: Longitude = 123

I created a utility type called "FromType<T>" that does it and instead of using a normal property i used a unique symbol to avoid naming clashes

declare const derivedTypeSymbol: unique symbol;

export type FromType<T> = T & { [derivedTypeSymbol]?: never };

[Danielo]

Those who don't understand the value of branded (AKA nominal types) are just worse developers, period.