365 karma · joined August 24, 2007
A DSL family based on a flexible core (with a lispish intermediate language even) might be a viable approach.
In many situations, simplicity and restrictions (constraints) in DSLs is better than flexibility and expressiveness in a general purpose language, because it can offer new possibilities for domain specific optimizations due to domain specific constraints.
Just like new notations in math led to breakthroughs in many math branches, new syntax can bring new life to software in many specific domains.
The key to such systems seems to be making DSLs easy to build and optimize using a suite of common building blocks (human (cs people) friendly intermediate languages (like lisp as opposed to VM byte codes) and libraries.)
I think it would be a good revenue strategy, if they charge $dollars to display top 10 positive features and top 10 negative features of any given query-document pair without any real weights/scores (maybe re-squashed with some logistic function). The $dollars amount is computed dynamically to offset the negative impact of the partial reveal of the ranking algo/model. This can be a tremendously useful tool for troubleshooting search results by site owners.
Abolish software patents, now!
The Acer has an HDMI output. I connected it to my 24" 1920x1200 Samsung and point and clicked the monitor applet on the gnome panel and viola, dual monitor support at full resolution without having to fiddle xorg.conf! Point and clicked to configure the wifi on both machines without any problems. Man, I was ecstatic, probably due to the low expectation from my Gentoo experience -- I was expecting to vi a few things to make them work :)
To be honest, I did have to add a fixmtrr.sh to gdm PostLogin and a line (MigrationHeuristic greedy) to xorg.conf to fix the intel video performance regression in Jaunty on both machines, when I felt the desktop effect was a bit sluggish. Now the desktop animations are smooth as butter even on the netbook.
I did choose to install 32-bit Ubuntu with server kernel (to get PAE in Jaunty) to take advantage of the full 4GB RAM, instead of 64-bit because flash and a few other things don't work as well as in 32-bit.
Before the MBP, I've been using a $1000 amd64 notebook with 1.5GB RAM for 3 years without any issues, running Gentoo (! did need to google to fix multi-monitor support and ndiswrapper/wpa-supplicant for wifi) and it felt snappier than the mac with much faster processor running Leopard (up to 10.5.8).
Now I'm using a $600 laptop (with 4GB RAM and 320GB HD with higher display resolution than the MBP: 1680x945 vs 1440x900) and a 2.5lb $200 netbook running Ubuntu Jaunty. Everything worked out of the box including wifi, webcam and desktop effects. Feels much snappier than the Mac as well. All it took is a little googling _before_ buying the machines :)
It's much easier for Apple to QA limited configurations. Frankly, I'm quite pleased with the progress of Linux desktop.
Just another experience and perspective...
Interesting so far besides some syntax ugliness and lack of macros, but not yet good enough for many system programming projects, especially given the state of the garbage collector. GC is the hardest thing to implement large-scale, concurrent, memory intensive applications (e.g, database servers). Java spent 18 years to perfect its GC to be the current state of the art, which still sucks for these applications.
I hope they can come up with a concurrent garbage collector that can work on > 16 GBs of RAM with sub ms max latency :)
I think the best interpretation for NoSQL so far is "Not only SQL", which has interface implication as well.
I'd love a bookpad that has two screens that fold together like a book. One screen is LCD that can serve as keyboard/(multi)touchpad/video screen and the other e-ink screen for reading books.
The erlang code is also much denser. I gziped the code to compare a fairer symbol count: it's 1535b vs 2916b, a 47% saving, not bad but not that impressive either, considering the refactoring in the new code.
From user's point of view, the new distribution is 4x larger (10MB vs 2.5MB) and uses much more memory, which is a bad deal. It's OK for a developer to scratch his itch but dramatizing the benefit of such scratch doesn't help anybody.
I personally find thrift IDL trivial to manage and is probably the only sane way to support a dozen languages (statically and dynamically typed) in a type safe and efficient way.
BERT-RPC is simple, but what if you find your server too slow and needs to be rewritten in another language? I think the Thrift approach makes that simpler.
IMHO, design patterns transcend language idioms and enable people to understand/communicate higher level abstraction.
http://setiathome.berkeley.edu/top_hosts.php
BTW, how do you ensure somebody is not submitting a malware (intentional or not) that can DDoS someone by crawling the same host at pretty much the same time?
GAE has nothing to do with this, it's a shared cluster, such that any benchmark is not reliable and comparable. It also has nothing to do with the SQL discussion, as it doesn't support joins either.