luvs2code
FLTK looks horrible next to most modern applications. But FLTK 2.0, which has been abandoned for 10 years, actually looks pretty modern and the API is actually pretty elegant. There was some kind of split in the community about FLTK 2.0 breaking backward compatibility and I guess the 1.0 people won in the end.
Its not exactly an elegant solution I have to admit. But the licensing problems with QT make a lot of people nervous, GTK seems to be pretty polarizing, and for whatever reason WxWidgets and FLTK never really got much adoption/didn't progress very far.
[0] https://learn.microsoft.com/en-us/windows/wsl/tutorials/gui-...
But referencing the parent comment's discussion of business processes, its highly unlikely the problems will appear until Volvo tries to move to some other vendor or swap out the software solution for the next greatest thing.
What's interesting is that insurance companies seem to measure bad driving using a few different metrics including deaths per miles traveled [5]. Single vehicle crashes were also very dangerous in the rural states like Wyoming (deer are a serious problem), but for some reason Rhode Island tied with Montana at 70% of all accidents being single vehicle accidents[6].
I also couldn't find an annual figure for people disabled in car accidents, but a 2004 study found that about 1.2 million Americans live with permanent injuries from car accidents and about 41% of them are unable to work [6].
[0] https://www.nhtsa.gov/risky-driving/drunk-driving [1] https://www.nhtsa.gov/risky-driving [2] https://www.nhtsa.gov/risky-driving/drug-impaired-driving [3] https://www.nhtsa.gov/risky-driving/distracted-driving [4] https://worldpopulationreview.com/state-rankings/worst-drive... [5] https://www.iihs.org/topics/fatality-statistics/detail/state... [6] https://pubmed.ncbi.nlm.nih.gov/15474547/
1) Why they had the information on their website in the first place 2) Why the information in the past was wrong (in light of new evidence) 3) Why the current information should be taken seriously in light of the aforementioned misinformation.
I'm working on a project, for fun not for money, that uses Golang and talks to a SQLite database for things like accounts and user content. So far I really enjoy writing it a lot but I have to admit that it would probably have issues if it scaled to a large number of users.
In fairness to SQLite it was designed in a different era technologically. Maybe there will be a replacement for the web app era if we distill what we like about SQLite