5 ms·
Agreed, the law of leaky abstractions is pretty brutal. When you're writing serious systems you always have to peek under the hood -- e.g. you have to reason a
by chubot 15y ago
Agreed, the law of leaky abstractions is pretty brutal. When you're writing serious systems you always have to peek under the hood -- e.g. you have to reason about data structure sizes in the JVM, or check out the code that GCC outputs, or look at the Python interpreter source code. Having a bunch of monolithic magic with its own world view sitting between you and the machine is a big barrier.
I'm skeptical of anything that tries to present a grand unified model. GWT is another example of where this strategy fails IMO.
As noted below, CoffeeScript is a different case that illustrates the point. It seems moderately successful (I haven't used it) precisely because it's a such a modest abstraction. It aims to be a 1-to-1 with JavaScript, and keeps the semantics of JavaScript, rather than imposing its own semantics which are inevitably at odds with what browsers/servers are really doing.
- lihaoyi 15y agoWe've heard this all before, though. 40 years ago, Machine Code was where it was it, and people scoffed at those who were lazy enough to use an assembler. Then Assembly was where it was at, and the abstraction that C provided was leaky and poor, and compiled code could never be as good as hand-written assembly coded directly against the individual processor instruction set. The problem with this argument is that it applies just as much in the two above examples as it does in this one, and it's clear that C has really taken off. Making good abstractions is damn hard, and the law of leaky abstractions is brutal, but the success of C, and even Java (a virtual machine on top of a compiler on top of a assembler on top of the machine!) shows that it can be done. I'm pretty happy I can write code in C and can't imagine worrying about things like different instruction sets, registers, L1/L2 caches, etc. just for a basic "hello world". Perhaps in the future, people will think it equally crazy that we had to worry about details like what database we use, how we serialize data over the wire, manually creating ajax endpoints, etc.. Perhaps they'll let the compiler do all this work and only dive into manually fiddle with this stuff when they need to squeeze the last 10% performance out of the system, just as C programmers sometimes drop into ASM today.
- chubot 15y agoIt doesn't -- C is analogous to the coffeescript case; it's not at all like Opa. It's the minimal portable abstraction over digital computers. Given some C code, it's not hard to predict roughly what instructions it compiles into. It precisely illustrates the point, because there were dozens of more complicated abstractions (languages) that failed. They claimed to do more for you, but what they did conflicted with reality and failed (in that era, usually because it was hard to reason about performance). C is humble and makes few assumptions. "Abstraction is layering ignorance on top of reality" -- Richard Gabriel My opinion is that anything which tries to abstract network communication and make it "transparent" is going to run in to problems at scale. For some reason there is this endless desire of programmers to extend their type system across the wire. It's been tried so many times. The goal of Opa appears to be "transparency" as discussed here -- making distributed computing look like single-machine computing. This was also the goal of GWT. http://scholar.google.com/scholar?cluster=7009698499164949721&hl=en&as_sdt=0,5 http://scholar.google.com/scholar?cluster=700969849916494972... Also related: http://scholar.google.com/scholar?cluster=17011909832902326140&hl=en&as_sdt=0,5 http://scholar.google.com/scholar?cluster=170119098329023261...
- lihaoyi 15y agoDoesn't the C compiler do all sorts of optimization magic that makes the output of the compiler sometimes hard to predict? C is also not the only language that succeeded; C++ and Java are doing pretty well, and I've used them quite alot without delving into the sausage factory of GCC/javac. Scala is doing pretty well too, with it's 20 stage compilation process! I disagree that anything trying to abstract away network communications will fail; I doubt that every engineer at google is a full-stack expert who single-handedly sets up a massive-scale service every day by hand. More likely, they have developed a set of somewhat-reusable abstractions that they can build upon for a variety of services. Hadoop is another example where the whole network thing is abstracted away. Amazon S3/Cloudfront is yet another. Difficult, but not impossible. Perhaps Opa is trying to be the minimal portable abstraction over a full-stack service. I know GWT tried to be the same thing and failed, but one failure doesn't mean you give up, and I'm glad they're still trying.