4 ms·
For small ad-hoc multi-processing servers that web shops are writing. Maybe, that seems like a good use case. Not as exotic as Erlang, and not a very demanding
by mhd 14y ago
For small ad-hoc multi-processing servers that web shops are writing. Maybe, that seems like a good use case. Not as exotic as Erlang, and not a very demanding environment.
No big chance for enterprise or academia. And I believe that for ordinary "check this, forward that" backend programming, Ruby, Python and Perl will still remain staples, with a few percentage points shifting back and forth, as usual. Rails didn't end Python.
On the other hand, I wouldn't shed a tear if it would eat up the majority of node.js' marketshare.
- eckyptang 14y agoEnterprise here. We're knocking huge monolithic applications sitting on CLR and JVM processes into greater numbers of smaller stand-alone components (SOA style). Go fits here very well indeed. Our authentication, filestore, directory services, messaging and web front end are all easy targets.