Nearly $300 seems a bit too rich for my blood - will definitely buy one second hand once I can get one for about $100.
Readit NewsUnsurprising - people don’t pay, and their audience is perhaps a bit more likely to use Adblock, not to mention the decline in news in general.
endisneigh commented on EcoFlow's $200 PowerStream theverge.com/24150901/eco... · Posted by u/CHB0403085482
What could go wrong?
i honestly cant imagine paying for a search engine with whats out there for free
You’re getting downvoted but I agree. I didn’t see the value and stopped after a while of paying. It is sad that basically any comment that isn’t pro-Kagi is downvoted but I guess that’s the Reddit-ification of this site.
Most people who complain about Google don’t even use it properly (e.g. PSE).
A smaller competitor wants and advocates for itself. Makes sense but is it really surprising? It would be strange otherwise.
I do wonder how far one can get charging for search.
\s, I hope? Not using US-made products is basically impossible in the modern world.
It’s really not. It’s just inconvenient.
endisneigh commented on A single server can go a long way these days twitter.com/kelseyhightow... · Posted by u/tosh
The title and FTA are true but the economics for a startup is tricky.
One of the spectrum is true bare metal - setting up a data center, space, power, cooling and all of that.
Next step might be colocation.
The other end of the spectrum might be something like Firebase or DynamoDB. A step to the left from there might be Cloud Run, and then GKE.
It’s difficult to know how to spend your time and money as a function of the associated costs and maintenance.
Unfortunately from what I’ve seen the big clouds are a bit too expensive compared to the likes of Hetzner et al to just overprovision and forget about it.
I will say that it’s getting easier to have a self hosted set up that supports failover well with CockroachDB, TiDB and such.
The app side still needs refinement. Maintaining a k8s cluster on bare metal isn’t trivial.
My point is that you can handle a billion of rows on a single PostgreSQL instance.
Looking at the sheer number of rows isn’t really helpful - you’d need to know the query profile. Any database can simply store a billion rows.
Denormalizing data always locks you into certain access patterns, regardless of your ability to evolve schema.
You do not have to denormalize data to use dynamodb, just like how data doesn’t have to be normalized to use a relational DB.
Man people have no clue what they’re talking about lol
Regardless, too much expense for too little revenue.