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

Components will kill pages

bitsandbytes.dev

Post reply on HN
Print view View original

31–40 of 52 posts

Re: Components will kill pages

#31

Post by dfdsf2 »

CuriouslyC wrote: post #16
gassi wrote: post #7

> In a world where we can type anything into a text box and get the information back instantly we are circumventing the need to visit websites altogether. This is purely anecdotal, but the only people in my extended circle making this transition (to any extent) are the technically savvy; everyone else is slowly realizing how awful AI tools and "AI-first experiences" can be and are actively trying to avoid them.

AI in apps is garbage. Cheap, low quality models and inflexible interaction patterns. AI agents using frontier models, configured nicely, that interact with programs that have APIs are pure gold.

I read the first line and thought - this guy gets it.

The read the second line and erm.... maybe not. The whole Agents thing has been pushed for almost a year now and it hasn't disrupted the profession of engineers on a noticeable scale.

Re: Components will kill pages

#32

Post by CuriouslyC »

dfdsf2 wrote: post #31
CuriouslyC wrote: post #16

Earlier quoted context omitted.

AI in apps is garbage. Cheap, low quality models and inflexible interaction patterns. AI agents using frontier models, configured nicely, that interact with programs that have APIs are pure gold.

I read the first line and thought - this guy gets it. The read the second line and erm.... maybe not. The whole Agents thing has been pushed for almost a year now and it hasn't disrupted the profession of engineers on a noticeable scale.

Code how you want (or however your boss will let you). My comment was based on my empirical observations, your mileage may vary.

Re: Components will kill pages

#33

Post by dfdsf2 »

kylehotchkiss wrote: post #19

> Imagine your own product. You likely won’t expect users 5 years from today to navigate 5 pages deep, apply filters and sort data just to try to derive the answer themselves… will you? Yes, I do, because outside of tech circles, AI adoption is not as pervasive/ universal as the loudest voices keep suggesting. I’m not dismissing its value, but gentle reminder to spend more time around nontechnical people, listen to h…

I regularly ask people who are in non-tech professions re. the adoption of AI and whether it has benefitted them. The answer is a resounding no. If anything managers are starting to pull-back on the adoption.

This place is hyper-concentrated on the tech in a particular context and has no resemblance of whats going out there in the big wide-world outside of high-tech software production.

This is the year that revenue has to start showing up materially across a wide range of contexts or else fear will over-take the market and investors will start pressuring the big tech firms to pull back on capex. It is their money after all, not the management.

Re: Components will kill pages

#34

Post by jcdcflo »

We’re going the other way where we are removing IP from public view.

Don’t count out on device, that’s where most of our focus is. If we can convert the voice / text to programatic commands on device, then we control the experience and don’t let the wolves through the gate.

Re: Components will kill pages

#35

Post by aubreyc »

How is this different than MCP Apps that you pre-build for your org using something like https://creature.run

I like that MCP Apps just offer tools, and AI doesn't have to deal with JSON and generative UI. Basically, you can cache UI as an MCP App by generating it up-front, to constantly save on tokens and time, and let AI use tool calls which it is getting constantly better at.

Re: Components will kill pages

#36

Post by wackget »

aubreyc wrote: post #35

How is this different than MCP Apps that you pre-build for your org using something like https://creature.run I like that MCP Apps just offer tools, and AI doesn't have to deal with JSON and generative UI. Basically, you can cache UI as an MCP App by generating it up-front, to constantly save on tokens and time, and let AI use tool calls which it is getting constantly better at.

> "Templates, hot module reloading, a simple SDK, and AI guidance help you and your team rapidly vibe code MCP Apps with ease."

Excuse me while I go vomit. If the future of the web is vibe-coded slop, I want no part of it.

Re: Components will kill pages

#37

Post by tejush8991 »

bccdee wrote: post #25

> [Given] a method for chat applications to understand components exposed from the website in question [...] AI chat applications win, and so does the brand that gets to keep ownership of how it tells the story of its product to its users. Never happening. The brand may "keep ownership of how it tells its story," but it loses its users. You have turned your tool into a series of widget in someone else's application,…

Curious if something like webMCP or an open layer that negotiates between the model provider and the website might mitigate the 'middleman' risk here?

Re: Components will kill pages

#38

Post by Legend2440 »

bccdee wrote: post #25

> [Given] a method for chat applications to understand components exposed from the website in question [...] AI chat applications win, and so does the brand that gets to keep ownership of how it tells the story of its product to its users. Never happening. The brand may "keep ownership of how it tells its story," but it loses its users. You have turned your tool into a series of widget in someone else's application,…

>They may integrate chatbot components into their apps, but they will not permit an inversion of control where their product becomes a component in a chatbot.

You may not have a choice. The chatbot can navigate the same UI your users can. People will use chatbots to use your product, whether you want them to or not.

Re: Components will kill pages

#39

Post by aubreyc »

wackget wrote: post #36
aubreyc wrote: post #35

How is this different than MCP Apps that you pre-build for your org using something like https://creature.run I like that MCP Apps just offer tools, and AI doesn't have to deal with JSON and generative UI. Basically, you can cache UI as an MCP App by generating it up-front, to constantly save on tokens and time, and let AI use tool calls which it is getting constantly better at.

> "Templates, hot module reloading, a simple SDK, and AI guidance help you and your team rapidly vibe code MCP Apps with ease." Excuse me while I go vomit. If the future of the web is vibe-coded slop, I want no part of it.

You must have missed the past year. Welcome back.

MCP Apps are perfect for vibe coding. They solve simple, specific problems. So yeah, vibe code them all day long.

Re: Components will kill pages

#40

Post by [deleted] »

bccdee wrote: post #25

> [Given] a method for chat applications to understand components exposed from the website in question [...] AI chat applications win, and so does the brand that gets to keep ownership of how it tells the story of its product to its users. Never happening. The brand may "keep ownership of how it tells its story," but it loses its users. You have turned your tool into a series of widget in someone else's application,…

[deleted]
Post reply on HN