Posts by ryantownsend@webperf.social
(DIR) Post #AVj1ua7dnVyh3dkBxg by ryantownsend@webperf.social
2023-05-16T21:01:51Z
0 likes, 1 repeats
Today I learned you can build your own custom form elements which will validate/serialize upon submission, just like native HTML inputs [1]Support for the ElementInternals interface landed in Chrome & Firefox years ago, and finally in the latest Safari (16.4) but there's a polyfill if you need backwards compatibility [2][1]: https://web.dev/more-capable-form-controls/[2]: https://github.com/calebdwilliams/element-internals-polyfill#webplatform #javascript
(DIR) Post #AatBVNGzirxS8K5bii by ryantownsend@webperf.social
2023-10-18T08:36:15Z
0 likes, 0 repeats
@vanilla I experienced this in the past with Sass, SCSS and CoffeeScript, but it's definitely been occuring at an accelerating pace, since the introduction of the ever-green browsers, given features can be adopted far quicker these days.
(DIR) Post #AdAWX4BZT3cGoBaa0W by ryantownsend@webperf.social
2023-12-25T13:04:27Z
1 likes, 0 repeats
Merry Christmas everyone!
(DIR) Post #Ai9Ot26rlD1XjPO6nQ by ryantownsend@webperf.social
2024-05-22T13:16:09Z
0 likes, 1 repeats
Finally got myself a ‘new’ phone today, it’s an absolute banger.No, it’s not an iPhone 15 Pro Max, it’s a Samsung A51 for #webperf testing and it scores less than half an iPhone 7 on Geekbench 😬 you can feel the input lag even during device setup!Hat tip to @slightlyoff for the recommendation. Worth reading: https://infrequently.org/2024/01/performance-inequality-gap-2024/
(DIR) Post #AkMJTQkMoPgei1Rt5s by ryantownsend@webperf.social
2024-07-27T11:11:55Z
3 likes, 4 repeats
👏 more 👏 developers 👏 need 👏 👏 hear 👏 thisI can count on one hand the number of my clients over the past couple of years who haven't either over-architected for scale or were unnecessarily concerned about it.You don't need to understand Distributional Little's Law to figure this out, it's obvious with primary school level math.Excerpt from https://tailscale.com/blog/new-internet
(DIR) Post #AoLnY8bD8YYny6CZqS by ryantownsend@webperf.social
2024-07-27T13:38:46Z
0 likes, 0 repeats
@ceulig I find it's more often driven by developers themselves.For the past decade+ we've had big tech firms fighting over talent, so they present solutions to their specific problems as panacea to keep the spotlight on them and drive open source adoption.On the flip side, developers want to believe they will need that level of scale, that they'll witness the same problems and they want their CVs to include the tech that shows they are in the big leagues.A vicious cycle.
(DIR) Post #AoNU90nLVSTJiA6SxM by ryantownsend@webperf.social
2024-07-27T13:47:56Z
0 likes, 0 repeats
@grumpasaurus fwiw, I see Kubernetes as basically self-hosting, yes it might be atop IaaS but your own team is responsible for uptime, security patching etc.Most businesses should be outsourcing to a PaaS like Heroku, Render etc.For 99%+ of use-cases, until your bill hits six figures monthly, it just doesn't make sense to hire DevOps/Infra people.
(DIR) Post #AoNU928IX2pFrQuiFk by ryantownsend@webperf.social
2024-07-27T13:58:23Z
0 likes, 0 repeats
@grumpasaurus absolutely, context is always important, hence my use of "most businesses" and "99%+"Ultimately: most applications just aren't special. Many are barely more than simple CRUD.It's not uncommon that the people on hand are the problem... they are the ones driving the infrastructure complexity in order to keep their jobs and pad their CVs. It can mean swapping them out for more productive people who focus on shipping.
(DIR) Post #AoNU93ZdAuHeKUi3Um by ryantownsend@webperf.social
2024-07-27T14:11:03Z
0 likes, 0 repeats
@grumpasaurus not directly, but a DevOps team isn’t going to advocate moving away from Kubernetes/IaaS/bare metal and just using Heroku or Render.React has seen enormous, continuous adoption despite very apparently flaws because “that’s where the employment/money is” (I’ve researched this before for my conference talks, it was the #1 voted answer on Reddit for why people use it)