Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

AI is stifling new tech adoption?

vale.rocks

Post reply on HN
Print view View original

121–130 of 442 posts

Re: AI is stifling new tech adoption?

#121

Post by efavdb »

matsemann wrote: post #86

I actually asked this a while back, but got little response: https://news.ycombinator.com/item?id=40263033 > Ask HN: Will LLMs hurt adoption of new frameworks and technology? > If I ask some LLM/GPT a react question I get good responses. If I ask it about a framework released after the training data was obtained, it will either not know or hallucinate. Or if it's a lesser known framework the quality will be worse tha…

Supporting anecdata: I was interested to see that chatgpt doesn’t know how to use one of my (small, not too popular) open source python packages — despite having blog posts and documentation on them, all from more than five years back.

Re: AI is stifling new tech adoption?

#122

Post by tcoff91 »

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 is better than all of those because of the existence of React Native, React Three Fiber, Remotion, etc…

It has the best ecosystem of libraries and it’s not even close.

If you write your web app in Vue and decide you want mobile apps later you won’t be able to share much code there.

Re: AI is stifling new tech adoption?

#123

Post by [deleted] »

OuterVale wrote: post #109
lackoftactics wrote: post #83

> OpenAI’s latest models have cutoffs of late 2023. The first paragraph is factually incorrect; the cutoff is June 2024 for 4o. Awww, no more new JavaScript frameworks and waiting only for established technologies to cut through the noise. I don't see that as a bad thing. Technologies need to mature, and maintaining API backward compatibility is another advantage.

Author here. May I request a source for that? Platform docs state: > The knowledge cutoff for GPT-4o models is October, 2023. https://platform.openai.com/docs/models#gpt-4o

[deleted]

Re: AI is stifling new tech adoption?

#124

Post by d_watt »

It's always been a thing with modes of encapsulating knowledge. The printing press caused the freezing of language, sometimes in a weird place*

Where great documentation was make or break for a open source project for the last 10 years, I think creating new projects with AI in mind will be required in the future. Maybe that means creating a large amount of examples, maybe it means providing fine tunes, maybe it means publishing a MCP server.

Maybe sad because it's another barrier to overcome, but the fact that AI coding is so powerful so quickly probably means it's worth the tradeoff, at least for now.

*https://www.dictionary.com/e/printing-press-frozen-spelling/

Re: AI is stifling new tech adoption?

#125

Post by tcoff91 »

Hasu wrote: post #106
9rx wrote: post #56

Earlier quoted context omitted.

But equally impressive that the Javascript community has actually managed to continue to use a single framework for more than five minutes without jumping to the next.

React is almost 12 years old and has dominated frontend development for almost a decade. I'd bet most JS backend projects still use Express as the webserver, and it's even older than React. Can we please retire this meme? It's stale and adds nothing to the conversation.

Yes thanks to React we can finally retire this meme. It was very true before react became dominant though.

Re: AI is stifling new tech adoption?

#126

Post by Secretmapper »

lackoftactics wrote: post #83

> OpenAI’s latest models have cutoffs of late 2023. The first paragraph is factually incorrect; the cutoff is June 2024 for 4o. Awww, no more new JavaScript frameworks and waiting only for established technologies to cut through the noise. I don't see that as a bad thing. Technologies need to mature, and maintaining API backward compatibility is another advantage.

> Awww, no more new JavaScript frameworks and waiting only for established technologies to cut through the noise. I don't see that as a bad thing. Technologies need to mature, and maintaining API backward compatibility is another advantage.

I think this kind of discussion is immature and downplays the point of the article.

A good example of this that I just encountered: Rust. Just asked Claude/ChatGPT for rust stuff recently, and it still gives a lot old/depreciated methods for a lot of things. This has been the case for Godot 3 vs 4 as well.

Re: AI is stifling new tech adoption?

#127

Post by throwup238 »

snek_case wrote: post #105
raincole wrote: post #95

Earlier quoted context omitted.

I know nothing about pathology, but in terms of software, I think slower adoption to new tech is what we need, especially when the "new tech" is just a 5% faster javascript framework. By the way, for content creation, the only platfrom that really favors new creators is TikTok. Whether it leads to higher content quality is left for one's judgement.

That's not wrong. There is a lot of hype-driven development in the programming world. People are always jumping on the latest web frameworks and such. A little bit more stability is not a bad thing. That being said, I think that people underestimate how fast LLM technology can evolve. At the moment, lots of training data is needed for LLMs to learn something. This may not always be the case. In 2 to 5 years, it may b…

After watching the entire world’s reaction to AI, at this point my conclusion is that hype driven development is human nature, and we just need to come to terms with that (but you will have to drag me kicking and screaming).

Re: AI is stifling new tech adoption?

#128

Post by ragnese »

raincole wrote: post #95
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…

I know nothing about pathology, but in terms of software, I think slower adoption to new tech is what we need, especially when the "new tech" is just a 5% faster javascript framework. By the way, for content creation, the only platfrom that really favors new creators is TikTok. Whether it leads to higher content quality is left for one's judgement.

> I know nothing about pathology, but in terms of software, I think slower adoption to new tech is what we need, especially when the "new tech" is just a 5% faster javascript framework.

I hope that's not the definition people are using when discussing adoption of "new tech".

When it comes to the topic of AI and "new tech adoption", I think about something like the Rust programming language.

I apologize if it chafes the people reading this comment that I'm something of a Rust evangelist and I'm working from a point of view that Rust's very existence is a (large) net-positive when it comes to programming and how we think about programming language design.

My fear with AI tools in their current state is that it will slow down innovation in programming languages. Rust gained popularity because it brought things to the table that made writing safe, performant, and correct (thinking about the strong, expressive, static type checking) software much easier than it had been with the old incumbents (in certain domains).

But, if Rust were released today or in the near future, would it take off? If we could, hypothetically, get to a point where an AI tool could spit out C or C++ code and push it through some memory sanitzers, Valgrind, etc and just iterate with itself until it was very likely to be free of memory safety bugs, why would we need a new language to fix those things? I guess we wouldn't. And it wouldn't really matter if the code that gets generated is totally inscrutable. But, it saddens me to think that we might be nearing the end of human-readable programming language research and design.

Re: AI is stifling new tech adoption?

#129

Post by cbg0 »

jajko wrote: post #99
dsign wrote: post #85

Earlier quoted context omitted.

Where I live, specialists can't even speak English, so I doubt very much that they are up to date on anything. And I live in a first-world country.

On a first glance this may look like bad comment but there is sound reasoning, I see it with friends who are top notch doctors and surgeons in french part of Switzerland. Many articles and conferences are in english, often dont get translated (well), and one friend who is urology surgeon specifically mentioned this as an issue in his (former) department in Switzerland's biggest hospital (HUG in Geneva). They simply l…

I'm also in a country where English isn't the first language and for the doctors that do wish to stay up to date on what's going on, there are ways for them to do it, and translation technology is pretty top-notch already.

Aside from time constraints and perhaps no incentive to stay up to date, we do have to remember that some of these new discoveries always take time to find their way into becoming SOTA treatments everywhere, due to costs, regulations needing updates, special training or equipment being required, as well as sometimes only being marginally better than existing treatment options.

Re: AI is stifling new tech adoption?

#130

Post by CharlieDigital »

sesm wrote: post #93
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.

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 performance...).

I wrote about it here with code examples that work in JSFiddle: https://chrlschn.dev/blog/2025/01/the-inverted-reactivity-mo...

The short of it is that by pointing the reactive callback to the component function, it means that state within the component function has to be managed carefully. This doesn't happen in Vanilla, Preact, Solid, Svelte, and Vue because they point the reactive callback (via "signals") to a handler function that captures the component state in a closure. This is also why they are all faster and consume less memory than React.

Because React points the reactive callback to the component function, it effectively starts from a clean slate each re-render so the purpose of React Hooks is to move state out and inject them back (thus they are called "hooks") when it re-renders. In Preact, this is not the case since it uses signals: https://preactjs.com/guide/v10/signals/

A short video of the same examples if you prefer: https://youtu.be/7OhyP8H7KW0

Post reply on HN