4 ms·
"However, I hope people consider carefully the social costs of creating a new programming language especially if it becomes popular, and understand that in some
by michaelmrose 8y ago
"However, I hope people consider carefully the social costs of creating a new programming language especially if it becomes popular, and understand that in some cases creating a popular new language could actually be irresponsible."
Passion isn't fungible and there is zero gauruntee that the person who creates an interesting new language wouldn't have chosen to binge watch Netflix instead.
Furthermore without a crystal ball it's difficult to separate ahead of time which efforts will move us forward in some small or large ways.
The entire premise of this post is flawed.
- jacquesm 8y ago> it's difficult to separate ahead of time which efforts will move us forward in some small or large ways. That's the point: most efforts do not move us forward but instead move us backwards because fewer people are working on the things that matter. It's a solid argument and it applies to far more of the open source community than just to programming languages, in fact programming languages are the smaller part of the issue, but the argument still applies. > The entire premise of this post is flawed. I don't think so. I would not dismiss an article without at least trying to make a genuine effort to understand the point an article makes. The fact is that it takes effort to launch a new programming language beyond just writing some code and the long term commitment should be there if you are going to let other people run their production systems on what you throw into the world. This doesn't mean you don't get to scratch your itch, it means that once your programming language gains adoption beyond some people playing around with it you can't just walk off and say that it isn't your problem. Oh, and it is 'guarantee'.
- a_imho 8y agoThe fact is that it takes effort to launch a new programming language beyond just writing some code and the long term commitment should be there if you are going to let other people run their production systems on what you throw into the world. From my admittedly limited knowledge JavaScript seems to contradict this claim. I don't agree with the article either, one could make the same argument for every piece of new code written.
- fnord123 8y ago>I don't agree with the article either, one could make the same argument for every piece of new code written. No you can't. The issue is that languages generally have their own runtime and object linkage system. If you create a new one that doesn't play nicely with C linkage/runtime, JVM, .Net, or compiles down to javascript (or wasm) then you are creating an entirely new platform and this creates the fragmentation. For example, Python and Rust play nicely with C linkage. Scala runs on the JVM. These play nicely with other systems. You can have Python code that calls Rust code that calls C code and it all fits together. But you may struggle to have Python code calling Lua code calling Julia code. "every piece of code written" doesn't have this problem at all. If you write something in an existing language then you are contributing to that ecosystem instead of making a new ecosystem. And if you are making a new ecosystem, for pity's sake please consider making that ecosystem play nicely with at least one existing ecosystem.
- jacquesm 8y agoJavaScript is a pretty good example of a language that overshot its goal and that would have benefited from evaluating the cost of its release. It was put together in a hurry, without much in terms of forethought and we're paying the price every day. > I don't agree with the article either, one could make the same argument for every piece of new code written. So you do agree. Yes, you could make the same argument for every piece of code, and that's precisely the point, the author chose to use programming languages where the problem is the the least visible. But that does not invalidate the point, it strengthens it.
- deleted 8y ago[deleted]
- hvidgaard 8y ago> the long term commitment should be there if you are going to let other people run their production systems on what you throw into the world If you adopted a language that is not mature for production, then you knew the risk when you made that choice. Innovation in PL happens with these small languages, and it's a good thing.
- jacquesm 8y ago> If you adopted a language that is not mature for production, then you knew the risk when you made that choice. True, but at the same time I can't help but think that a few hundred programming languages are all equally useful and all equally deserving of their continued existence. > Innovation in PL happens with these small languages, and it's a good thing. I do not see the author as having any beef whatsoever with 'small languages used for innovation', I think he has a beef with small languages that pretend to have staying power behind them when in fact they do not. Quite a bit of this stuff is people experimenting and making a 'me-too' version of something, and I have done this many times myself. But once you release a thing like that into the world you should be ready to step up and commit to it. If not then you might as well keep it to yourself.
- michaelmrose 8y agoThe best test of staying power would be longevity and engagement by a large community. If a new language lacks either it is obviously far more likely to cease to exist a few years from now. It's hard to pick unproven future winners fortunately you don't have to do this. Use what you know works.
- Razengan 8y ago> things that matter. Very, very subjective.
- delhanty 8y ago>it means that once your programming language gains adoption beyond some people playing around with it you can't just walk off and say that it isn't your problem Assuming that you don't work for them and that you don't have a contract for support with them, then why can't you just walk away? In fact I'd go further: it would be healthy if people that needed support for open-source got used to the idea of paying for it.
- jacquesm 8y ago> Assuming that you don't work for them and that you don't have a contract for support with them, then why can't you just walk away? The ability to do something does not always correlate with morality.
- delhanty 8y agoWhich is more immoral, A or B? A. An unpaid programmer choosing to walk away from their open-source project. B. The world's richest companies running their production systems on open-source, but failing to adequately fund development. Here's the best example: OpenSSL and HeartBleed up until 2014 [0]. >Tech giants, chastened by Heartbleed, finally agree to fund OpenSSL > IBM, Intel, Microsoft, Facebook, Google, and others pledge millions to open source. > >... > >Steve Marquess wrote in a blog post last week that OpenSSL typically receives about $2,000 in donations a year and has just one employee who works full time on the open source code.Given that, perhaps we shouldn’t be surprised by the existence of Heartbleed, a security flaw in OpenSSL that can expose user passwords and the private encryption keys needed to protect websites. [0] https://arstechnica.com/information-technology/2014/04/tech-giants-chastened-by-heartbleed-finally-agree-to-fund-openssl/ https://arstechnica.com/information-technology/2014/04/tech-...
- jacquesm 8y agoI think there are quite a few more choices available than your 'A' and 'B'.
- 8y ago
- jasode 8y ago> I would not dismiss an article without at least trying to make a genuine effort to understand the point an article makes. And likewise, you didn't seem to understand michaelmrose's points and your reply didn't address his specific criticisms of the article and how it has 2 flaws. To me, your restatement has repeated the same 2 flaws: >most efforts do not move us forward but instead move us backwards because fewer people are working on the things that matter. It's a solid argument It's not a solid argument and the 2 flaws in O'Callahan's essay are: (1) Post hoc analysis flaw: Judging what moves us "forward" vs "backwards" is post hoc analysis. It requires a time machine. In reality, we always live in the present moment, and therefore, we can't know what inconsequential things today will eventually be a net benefit to society tomorrow. (2) Fungible & zero sum flaw. That a human interest level in any given activity is fungible and therefore zero-sum which supposedly takes away from other more worthy things. To apply the flawed thinking to the C Language, we would have to transport ourselves back to 1972 and O'Callahan would then criticize Dennis Ritchie for "inventing yet another language and fragmenting the landscape". Instead, D.R. should have focused his effort on languages that already existed like Cobol (1959) and Lisp (1958). Well, if Dennis Ritchie was not intellectually interested in enhancing the older ecosystems of Cobol and Lisp, it's a moot point. Imagine taking all those "Shown HN" posts of new programming languages[1] and lecturing people that they should have focusd their energy on existing "more important" things such as the broken C code in Heartbleed OpenSSL. That advice would be naive about human nature. Many people aren't interested in working on the OpenSSL codebase. If one believes that "video games" are a waste of time, it's flawed to assume that a programmer's 1000 hours on a "useless" game engine could have been redirected on developing algorithms for DNA analysis or writing code for a government healthcare portal to help the nation's citizens. Motivations matter. Similar arguments can be made for scientists choosing to working on particular problems in physics, math, and engineering. E.g. It was a "waste of time" for Andrew Wiles to work on Fermat's Last Theorem when "P=NP" is the "more important" problem. Well, the he worked on it because Fermat's problem fascinated him since he was a little boy and "P!=NP" didn't grip him in the same passionate way. > and the long term commitment should be there if you [...] , it means that once your programming language gains adoption beyond some people playing around with it you can't just walk off and say that it isn't your problem. I just wanted to note that this particular opinion of "language inventor's ongoing commitment required" was not stated in O'Callahan's essay. [1] https://hn.algolia.com/?query=show%20hn%20programming%20language&sort=byPopularity&prefix=false&page=0&dateRange=all&type=story https://hn.algolia.com/?query=show%20hn%20programming%20lang...
- michaelmrose 8y ago> This doesn't mean you don't get to scratch your itch, it means that once your programming language gains adoption beyond some people playing around with it you can't just walk off and say that it isn't your problem. Why not? You display a lack of perspective that is similar to the author of the article you confuse what would be convenient and useful for you personally with a universal good. If would be good for you if people who gave you free tools acquired a commitment to continue to support and grow these tools without a contract or cash but there is no particular reason this ought to be so. Even if you want to pay there is even no reason why anyone has to be willing to take your cash if they aren't inclined to sell you their labor. Try going to walmart and seeing if you can buy the cash register. Similarly the original author believes that if more people just worked on fewer projects that he prefers these projects would be better. This ignores the fact that historical progress including the projects he prefers have benefited from a chaotic environment where people work on what they not the author prefer.
- im3w1l 8y agoTo be the devil's advocate (as in I don't really hold this position but would like to see it debated): Maybe we would be better off if people watched Netflix instead.