News for hackers. Stuff that matters.
Re:The Future of Programming (2013) by macintux on Tuesday October 24, 2017 @11:02AM (#15542069)
One of my all-time favorite talks. The IT industry is pretty bad in general at knowing what problems have previously been solved.
Re:The Future of Programming (2013) by robbrit on Tuesday October 24, 2017 @11:56AM (#15542541)
In many cases, we have to first acknowledge that the problem exists before we attempt to apply some of these solutions. I've noticed myself seeing solutions to problems that I didn't know I had, only to brush off the solution as though it were only an interesting curiosity with no real practical use. It was years later when I went back to that and realized how useful it could have been.
Re:The Future of Programming (2013) by pierre_d528 on Tuesday October 24, 2017 @02:38PM (#15544064)
Treasures from Alan Kay and friends can be found here: http://www.vpri.org

Do check the STEPS project: a complete system in 10_000 readable LOC.

Really exceptional.

Bret Victor can be found here: http://worrydream.com

Friends can be found here: https://harc.ycr.org/member/

Make sure to check Alan Kay's answers on Quora: https://www.quora.com/profile/Alan-Kay-11

Re:The Future of Programming (2013) by fhood on Tuesday October 24, 2017 @12:26PM (#15542826)
This was one of my professors favorite gripes. He loved to tell stories about how companies would reinvent algorithms (usually multiple times) that had been published in the 70's and 80's
Re:The Future of Programming (2013) by zvrba on Tuesday October 24, 2017 @12:57PM (#15543075)
The problem here is search. The problem may have been solved, but finding the relevant paper is like looking for a needle in the haystack. It doesn't help that terminology has changed during the years...
Re:The Future of Programming (2013) by mrec on Tuesday October 24, 2017 @01:17PM (#15543256)
> It doesn't help that terminology has changed during the years...

As has hardware. Trivial example, but linked lists made a lot more sense in the 1970s than they do today.

Re:The Future of Programming (2013) by acuozzo on Tuesday October 24, 2017 @04:04PM (#15544793)
> The problem here is search.

And training.

I've had to reinvent algorithms I know already exist for my hobby work because they were invented to solve another unrelated problem I'm not familiar with and phrased using domain language I don't know.

Re:The Future of Programming (2013) by tj-teej on Tuesday October 24, 2017 @03:43PM (#15544604)
The problem with the solution to the problem of search is searching for the solution to the problem of search?
Re:The Future of Programming (2013) by BjoernKW on Tuesday October 24, 2017 @01:40PM (#15543452)
Apart from making information easily retrievable, which ironically academia at least used to be notoriously bad at, inventing an algorithm and using it effectively in an application in many cases are two very different matters.

These arguments often get handwavy rather quickly. Real-life applications have to accommodate edge cases and non-functional requirements, something a scientific paper doesn't need to account for.

That's perfectly fine. It isn't a scientist's job to worry about implementation details but those shouldn't be brushed off lightly either.

Re:The Future of Programming (2013) by romaniv on Tuesday October 24, 2017 @11:33AM (#15542310)
Yeah. Almost every time I watch a Marvin Minsky or Alan Kay video of any kind I'm surprised with info on some awesome technology or research from the 60s or 70s.
Re:The Future of Programming (2013) by skadamat on Tuesday October 24, 2017 @12:26PM (#15542824)
I think you'll like the discussion he had at CMU a few years back, which focused a lot on the technology side of things https://www.youtube.com/watch?v=PFc379hu--8
Re:The Future of Programming (2013) by pjmlp on Tuesday October 24, 2017 @11:40AM (#15542393)
You should also check the systems programming research that was happening on those days, NEWP already had UNSAFE blocks that required "root" blessing to be executed.

Or the IBM RISC research using PL/8.

And many other examples, lost in research papers from all those companies.

Re:The Future of Programming (2013) by pjmlp on Tuesday October 24, 2017 @11:37AM (#15542351)
Also for me.

When I delve into the digitized copies of these researches, I am always fascinated by the little treasures I find out.

And by being old enough to have experimented with some of them it saddens me the amount of left turns we have taken, for some to still be happy with a plain phosphor terminal experience.

Re:The Future of Programming (2013) by shalabhc on Tuesday October 24, 2017 @12:41PM (#15542932)
> what problems have previously been solved

And we're worse at identifying what the problems actually are.