Modern Web

Hold on there, cowboy. The innate superiority of strings over DOM based templating is not universally accepted. Because it's not unequivocally proven. In fact, a few years ago there was an obvious tide toward experimenting with alternatives to string based templating noticeable in several some high profile efforts in the client side templating space. See http://modernweb.com/2014/03/24/string-templating-considered-harmful/ for a recent overview that is pretty decent. Boris Moore did a lot of publishing about it, as I recall.

Here are some interesting links I found on implementing reactive programming in databases, Javascript, and Android: http://news.dice.com/2013/12/06/why-reactive-programming-for-databases… http://modernweb.com/2013/09/30/functional-reactive-programming-in-jav… http://mttkay.github.io/blog/2013/08/25/functional-reactive-programmin…

Here are some relevant test results which are about 4.5 years old now: https://modernweb.com/is-jquery-too-big-for-mobile/ At the time, your 3 round trips would have cost about a full second, which is roughly the same as the worst case JITting time for jQuery in those same tests. That worst-case result was on a slow Android 2 device. Cellular network speeds have gone up, but certainly not as much as mobile processor speeds, so if you re-did those tests today with modern networks and devices, it’s probably a net benefit to pull the jQuery once, then JIT it on each page load, as compared to making even a single extra round-trip per page load. > Processors aren’t getting any faster. That’s true on the server side as well. The article talks about externalized costs, but if you just shift the computing burden to the server, how do you pay for that? You could load the page with more ads, which eats up the network bandwidth and JIT savings you just bought by moving the processing to the server. Or, you could charge the users more than you currently do, which is economically little different than shifting the computing burden to the users, implicitly requiring them to buy faster mobile devices and better mobile data plans. Consider also that the number of bugs created per line of code is roughly constant for each pairing of developer and programming language, so who pays for the costs of the extra bugs you’d expect to find in 2-3x more LOC? TANSTAAFL. > JS-heavy pages…

Seems similar to this, which was posted here about 6 weeks ago: https://news.ycombinator.com/item?id=23985825 The linked site for this submission is branded/copyrighted Pluvior. The previous submission linked to the domain https://pluvoir.netlify.app (though this now redirects to a dedicated domain - rainbowhunt.com). The credits on the two sites look very similar: https://rainbowhunt.com/credits.html https://itsrainingday.netlify.app/credits.html On the previous submission, the author of the rain effect showed up to comment about their work: https://news.ycombinator.com/item?id=23987120 The only real difference with this submission is that it uses a different library for the rain effect; this one uses rainyday.js by Marek Brodziak instead - https://modernweb.com/creating-a-realistic-rain-effect-with-canvas-and… I don't think there's enough new/original work here to count as a new Show HN.