1,115 reputation
510
bio website adaptivepatterns.net
location
age 35
visits member for 1 year, 10 months
seen Mar 3 at 16:25

Just following the worldwide JSRenaissance.


Jan
17
comment Is JavaScript “write once run everywhere”?
Interesting, Palm OS - isn't that Web OS in LG TVs now...
Jan
17
comment Is JavaScript “write once run everywhere”?
Isn't JavaScript independent of the DOM?
Jan
8
comment Is there a good reason to avoid node.js for non-realtime web apps?
-1 - Subjective points. "Preferred Syntax", "Documentation not as good", "Obsessive Callbacks", and "Already Done in my language" - are all vague and subjective. We've heard these before. They are debunked. No reason to avoid Node.JS here. Downvote.
Jan
8
comment Is there a good reason to avoid node.js for non-realtime web apps?
+1. Human Resources - and the unwillingness of some to learn JavaScript - is an inconvenient truth. This answer states it well. But, avoiding Node "because people Hate JavaScript" is not the logical progression either. Where would we be technically if we avoided every innovation - that someone else hated? Nowhere. The challenge with node is A) Getting new talent, or B) Educating traditional talent into new talent. To that point - we are seeing JavaScript code schools pop-up everywhere since John Resig's foresight in founding Khan Academy. In short, this is the way of things. +1. Well stated.
Jan
8
comment Is there a good reason to avoid node.js for non-realtime web apps?
-1. I agree this answer will not be valid in 2015. But that is also reasoning for downvote.In essence - the decisions of today ARE the decisions for tomorrow. It nullifies the 8 bullet points above - if we can see that they are only temporarily relevant. 1)Scaling - Walmart Mobile scales, not a reason to avoid Node. 2) Isomorphic JS is no joke. Not a reason. 3) Server Sexyness? Most users know only ux. 4) Best practice is subjective, 5) Not Hot? -subjective 6) Easier? -subjective. 7) Stability is a temporarily relevant point. 8) NPM projected to pass Maven in 2014. No reasons here. Downvote.
Jan
8
comment Is there a good reason to avoid node.js for non-realtime web apps?
+1 - the notion of node.js as a server-side proxy ('in conjunction with traditional web server') gained traction earlier this year and is worth looking into - especially if you have a large traditional architecture to manage. It is a design pattern that seems to make sense for the enterprise. But, it is worth noting - this is not a reason to AVOID Node.js but a reason to use it for specific purpose.
Jan
8
comment Is there a good reason to avoid node.js for non-realtime web apps?
-1 vague. 1)Just because you have N years experience in X - does not mean you should avoid Node.JS. Are you proposing willful ignorance based on experience? And what are the "Generic reasons"? 2) 'other applications that let you write a generic application faster' - is purely subjective. 3) 'other *than "*I hate *JavaScript' - is also subjective and not a valid reason to avoid a flourishing technology. *spelling.
Oct
6
comment How to have a maintainable and manageable Javascript code base
+1 I've also heard buzz on Steal.js. And thanks for the insight on it.
Oct
6
comment What should someone learn to become a great web-app builder by 2015
+1 Well said. JavaScript is being used to write so many layers of the stack, it is hard to think it would not be applicable in the future.
Oct
6
comment What should someone learn to become a great web-app builder by 2015
+1. Agree completely. Go look at their examples. If you can set up one, you can set up all. Very robust.
Sep
24
comment Why is there a large discrepancy between the stackoverflow tag frequency and the TIOBE Index?
Fair enough and yes I agree to that point. My thoughts were to the notion of "most used". Please cite that source. And to "Schools drop C++...Java...trend." Amazingly, Khan academy (John Resig) starts a CS101 in JS and it is impressive. Those were the differences. All the best!
Sep
23
comment Why is there a large discrepancy between the stackoverflow tag frequency and the TIOBE Index?
-1. I disagree. First paragraph is arguable. Check out Khan Academy and this: redmonk.com/sogrady/2012/09/12/language-rankings-9-12 I was in C for years, converted to JS.
Sep
20
comment Multiple attribution in Python, JS, …?
Please include code example.
Aug
30
comment Rush to client-side in web development
Tell me. Is JS in Windows 8, hype? -1. I agree with first point, but your second point on hype, needs clarification.
Aug
30
comment What to do when projects are slow and you are being held up by others?
+1 LEARN. Well said.
Aug
26
comment Rush to client-side in web development
Yes Sir, server-side frameworks promise the same benefits, yes. What needs to be known is that there are additional benefits, found unexpectedly, in emerging technology. It is at the lowest level (c) in the io. The threads wait. In JS it has a callback. It does not wait. So there is an io optimization at the lowest level. This realization is now, quietly, adopted in a large way by Microsoft. Which is why their OS is JS. Final point, this yields optimization and meta optimizations - at all levels. Because the language is flexible. A simple-invisible thing. Not known. Hope that helps.
Aug
25
comment Rush to client-side in web development
What, hype? -1 Good luck with that when Windows 8 makes JS a first-class citizen. Yes, server-side UI architecture written in node.js maybe. We need to learn it because it is non-blocking.
Aug
25
comment Rush to client-side in web development
hard truths... +1.
Aug
25
comment Rush to client-side in web development
Well said... +1.
Aug
25
comment Git workflow / practices for a small project (flowchart in png)
+1 OMG! - Beautiful!