Syntax Snack Pack Issue #29: We don’t need to “rustify” JS... and 50 different React Hooks for your next project

You are viewing the Newsletter Archive. Published Wednesday Sep 25, 2024
← Back to all issues

A Tasty Treats NEWSLETTER for Web Developers

Issue #29:

An explainer for web development using only vanilla techniques
"Generated source code should be committed" 🔥
And most importantly, what does Taylor Otwell really think about the Lamborghini memes?

extra fun stuff

Oops we dropped something... really sweet swag 🛹
Come hang out with us in SF next month, RSVP here

The React 19 Cheat Sheet

CJ'S find

All the new things you can do in React 19 with examples!

scriptkavi/hooks

wes picked this one for you

A collection of 50 different React Hooks for your next project - some really handy ones including Long Press, Geolocation, History State and Copy to Clipboard.

Plain Vanilla

HAND-SELECTED BY CJ

An explainer for doing web development using only vanilla techniques. No tools, no frameworks — just HTML, CSS, and JavaScript.

All Hail The Algorithm

Some good stuff™ we posted this week

The Feed

New episodes 3×/week + YouTube!

You Need These 30 Apps - PART 2

Syntax Assistant Desktop App

Taylor Otwell's opinions on PHP, React, Laravel and Lamborghini Memes

Is Cursor AI the VS Code Killer?

SHAMELESS PLUG

[BLOG]

Improve Web Performance by Optimizing JavaScript Bundle Sizes

Nobody likes slow front end response – not you, your users, or search engines. Learn how to get ahead of bloated JavaScript bundles and improve your web performance in this blog.

READ THE BLOG

Dmitrii Kovanikov

@ChShersh

My hottest tech take: generated source code should be committed.

It happened to me so many times when the code generation logic was changed, a bug was introduced and there were no git diff to even compare with the old versions.

11:36 PM • Sep 13, 2024

Retweets

1329

Likes

Read 155 replies

Generated source code should be committed

gingerBill

@TheGingerBill

"Cold" take: HTML5 being pushed as the "Flash replacement" made things worse in general, except for the "performance" aspects.

Flash was what people wanted when they were designing "multimedia" applications on the web. HTML5 was not what they wanted, and we all suffered for it.

10:51 AM • Sep 17, 2024

Retweets

371

Likes

Read 28 replies

HTML5 was not the flash replacement we were promised

daniel roe 🇺🇦

@danielcroe

overall, in the open-source world, my money's on JS and future adaptations that allow it to compile to native code.

for certain specialised use cases, I think rust and similar languages can be perfect.

... but we don't need to 'rustify' js.

http://roe.dev/ama

#ama