4 ms·
Paraphasing this page - "Firefox has a lot of performance problems already from our architecture, we didn't necessarily integrate Sqlite in the best way on top
by WhatIsDukkha 6y ago
Paraphasing this page -
"Firefox has a lot of performance problems already from our architecture, we didn't necessarily integrate Sqlite in the best way on top of that"
"If you make a bad sql schema it will make it worse so maybe you should think of doing something off the cuff with json files that might be just as likely to be terrible"
It's really nice to be able to read a sql schema when you are trying to understand an application.
It would be a shame to lose that because core issues weren't addressed more broadly.
- BossingAround 6y agoI think there's a balance. Pretty much every performance issue can be reduced to "if you don't know what you are doing, it's gonna be slow". But, there are systems that enable you to make mistakes quite easily, and there are systems that make it more difficult to make mistakes. I think these issues are often transferable to regular DBs, but you typically don't run a full-on DB on your smartphone, which has very different performance and memory footprints/limitations. It's good to take it into consideration when using DBs on mobile devices (or, consider whether you really do need a DB, albeit small and nimble like SQLite).