Rather than quibbling over syntax, I'd like to comment on a real concern I have about blogs, particularly ones that engage in hagiographies on things they don't appear to rightly understand. Nota bene: I am a user of Flask and have been one for quite some time. I am incredibly fond of it and it has replaced Django for most things I do in web dev. I am very familiar with it and its limitations/ugly corners. Familiarit…
I think this is a very valid point, and it comes up quite frequently in comparison of frameworks and libraries. One example that was annoying me recently was in trying to select a Javascript client-side MVC (MVVM, etc.) framework for a single-page application. The internet is full of people busily comparing, contrasting, arguing about, and recommending JS frameworks. Problem: 95% of them are doing so based on a No re…
I feel your pain on figuring out which JavaScript SPA framework to use. I don't think I've seen any particularly compelling examples in public of even Backbone.js, which is currently the most popular one to use. The templating and sync semantics aren't appealing.
And yes, some of my proudest moments, too, have been making a The hairy problems are when the rubber meets the road and whether or not the solution I've built on is going to be appropriate or not. Those are going to be >100 line of code problems.
I have to be able to build things of at least moderate complexity with a framework without blood gushing my eyes and ears.
The superficiality of this non-content makes my spleen rupture.