Re:Announcing Azure Command-Line Interface 2.0 Preview
by dragonwriter on Tuesday September 27, 2016 @06:16PM
(#12593683)
Node.js wasn't built for baby devs, it was built for professional devs who had to use JS anyway because browsers to be able to use the same technology on the back-end rather than using different languages front- vs. back-end.
[ Parent
| on HN ]
Re:Announcing Azure Command-Line Interface 2.0 Preview
by mhuffman on Tuesday September 27, 2016 @10:08PM
(#12594911)
There is this radical idea in software development that sometimes you use the language that is best for the job -- not just the one you are already using!
Re:Announcing Azure Command-Line Interface 2.0 Preview
by WayneBro on Tuesday September 27, 2016 @10:11PM
(#12594925)
Right...but it still wasn't built for people who do not know how to program very well. It was written for JavaScript programmers. Nothing else really needs to be said other than that.
Re:Announcing Azure Command-Line Interface 2.0 Preview
by mhuffman on Wednesday September 28, 2016 @10:05AM
(#12597663)
Well I disagree. It was written as a limited browser scripting language in 1992. I was never meant to be a full-blown development language. So, I guess that needed to be said ...
Re:Announcing Azure Command-Line Interface 2.0 Preview
by WayneBro on Wednesday September 28, 2016 @05:35PM
(#12601557)
OK but I was talking about Node, not JavaScript.
You certainly cannot say that JavaScript was NEVER meant to be a full-blown development language though because now it is since it has grown into that overtime. Just because it wasn't originally conceived as such does not mean anything. The same thing happened with BASIC and Visual Basic. It doesn't mean anything.
It's like saying that wheels have no value because the original wheel was never meant to be used in autonomous cars.
Re:Announcing Azure Command-Line Interface 2.0 Preview
by mercer on Thursday September 29, 2016 @04:22AM
(#12603948)
While I agree that it wasn't created for 'baby devs', wasn't the primary reason for Node.js' creation that Ryan Dahl wanted an async ecosystem/platform, and javascript had the 'advantage' of not already being used server-side, so there would be no confusion over sync/async libraries/modules?
At least that's what I recall from reading/watching the initial videos back when it was released. At the very least I've never heard the 'same language front and back' argument until later on in Node's life.
But perhaps I misremember?