A Tasty Treats Newsletter
for Web Developers.

ISSUE #16:

Did we get it wrong - was Flow better than TypeScript?? A little design inspiration, bc we all need a little help sometimes. Some Lofi beats to code to and other delicious snacks.

COMMUNITY QUESTION

Last issue's question was submitted by Tanner Hoisington, who asked about the trade-offs of using TypeScript for projects. Check out Scott's response video if you missed it.

SUBMIT YOUR QUESTION

anything goes!

🍬 Lofi Beats

Combine various lofi beat styles with noise generators to create unique ambient sounds to work to.

🍬 Mobbin

Need some Web Design Inspiration? Seems like half these “inspiration” websites are just huge images with Inter font on top. This site has some great categories for everything from marketing landing pages to application design.

🍬 Kotekan

Bun + React Server Components? Buntime? An interesting take on a new React framework.

Since Bun natively supports JSX and TypeScript, they are able to do the entire server part without a bundler.

TASTERS

👀 a sneak peek into upcoming episodes

#749 Fri, March 29:

Coding Shopify with Anne and Trudy of Design Packs

#750 Mon, April 1:

New CSS and JavaScript You should be using

#751 Wed, April 3:

UI Components: ShadCN, Tailwind UI, Headless, React Aria, Radix UI

🔥 ESM vs CJS is a waste of time

Jarred Sumner

@jarredsumner

@jullerino my hot take here is 

ESM vs CJS is a waste of everyone’s time, “moving forward” is a distraction. The users of your app/service don’t care about the JavaScript module format your code is written in.

Julius

@jullerino

To all the folks in the comments complaining about going ESM only. The ecosystem is never going to move forward if there’s no incentive to update your codebase from legacy code. 🌶️More libs should drop CJS support https://twitter.com/kettanaito/status/1769338363364946346

6:55 PM • Mar 17, 2024

Retweets

Likes

Read 2 replies

🔥 Wait, was Flow better than TypeScript? Did we get it wrong?

Dan Abramov - React Core Team - details how a new feature in Flow allows you to restrict the type of children that are rendered as a component children

dan 2

@dan_abramov2

it’s a shame flow has completely fallen off the open source radar. this feature is huge for design systems (eg <Select> can restrict children type to <Option> or anything that *eventually* renders <Option>). but with flow not being competitive, TS has no incentive to follow https://twitter.com/haroenv/status/1765650599528333612

SAN FRANCISCO MEETUP