322 karma · joined August 13, 2011
Email: myhnusername@gmail.com
b3d7f93183685bb05f58b1553eb90aab38ba623ab3a6208a4d76d808b1825bf4
FYI, Bootstrap Tour also has the "element highlight" feature. It's called "backdrop".
I'm 27 years old from West Africa.
lodash is the only one to be performance focused. underscore always uses the native methods when possible.
It will be per install. I just put that price as a baseline. It will be adjusted depending on the needs and use cases. If you would like to talk about it in depth, shot me an email.
It's AGPL. The commercial licenses are for people or companies who may want to modify it without releasing their modifications back to the community. If they don't want to contribute their code, they will at least contribute financially.
- Comparing template engines only (with the riot solution having less features) doesn't give a complete picture for comparing speed. There are dozen of other parts to make a web app. The template is only a small part. Benchmarks aren't even a good way to compare speed. It's how the user feels when using the resulting app and interacting with the UI that matters.
- TodoMVC is a very small app for comparing productivity. E.g. your router implementation doesn't take into account IE bugs, and researching such bugs instead of using a proven solution can be less productive.
I agree with you that modular and maintainable web apps can be developed with jQuery only, and even plain JavaScript only. I dislike, as much as you do, "Backbone developers", "AngularJS developers", "Ember.js developers", etc. who can use only one framework, can't properly structure an app without using a framework, and claim that the framework they use is the only good one to solve any problems and build any type of app.
A good developer should be able to choose the proper solution for a particular problem. There's no one size fits all solution for every problem.
> Current frameworks persuade false beliefs with shiny websites and finely crafted marketing without transparent, scientific analysis. They solve hypothetical problems and cause new problems instead. Unfortunately, large communities are dealing with irrelevant issues.
You're telling jashkenas (indirectly) that he "persuade false beliefs", "without scientific analysis", that he's solving "hypothetical problems" and "dealing with irrelevant issues" and plenty of other things like that... and what response do you expect from him?
> I was hoping you were closer to a scientist.
You already told him he's not a scientist, see above.
P.S.: I don't follow any "religion". I use framework or plain JavaScript depending on the project, and I find it sad when anyone promotes their solution as the only good one.
> To do this, Assembly must keep and manage all intellectual property derived from Assembly apps. In exchange for that ownership, we give you perpetual income based on the extent of your contribution to all projects you work on.
The OP is speculating about the future and the flaws you cite are valid now, but will they be valid in the future? What prevents iOS from getting improved multitasking in the future? Phone/pads don't have enough RAM or cheap storage now. What prevents them from getting that in the future?
The OP wrote "Jump forward in time to a year from today.". You're trying to see fanboyism where there's none (or at least not as much as you want to believe).
If Canonical could promise something similar to what the OP described with that famous Indiegogo campaign, don't you think it may be possible for Apple to do that for the next iPhone/iOS release?
Version 3 is very modular. You can compile the LESS files yourself and include only what you need.