461 karma · joined August 4, 2011
edit: What I meant by "cleaned-up" Pascal was addressing some of Kernighan's criticisms as seen in https://www.lysator.liu.se/c/bwk-on-pascal.html (also, the Pascal syntax is a bit bloated)
That's right, and that's also why the prestigious researchers and universities, those with an already established reputation, have a responsibility: collectively leave the editorial boards of for-profit publishers, set up alternative venues with the help of university libraries. Share the archival, indexing and discovery effort among universities via peer-to-peer digital library federation.
All the tools are there. The same way that places like Stanford, Berkeley and MIT made MOOCs a thing, they can revolutionize scientific publishing.
There's already such venues such as JAIR for AI research (and that was set up looong ago without all the tech we have today), so it's certainly possible. It just needs to become the norm rather than the exception.
The point I was trying to make was about the distinction between programming with a limited set of building blocks vs programming with a large and open-ended selection of libraries. They don't require the same skill set, and one seems more fun to me than the other.
Today, the set of building blocks is unlimited. The challenge is to find the right building block for what you want to do, using the infinity of resources available to you (all the APIs, libraries, Google, GitHub, StackOverflow, blog posts). You're drowning in complexity, even if what you want to program is straightforward. And you are constantly mindful of writing idiomatic code, always wondering if there's a better way to do the same thing, which is normally a good thing but can be time-consuming and getting in the way of the fun part that is the problem solving.
In principle I agree with this, but the economic reality of North American universities is that programs that don't draw a large enough income will lose to those that do. New programs are introduced based on how many people they can attract (the Market), not based on how necessary they are for the generation, preservation and transmission of knowledge.
JavaSpaces, TSpaces emphasized the over-the-internet aspects of it, which didn't matter to us for our project. We ended up finding and using something much simpler called LighTS. With all the nice support for concurrency in Java these days though, it wouldn't be much work to put one together from scratch.
Interestingly, nobody eats the "narenj" directly. They usually squeeze its juice on a fish dish. It gives it a very nice flavour.
I'm aware of sites that tell you whether you need a blockchain or not for your application, but they don't say what to use if only one or two of the requirements for a blockchain are not needed. What would a decentralized DNS strictly need if the notion of transaction wasn't required (but only the latest value)?