This is a great deck... but leaving TLA+ out of Formal Methods? It is hands down the most important thing going on there. And it is a combo between academia and industry. Amazon uses it extensively.
Near Future of Programming Languages [pdf]
41–50 of 306 posts
Re: Near Future of Programming Languages [pdf]
#42This could be titled "Static typing is not going to save you"? There's nothing but static typing languages and related theorem provers from the timeline slide onwards and the conclusion is that it's too hard.
This is a good companion piece for the recent Rich Hickey Clojure/Conj talk :)
Re: Near Future of Programming Languages [pdf]
#43TLDR The future of programming languages should involve not naming your language "Coq". I know I am going through the lowest common denominator, but how do you explain to your boss that you're proficient with using Coq. Ugh. Or professor, since apparently it's a proofing language for academia.
I would just pronounce it like "coke" and it would just sidestep the whole pronunciation issue. I'm not sure how most people pronounce it but that's what I would do to talk to my boss about it.
This is the precise reason why "route" is pronouced "root" but "router" is mysteriously pronounced "raow-ter". No-one's gonna stand in front of a room full of people and talk about the "rooter".
Re: Near Future of Programming Languages [pdf]
#44This is a great presentation, I wish I could hear the talk track.
While we can all differ on the right "winner" for the next programming language (I don't think Clojure is the right answer, someone else might), we are all stuck with the same set of facts - and this covers the state of things very well.
Most importantly, it explains certain truths of the social/economic ecosystem for programming languages - which is what gave us Java, Python, Javascript, and a few other really popular systems that seemed unlikely to succeed when they first appeared. The reasons for their success have just as much to do with "ecosystems" than with language features.
Re: Near Future of Programming Languages [pdf]
#45This could be titled "Static typing is not going to save you"? There's nothing but static typing languages and related theorem provers from the timeline slide onwards and the conclusion is that it's too hard. This is a good companion piece for the recent Rich Hickey Clojure/Conj talk :)
I don't really see where you get that. Is dynamic typing demonstrating a lot of sustainable success?
Re: Near Future of Programming Languages [pdf]
#46What people who do academic analysis of programming languages often miss is culture . So much about what programming language gets used has to do with what ecosystem it's been targeted at and what colleagues in that ecosystem are using.
I couldn't agree more and was just making this point to someone last week - for many of the well-established languages, 80% of the reasons to use or not to use them is the associated culture, from the qualifications of the average applicant to the prevailing approaches to solving problems.
Re: Near Future of Programming Languages [pdf]
#47TLDR The future of programming languages should involve not naming your language "Coq". I know I am going through the lowest common denominator, but how do you explain to your boss that you're proficient with using Coq. Ugh. Or professor, since apparently it's a proofing language for academia.
Hopefully you have a mature boss.
Does he let you use git? (Git is a mild insult in the UK)
Re: Near Future of Programming Languages [pdf]
#48Very disappointed not to see Cilk included.
Do you mean this Cilk? https://en.wikipedia.org/wiki/Cilk
Re: Near Future of Programming Languages [pdf]
#49TLDR The future of programming languages should involve not naming your language "Coq". I know I am going through the lowest common denominator, but how do you explain to your boss that you're proficient with using Coq. Ugh. Or professor, since apparently it's a proofing language for academia.
I would just pronounce it like "coke" and it would just sidestep the whole pronunciation issue. I'm not sure how most people pronounce it but that's what I would do to talk to my boss about it.
"I'm a coke user boss, have you ever tried it? If I have a hard problem it really focuses the mind."
Re: Near Future of Programming Languages [pdf]
#50TLDR The future of programming languages should involve not naming your language "Coq". I know I am going through the lowest common denominator, but how do you explain to your boss that you're proficient with using Coq. Ugh. Or professor, since apparently it's a proofing language for academia.
"Coq" means "Rooster" in French. Coq (the software) started development at INRIA (France) in 1984 as a small R&D project. I am not particularly shocked that the original developers did not realize the possible double meaning in another language, and being as dismissive as you are seems uncalled for. There are countless startups whose names in English mean something else entirely in another language. For example "Cocu…
I think the verge, could be translated from french as the rod ( and often used as a slang for this rod ).