It's that time again. Here are my annual goals for the 2026 year ahead and look back at this past piece of crap year. As usual, I welcome your thoughts. Happy New Year, everyone!
docs.google.com/document/d/1...
It's that time again. Here are my annual goals for the 2026 year ahead and look back at this past piece of crap year. As usual, I welcome your thoughts. Happy New Year, everyone!
docs.google.com/document/d/1...
What can I say? This is my goal every time.
I'll get you next time, @marktechson.com!!! Next tiiiiiiiime!!!! LOL
Airlines should be required to give you points or credits for every minute you have a delay with every flight.
T-1 until the first in-person ViteConf! π
And we can't wait to hear from @thepunderwoman.com about @angular.dev and @vite.dev, as well as a tool helping to improve AI Code π
Google is cooking!
PS: We have to get back to the clown and the Ferengi
Catch the free live stream on viteconf.amsterdam β¨
Screenshot of Jessica in her talk with a Skeletor gif captioned with "(laughs in evil)".
Thanks for having me!
A huge shoutout to our amazing speakers for sharing their knowledge and inspiring talks: @ryansolid.bsky.social, @kentcdodds.com, @thepunderwoman.com, @lydiahallie.com, @thealexlichter.com, @victorsavkin.bsky.social,
@ryansolid.bsky.social, @phenomnomnomin.al, @wordman.dev, and Luca Mezzalira πππ
Does anyone have any suggestions for trying to use element.getAnimations() or getComputedStyles while there's another action spamming recomputes on the page? They return empty in this case, even when behind a requestAnimationFrame.
I sat down with @joshuakgoldberg.com for the Software Engineering Daily (@softwaredaily.bsky.social) podcast. It was a fun time! You can listen to it here: softwareengineeringdaily.com/2025/09/11/a...
Our panelists are:
β @evanyou.me - Creator of Vite
β @biilmann.blog - CEO at Netlify
β @ryansolid.bsky.social - Creator of SolidJS (remote)
β @tannerlinsley.com - Owner at TanStack
β @thepunderwoman.com - Angular Team
Hosted by @sarah11918.rainsberger.ca & @thealexlichter.com!
Angular repo summary, 1238 open issues, 123 open pull requests, 24 discussions, 474 releases
Appreciation post for @thepunderwoman.com and @jeanmeche.com β¨ thank you for relentlessly working through our issues backlog, down to 1.2k from 1.5k over the past month ππΌ
Who needs a gym when you can just carry heavy boxes several blocks to DHL.
Yeah, absolutely, and I know that's frustrating to not know and not have any visibility other than our comments responding that it's breaking or needs a migration.
Sometimes we don't even know how breaking a change is at first. Many times we do, but even then it might be nuanced. Sometimes we didn't think it was breaking, land it, then find out it broke a ton, and have to roll it back. But yeah, otherwise I agree indicators would be nice.
We do our best to communicate our reasoning, but we get some people who are very upset. We see the passion. It's not easy to say no to someone. Just know there are real people on the other end.
The point I'm making here is that if a PR is closed, it's not because it's personal. It's also not because it's not a valuable fix. It's also not because "We just don't want to improve X, Y, or Z". We always do. We just sometimes can't, and it may not be immediately clear why to the contributor.
Yeah, exactly the kind of thing I mean. Additionally, we WANT to land contributor PRs. We're thrilled people are contributing. We also totally recognize the passion people have for the right solution. We wish it was always as easy as approve and merge.
We get the occasional contributor that gets upset when their issue / PR is closed, and I really wish we could show them the details of how hard it would be to land their change. We're truly not rejecting it for no reason.
When open source projects reject a PR, we're not doing it out of animus. Many times people create PRs with valuable changes, and while correct, would break so many people that we can't land it without a massive effort. We can't always commit to that. A lot of factors go into these decisions.
Wonderful! Always great to hear! β₯οΈ
Pshhh... But that requires effort... π
This is also my hunch. I don't think it causes reflow. What's strange is it will return an empty array if something else has caused a recalculation of styles. It feels somewhat unsafe to use because of that.
Does anyone know if `element.getAnimations()` causes a reflow, like getComputedStyles does?
I was in Paris for a long weekend between Friday and Monday. In that time, I walked 82,788 steps for a total of 58.53 km / 36.37 miles. My feet still hurt, but it was worth it.
β‘ Speaker highlight: Jessica Janiuk, Staff Engineer @angular.dev
Angular lived through a renaissance recently
With new features and improved DX but also betting on Vite & testing via Vitest
But is this the end? No!
@thepunderwoman.com will tell us about Angularβs Vite future.
viteconf.amsterdam
The only way you can get that is at a code jam.
Very important for TDD. That's how you properly do red green testing.
For those that are trying to learn more advanced JavaScript, currying is when you take a function and then serve it with a creamy sauce and some spices typically with meat, fish or vegetables. Hope this helps!
I went an entire day not noticing I had two different shoes on. Same type of shoe, but different colors. I only discovered it when I took them off when getting home. I'm not sure whether to be embarrassed or impressed.
I bet he got a lot of $$$.