Overly opinionated software developer on the Angular team at Google. Web development is hard, so I build tooling that makes it easier. I love forcing web tools to do things they were never supposed to do.
All but the last boss down. Only one attempt on him so far and got flattened, but it was a run which got somewhat screwed over by the party getting lost in the city event, so we were significantly underleveled.
Feels like a cool boss though, looking forward to future attempts.
Although, I did lead most of the Fulghor run and had pretty good routing if I do say so myself.
We even successfully completed the rot forest despite that being my first time seeing that event. Next time I'd love to prioritize it more and see how many bosses we can take down.
I was about to say I've found #Nightreign surprisingly easy, even queuing with randos. Beaten the first four bosses so far, most first try, and it doesn't feel like we got particularly lucky or were particularly skilled.
Then I had three absolutely terrible runs in a row, so 🤷.
It's bad for privacy, it needlessly excludes those without phones, it's slower to enter, it causes a notification I don't want, and it clutters my messages.
It quite literally provides *negative* value and makes the entire experience worse.
Just add a skip button! That's all it takes.
Dear every point of sale developer: There is no need to ask for a phone number when I'm literally standing in the store!
Managed to put a little time into #EldenRing #Nightreign, initial impressions are generally good. Actually managed to get chicken dinner on the first run, even playing with two randos. #Ironeye is very easy to play when your teammates don't die.
Biggest issue IMHO is lack of voice chat making it very hard to coordinate with teammates. Pinning points on the map just isn't sufficient for a game this complex and fast paced.
A couple half-assed solo runs also suggests it is significantly harder alone, but I might just need practice.
We're also looking for a mascot! Take a look at the candidates and give your honest feedback.*
* As long as that feedback isn't in favor of the version with an impossible backside.
Lots of cool stuff in this release, I'm particularly excited with the integration into the #ChromeDevTools performance panel. It really helps build clarity around how Angular is contributing to page performance.
Even more exciting DevTools features coming soon to an Angular extension near you!
Angular v20 is now available! ✨
Check out the blog post for more info about the cool features and be sure to tune into the v20 developer event premiering tomorrow, May 29 at 9 AM Pacific
https://blog.angular.dev/announcing-angular-v20-b5c9c06cf301
@knowler Obviously, can't lock the main thread.
The existence of `Object.freeze` implies the existence of `Object.thaw`.
@mb21 Yeah, I suspect I'll need to do some kind of approach like that. I was just hoping something would help me focus on the CSS contributions a little more effectively.
@mb21 I'm being somewhat intentionally vague because there's a huge set of work the browser needs to do for styling and I'm hoping for some overview of the major pieces and how to measure them.
Specifically, I'm looking at evaluating some changes in the way CSS is shipped to the browser and I want to be able to measure what kind of impact that has.
Is there any good content out there about benchmarking #CSS performance? Including parsing, evaluation, recalculation, any work done related to a `<style>` tag.
I see https://web.dev/blog/at-property-performance, which is a great case study, but seems focused on selector performance. Is there something more broad?
"Happy Friday" should really be "Happy Saturday Eve".
@skryking Honestly I think this year was better than last year.
But fundamentally, shipping big changes is just a bunch of incremental improvements. You don't realize how significant they are without looking at the larger context and progress.
So how long until #Google hires Robert Downey Jr. and Paul Bettany to do an #AndroidXR demo?
