645 karma · joined September 6, 2012
http://www.markstefik.com/wp-content/uploads/2011/04/1982-Bo...
I also had access to a Mac, had an HP-9000 unix workstation (running X Windows) sitting on/under my desk, and had some exposure to Smalltalk-80 at the time. What blew me away was how mature and strange the Alto was; it was so obviously advanced, but was so difficult to understand. At that time, it was an 'old' machine, but somehow seemed like it was sent from the future.
The US has exactly the same law.
Also, let's get down to brass tacks - I don't see the actual queries that are being graphed in the MemDB post, and what is that graph actually measuring?
I think the LMDB team has done a really good job with this type of comparative benchmark. They took the LevelDB benches, then ran them against a lot of competitive products, both new and legacy, and gave a really good view of the entire field, in terms of performance on a number of dimensions:
The article is about software, algorithms and modern database technology. Oracle has basically been flogging the same code base for twenty odd years, and claiming they are competitive by running their ancient, single node system on more powerful nodes. It is pure BS. Using a modern, distributed, in-memory store like MemSQL on crap nodes (AWS), still beats the pants off Oracle's ancient single node POS running on a super-computer.
I wonder if the situation is much different in the US. The health care system is certainly different. One gets the impression the system in the US preys on seniors as employer benefits evaporate after retirement while insurance premiums skyrocket or are denied because of 'pre-existing conditions'.
I am neither a jerk nor an American nor incorrect.
Had Alan Kay coined the term "object orientated", I would use it without question.
"orientated"??
I hate to be a stickler, but you cannot say "object orientated" any more that you can say "the object was instantiatated", or "Xerox inventated Smalltalk".
The author of LMDB doesn't really make bold claims, he actually just included LMDB (and the venerable Berkeley DB) in LevelDB's published benchmarks. The benchmarks were developed by the LevelDB team.
This makes sense for the current generation of storage sub-systems, though it would be misleading to say using memory map technology will be "obsolete in half a decade". The 48 bit limit is arbitrary. Manufacturers have 56 bit designs on the table right now, and there is nothing stopping them from implementing full 64 bit virtual address support.
Seriously.
I certainly wouldn't discourage anyone from watching the video. At least read the slides!
http://gotocon.com/dl/goto-aar-2012/slides/MartinThompson_My...
We use git to push configuration data to (near) real-time systems that keep this data in local memory mapped key-value stores. It's essentially a fully replicated, eventually consistent key-value store, and git plays a staring role.
We regularly push multi-gigabyte files through this system with ease, with only a few tweaks on git's configuration. Git has some major advantages. It's fast, can handle large files, and you can piggyback on the versioning system to ensure that multiple writers aren't competing. Also, git is highly configurable and has a lot of out-of-the-box options for easily setting up git servers.
It's GNP is $19.9B.
The population of WhatsApp is 50 employees!
This is false.
I went through a rather large Smalltalk phase in the first half of the nineties, and was kindly lent a copy of the 1981 magazine by a fellow hacker (and archivist!) for a few months before reluctantly returning it sometime in 1991. I loved how the journos went through great lengths describing what "cut/copy/paste" was. It's almost travel writing.