2 ms·
You only ditch compatibility for existing content. You still keep some level of compatibility with developer knowledge and teaching material. Most websites and
by est31 6y ago
You only ditch compatibility for existing content. You still keep some level of compatibility with developer knowledge and teaching material. Most websites and electron apps don't need a WebSQL implementation, yet all electron apps ship with one, bloating the downloads for all users.
- solson4 6y agoOr maybe even have those sort of features be broken out as modules. Can have a flag that says you’re using this JavaScript library or that css layout module at compile time and not ship with anything else.
- SahAssar 6y agoI don't think WebSQL is the best example. Chromium uses SQLite for other things (bookmarks, history, etc.) and WebSQL is mostly a JS API for interfacing with SQLite so I'm guessing the overhead isn't huge (and SQLite is pretty small to begin with).
- est31 6y agoGood point, and while the average Electron app probably doesn't need history or bookmarks, there are probably use cases it would still need WebSQL for. Another example would be the ffmpeg copy it ships to play back videos of various formats, even though the electron app only plays back a few hardcoded animations that all are in a single format.