I think its more likely the documents were the original street plans and guides which, when viewed from sufficient distance above, spell out the name of the last remaining descendant of Jesus and was designed by Da Vinci himself.
Prove me wrong. You can’t. They destroyed the records.
Windows needs to be restarted from a garage but other arms are not doing too badly/ not dying quite so badly. Games are a good spinner for MS; Office, exchange and AD are still ubiquitous for offices and they may even make that Azure mess into a reasonable product (Especially if they keep targeting transcoding based industries)
Phone aside I can't be the only person who finds the whole scrolling/animation thing just a bit obnoxious, can I? Such a slow way to get to the information.
For backend programming, SQL is certainly the most familiar language.
We don't generally send SQL over the wire, though. :-)
That is to say, front-end programmers usually work with a middleware (or backend-as-a-service) layer that translates REST/JS API requests into backend storage, and PgREST simply implements this layer with Postgres itself.
How are these protocols different from the rails style JSON-over-REST I've been writing unchanged since 5 years ago? The kind of thing public web APIs for the likes of soundcloud expose?
EDIT: I did some research: there is no difference. It's just plain ol' rails-style REST. This project is basically taking your thin sinatra/express/flask API layer and pushing it into the database itself, for reasons I am as yet unable to ascertain.
Excellent question! The REST API part should be familiar to any Rails programmer.
The main difference is that back-end models, validation rules, triggers and views are coded in DB level via stored procedures written in Node.js-compatible modules, so it's enforced for both SQL- and HTTP-speaking clients.
As you pointed out, this is simply an instant JSON-over-REST API server on top of existing Pg databases, and is not intended to replace the need for traditional frameworks with server-side templating.
Ah, so I guess I could stop avoiding traditional SQL features like triggers for fear of having code floating around outside my main app codebase, and it would generally make everything more centralised. I wouldn't have to worry about my workers having access to the correct model code and so on. Interesting.
EDIT: how easy do you think it would be to do the authentication etc outside, at the level of the nginx proxy?
Prove me wrong. You can’t. They destroyed the records.