News for hackers. Stuff that matters.
Re:Omega - Language of the Future by viraptor on Saturday September 25, 2010 @12:10PM (#1727217)
So true. Not so long ago, we thought that using natural-language-like text can enable non-programmers to work with code... (and then did it again with rules engines (and we'll do it again at some point in the future)).

Re. 2: didn't we go through this when SOA and SOAP were all the best thing since sliced bread? The problem with APIs is not with versioning per se (if want to use URIs, just stick version number in the first position, webservices do that) - it's about what happens to dependencies. You have to call v5, you've got v1..v8 available, but another library you use talks to v3. Can you share objects? How is the v8-compatible state affected when v5 and v3 are doing the work? Which api is called when in your v5 area you call a method on a v3 object?

Re. 3: Yeah... I was considering tackling that for my degree at some point. The source file is just a placeholder that can contain some string generating new placeholders - why don't we simply start working on it that way?

Re:Omega - Language of the Future by derefr on Saturday September 25, 2010 @05:15PM (#1727883)
Combine 1, 2, and 3, and you can make the function name just the content hash (of its AST, not its string representation)—the name becomes metadata. Every function call, then, just refers to another hash, which the loader (or the linker, if you want to inline for performance) just Googles and uses the first result that hashes right. Basically, all libraries become one library—called the Internet. Or, to put it alternately, every function, protocol, and data structure would be versioned inividually, as if they were all files stored on a Git repository.