News for hackers. Stuff that matters.
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.