AI is stifling new tech adoption?

Post by sesm » Fri, Feb 14, 2025, 4:38 PM UTC

CharlieDigital wrote: post #130

sesm wrote: post #93

Earlier quoted context omitted.

Doesn't Preact use the same model but prioritise bundle size over performance?

It's not the same model. Many, many (if not most) devs probably do not realize that React has an "inverted" model of reactivity and is in fact the root cause of it's performance woes. To the extent that the React team spent 2+ (almost 3?) years working on a compiler to address the issue by adding in the correct memoization primitives in a compile phase (trading increased memory consumption for more runtime performanc…

Post by gosub100 » Fri, Feb 14, 2025, 4:42 PM UTC

diggan wrote: post #150

killjoywashere wrote: post #30

Pathologists as a specialty has been grousing about this for several years, at least since 2021 when the College of American Pathologists established the AI Committee. As a trivial example: any trained model deployed will necessarily be behind any new classification of tumors. This makes it harder to push the science and clinical diagnosis of cancer forward. The entire music community has been complaining about how o…

> The entire music community has been complaining about how old music gets more recommendations on streaming platforms, necessarily making it harder for new music to break out. Compared to what though? Compared to Limeware/Kaazaa back in the day, or compared to buying records in a store? Personally, I find it easier than ever to find brand new music, mostly because Spotify still surfaces new things with ease for me (…

Post by tobyhinloopen » Fri, Feb 14, 2025, 4:46 PM UTC

spacephysics wrote: post #22

CharlieDigital wrote: post #8

As the saying goes: while (React.isPopular) { React.isPopular = true } It's actually quite sad because there are objectively better models both for performance and memory including Preact, Svelte, Vue, and of course vanilla.

React has become the Java of late 90’s to mid 2000’s. Loads of libraries, documentation, and developers which creates a flywheel that will grow those aspects over the next X years. Until something comes up that is magnitude better in performance/maintainability, and even then it’ll take years to dethrone the status quo. Good questions in these comments essentially asking, does the level of training data on these mode…

Post by tobyhinloopen » Fri, Feb 14, 2025, 4:48 PM UTC

matsemann wrote: post #89

hiAndrewQuinn wrote: post #58

>Consider a developer working with a cutting-edge JavaScript framework released just months ago. When they turn to AI coding assistants for help, they find these tools unable to provide meaningful guidance because their training data predates the framework’s release. [... This] incentivises them to use something [older]. That sounds great to me, actually. A world where e.g. Django and React are considered as obvious…

What if it happened just before React, and you therefore got stuck with angular? Should we now be stuck with React forever just because it's okay-ish, never allowing future better framework to emerge?

    $(function() {
      // yay
    })

Post by 3D30497420 » Fri, Feb 14, 2025, 4:50 PM UTC

carlosdp wrote: post #162

I don't think this is a bad thing. Pretty much all of the author's examples of "new and potentially superior technologies" are really just different flavors of developer UX for doing the same things you could do with the "old" libraries/technologies. In a world where AI is writing the code, who cares what libraries it is using? I don't really have to touch the code that much, I just need it to work. That's the future…