5

Cameras don't draw. That is the by and large of it. Photo's are not drawn, and anything compositing a photo into it still has that not a drawing issue. Processing and Bandwidth aren't free A drawn image still has to be rasterised for display on a rastered device such as monitors, and most printers. That requires computation, and many devices are slow/...


4

To allow a variety of queries on such data, which transfer only the requested amount of bits and bytes over the network, one needs to preprocess and optimize the data for this purpose, there is no way around this. That is exactly what databases are made for. Trying to make things simpler by "avoiding a database" will end up in building a database ...


4

SQL is a relational query language. Most Web Service APIs do not expose a relational data model, they expose a graph data model. Hence, you need a query language for graphs. Another, more theoretical reason is that, as of SQL 2003, SQL is Turing-complete which means I can write a query that never terminates. This opens the service up to Denial-of-Service ...


3

If it's a small amount of information, you can store it in cookies on the client's device. If it's more data, you might try web storage or even a database on the client. There is also the option of storing it on the server in whatever format, most likely inside a DB, but don't store it based on the IP. IPs can change and multiple users can share the same IP. ...


3

I've been writing SQL for ~20 years and GraphQL seems like yet another technology to master. The exact same thing would happen with a subset of SQL. Keywords such as SELECT and WHERE would look familiar, but it would be a different technology, with its own quirks. SQL features The difficulty, actually, is to create the actual subset of SQL. The starting ...


2

You would have to parse the SQL into some safe intermediate format and then generate the actual SQL from that. Just sanitizing the passed SQL would not be safe enough IMHO. So it is not trivial to implement, and you will not get anything "for free" by using the same query language as the underlying database engine. So if the purpose is just to ...


1

Just keep it in memory Even the full county level CSV data is relatively small (16 MByte) so it would be possible to fully cache it in backend memory without a database and keep a simplistic index on state and county in memory. The data could be held as copies of the lines of original CSV file, so your backend could deliver it with minimal effort in the ...


1

SQL recordset as a HTML Table - a bad practice? No. But I think you're really asking if editing is ok. I say it is ok. I've done this with ASP (i.e. like "Star Wars" when there was only the one movie). The point was to have user-enterable and editable data. Here is what worked for me. NEVER let the user create, edit, or delete keys. Must keep key ...


1

One likely reason to not allow uploads of SVG files is that they support embedded scripts. These could potentially be used for XSS or other nefarious purposes. Personally, I think it was a mistake to make this a feature of SVG for precisely that reason.


Only top voted, non community-wiki answers of a minimum length are eligible