Hacker News Reader

Comment by stavros | Hacker News Reader

In what way? This seems very useful.

Plugins are coming, and wrappers are still having to pay openAI and on top of that their own slice of the pie. Since wrappers aren't really cultivating the information themselves, nothing is stopping you from making your own either, the openAI API isn't a big difficult secret. You can even ask openAI to write your own integration for you!

You can probably also ask openAI about the nextjs/tailwind starter repo everyone of these wrappers keep relying on too.

100% agree on the wrappers. Though, keep in mind that even if you can write your own it does not mean you can support it or even keep up with the latest trends / features. Hacking something over the weekend is doable but supporting long term will take countless of hours which can be spent elsewhere.

You overestimate the willingness and ability of the average org to implement and support things like this on their own.

I do not, I recognize that they care far more about costs and don't mind throwing one developer at problems internally than outsourcing it to a middleman of a middleman who is overcharging just for access to an API that isn't theirs.

Reminder, it's going to get easier to implement things. It is going to get easier to support things. Neither of these two reasons are going to be the catalysts they used to be for businesses anymore.

It's effectively a tiny frontend, doing 0.01% of the work, which is attached to another (highly available) product.

Reply on news.ycombinator.com