How do you select features for inclusion in a new programming language? You certantly won't skip something that every other programming language already has. But, how did it work when there weren't so many languages to look at? and how did it work if a language was not designed by a single author or a small team, but by an international committee?
If the collective noun for a group of programmers is a "merge conflict", the noun for a group of people with the same goal is "team". "Committee", on the other hand, is a group of people that say to have the same goal, but has a personal idea of what it means. Let's know a little history least we repeat it.
I'll give you intrigue, academy vs industry politics, subterfuge, international phonecalls, philosophycal debate and semantic differences: all of that and more in The Amsterdam Plot!
If the collective noun for a group of programmers is a "merge conflict", the noun for a group of people with the same goal is "team". "Committee", on the other hand, is a group of people that say to have the same goal, but has a personal idea of what it means. Let's know a little history least we repeat it.
I'll give you intrigue, academy vs industry politics, subterfuge, international phonecalls, philosophycal debate and semantic differences: all of that and more in The Amsterdam Plot!
Michele Mauro
Aton SB
A passionate developer from more years that I'm willing to admit, I've seen computers, software, tools and methods of many different sizes. Some of them I recall fondly, some I try to stay very away from. Since I love to talk and hear others talk about computer science and programming, I've been to many conferences, user groups, university classes and meetups, and spoke in some of them about my experiences and opinions. I usually work in Java and Kotlin, and had the luck of writing some Scala in the past. I am happy the most when my work makes others work less and better.
Browncoat, Kitsune, ☂, He/Him.
Browncoat, Kitsune, ☂, He/Him.