The Blimp Tech Stack: Frontend

None of that makes a good argument for why you need to reconsider your frontend, it's just a list of cool libraries.<p>Developers like to try new technologies, and like to improve things and make their life easier (which often involves some form of re-write). This is natural. But does the new stack justify the time that was spent moving over?<p>I'm assuming it was worth it, but it would be nice to see something actually backing that up.

Why do you change the title when you post it here to be so provocative and arrogant? Linkbait?<p>"Why you need..." just sets you up for a negative reaction such as "who are you to tell me what I need to do?" and "what makes you think this is at all relevant to me?" and "what arrogance to think you have all of the answers for everyone"<p>The actual post you are linking to has none of the presumptive arrogance implied by the "why you need" titling and reads like quite a reasonable discussion of choices the author made that made sense for their particular requirements and environment. None of it applies to me and my situation, but I can read it with a much more open mind that I was initially inclined to based on the "why you need" language.

slightly off topic. I REALLY wish GetBlimp showed pricing on the site before signup. only thing i see is "start with our free plan, then prices start at $12" on the homepage, then signup page etc i have no idea what prices will rise to.

REST API bound simplistic and stateless frontends are easier said than done. Does anyone know a DRY way of achieving this. I like the AngularJS approach of keeping state(of DOM - a.k.a what the user sees) and let it flow. But still, as a Javascript noob, every library seems messy and unworkable :(<p>Any advice on this?

"You should try Angular"