AI is stifling new tech adoption?
171–180 of 442 posts
Re: AI is stifling new tech adoption?
#172Earlier quoted context omitted.
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…
The blogpost in the first link doesn't mention Preact at all. Preact is mostly API-compatible with React, and it having a different underlying model is an extraordinary claim that requires extraordinary evidence. I've read the docs on Preact signals, and they look like React refs, but put outside of components. edit: the last paragraph about refs
> ...a different underlying model is an extraordinary claim that requires extraordinary evidence
You are looking at the syntax and not the reactivity model (how it determines what functions to call when a change happens).The post doesn't need to mention Preact because every other framework is signals-based except for React. Vue is simply the stand-in for "signals-based reactivity". Vue has different syntax from Preact (though it, too, can also use JSX), but it has the same reactivity principle.
https://preactjs.com/guide/v10/signals/
> What makes Signals unique is that state changes automatically update components and UI in the most efficient way possible. Automatic state binding and dependency tracking allows Signals to provide excellent ergonomics and productivity while eliminating the most common state management footguns.
It uses the same underlying reactivity model as Vue, Svelte, Solid, and Qwik.Vue docs: https://vuejs.org/guide/extras/reactivity-in-depth.html#conn...
Solid docs: https://www.solidjs.com/docs/latest/api#createsignal
Svelte: https://svelte.dev/blog/runes#Signal-boost
Qwik docs: https://qwik.dev/docs/components/state/#usesignal
In the blog post, Vue is the stand-in for signals-based reactivity. All signals-based reactivity models work the same way at a high level (their difference being primarily in their low-level DOM diff and update).
My prediction is that even React will eventually end up signals based because of TC39 Signals: https://github.com/tc39/proposal-signals
Re: AI is stifling new tech adoption?
#173Earlier quoted context omitted.
had to have hooks though. And vanilla-OO had to go in favor of trapping state in closures, which is cooler because it has functions and not methods.
You can still use vanilla-OO React. Do you complain when other frameworks add new features without breaking backwards compatibility?
If you search anything about React now, 90% of the docs are hook-based. Beginners of React in 2025 will be guided to use a default pattern which has worse runtime footprint and adds a whole suite of new tool-specific coding guidelines ("rules of hook"). After years with it, I struggle to see what it has added in terms of building front-end SPas, yet the pattern is now the default for all using React.
Re: AI is stifling new tech adoption?
#174Pathologists 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…
I keep thinking I'm going crazy until Rick Beato explains that yes, I am just an RNN Meat Popsicle and the world is interpolated:
Re: AI is stifling new tech adoption?
#175This is truly terrible. What happened to a new JS front end library every week? If this keeps up, we won't get to completely throw away all of our old code and retool every two years (the way we've been operating for the last 20 years) How will we ever spend 85% of our time spinning up on new js front end libraries? And don't even get me started on the back end. If AI had been around in 2010, we probably still have s…
Re: AI is stifling new tech adoption?
#176I 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…
This attitude works for write-and-forget workflows where the only thing that matters is whether it returns the answer you want (AKA "hacking it").
Once you add in other concerns: security, performance, maintainability, it can fall apart.
Re: AI is stifling new tech adoption?
#177Earlier quoted context omitted.
I doubt it is easier to retrain a large, dispersed group of humans on a new classification of tumors than it is to retrain a model on the same.
Not if they're trained to work through the problem each time they encounter it and stay up with their clinical training. The day the new classification drops many have already heard about it. You also assume that all the models in use will in fact be retrained. Generally, this position flies in the face of lived experience. AI is in fact stifling adoption of new things across many industries.
I suffer from a chronic illness. I saw 5 different specialists over the past 2 years, and each one gave me different treatment. A couple even relied on information from the 70s and 80s. One even put me in the ER because he changed my treatment after I explicitly told him not to.
Another example: Back in my 20s, I injured my back. I took my MRI results to six different doctors - and I'm serious here, every one gave me a different diagnosis. In the end, I fixed it myself by doing my own research and treatment (2 years of physical therapy). One doctor said I had pain because spine fragments were lodged in my spinal cord (not true). Two of the doctors were even pushing me into invasive surgeries, and I'm so glad I told them no.
I don't understand the praise for doctors. If I had to generalize, I'd guess the majority give up learning after achieving wealth and status. seems like an art and not a science. I will emphatically welcome AI treatment.
Re: AI is stifling new tech adoption?
#178This is truly terrible. What happened to a new JS front end library every week? If this keeps up, we won't get to completely throw away all of our old code and retool every two years (the way we've been operating for the last 20 years) How will we ever spend 85% of our time spinning up on new js front end libraries? And don't even get me started on the back end. If AI had been around in 2010, we probably still have s…
Re: AI is stifling new tech adoption?
#179I think it's unrealistic to expect a general purpose LLM would be an practical expert in a new field where there are potentially 0 human practical experts.
Re: AI is stifling new tech adoption?
#180Pathologists 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 (…