I was thinking the same thing. The impact _why left on ruby is one of the things that make it such a unique language with interesting and weird projects like this. I love it.
This is great. It's nice to see an article from someone who doesn't "do" TDD, but also isn't ranting about how tests are useless. I personally use and prefer (test-first) TDD but still agree with all of the advice in this article.
If you just handle the client side part, you don't really need to learn any of it. If you do need to get into the server-side, Elixir/Phoenix seems like a great fit if you are doing real-time/concurrent stuff (websockets are dirt-simple). If you just need a persistent storage backend, RoR or Django will get you up and running quickly, and both are adding their own websocket support as well.
I don't think this wiki page is intended to show specific examples. But here's one I really like that isn't a typical MVC web app: https://www.youtube.com/watch?v=XHnuMjah6ps
The process he's using there falls in line with the higher-level experiences described on the wiki.
I like that it flips the usual look of bootstrap. Colors and sharp flats instead of grays and depth/shadows. It's not immediately obvious this is a bootstrap layout like with most.
