t. nguyen

@tnsicdr.bsky.social

frontend developer of the javascripty kind my views, words, and opinions represent me and only me and no one else

the most realistic scene in Jurassic Park is when two scientists make a questionable decision — traveling to an undisclosed location with a strange man — on the promise of three years of modest funding

My normal gas station was under renovation and I ended up going to a bp station to refuel- and it was weird… I’m used to the green nozzle being the diesel one elsewhere

I think I need to push back more on he concept of mobile when designs come back- and focus on having designers consider the whole picture- because on a desktop, in a small width viewport, horizontal scroll is clunky without a trackpad

PHP and Node.js are NOT rivals. They are partners. Together, they can change the game. Join us for a webinar that bridges the gap. "Node loves PHP: Reuniting Web’s Power Duo for the Microservices Era" is happening on June 4, 2025, at 05:00 PM.

Bild

Prepping my Death of the Browser talk for ‪@futurefrontend.bsky.social‬ in Helsinki next week. It's never the same talk twice! This one focuses more on what web devs can do to lean into (or out of) agentic and LLM use. Can't wait to sauna <3

kind of want to write up about this concept of “infinite scaling” (mentioned in github.com/facebook/rea...) sometime but not sure if it’s gonna sound too pretentious. it’s an interesting property i don’t often see discussed

Chrome 136+ ships a new V8 version that supports a "compile hint", which makes V8 parse and compile all functions in that file eagerly. Great for entry points – where you know all functions will very likely be used. Less so as 'one weird trick to make all your JS faster'.

In our experiment with popular web pages, 17 out of 20 showed improvements, and the average foreground parse and compile times reduction was 630 ms.

You can trigger eager compilation for the whole file by inserting the magic comment
```
//# allFunctionsCalledOnLoad
```
at the top of the file.

This feature should be used sparingly though - compiling too much will consume time and memory!

If you write code to make websites (HTML, CSS, JS, Web API, Media) and you get frustrated trying to wrangle your code to work in Safari, which bugs are blocking you? Which existing features would you most like to see improved? If you got a chance to order priorities which effort would you put first?

This deepseek situation demonstrates the underwhelming, wasteful output of the western tech industry perfectly. It’s all built for making billionaires richer and that’s why it’s burning you out.