Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I get where you're coming from, but isnt the whole idea of open source "if you dont like the approach, you're free to fork the code and do it the way you think is right?"

As long as the fork doesnt violate trademark (turso vs sqlite) it is working-as-intended?

I, for one, encourage this kind of behavior. We should have more forks. More forks = more competition = better results for everyone.

---

To make an analogy. Would you say the same thing if this were a for-profit company?

"I cant believe someone else is competing the same space as $x. $x is hugely successful, and so many people use it. I dont know why there's an alternative"



Both forking sqlite, and disliking the forking of sqlite, are allowed.

Plus, it's just technically bad. Most cases where you'd want to scale up sqlite are better served by a client/server database.


>Most cases

But not all of them, right? I don't need scaling across different hosts, but I need scaling between different threads on the same host. And I don't want for that PostgreSQL, MySQL, Oracle an other stuff like that.




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

Search: