What will programming look like in 2020? (2012)
lambda-the-ultimate.org
What will programming look like in 2020? (2012)
1–10 of 151 posts
Re: What will programming look like in 2020? (2012)
#2Re: What will programming look like in 2020? (2012)
#3https://web.archive.org/web/20210925211554/http://lambda-the...
P.S. these are predictions made in 2012 of what 2020 was going to be like.
Re: What will programming look like in 2020? (2012)
#4Re: What will programming look like in 2020? (2012)
#5Server has apparently fallen over. Wayback Machine link: https://web.archive.org/web/20210925211554/http://lambda-the... P.S. these are predictions made in 2012 of what 2020 was going to be like.
Re: What will programming look like in 2020? (2012)
#6I think mostly we do have gone in that direction, even if probably even slower than the (already cautious) commenter predicted.
Honest question: why are we as a community so slow at evolving a good, solid programming environment?
I get that each time a new language is introduced, porting over all the existing code + training the people is an immense task. But this is _exactly the problem_, right?
Why aren’t we able to stop for a while and sort out once and for all a solid framework for coding?
It’s not a theoretical ideal: I’m very convinced that the dumb piling up of technologies/languages/frameworks that we use now is significantly slowing down the _actual daily work_ we do of producing software. Definitely >>50% of my time as a programmer is spent on accidental complexity, that i know for sure.
It’s very practical: at this point this whole thing simply feels like very bad engineering, tbh?
Re: What will programming look like in 2020? (2012)
#7No one mentioned containers or anything related.
Re: What will programming look like in 2020? (2012)
#8Looking back, the biggest changes between now and 2012 are:
* Git (and github) took over the world in the version control. Git was already the leader in 2012, but mercurial was doing ok and svn was still around to a much greater extent.
* Docker/Kubernetes and the container ecosystem. There was a guess here about app servers, but the poster seemed to thinking of PaaS platforms and Java app servers like Jetty more so. I guess you could say "serverless" is sort of in that vein, but it's far from the majority of use cases as the poster predicted.
* Functional programming ideas became mainstream, except in Go, which is a sort of reactionary back to basics language.
Overall though:
Good predictions:
* The IDE/editor space gets a shake up, though maybe not in the way any of the specific predictions guessed (the rise of VS code)
* Machine learning gets bigger
* Apple introduces a new language to replace Objective-C
* Some sort of middle ground to the dynamic/static divide (static languages have got local type inference, dynamic languages have got optional typing)
Bad predictions:
* No-code tools are still no further along mainstream adoption than 2012
* Various predictions that Lisp/ML/Haskell get more mainstream rather than just having their most accessible ideas cherry picked.
* A new development in version control displaces git
* DSLs, DSLs everywhere. DSLs for app development, DSLs for standard cross database NoSQL access,
Re: What will programming look like in 2020? (2012)
#9> I predict that functional programming will continue to gain ground as people discover the benefits of immutability and easy parallelism—but the functional language will not be Haskell, nor Scala, nor Clojure. At a guess, people will use something with:
>Strong tooling and libraries
>An accessible type system
>Deterministic memory behaviour
>By-default strict evaluation
>Commercial backing
>Every mainstream functional language is lacking in at least one of these areas.
Re: What will programming look like in 2020? (2012)
#10For a mere 8 year timeframe, the predictions seem rather poor. It feels like there was such a push among people to have the forward thinking ideas that they overestimated how much would change. Looking back, the biggest changes between now and 2012 are: * Git (and github) took over the world in the version control. Git was already the leader in 2012, but mercurial was doing ok and svn was still around to a much great…
I feel like there is also a return to basic imperative programming, with OO and functional where it makes sense.