You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
But the tides are already turning and more and more web developers are starting to understand that the whole Node thing was a big mistake. Look out for Elixir based sites pushing server rendered content over websockets.
Server-side rendering is an *absurd* solution that depends on a severe misunderstanding of the problem in order to seem to make any sense at all.
You would want to render those fancy templates on the server and just push plain HTML to the client.
Computers, how do they work???
What’s absurd is having the client querying you database and iterate over the result when or if it succeeds - stuff like that.
This is what I ment with SSR:https://en.wikipedia.org/wiki/Server-side_rendering …
Oh, I see they have changed the name now. That page used to be named Server-side rendering.
So SSR is basically what almost all servers do today, but they have a tendency to push a lot of logic over to the client - making the browser do a gazillion asynchronous function calls on the server.
I will agree that it is silly and unnecessary to do a bunch of asynchronous function calls. Communication should be kept to the minimum necessary to do the job. But, this doesn't mean the server should do more work, it just means the client should be architected less terribly.
What I'm missing is more like a thread based approach, where the client just have a thin layer updating the DOM.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
New website: 