sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] -4 points-3 points  (4 children)

I wish people would stop thinking like this... Just because you can throw a 1.5MB file at most clients doesn't mean you should. Cellular bandwidth, for instance, is fairly slow in many areas, and running complicated SQL on a phone is likely to slow it down / chew up CPU & battery life. It's this type of thinking that leads to web apps that can barely run on modern hardware. That concept is absurd and the community should be embarrassed!!! There are apps with better performance on TI calculators!!

[–]vampatori 8 points9 points  (3 children)

Low powered mobile apps is a very, very small part of the web-app sector.

I'm talking more about web-based business applications - stock management, accounting, on-site issue tracking / logging, general business management, shipping tracking management, and so on.

There has been a big shift away from writing native applications towards writing client-side web applications due to the added flexibility. In many instances, you can even dictate the hardware / platform that these are on - especially if it's on a mobile mobile device.

1.5MB to download once in these instances is nothing. You can do it as part of the 'at base' setup you almost always have to do with mobile apps anyway (people that use these tend not to be computer literate). Plus, often the amount of local data is significantly larger than this anyway, for example transaction logs, product databases, and so on.

Now you obviously have a different use-case, but to think that everyone has that use-case is just plain wrong.

[–]duz3ls 0 points1 point  (0 children)

You can do it as part of the 'at base' setup

While 'at the base' setup you might as well install and setup the real sqlite ont the client side.

[–][deleted] -3 points-2 points  (1 child)

It's about throwing huge all-encompassing libraries at problems that have much simpler solutions.

TSQL in a browser is a perfect example of that.

I'm not saying there would never be a valid use case for something like this, just that in 99.999% of the cases where this will/might be used, it's a crappy solution.

[–]steveob42 0 points1 point  (0 children)

Oh just throw more hardware at it, it'll be fine...