1 karma · joined December 28, 2011
When you fully understand how your existing app performs (and why it performs) you may start making informed decisions.
Profiling is a highly technical art that is beyond even most competent programmers. You need a good systems engineer who is proficient with the tools used to examine application performance on your system, and understands the different technology stacks involved (networking, disk I/O, cpu/threading/scheduling, virtual memory etc.). If you can reproduce the problem, they should be able to pinpoint the cause.
Also, you may want to read up on Node.js and understand what benefits it brings to the table - it is not a silver bullet that solves all Web application problems.
The basic line is something like "if it has been well engineered, and someone has put a whole lot of effort into it, and its a bit different to everything else out there, then we are basically obliged to give it high marks".
They seem incapable of judging devices by the most basic and important standard: user experience. If the user experience is bad, then nothing else matters. A user interface is not brilliant if no one wants to use it.
WinPho7 is the best current example of this going round. Almost universally acclaimed by reviewers, almost totally ignored by consumers.
Facebook is full of human beings sharing their lives - Google+ is full of jerks who see Facebook as an API. Friend that? No thanks.