3 ms·

Oh, you think I'm just pushing for Java. I'm not. I'm saying having one language is better than 100. People can't share code very well if there's so many langua

Oh, you think I'm just pushing for Java. I'm not. I'm saying having one language is better than 100. People can't share code very well if there's so many languages. Languages themselves don't need to be completely reinvented like things in the real world (cars, etc). For example C/C++ has been around for decades and no one ever said "Burn it all down and start over."

rottc0dd 6y ago
I am a noob and I am happy to be corrected. Every language is designed with a specific design decisions and tradeoffs intended for hopefully wide audience. I think C and unix culture reflects this in some way. It is home grown environment by handful engineers working initially their own sake. You cannot objectively say, "Everything as file" is good concept, but if you are just handful of people tackling myriad of problems, it should have been liberating to have a too simple of an abstraction. It might be pile of hacks on pile of hacks but, it worked for the time. Whether it is good or bad, depends on what you want to achieve. I think more communities can benefit from more focus on what they are and how they want to do things than trying to be "be all, do all" thing. I might not want to solve problems the way somebody else would solve the problem and I would use a tool to best fits my way of thinking. Even if there is only one language, fragmentation is inevitable. Because, all people might not have the same way of working or thinking. Even if it is written in same language, one might not understand idioms of somebody else. It is easier to read a language with community adopted idioms, than a language that is made for all people. I have been using Java, but the erlang concurrency primitives looks great. But, it would be hell, if single code base has all possible primitives and style. Asking people to have one language to work is not different from asking people to think in one single way. Edit: added couple more rants.
- dgb23 6y ago
  I think this one of the important, good reasons. Others range from NIH to runtime considerations to strategic ones.
necovek 6y ago
> Languages themselves don't need to be completely reinvented like things in the real world Why not? And why things do "in the real world"? The fact that languages should evolve (and that they do) is not in opposition to a need or desire for new languages.

rottc0dd 6y ago

I am a noob and I am happy to be corrected. Every language is designed with a specific design decisions and tradeoffs intended for hopefully wide audience. I think C and unix culture reflects this in some way. It is home grown environment by handful engineers working initially their own sake. You cannot objectively say, "Everything as file" is good concept, but if you are just handful of people tackling myriad of problems, it should have been liberating to have a too simple of an abstraction. It might be pile of hacks on pile of hacks but, it worked for the time. Whether it is good or bad, depends on what you want to achieve. I think more communities can benefit from more focus on what they are and how they want to do things than trying to be "be all, do all" thing. I might not want to solve problems the way somebody else would solve the problem and I would use a tool to best fits my way of thinking. Even if there is only one language, fragmentation is inevitable. Because, all people might not have the same way of working or thinking. Even if it is written in same language, one might not understand idioms of somebody else. It is easier to read a language with community adopted idioms, than a language that is made for all people. I have been using Java, but the erlang concurrency primitives looks great. But, it would be hell, if single code base has all possible primitives and style. Asking people to have one language to work is not different from asking people to think in one single way. Edit: added couple more rants.

dgb23 6y ago
I think this one of the important, good reasons. Others range from NIH to runtime considerations to strategic ones.

necovek 6y ago

> Languages themselves don't need to be completely reinvented like things in the real world Why not? And why things do "in the real world"? The fact that languages should evolve (and that they do) is not in opposition to a need or desire for new languages.