Firefox lost me when they conspired to kill WebSQL.
They were the ones used the vast marked share they had to push the trendy thing of the day, namely nosql and IndexeDB, a technology which is bemoaned by web developers today.
I think the fact that there is another post about SQLite on the front page right now, attests that it would have been better to just standardise that. But then all those greenfield "spec hackers" wouldn't have had the fun of building cloud castles.
As a web developer and a browser user I'm tired of things not working. And if that means less options in terms of browsers I don't care as long as the browsers that are there give me a solid foundation to work with.
I'd rather have less options with more freedom of choice because all the different options are compatible and interchangeable, than many options but little choice, because their features sets are all disjoint and nothing is compatible.
WebSQL was never a spec. It was literally implemented as ‘be bug compatible with this specific version of SQLite’. There was no way that that was going to be accepted by Mozilla and Microsoft.
There was actually an offer to turn SQlite3 into a spec under the condition that Firefox agreed to implement it.
Firefox declined since they didn't want to "confuse" developers with too many options.
I think the fact that there is another post about SQLite on the front page right now, attests that it would have been better to just standardise that. But then all those greenfield "spec hackers" wouldn't have had the fun of building cloud castles.
As a web developer and a browser user I'm tired of things not working. And if that means less options in terms of browsers I don't care as long as the browsers that are there give me a solid foundation to work with.
I'd rather have less options with more freedom of choice because all the different options are compatible and interchangeable, than many options but little choice, because their features sets are all disjoint and nothing is compatible.