R
Ruben Dröge
Guest
I like the article, but reading the comments was even more interesting! In fact, they kind of proof the issues the JS world is facing at the moment which the writer has pointed out. No consensus whatsoever, some like standards, some hate them. Some want frameworks, some want libraries…hence the fragmented environment J From: agent_008_nl [mailto:bounce-agent_008_nl@community.progress.com] Sent: Monday, May 18, 2015 11:01 AM To: TU.Mobile@community.progress.com Subject: RE: [Technical Users - Mobile] jsdo built into a small framework RE: jsdo built into a small framework Reply by agent_008_nl Curious to see how the open source kendo components will fit in my framework! "Prefer dedicated libraries to monolithic frameworks. When you choose a framework, you make a large, long term committment. You sign up to learn about the framework's various inner workings and strange behaviours. You also sign up to a period of ineffectiveness whilst you're getting to grips with things. If the framework turns out to be the wrong bet, you lose a lot. But if you pick and choose from libraries, you can afford to replace one part of your front end stack whilst retaining the rest." "There will never be a perfect framework so you can just hack the most relevant features together. By using small libraries - components with a dedicated purpose and a small surface area - it becomes possible to pick and mix, to swap parts of our front end stack out if and when they are superceded. New projects can replace only the parts that matter, whilst core functionality whose designs are settled - routing APIs, say - can stay exactly the same between the years." www.breck-mckye.com/.../the-state-of-javascript-in-2015 Stop receiving emails on this subject. Flag this post as spam/abuse.
Continue reading...
Continue reading...