Gregory's ServerLike, was it just a cash grab, or was it ALSO a smattering of "hey pipe down with all that talk about inclusivity, that affects what, like 2% of our users, pft also what do you mean performance is better for accessibility, EYEROLL"
|
9 comments
I feel like if I posted this on the other site it would just spawn subtweets like "🙄 wow guess I'm racist now because I like to use X framework" @hbuchel I'm no frontend JS expert but the guy seems to have hit a nail on the head. I now have a clear picture as to why *selecting text in an input field* in an internal corporate webapp I need to use is slow as shit. All powered by the newest shiny Dart frameworks giving tens of megabytes of JS for my browser to run. @hbuchel I also wish to add that pure client-side Javascript powered content rendering has made reliable archival of web information very hard. @enkiusz Oh yes. I remember some discussions about how this world of frameworks killed off that early "learn web dev by looking at view source" and people kind of hand waved that off ("who does that anymore", "there are better ways to learn", etc) But this is the other side of that. So many of these apps/websites are just broken if you try to archive/save them. @enkiusz And I feel like this is such a special part of the web, the GOOD part, the preserving of information. It's definitely deteriorated. @hbuchel would love to read this. i don't really follow much in like, various language communities, but the excessively fast churn of the javascript framework/tooling ecosystem vs. other languages feels quite exclusionary.  @hbuchel Oh yeah, that would be an interesting blogpost! If there's any merit to this idea? Good theory anyways... |
I need someone who is much better at writing to talk about this intersection of bigotry and ignorance and how it led us to the current state of JS frameworks LOL Even typing that out seems like "wow that's kind of a leap" but then I also watched it happen so, yeah