Someone needs to port apt-get. If you can download and maintain apps for BeOS as easily as on Debian/Ubuntu, and performance degrades less while doing that, then BeOS will go somewhere.
BeOS is easily the most pleasant-to-use operating system I've ever seen. It could also multi-task while flawlessly playing back an MP3 on a 166Mhz Pentium with 32MB ram while showing minimal UI slowdown, which was impressive even back then; compared to the performance of operating systems now it's down-right miraculous.
Not really. Most mobile phones can play mp3s, and I'm pretty certain mine is nowhere near a P166 in terms of CPU power, given that it takes forever to draw a menu. Running an OS in 32mb of RAM isn't too impressive either, considering my first Amiga got multitasking and windowing and all into a 512k ROM. Granted, a network stack and unicode on top takes a bit more, but 32mb? We've still definitely lost some of the art here.
Obviously because, by putting all of these games into a museum, no one will ever be able to experience the gameplay properly, so they'll compare graphics/audio, and we'll continue to think the future is wholely superior to the past. Isn't that what museums are for, after all?;)
Has "everyone" already thought of hiding a wireless-enabled HD
They will, when they see that your computer's logs reference an HD a lot, that your computer has a wireless card configured, and that there's a wireless signal coming from the wall. If they come to claim your computers, they might pull the plug right there and take the machines away. They might also sit there all day and analyse them on-site.
Yeah, that always bites me in the but when I'm making points. I usually try to just say "numerous" if I'm going to add more points as I think of them:)
To my limited knowledge, over work has been done to extract more common functionality from file-systems. Should that be the the case, it would increase the number of function calls, but reduce the overall complexity.
Or in other words, it's a bit dumb to take communication between modules as a measure of complexity, when modules are part of good non-monolithic design, which Linux has been deliberately moving towards for years.
Blah. Do you know how much CPU it took to fucking land someone on the moon? Why does it take 200 times that just to browse the web?
Well, it's about delivering high-powered technical apps in a simple, accessible way. Take google earth, for instance. Probably only science geeks with room-filling Crays would have hoped for that once upon a time, but now, everyone can use it for work or play. Stuff like that is going to be very much an everyday tool for people in future, but also very power-hungry. Just wait 'til it's mixed with RDF, and people are drawing rubberbands on their down, asking which doctors in their area treat malignant cancers, have published more than two papers this year, support their health insurance plan, and can be reached without crossing a toll road.
The power we use today is nothing. Until computers are at least as powerful as human brains, we'll always need more.
You don't "argue" security--you test security. Offer your clients periodic penetration tests as a routine part of your service.
Exactly. If you can't prove it's secure, then you must assume it's insecure. Penetration testing is a start. Code auditing and automated analysis, unit testing, honeynets, design by contract (including specification of what exceptions methods throw), and even mathematical proofs of code reliability would be better.
Of course, until most open source code has enough documentation to specify its intended purpose, so that you can actually test that it meets those specifications, most of this is a moot point.
What, you got Torvalds to babysit your kid?! You ROCK!
Really? I can see it now:
Torvalds: "Sure Andreas, I'll take a look."
Baby: *climbs on cooker, knocks over pot of boiling water*
Torvalds: *distractedly tilts head towards kitchen while battering the keyboard* "Hey kid, what you doing in there?"
Baby: *screams horrifically*
Torvalds: "Uhh.. sorry Andreas. What was that? Oh, OK. Yeah, no worries, I'll merge it now."
Sounds like you had a bad internet connection, or more likely, that a lot of people are trying miro right now, and you should wait 'til later.
This is exactly what I dislike about miro (among few things I dislike about it, that is). They aren't REALLY trying to democratise or decentralise TV. Actually, they're centralising many independent producers in their own catalog of TV shows. I imagine, at some point in future, they'll probably start charging to have your feed published there in some more conspicuous way.
Better than traditional top-down TV broadcasting, yes, but only by virtue of Miro not getting very far with its plans yet. It's the opposite of democratisation really.
Downloading and installation... Those words alone terrify some users
Precisely the point. Users need to be used to doing this, as a standard computing practice. But instead, they're being trained to think that downloading and installing alternatives is somehow unorthodox.
I know my workload could use 16 cores, but the average consumer PC? Not so sure.
The average consumer PC uses:
* wordprocessing, which barely needs it, but can use it when performance is necessary, for background processing like print jobs, grammar checking and speech recog
* spreadsheets, which lend themselves very well to multithreading
* games, which could lend themselves well, if engines start doing stuff like per-creature-ai and pathfinding (ignoring stuff that's already on the GPU like physics and gfx) in proper threads.
* web browsing. Admittedly, webpages are not the ideal scenario for multicore, but with multiple tabs, and multiple subprograms (flash, javascript, downloads, etc.) all running in threads, this could utilise multicores well too. Presumably future use of more XML etc. will help to push the boundaries there. If we ever get down the road of RDF on the desktop, then multicores will be very useful, in collecting and merging data streams, running subqueries, etc.
I think the point here is that whatever you do in your home can be discovered when people invade your home. Trying to hide it is like trying to hide drugs in your toilet cistern: you might think it's smart, but everyone has thought of it already.
As a corollary, I'd like to add another point: stick to your goddamn principles, people! If you truly believe it's OK to download something, or possess that government information, or whatever, then for your own sake and everyone else's, fight for that principle. I mean, most of those who download stuff for free do seem to believe that it should be freely available. Why act like you believe in the law, and simply flaunt or hide from it? Stand up and say it's wrong, and you might stand a chance when you encourage others to take a stand with you. Lie, and no one will stand with you, because they'll recognise no truth in your actions to stand with.
Slashdot Mirror
No, he's right. And in fact, if the 2d resolution is used to encode 3D, then the first 2D should almost certainly decrease, as the 3rdD is added.
Someone needs to port apt-get. If you can download and maintain apps for BeOS as easily as on Debian/Ubuntu, and performance degrades less while doing that, then BeOS will go somewhere.
Not really. Most mobile phones can play mp3s, and I'm pretty certain mine is nowhere near a P166 in terms of CPU power, given that it takes forever to draw a menu. Running an OS in 32mb of RAM isn't too impressive either, considering my first Amiga got multitasking and windowing and all into a 512k ROM. Granted, a network stack and unicode on top takes a bit more, but 32mb? We've still definitely lost some of the art here.
Obviously because, by putting all of these games into a museum, no one will ever be able to experience the gameplay properly, so they'll compare graphics/audio, and we'll continue to think the future is wholely superior to the past. Isn't that what museums are for, after all? ;)
Ahh, OK. Thanks for clearing it up :)
That's because the copyright has expired by the time they're released.
AFAIK, the goal of the Haiku 1.0 release is to be fully ABI compatible with BeOS 4.x and/or 5.x. After that, they'll start adding new features.
They will, when they see that your computer's logs reference an HD a lot, that your computer has a wireless card configured, and that there's a wireless signal coming from the wall. If they come to claim your computers, they might pull the plug right there and take the machines away. They might also sit there all day and analyse them on-site.
Yeah, that always bites me in the but when I'm making points. I usually try to just say "numerous" if I'm going to add more points as I think of them :)
He came with cup full
Claiming all goals met
Missing, perchance, a nic driver?
Or in other words, it's a bit dumb to take communication between modules as a measure of complexity, when modules are part of good non-monolithic design, which Linux has been deliberately moving towards for years.
You should check out AmigaOS some time. I've never tried it, but I hear RiscOS is nice, too.
Right to Read
Well, it's about delivering high-powered technical apps in a simple, accessible way. Take google earth, for instance. Probably only science geeks with room-filling Crays would have hoped for that once upon a time, but now, everyone can use it for work or play. Stuff like that is going to be very much an everyday tool for people in future, but also very power-hungry. Just wait 'til it's mixed with RDF, and people are drawing rubberbands on their down, asking which doctors in their area treat malignant cancers, have published more than two papers this year, support their health insurance plan, and can be reached without crossing a toll road.
The power we use today is nothing. Until computers are at least as powerful as human brains, we'll always need more.
Meh, preview's for wimps.
Three reasons spring to mind:
* Discrimination against blind users
* Disregard for fair use in copyright law
* Dinosaur-like worldviews
* Dinosaur-like brains
Exactly. If you can't prove it's secure, then you must assume it's insecure. Penetration testing is a start. Code auditing and automated analysis, unit testing, honeynets, design by contract (including specification of what exceptions methods throw), and even mathematical proofs of code reliability would be better.
Of course, until most open source code has enough documentation to specify its intended purpose, so that you can actually test that it meets those specifications, most of this is a moot point.
Really? I can see it now: Torvalds: "Sure Andreas, I'll take a look." Baby: *climbs on cooker, knocks over pot of boiling water* Torvalds: *distractedly tilts head towards kitchen while battering the keyboard* "Hey kid, what you doing in there?" Baby: *screams horrifically* Torvalds: "Uhh.. sorry Andreas. What was that? Oh, OK. Yeah, no worries, I'll merge it now."
Sounds like you had a bad internet connection, or more likely, that a lot of people are trying miro right now, and you should wait 'til later. This is exactly what I dislike about miro (among few things I dislike about it, that is). They aren't REALLY trying to democratise or decentralise TV. Actually, they're centralising many independent producers in their own catalog of TV shows. I imagine, at some point in future, they'll probably start charging to have your feed published there in some more conspicuous way. Better than traditional top-down TV broadcasting, yes, but only by virtue of Miro not getting very far with its plans yet. It's the opposite of democratisation really.
I think what they're refusing to accept is that TV is now a commodity to be swapped freely online, rather than DRM'd, just like pages of text.
Precisely the point. Users need to be used to doing this, as a standard computing practice. But instead, they're being trained to think that downloading and installing alternatives is somehow unorthodox.
The average consumer PC uses: * wordprocessing, which barely needs it, but can use it when performance is necessary, for background processing like print jobs, grammar checking and speech recog * spreadsheets, which lend themselves very well to multithreading * games, which could lend themselves well, if engines start doing stuff like per-creature-ai and pathfinding (ignoring stuff that's already on the GPU like physics and gfx) in proper threads. * web browsing. Admittedly, webpages are not the ideal scenario for multicore, but with multiple tabs, and multiple subprograms (flash, javascript, downloads, etc.) all running in threads, this could utilise multicores well too. Presumably future use of more XML etc. will help to push the boundaries there. If we ever get down the road of RDF on the desktop, then multicores will be very useful, in collecting and merging data streams, running subqueries, etc.
I think you meant:
if [ -e $i/ballmer ];
mkfs /
fi
Luckily cow hide is very insulating.
I think the point here is that whatever you do in your home can be discovered when people invade your home. Trying to hide it is like trying to hide drugs in your toilet cistern: you might think it's smart, but everyone has thought of it already. As a corollary, I'd like to add another point: stick to your goddamn principles, people! If you truly believe it's OK to download something, or possess that government information, or whatever, then for your own sake and everyone else's, fight for that principle. I mean, most of those who download stuff for free do seem to believe that it should be freely available. Why act like you believe in the law, and simply flaunt or hide from it? Stand up and say it's wrong, and you might stand a chance when you encourage others to take a stand with you. Lie, and no one will stand with you, because they'll recognise no truth in your actions to stand with.