Cool blog post. One thing I am not sure about. If access to WiFi can lead to the mentioned or other risks, then something else is probably seriously wrong in the chain.
Please do not express your opinion as the opinion of the majority. Instead of discussing license choices, create your project and open source it as you like. Do not tell others how to build their business, especially on HN.
From my point of view, for example, GPL is not "open" at all. And yet it is on the list. In my opinion, BSL is even more "open" than GPL. Feel free to have a different view.
It is open for me to use as I please. And I don't want to destroy their business. I can understand your ideological drive, but in reality it doesn't matter until you behave unethically and steal their intellectual property. Do you want that?
TBH, I love BSL licenses. You can use it as you want for free, except being a competitor, and there is a high chance of a sustainable business model. (What benefit do you expect if the company goes bankrupt?) Despite the unpopular opinion, you have free and easy access to the code, so it is open source in the sense of words. Just not in the sense that you can steal their business like AWS does. Feel free to start a similar project, invest your time and money, and make it available under whatever license you want.
Great example! I think your example exactly points out why PBP of 0 is soo awesome in this case! You can invest $1000 immediately and get another customer in 0 months instead of 10. If they pay upfront again, so you can invest it again and so on.
Oh, it looks like Cloudflare is no longer a good choice. We had very similar experience with Ionic. We tried to put our money in, but no one was interested.
I have never seen this screen. Why don't you just click the "Keep Windows 10" button? But TBH, I wish the same from many other projects. Update python 2->3 was really painful for the whole community. Same for cjs->esm. I am pretty sure both would have been much faster and less painful if it was a hard switch.
Not sure I agree with the author. It took me less than 3 seconds to understand the initial code, but at least 10 seconds to understand the final result, even I had the knowledge of the initial function. But in some context this pattern can make a perfectly sense. Just not in this example.
Furthermore, from my point of view, creating an anonymous function and then store it in a variable is a bigger code smell.
Off-topic question: What are 70 Mio. code lines for? I mean, yeah, there are some services like Uber, Uber eats, but gosh, 70 Mio.? I have worked on very sophisticated products with a bit more than 1 Mio. LOC... Do I miss something in Uber apps and services?
> I would be curious to hear more justifications from him for this.
Not sure I understand you. Why do post-acquisition wealth need an justification at all?
> Founders really take far less risk than employees.
If it would be true, why aren't you a founder? You know, blaming other people for wealth/startup/marriage or government/party/boss/partner is easy. But when it comes to actual execution, most of these people come up blank.
You have worked for a startup. Well, you was aware of the risks. But I'm pretty sure the founder had more risks than you. I say this as someone who founded a company recently.
No, it isn't. While kv is easy on its own, the IDB API was never the right answer to the demand. This is exactly the reason why we (devs) are so hot about the persistent client-side storage. We want just use something like SQLite (or WebSQL, or Postgres) and forget about the IndexedDB nightmare. I'm pretty sure, we will see a huge boost around libraries and tooling when the things get more stable eventually.
You already gave a great overview of issues. But inventing something totally different from what people know without any reason doesn't make any sense. Look, YugaByteDB, CockroachDB, and some others use Postgres-compatible protocol/dialect. You can use most of standard tooling/query-builders/ORMs to speak with this databases. Why not use Redis or Cassandra protocol? Damn, leaving WebSQL as is would be much better choice. And please, don't say that "Web is different".
Although I agree that modern web apps suffers from the size already and additional 300kb doesn't hurt in this case, but one of the most popular use cases for the client DB is the offline capability for an small footprint web app. You know, it is when your connection is poor or even absent. 300kb hurt really badly.
> Also, couldn't the implementation of that storage spec. be shipped in the standard JS web APIs (i.e. by the browser)? Why would it be in every app?
Actually, that is exactly what happens to WebSQL and IndexedDB. WebSQL got deprecated, they were not able integrate SQLite, and created IndexedDB, which is hated by many developers. Just an example:
https://news.ycombinator.com/item?id=27511941