Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

What will programming look like in 2020? (2012)

lambda-the-ultimate.org

Post reply on HN
Print view View original

71–80 of 151 posts

Re: What will programming look like in 2020? (2012)

#71

Post by GuuD »

CardenB wrote: post #63
lelanthran wrote: post #62

Earlier quoted context omitted.

Cherry picking only the accurate prediction makes it seem like the predictor is really good! Look at the rest of that quote: > The human, computer pair, will also interactively suggest, confirm and fine tune specifications of mathematical properties and invariants at points in the the program. That hasn't happened and as far as I am aware, is not even close. > This will help the computer assistant to not only better…

Can you explain how this is worse than random chance?

It is, for people who think that the chance of meeting dinosaur on the street is 50% (you either do or don’t)

/s

Re: What will programming look like in 2020? (2012)

#72

Post by still_grokking »

midwestemo wrote: post #11

>What will programming look like in 2020? It will be a complete shit. http://lambda-the-ultimate.org/node/4655#comment-73750

The reply made me smile:

  So...

  Nothing changed, then.
http://lambda-the-ultimate.org/node/4655#comment-73758

Re: What will programming look like in 2020? (2012)

#73

Post by Shoetp »

> 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.

This user casually predicted Rust.

Re: What will programming look like in 2020? (2012)

#74

Post by skohan »

Micoloth wrote: post #6

The “ Some safe and some bold predictions” comment is almost exactly my view on how programming should evolve. (functional, reactive, going toward dependent types etc ) Interesting how in 2012 it was already so clear! I 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, sol…

Reactive is a mistake. It's a tool for a specific job, sure, but it's too big and opinionated of an abstraction to use it everywhere. The future of programming should be reality based.

> Why aren’t we able to stop for a while and sort out once and for all a solid framework for coding?

There's never going to be one "solution" here. There will always be tradeoffs depending on the constraints of a given domain or problem space. One-size-fits-all solutions end up not being great for anything, since they have to make so many compromises.

Also great tools are made through solving real problems. If we just went to plato's heaven and dreamed up a "perfect" programming environment, we would end up with something which solves our problems in theory. But the issue with this is that our problems don't exist in theory, they exist in reality.

Re: What will programming look like in 2020? (2012)

#75

Post by skohan »

Mikeb85 wrote: post #28
nwomack wrote: post #17

Earlier quoted context omitted.

Except that it’s not really “gaining ground”, all things considered Rust is not that popular.

But more and more people are using things built in Rust. Which is what I'd call gaining ground. Was playing around in Deno. Yes it's JS, but it was built in Rust. In some respects, that's the true test of a low-level language. Things built in it. C isn't popular. But you'd never say it's not popular because it's what everything is built on.

A lot more people get a paycheck every month writing C than Rust. C is an incredibly relevant and popular language.

Re: What will programming look like in 2020? (2012)

#76

Post by brabel »

Shoetp wrote: post #73

> 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. This user casually predicted Rust.

Accessible type system? Hm, I would think this would be more about TypeScript than Rust.

Re: What will programming look like in 2020? (2012)

#78

Post by still_grokking »

daxfohl wrote: post #36

Nobody predicted GDPR or the need for multicloud. Wonder what the big new grunt work for 2030 will be.

Well, GDPR is almost 1:1 identical to the regulations being in place "since forever" in Germany.

What actually changed is that it's now more enforceable. Before GDPR there where all those laws but nobody cared really as there weren't proper punishments in place.

My idea for 2030: We're going to tackle all that web-development legacy as we're going to leave the time-sharing mainframe model again (actually for the same reasons as last time… ;-)). But maybe I'm to optimistic, and it'll be 2040 by than.

Re: What will programming look like in 2020? (2012)

#79

Post by still_grokking »

Shoetp wrote: post #73

> 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. This user casually predicted Rust.

I wouldn't call a "mutability first" language which relies mostly on side-effects "functional".
Post reply on HN