Live data from Hacker News

What will programming look like in 2020? (2012)

lambda-the-ultimate.org

41–50 of 151 posts

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

#41
post #8

For 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…

> * No-code tools are still no further along mainstream adoption than 2012 In 200 years, people will still be predicting the rise of no code solutions. If you are executing diagrams and schematics, you still have code. And the people maintaining that code are still coding. That is, they are coders. They're just working in a whole new stack that doesn't have git, diff, a variety of editors, open standards for encoding…

There's no such thing as no-code, it's just a question of the properties of the coding scheme. For example C.S. Peirce proposed a turing-complete "no-code" graphical logic (aka programming) language[1] in the 19th century.

[1] http://www.jfsowa.com/pubs/egtut.pdf

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

#42
post #8

For 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…

> * No-code tools are still no further along mainstream adoption than 2012 In 200 years, people will still be predicting the rise of no code solutions. If you are executing diagrams and schematics, you still have code. And the people maintaining that code are still coding. That is, they are coders. They're just working in a whole new stack that doesn't have git, diff, a variety of editors, open standards for encoding…

true, it's mostly a matter of altitude on the abstraction ladder, and not dealing with textual notation (it's all graphs underneath anyway)

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

#43
post #19

“HCI-ware (and wear) While increasing heterogeneous and concurrent architectures will certainly impact languages and frameworks (and there is much progress there already, e.g. to leverage clouds or GPUs), I'm more interested in how things like Project Glass, LEAP motion, Emotiv, and Touché might impact programming. Project Glass could provide pervasive access to eye-cams, voice, and HUD feedback. Something like that…

Personally I feel that Minority-Report-y predictions are foolish, because is ignores the human aspect in the name of glitz. Specifically, how tiring it is to hold your arms in the air all day.

I think the example of mail is instructive. Contrary to some "zeerust"-y predictions, we don't buy virtual stamps from the virtual store to virtually lick them before virtually walking to the virtual mailbox. Even with the vastly improved capabilities of 30-40 years in 3D technology, the concept is immediately bizarre.

In practice, we instead boiled away most of the extra bits and ended up with e-mail, which tries to minimize even the body-movement needed.

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

#44

Earlier quoted context omitted.

Its honestly not that hard to predict, with a bit of statistics and some insights into early deep learning, its obvious that alot of data with discernable patterns will produce good results.

What will programming look like in 2028?

2028 will be the year of Linux on the desktop, so…

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

#45

Earlier quoted context omitted.

No good deed goes unpunished.

I hope that made you feel good! Seriously, someone goes to the trouble of finding the archive link because the server is having trouble (note that someone else had mentioned it too, not just me), and it gets modded down. Why? What possible justification is there for that? Then even mentioning the ridiculous modding down gets modded down further. Why? (and no, "because those are the rules" isn't a reason... did it eve…

Complaints about downvotes are boring, and are often made redundant when the comment is upvoted again, as happened here.

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

#46
post #13

A couple small threads from back then: What will programming look like in 2020? - https://news.ycombinator.com/item?id=4962694 - Dec 2012 (3 comments) Ask HN: What will programming look like in 2020? - https://news.ycombinator.com/item?id=4931774 - Dec 2012 (12 comments)

> Unit testing will be built directly into languages as an intrinsic part, like compiler optimization or GC.

Rust and Zig have this, right?

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

#47
post #8

For 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've given Go lots of shit, but once generics land and are widespread, I suspect it will undergo a culture shift.

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

#50
post #37

Earlier quoted context omitted.

Does anyone actually use Copilot day to day? How much time does it actually save?

Writing boring chores or repetitive code is amazing. Need to handle all cases in a case in pretty much the same way but changing only one thing? Write the first one, the rest is auto coded perfectly.

But isn't much better to just manually code it into reusable function and use it repeatedly, instead of letting AI generates all the boilerplate code and causes maintenance headache down the road?
Post reply on HN