Hacker Newsnew | past | comments | ask | show | jobs | submit | proxy9's commentslogin

Fun software but the only issue with Instant is their pricing. Once they gain adoption, I expect them to significantly raise their rates, I can seen them charging over $1 per GB easily. And like with any vendor lock-in, you’re stuck paying whatever they decide to charge. Observe with caution I'd say


> vendor lock-in

For what it's worth, Instant is fully open source. The UI, the sync engine, and the multi-tenant database live here:

https://github.com/instantdb/instant


Vendor lock-in from vibe-coded apps is going to be brutal. It's an all-out turf war.

But hey, rewriting the plethora of vibe-coded long tail* apps might be a major source of employment in the future.

* small but loyal and profitable userbases


Why lock-in? The interface is just a conversation and the non-programmer won't know whether it's InstantDB or whatever else in the background, as that's the whole point of vibe coding. I can only see issues taking out your data into another system, but even that can be vibe coded (can it?)


What I dislike about Twitter lately: - overarching political propaganda - crypto bros - AI bros - profit chads - constant fighting over idiotic topics, some driven by Musk itself

What I care for when I open Twitter: - news - hearing from other people from the dev community

If Threads can deliver this, I will be hooked


Threads need to realize the importance of the blue check and implement it. Prior to Musk, I would see a tweet, open the replies and look for the blue checks to see what "prominent" people were responding. Now that the blue check means nothing, that's impossible and you have to weed through all the content.

You can argue that's a good thing, that a person with 10 followers might be as interesting as someone with 100,000 followers, but it's not for me.


They are already doing it via Meta Verified, which is already a big step us vs Blue since they actually check your id


But you still have to pay don't you? I like verified users, but I also want to know who is prominent user. So maybe two badges? One just for verified ID and one for prominent user (the old blue check).


i look for the same things and i get that out of twitter, its pretty satisfying

you have to engage with what you want to see, if you join in arguments or constantly like posts of a political viewpoint then you'll never find peace

ie, look inward


Which means a lot will be censored, if they don’t censor you end up with the same convo people want to talk about in the current times


Remember when we used to call that filtering and it was a feature and not a con?

Not for actual censuring in cases where it’s demonstrably harmful - but I’m not required to give attention to someone’s opinion just cause they feel like blasting it into the void. Twitters gone too far the other way.


If we look at the current situation on Twitter, a lot of content that gets pushed by the algo is dumpster fire. Not sure how that benefits society


It's not just industries, we all do. If we are honest with ourselves, we are just some parasites to this planet


The impact of corporations is far greater than of individual citizens


The greatest idea corporations ever came up with was to convince us all that we can individually stop what’s happening. Remember the fantasy that many of us grew up on that recycling would save the planet? Turns out things like plastic recycling is a joke.

Or how about when the oil companies invented the idea of “carbon footprint” to convince the public it was their responsibility to curb emissions, even though the vast majority of pollution isn’t from consumers?


Inline editing is generally a bad idea. I don't see WSJ rocking this anytime soon.


The editing functionality is delegated to the CMS. Respectively content changes flow through the exact pipeline as changes originated directly from the CMS would. In fact, we allow the CMS to completely control the actual editing experience.

The main point of this feature is that if an employee does find a typo on some article, they can just fix it rather than going to the CMS, finding the actual place where that text is stored, making the change, etc.


Might be interesting for marketing guys but take it from a guy who’s worked with publishers. They hate inline editors.


It's both inline editing and the ability to link arbitrary rendered text to its originating CMS and content flow.

More detail here of how this scales to any content model complexity:

https://twitter.com/rauchg/status/1653800915827310593


I think they care. Vercel is VC money. Not even close to profitability. Anyone building anything but a toy needs to take into consideration that Vercel might not be here in 2 years from now


Gimme a effin break. Man people are increasingly lazy. We get excited about a Neondb wrapper now? Really?


Paid service on api / llama wrappers. Laaame


The APIs aren't free. For a large site, creating the embeddings and then serving lots of users would quickly get expensive. Although I do think this is overpriced.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: