So⦠what happens to turbopack? š¤
Announcing Rspack 1.0 - the next generation JavaScript bundler written in Rust, webpack compatible, 10x faster.
Check out the release blog for more details:
rspack.dev/blog/announcing-1ā¦
About š damn š time š
Even if Node remains dominant, Deno and Bun have done amazing work to push the ecosystem forward. A perfect case study for why diversity is essential in driving progress.
This deserves more attention. A lot hand coded helpers, or utility libraries can be replaced by std/*. Benefits are itās all maintained by one trusted team, itās well designed, and it supports multiple runtimes, package managers and web standard APIs.
āAdding features for people at the bottom of the funnel [vs] those at the topā
The importance of considering this when building new features canāt be understated.
Ben Heidemann retweeted
I made an HTML/DOM viewer you can paste into your console to view or debug any website in 3D. Choose from random/gradient/clear colors or whether layers have sides.
You can save it as a bookmarklet so it's 1 click away. It's just a tiny IIFE JS function.
gist.github.com/OrionReed/4cā¦
Ben Heidemann retweeted
thereās a lot to be learned here
nextjs has the unique option of solving problems via infra since itās designed to run on vercel
so when they wanted to build a similar feature they invented PPR and obsessed over delivering everything over a single streamed http response - something you need highly specialized infra for
frameworks like astro donāt have this ability - they need to make sure their features work everywhere. and to work everywhere your guiding star has to be simplicity (not easy)
additionally thereās good judgement recognizing at the end of the day this is a small feature - not worth turning the world over for
the funny outcome here is it turns out the simple approach also ends up being more performant
this isnāt surprising! complicated infra with unnecessary network hops has very unpredictable performance
itās a good lesson on realizing how easy it is to assume because something is more complicated it must also be better
good job astro team
gotta go fast

ALT Performance To test the viability of this idea we built server-islands.com. This demo is inspired by the Next.js Partial Prerendering demo, reskinned to suit Astroās personality. Server Islands has a lot in common with Partial Prerendering (PPR), especially in its goal of allowing increased cacheability of pages. Metrics partialprerendering.com server-islands.com Time To First Byte 0.838s 0.766s First Contentful Paint 1.740s 1.251s Largest Contentful Paint 1.740s 1.405s Total Blocking Time 0.093s 0.018s Source WebPageTest WebPageTest
If youāre not listening to this podcast, you should be š
ICYMI: In the most recent OTMT podcast episode, @jaffathecake and I talk about putting React in the browser.
While thatās good clickbait, the episode is about about past and present platform proposals that aim to help frameworks with managing the DOM.
offthemainthread.tech/episodā¦
MIT linguist: Do LLM understand language? | Edward Gibson and Lex Fridman youtu.be/rHAyCMbTZms?si=IYzc⦠via @YouTube
2/3 - Claude Prompt
There are 3 doors. Behind door number 1 is a car. I know that there is a car behind door number 1, so I choose door number 1. Monty Hall opens door number 3. Should I switch my choice?
3/3 Claude Response
In this scenario, you should not switch your choice. Here's why:
The Monty Hall problem relies on the host knowing what's behind the doors and always revealing a goat (or in this case, a door without the car). The probability of winning increases for the contestant if they switch doors after the host reveals a goat because the host's action provides additional information.
However, in your scenario, you state that you know the car is behind door number 1, and you've chosen that door. Monty Hall opening door number 3 doesn't give you any new information or change the probability of the car being behind door number 1.
If you're certain the car is behind door 1, and that's the door you initially chose, then switching would actually guarantee that you lose the car.
The Monty Hall problem only works when you don't know which door the car is behind, and the host uses their knowledge to reveal a goat. Since those conditions aren't met in your scenario, the best strategy is to stick with your original choice of door number 1.
Is there an equivalent to the Turing test for @udiomusicā¦? If so, itās passed with flying colours.
Now that the ES decorators and ES decorator metadata proposals have reached stage 3 in the TC39 process, @typescript has added support. Unfortunately itās not compatible with legacy decorators, and doesnāt support type reflectionā¦
Should this rule be applied to legacy features which have seen mass adoption? Many popular frameworks, such as @angular and @nestframework, are currently stuck on this legacy decorators, with no path to adopt the standardised syntax, other than breaking changes to their APIsā¦










