hifier

This is not my experience. Companies with strong engineering organizations that are parallel with and equal to the product/business org structure would not have a product management bias. I would only work at a company where engineers are managed by other Engineers who are partners with the product and other business teams, not reporting to them. (I'm a Software Engineer).

I also think that engineers would be paid much better than product managers in such an organization, given the higher demand for engineering skills (there should be more engineers than product managers on any given team) and a smaller pool of potential hires.

"The new keyword was added to the language partially to appease classical languages, but in reality it tends to confuse developers more than help them. Instead, there are native ways in JavaScript to declare objects and arrays and you should use those instead."

Umm... what? Ever heard of constructor functions and prototypes?

...to be fair there is a small note on this at the end of the article, but this concept in javascript is far from secondary. It deserves more than a footnote. 'new' is not something to be avoided as implied here.

It would simply be a change in the templates that you use and how the changes are communicated to the client. It could still work the same way from the perspective that the changes are pushed to the client and the DOM is automatically replaced. The reason that I ask is that this could offload some of the server side processing to the client and also reduce the amount of data transfered over the wire. The server would be pushing JSON instead of HTML. From the dev's perspective you'd just be using a different templating framework. I wonder how the current implementation would scale, I imagine it would take some serious processing power to get to 100k+ concurrent, active users.

This looks really great. Does anyone have any thoughts on how this could be combined with client friendly templating so that the rendering of the partial could be done client side for updates, but server side for the initial page load?

I'm wondering if this is the mindset that most people have. The idea of putting you're entire personal dataset (and work dataset?) into a free service has always seemed terrifying to me. Especially one whose entire business model is based on using that data to serve you ads! I keep local copies of everything and backup daily. I don't trust anyone with such a complete picture of my digital life. 'The cloud' is overrated, at least the free, ad supported version is IMHO.

These kinds of questions are very different from questions about browser quirks. These questions get at the depth of understanding of the language itself. It is akin to understanding how a C++ program is going to use the stack and the heap, etc. Only after understanding the language fundamentals can you answer these questions and only then can you truly understand the code you are writing. With depth of understanding comes an ability to make better decisions about how and when to use and tool. Almost anyone can use jQuery, but writing it or something like it requires a different level of knowledge.

This is getting a bit off topic, but agreed it's a factor. My point is mostly about the mindset. You don't have to wait until some government prescribed age to do what you want. We make our own future.

Your ability to retire is tied to your financial situation. What does that have to do with the government?

Why let someone else prescribe your retirement age?!

This does not measure 600k concurrent active connections because each client only sends a request once every 5-45s. To see how many concurrent active connections you can support you need to understand how much RAM each connection consumes and how much RAM is available to your application.