"And then we've got this sort of dichotomy between efficiency and clarity. You know, to make something clearer, you add a layer of abstraction and to make it more efficient you remove a layer of abstraction. So go for the clarity bit. Wait ten years and it will be a thousand times faster, you want it a million times faster, wait 20 years."
That's... one way to make something clearer. It's also a way to hide complexity behind leaky facades. "Just add a layer of abstraction" is horrible advice.
Thanks a lot, I never watched this, it’s absolutely awesome.
I laughed a lot and
I actually cried in the slide about legacy code when the first line was “programmers who wrote the code are dead” :(
It is a great talk. Based on that I took his course on Erlang at FutureLearn, which was also very good. Sadly, when I sent that link to some colleagues at work they shrugged and have since kept adding more and more dependencies and complexity to the front-end build. It's very hard to stop momentum once it's got going, culturally.
Guess I'm alone in not seeing what's so good about this talk. He only presents problems, and in an extremely disorganized way. The closest thing to a solution is "wait, hardware advancement will eventually make your slow code fast."
It's definitely entertaining, but that's about all I can give it.
There's a time and place for things. Posting multiple critical comments in a commemoration thread is maybe not the best time or place, and better kept for later?
The idea of "no copies – everything exists in one place and has a unique ID" was new to me. I still don't know if it's a good idea, let alone practicable, but it's great food for thought!
https://youtube.com/watch?v=lKXe3HUG2l4