Re:Polyfill supply chain attack hits 100K+ sites
by program_whiz on Tuesday June 25, 2024 @03:16PM
(#40792421)
in a strange way, this almost makes the behavior of hopping onto every new framework rational. The older and less relevant the framework, the more the owner's starry-eyed enthusiasm wears off. The hope that bigcorp will pay $X million for the work starts to fade. The tedium of bug fixes and maintenance wears on, the game theory takes it's toll. The only rational choice for library users is to jump ship once the number of commits and hype starts to fall -- that's when the owner is most vulnerable to the vicissitudes of Moloch.
[ Parent
| on HN ]
Re:Polyfill supply chain attack hits 100K+ sites
by chrisweekly on Tuesday June 25, 2024 @03:40PM
(#40792693)
Good point. What's often (and sometimes fairly) derided as "chasing the new shiny" has a lot of other benefits too: increased exposure to new (and at least sometimes demonstrably better) ways of doing things; ~inevitable refactoring along the way (otherwise much more likely neglected); use of generally faster, leaner, less dependency-bloated packages; and an increased real-world userbase for innovators. FWIW, my perspective is based on building and maintaining web-related software since 1998.
Re:Polyfill supply chain attack hits 100K+ sites
by wadadadad on Tuesday June 25, 2024 @07:11PM
(#40794763)
Would you consider yourself as to have "chased the new shiny"? If you don't mind, how many changes (overhauls?) would you say you've made?
Re:Polyfill supply chain attack hits 100K+ sites
by bobthepanda on Tuesday June 25, 2024 @11:48PM
(#40796201)
to be fair there is a whole spectrum between "chasing every new shiny that gets a blog post" vs. "I haven't changed my stack since 1998."
there are certainly ways to get burned by adopting shiny new paradigms too quickly; one big example in web is the masonry layout that Pinterest made popular, which in practice is extremely complicated to the point where no browser has a full implementation of the CSS standard.
Re:Polyfill supply chain attack hits 100K+ sites
by mb2100 on Wednesday June 26, 2024 @02:06AM
(#40796880)
CSS Masonry is not even standardized yet. There is a draft spec: https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_grid_la... and ongoing discussion whether it should be part of CSS grid or a new `display` property.
Re:Polyfill supply chain attack hits 100K+ sites
by trekz on Wednesday June 26, 2024 @06:31AM
(#40798404)
> in a strange way, this almost makes the behavior of hopping onto every new framework rational.
Or maybe not doing that and just using native browser APIs? Many of these frameworks are overkill and having so many "new" ones just makes the situation worse.
Re:Polyfill supply chain attack hits 100K+ sites
by sofixa on Wednesday June 26, 2024 @05:11PM
(#40804621)
Many of them predate those native browser APIs. Pollyfills, the topic at hand, were literally created to add modern APIs to all browsers equally (most notably old Safaris, Internet Explorers, etc.).
Re:Polyfill supply chain attack hits 100K+ sites
by ricardobayes on Wednesday June 26, 2024 @02:02PM
(#40802654)
To be fair, when it comes to React, I don't think there is a realistic "new shiny" yet. NextJS is (was?) looking good, although I have heard it being mentioned a lot less lately.