This is probably true. I only really talk to US startup devs.
601 karma · joined February 10, 2022
This is probably true. I only really talk to US startup devs.
"Competition is for losers."
But, from a business sense, doesn't it seem like they're doing it backwards? Why not make a best-in-class AI assistant app, build a big userbase, and take the money to research hardware and harass Apple concurrently? Why start with hardware first?
I recommend reading Ted Kaczynski's writing on oversocialization [1].
[1]: https://www.washingtonpost.com/wp-srv/national/longterm/unab...
Imagine the industrial capacity of total war today...
[1]: https://en.wikiquote.org/wiki/Theodore_Kaczynski#:~:text=The....
This is going to be a hilarious statement in 20-50 years.
It's funny because on HN of all places, where all wildly successful companies are ran as absolute monarchies, and all the devices we type on are produced by companies ran as absolute monarchies, there's this undeserved reverence for "democracy" as if it's some sacred church or something.
If the voting population is so easily swayed by a video scrolling app, maybe, just maybe democracy isn't such a good idea? Would you work for a company where the CEO makes important decisions based on the amalgamation of 30 second videos that happen to come across his/her feed? I wouldn't. I don't think I want to participate in a country ran like that either. I'd expect the decisions to appear schizophrenic, which quite frankly describes our current political situation in the US.
Like, we have 100K+ fentanyl overdoses a year in the US, and I don't see any TikToks "informing voters" about that. No one cares. In fact, I don't even expect normal people to care about it---in a healthy society they shouldn't even be aware of it. It would take a special person, who is egoically invested in the health of his population to change that. Someone like a startup CEO, ala Washington, Jobs, etc.
So no, you're not on the "safe side of history" by advocating for something that's politically fashionable at the moment. History is written (and re-written) by the winners, and I wouldn't put my money on "democracy".
We prefer vertical scaling over horizontal. The entire company is one server, which works for us since most of our customers are close to it.
In the future if we needed geographically distributed read replicas and failover protection I would probably go with LiteFS [1].
> if only one process can write to the db, how do you architect your system so that writes are performed by just one of the instances (the writer)
For multiple machines, LiteFS has ways of dealing with this. But the general idea applies to our system as well. All of our SQL is in either a read.sql or write.sql file. On startup, we open a connection pool for all the read queries and open a single connection for all the write queries. This keeps things clean and separated.
> how do you gracefully upgrade your app without any downtime?
We use a systemd socket and service. When the service is restarted with a new binary, systemd delays request processing until it's back online. It's really simple (thanks to our monolith setup) and entails zero downtime except a 1-2 second delay on unlucky requests. But as far as I can tell, no requests are lost.