On Wednesday, 29 July 2015 at 01:23:54 UTC, Etienne Cimon wrote:
On Wednesday, 29 July 2015 at 00:12:21 UTC, Brandon Ragland
wrote:
For actual web applications, and front-end development
currently done in your more traditional languages, D could be
used, in a style similar to Java's JSP, JSTL, and EL. Just
without the notion of scripts in the pages themselves, as this
would mean writing an on-the-fly interpreter, or compiling
whole pages, which surely isn't an option for a compiled
performant language; if we want it to be readily adapted.
Apologizes if I jumped around a lot, and misspelled. More
difficult than I thought typing from my phone.
Most developers nowadays are having a lot of success building
web apps with an AngularJS MVC & Vibe.d, rather than rendering
the page entirely from the back-end. Heck, they can even build
android or ios native apps with this architecture (see Ionic
framework). So I think this makes more sense than rendering
pages in the back-end, even if most legacy web stuff did that.
This is so very true. Unfortunately, it also assumes some things
which are still not true:
* Every visitor has a speedy connection
* Every visitor is on a powerful machine (so to speak)
The problem with the first is that, half the the US is still on a
connection with speeds less than 6mbps. Downloading a whole page
(such as your Facebook timeline feed, which can easily be 6+MiBs
[see Akami link]) takes a full minute. That's pathetic for any
kind of real-world business logic web app. Maybe okay for
Facebook, but we could do better.
I can't even begin to tell you how many friends I have who are
non-developers who complain on a daily basis that "they're phone
has faster connection" or "Facebook loads slow" or "Gmail takes 2
minutes to open".
The idea of pushing *everything* to the client to render (which
often means payloads of 4+MiBs) is ridiculous and not being fair
to over 80% of the world.
http://www.akamai.com/dl/documents/akamai_soti_q213.pdf?WT.mc_id=soti_Q213
