Ben Heidemann (@bcheidemann) header
Ben Heidemann (@bcheidemann) profile picture

šŸ¦€ (not affiliated with the rust foundation)

Joined October 2013
Photo by Ben Heidemann (@bcheidemann)Photo by Ben Heidemann (@bcheidemann)Photo by Ben Heidemann (@bcheidemann)Photo by Ben Heidemann (@bcheidemann)Photo by Ben Heidemann (@bcheidemann)Photo by Ben Heidemann (@bcheidemann)Photo by Ben Heidemann (@bcheidemann)Photo by Ben Heidemann (@bcheidemann)Photo by Ben Heidemann (@bcheidemann)Photo by Ben Heidemann (@bcheidemann)
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.
Both Node 20 and Node 22 can now import ESM from CJS with the flag --experimental-require-module. The ecosystem is healing. Time to go all-in on ESM.
1
81
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.
Over 4 years, 151 releases, and 4k commits later, the stabilization of the Deno Standard Library is finally complete šŸŽ‰ļø There's probably something in this closely audited library that you can use today. And no, you don't need to use Deno. šŸ§µļø
12
ā€œ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.
startups do not pivot enough it's mind blowing to me how comfortable people are staying in a no growth zone for so long it's not like they don't ship anything - they just keep adding features for people at the bottom of the funnel instead of the top
20
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…
124
1,266
206
10,699
864,923
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
13
37
3
545
108,513
Very likely going to use this for my next big project šŸ˜
SolidStart is finally here. This has been a giant 3 year effort. So thankful to have everyone that has contributed. I never wanted to make a metaframework but details do matter. And I'm proud of what we've accomplished.
4
97
The React compiler is pretty cool. @jherr compared it to optimising compilers for native code. I think he’s right, but there’s two important differences: 1) We don’t need this for peek performance (@solid_js) 2) On the web, size matters (React compiler adds a lot of extra code)
1
1
167
On the second point, I am aware that the React team are claiming the compiler actually reduced the time to load and code size. I have to assume this is for an already heavily optimised codebase like Instagram, because all the example I’ve seen generate significantly more code šŸ¤”
1
104
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…
35
MIT linguist: Do LLM understand language? | Edward Gibson and Lex Fridman youtu.be/rHAyCMbTZms?si=IYzc… via @YouTube
1
68
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?
1
33
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.
29
Is there an equivalent to the Turing test for @udiomusic…? If so, it’s passed with flying colours.
37
Hype!
This Post is from an account that no longer exists. Learn more
96
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…
1
1
149
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…
1
29