1,958 karma · joined June 26, 2011
Given the improvements in ES6, the fact that the JS community in general is so active, and the fact that I've seen some truly awful TS code (mainly where the devs want to pretend the web doesn't exist) I've been put off exploring TS too far much (beyond looking at the basic language features).
I'm not sure if I should be rethinking though?
Temporal coupling aspect I also find to be misleading, you can for instance use an ATOM feed (or equiv) to record events, its then up to clients to use them as appropriate.
Was wondering what you mean by that (not disagreeing just interested)?
Don't forget he was part of the REST/ROA group who were belittled when they said that Web standards were an alternative to the ridiculous number of Web Service standards and he was quite right in that case.
Rails is also a bit of a special case I think, it was a massive ecosystem that dominated the community it was in. That isn't true of any JS client-side framework right now so choosing one isn't necessarily a sensible investment when you look 3+ so years out.
Agreed that is an advantage of frameworks, but is it not more of an argument for a mature framework like Rails, rather than the current JS frameworks which appear and become (essentially)obsolete/niche in a year or two?
Something like React bothers me far less as it smaller, less imposing, and solves real problems I've seen with other frameworks (for example by pushing clear/consistent/simple communication paths).
"The fundamental idea is that frameworks aren't needed, use the capabilities already built into HTML+CSS+JS to build your widgets. Break apart the monoliths into orthogonal components that can be mixed in any combination"
Also this is a man with a very rich history in terms of the Web and Web standards so writing him off without giving what he is saying any real attention seems silly.
Wait, what....
I honestly think the framework enforcing architecture idea is more of an anti-pattern, even if you do use a framework you need to keep in mind that it wasn't built directly to fit your needs and that you may want/need to move in 6 months or a year.
I'm also not sure the utilities libraries will be copied from project to project, for example if you developed a utility library and were using Ember its quite likely the Ember abstractions would have impacted the library design. If you then move to say React..
"These frameworks work well for highly interactive apps with complex user interface requirements. We only needed a small piece of what a full framework would offer."
As you say its a tradeoff...
Agree socks might not be 100% clean but you have to draw the line somewhere, and the bottom of a sock is bound to be cleaner than the bottom of a shoe.
It is odd that whilst we use specially designed water jets and cleaning products to bathe our approach to bottom hygiene is just to keep scrubbing till there is nothing visible left.
Anyway looks like a good device, thanks for the link.
Its more that she doesn't even know what a surgeon does but thinks you can train a surgeon up in a day.
What with the homophobia and corruption scandals I doubt that's even possible anymore.