I don't care that much about not having 10000000000 apps and counting
I used to think this way too... and then I found that there are already pretty much all the apps I really need, or the feature support is built in.
And it's coming to our mid-range smartphones next March, or September, or not at all.
Here's an interesting article that says Microsoft (pronounced 'Ballmer') missed the boat: http://minimalmac.com/post/17758177061/microsofts-biggest-miss Tablets in general are proof that Microsoft Office is not 'required' to do useful work.
Tablets are proof that people who have no idea how that useful work is done can tout the latest fad as a solution for every need.
I've seen how this happens:
1. Gee, I can just fire INSERTs in SQLite like I did in SQL Server, isn't it convenient?
2. (few months in development) Crap, these queries thrash the flash medium and cause a lot of waiting on I/O, we need to batch them and use transactions more.
3. (with deadlines looming) Attempts to tweak the database access flags or even relax the durability requirements, to get out of the corner we have painted ourselves into.
It would be instrumental for better performing code if database access was always treated as slow and therefore asynchronous, but SQLite does not provide an easy-to-use async API.
Do you have any idea what are you talking about?
The GP probably does, but SRAM is still prohibitively expensive for any practical memory size for a smartphone.
And if you have to use SQL for whatever reason, don't use indices unless absolutely necessary. It seldom is, despite what school has taught you. The index has to get updated too, which causes additional non-sequential writes. The minor speed boost you may get from selects are easily eaten up by the major speed bumps you cause on inserts and updates.
In many applications reads (SQL SELECT) happen much more often than writes. In this case, indexing still brings an overall benefit. In fact, the hardware architecture of flash memory is tilted to fast reads versus very slow writes, so if you have to do any writes at all, you already pay the price. The non-sequentiality issue is also mooted by controller sicruitry in bulk flash devices like SD cards, which reallocates logical buffers for wear leveling, hiding bad blocks, and write optimization.
The real issue with SQL in embedded devices is mainstream transactional semantics applied to flash storage. Often the programmers are not even aware that each INSERT not framed in an explicit transaction causes a full flush to the medium, which may be disastrous not only to this application's performance, but other concurrent file I/O.
Uh oh. There is a war on, the war for users, and "we" must win.
Get a life.
True. The Alternate Tab extension made my peace with GNOME 3, and then it got improved to cycle the current screen first.
Actually it is not. If you use any applications built for new GNOME, you have to remove old GNOME because the bastards kept the old names of everything but broken the backward compatibility.
Any specific examples? What GNOME has been good about is proper side-by-side installability of incompatible versions of their libraries. GTK+ 3 coexists in my box with GTK+ 2.
Well, sorry about not using 12 xterm windows with vim or whatever it is for you. I can't feel your pain.
I don't believe there really IS a GAS SHORTAGE.. I think it's all just a BIG HOAX on the part of the plastic sign salesmen -- to sell more numbers!!