3 ms·
I think this is a good insight. It is about semantics -- how do you structure your program in a more functional way or how to you use immutable data structures
by rdtsc 12y ago
I think this is a good insight.
It is about semantics -- how do you structure your program in a more functional way or how to you use immutable data structures to model your domain, or do you use callbacks, or actors for your concurrency. Object oriented everything was a fad then functional everything is and so on. And while some languages are more opinionated about one way or the other, you can often structure or start to think in terms of different paradigms in most popular languages today.
At a higher level then you have to answer the questions of "Why do I want to structure my program with less global state?". Why does OO work well here?
Another point that is important to make I think is that languages are about the library ecosystem as well. There are plenty of cool research languages Alice, Oz, Curry [Haskell-like logic language] and others. But they lack a rich library ecosystem. So you go to build something and you find yourself writing the library ecosystem first. Which is instructive but not if you want to get to your goal of having a product first.
Then there is always the issue of syntax. I hear this about Erlang. Syntax is different, but I think that is not the hard part. If typing . instead of ; at the end of expressions is what kills it for you, what do you do with immutable data structures, and separating concurrent units of your code into actors. That is the harder and more interesting part.
I like Fred Hebert's idea here -- http://ferd.ca/on-erlang-s-syntax.html http://ferd.ca/on-erlang-s-syntax.html.