I used to live in Seattle. The OTHER reason that traffic is "so bad" there (besides the one mentioned by the poster -- crappy mass transit), is the there are only FOUR ROADS! Count -em, 4! What the hell good is a freakin' traffic meter gonna do me if there's no alternate routes to take? And believe me, if 520 is backed up, so is 90. If 5 is backed up, well you have to go WAY out of your way to get to 405. How on earth those people up in Seattle think they're going to solve any traffic issues without good public transportation is beyond me. That's why I moved to Portland...
All the discussion here seems to be focused on the underlying workings of the OS, memory spaces, and the Crush language. But to me the coolest thing was the Object Store: "...All file information (metadata) is stored in a database file and accessed with a search engine..." Whoah! How awesome is that?! Is this something that is implemented in any other OS's/File Browsers? There is so much talk all the time of how the "desktop metaphor is outdated and we need something new, but...what?" Well in my eyes, here is the ideal replacement for the files/folders/hierarchy/etc. I work with a LOT of computer-illiterate people, and it is very hard for them to find files on the computer (especially with a few network drives also available to them). They usually don't remember where they saved the file to in the first place! But with a system like this, where files are not arranged in a hierarchy, but rather you query for them much like a database, they can just pull up files that have attributes relevant to what they remember about it. I think this would be fantastic, and I wish I could figure out how to get this Brix-OS running so I could see the implememntation of this feature(!)
Slashdot Mirror
I used to live in Seattle. The OTHER reason that traffic is "so bad" there (besides the one mentioned by the poster -- crappy mass transit), is the there are only FOUR ROADS! Count -em, 4! What the hell good is a freakin' traffic meter gonna do me if there's no alternate routes to take? And believe me, if 520 is backed up, so is 90. If 5 is backed up, well you have to go WAY out of your way to get to 405.
How on earth those people up in Seattle think they're going to solve any traffic issues without good public transportation is beyond me. That's why I moved to Portland...
All the discussion here seems to be focused on the underlying workings of the OS, memory spaces, and the Crush language.
But to me the coolest thing was the Object Store: "...All file information (metadata) is stored in a database file and accessed with a search engine..."
Whoah! How awesome is that?! Is this something that is implemented in any other OS's/File Browsers?
There is so much talk all the time of how the "desktop metaphor is outdated and we need something new, but...what?"
Well in my eyes, here is the ideal replacement for the files/folders/hierarchy/etc.
I work with a LOT of computer-illiterate people, and it is very hard for them to find files on the computer (especially with a few network drives also available to them). They usually don't remember where they saved the file to in the first place! But with a system like this, where files are not arranged in a hierarchy, but rather you query for them much like a database, they can just pull up files that have attributes relevant to what they remember about it.
I think this would be fantastic, and I wish I could figure out how to get this Brix-OS running so I could see the implememntation of this feature(!)