4 ms·

I've never really understood the "one langauge" argument. I'm a good (not great) front-end JavaScript programmer, but I don't think that helps writing node.js.

I've never really understood the "one langauge" argument. I'm a good (not great) front-end JavaScript programmer, but I don't think that helps writing node.js. Sure, the syntax is technically the same, but the bulk of a node.js program looks and is written quite differently from front-end js (even js library writing). Surely having similar syntax (which is basically C-like anyway) isn't that big a deal?

jomamaxx 10y ago
"I've never really understood the "one langauge" argument. " Being able to do front-end and back-end in js is really nice, especially passing data back and forth in js-object like format. If you have not tried it, do so, I feel it does streamline things nicely. Node.js is a little lighter than most things and if you use it correctly I think it has advantages. I wouldn't build a bank on it however :)
- collyw 10y ago
  You can pass JSON using Python, or pretty much any server side language.
  - jomamaxx 10y ago
    Of course you can. But in some languages it's a pain. And you can't do python on both ends. Using JS on both sides is nice if the architecture is suited for it.
lugg 10y ago
The one language argument, as far as I can tell began when people tried to share code across the server and the front end, it sort of worked for one persons use case but nobody else really had much success with the endevor (at least that I'm aware of.) That argument is a pretty bad one and is the one most people like to assume people are talking about so they can make fun of it. The real argument, at least in my mind is that you can specialise and pretty much run your entire stack completely in js with only a bit of json and some html. Build tools, database access, deploy tools, dependency management, server side code, client side code, its all JS. For me, I don't agree that it matters, I don't even think having a diverse stack takes much longer to learn. But I do understand the fanfare for it.
jtolmar 10y ago
It's supposed to mean you can share object declarations. But it's javascript so that doesn't mean much. And it's not like the data format in the database and the gui is ever the same by the end of a project anyway, so two formats end up being needed anyway, so it's a bit of a pipe dream. The one case I've found where node really makes a lot of sense is if you're trying to build a webapp with a native version using the same code. Then node-webkit is the only game in town that doesn't involve a transpiler. Then again, the component parts are flaky enough that maybe the transpiler isn't so bad afterall.
humanrebar 10y ago
It seems like an appeal to hiring manager to me. "You'll have all the developers you need! Look, it's all javascript and everyone knows javascript!" The problem is assuming language proficiency is the defining characteristic of a developer. We really need to disabuse management of that idea. I'd rather teach a good 'microservice developer' javascript than teach a good 'javascript programmer' what makes a good microservice.

jomamaxx 10y ago

"I've never really understood the "one langauge" argument. " Being able to do front-end and back-end in js is really nice, especially passing data back and forth in js-object like format. If you have not tried it, do so, I feel it does streamline things nicely. Node.js is a little lighter than most things and if you use it correctly I think it has advantages. I wouldn't build a bank on it however :)

collyw 10y ago
You can pass JSON using Python, or pretty much any server side language.
- jomamaxx 10y ago
  Of course you can. But in some languages it's a pain. And you can't do python on both ends. Using JS on both sides is nice if the architecture is suited for it.

lugg 10y ago

The one language argument, as far as I can tell began when people tried to share code across the server and the front end, it sort of worked for one persons use case but nobody else really had much success with the endevor (at least that I'm aware of.) That argument is a pretty bad one and is the one most people like to assume people are talking about so they can make fun of it. The real argument, at least in my mind is that you can specialise and pretty much run your entire stack completely in js with only a bit of json and some html. Build tools, database access, deploy tools, dependency management, server side code, client side code, its all JS. For me, I don't agree that it matters, I don't even think having a diverse stack takes much longer to learn. But I do understand the fanfare for it.

jtolmar 10y ago

It's supposed to mean you can share object declarations. But it's javascript so that doesn't mean much. And it's not like the data format in the database and the gui is ever the same by the end of a project anyway, so two formats end up being needed anyway, so it's a bit of a pipe dream. The one case I've found where node really makes a lot of sense is if you're trying to build a webapp with a native version using the same code. Then node-webkit is the only game in town that doesn't involve a transpiler. Then again, the component parts are flaky enough that maybe the transpiler isn't so bad afterall.

humanrebar 10y ago

It seems like an appeal to hiring manager to me. "You'll have all the developers you need! Look, it's all javascript and everyone knows javascript!" The problem is assuming language proficiency is the defining characteristic of a developer. We really need to disabuse management of that idea. I'd rather teach a good 'microservice developer' javascript than teach a good 'javascript programmer' what makes a good microservice.