Yeah, I have to agree. I do think ChromeOS might be a good recession OS as they'll probably price el-cheapo netbooks at $199 with it. But I think netbook buyers are aware that they get what they pay for.
Seriously, the reality is that when Bob picks one of these devices up, he's going to return it after he figures out he can't run QuickBooks on it. And Jane won't buy it after she finds out Skype won't be available until later or that she has to switch away from Thunderbird to get her email.
Microsoft does understand that users go apesh1t when they can't run the software they want to run, despite Microsoft's prodding people to move to other solutions.
If Microsoft could just figure out how to prevent restarts on software installs, the cold boot scenario would be almost pointless. in the 3 months between software installs, I have not rebooted my PC a single time, and it always comes out of standby quickly.
Reducing cold boot time from 30 to 7 seconds just isn't a feature most users will see value in *if* Microsoft could just kill most of the scenarios where one would need to cold boot.
My eyes are still rolling with ActiveX. Asking users to decide to trust or not trust unmanaged code is such a crappy model. Everyone except Microsoft knew it from the start, and it only took them a decade to realize that even code written with the best intentions can be a real threat if it's even partially unmanaged.
(btw, I mean "managed" in a more general sense, not specifically the.NET environment)
I have this feeling that simulating the human brain ends up being practically meaningless without simulating the rest of the body. And, having some meaningful, long-term interaction with either the real world or an incredibly sophisticated simulation. I'm assuming one would "grow" the brain in the simulation rather than, say, capturing the full chemical state of every neuron in a living person's brain (which sounds pretty impossible to me).
Would they unlink? I'd think they would sense (or be notified) that the car in front of them is slowing down rapidly and follow suit.
To me, a bigger deal would be the lead car - a big, burly vehicle designed to withstand major pain - decides to force its way through a big ass pothole. Then one by one, all the followers submit claims to their insurance companies to fix their damaged suspensions.
You're handing control over to another driver, who may very well decide not to brake and cause a five car pileup, or worse.
I would think the reaction time of braking of all following vehicles would be measured in tens of milliseconds instead of hundreds of milliseconds for the average human driver. I actually might feel more protected from pileup in a road train than on my own (depending on reality, of course).
Are they taking into account speed increases? Maybe customers won't want a 20TB HD that runs 10% faster than today's HD. Maybe they'll want a 1TB solid state drive that runs 500% faster. I'll certainly trade 500GB for a 100% speed boost today.
I have a feeling that there are no big speed breakthroughs left in spinning magnetic media, but there are huge opportunities still waiting in solid state.
Yeah, exactly! I always want kids to learn the lessons that have made me so successful in life:
- Aim low. Real low. You'll always succeed that way. - Always try to fit in. You'll be promoted to middle management that way. - Never ask questions. People hate stupid questions, but they hate smart ones more.
Follow that and you'll be guaranteed to make 6 figures by the time you're 40.
- Heads: They are too pedantic about development practices in an organization focused on shorter term results. - Tails: They are too focused on shorter term results in an organization focused on pedantic engineering. - Uneven performance - productivity that tends to spike around review time but lag in the between months. Many managers aren't naive about this. - Embattling the lead developer. Some developers take a personal disliking to the lead for whatever reason, and take a position of disagreeing with every decision very loudly.
- Win7 is marginally faster than Vista, and it will run on far faster, more capacious hardware (on average). - The beta/RC was a huge try-before-you-buy program, which lends itself to a more positive view of the product. - It finally fits on a netbook, and those will be the rage once they start becoming really sexy. - $99 just isn't what it used to be.
I want to have a Director title. Should I learn how to brown nose, or should I learn how to backstab? Or maybe I should start with unnecessary empire building, first?
Try learning a simple assembly language or IL, like ARM or CIL. Or better yet, make up your own implementation (like, some stack-based evaluation system). Then, try writing your own language and see what you come up with. I tried this when I was taking CS and it really enhanced my practical understanding of much of the theory they threw at us.
Actually, this was exactly what they were having us do, I just didn't fully realize it because of all the jargon and terminology I found kind of above my head at the time. But the experience really did help me later think about things like Java and C++ actually work, and more importantly, why.
Just because a company *can* create a piece of software doesn't mean that creating that software comes without significant cost. Blizzard is not a dumb company, and I'm sure they weighed the benefits of a LAN server against the cost in time and money. Certainly they knew it would upset fans like yourself, but it was a calculated decision that just isn't worth getting that upset over.
Or are you just upset at me? I think you're reading to much into my last sentence - that was mean in jest, yet you seem to have taken it too seriously.
Slashdot Mirror
That can't be true. Black holes are infinitely funny.
The thought of crossing drumsticks makes me hope for the doomsday scenario.
Yeah, I have to agree. I do think ChromeOS might be a good recession OS as they'll probably price el-cheapo netbooks at $199 with it. But I think netbook buyers are aware that they get what they pay for.
Seriously, the reality is that when Bob picks one of these devices up, he's going to return it after he figures out he can't run QuickBooks on it. And Jane won't buy it after she finds out Skype won't be available until later or that she has to switch away from Thunderbird to get her email.
Microsoft does understand that users go apesh1t when they can't run the software they want to run, despite Microsoft's prodding people to move to other solutions.
If Microsoft could just figure out how to prevent restarts on software installs, the cold boot scenario would be almost pointless. in the 3 months between software installs, I have not rebooted my PC a single time, and it always comes out of standby quickly.
Reducing cold boot time from 30 to 7 seconds just isn't a feature most users will see value in *if* Microsoft could just kill most of the scenarios where one would need to cold boot.
My eyes are still rolling with ActiveX. Asking users to decide to trust or not trust unmanaged code is such a crappy model. Everyone except Microsoft knew it from the start, and it only took them a decade to realize that even code written with the best intentions can be a real threat if it's even partially unmanaged.
(btw, I mean "managed" in a more general sense, not specifically the .NET environment)
"The future is here" is probably the most false, yet constantly true statement ever.
I have this feeling that simulating the human brain ends up being practically meaningless without simulating the rest of the body. And, having some meaningful, long-term interaction with either the real world or an incredibly sophisticated simulation. I'm assuming one would "grow" the brain in the simulation rather than, say, capturing the full chemical state of every neuron in a living person's brain (which sounds pretty impossible to me).
If each core could model one small patch of skin on one of those busty 3D models, then, well, ... wow!
Hopefully they weren't doing just doing svn delete.
Bah, they'll just blame it on Bernie Madoff's QA like they always do.
I'm Steve Ballmer, and sudo was MY idea.
I agree with Glen Beck - Don't let the government take away our freedom to drive!! Say no to Obamatrain.
Would they unlink? I'd think they would sense (or be notified) that the car in front of them is slowing down rapidly and follow suit.
To me, a bigger deal would be the lead car - a big, burly vehicle designed to withstand major pain - decides to force its way through a big ass pothole. Then one by one, all the followers submit claims to their insurance companies to fix their damaged suspensions.
You're handing control over to another driver, who may very well decide not to brake and cause a five car pileup, or worse.
I would think the reaction time of braking of all following vehicles would be measured in tens of milliseconds instead of hundreds of milliseconds for the average human driver. I actually might feel more protected from pileup in a road train than on my own (depending on reality, of course).
Are they taking into account speed increases? Maybe customers won't want a 20TB HD that runs 10% faster than today's HD. Maybe they'll want a 1TB solid state drive that runs 500% faster. I'll certainly trade 500GB for a 100% speed boost today.
I have a feeling that there are no big speed breakthroughs left in spinning magnetic media, but there are huge opportunities still waiting in solid state.
Yes, where can I buy their mad songs on iTunes.
Yeah, exactly! I always want kids to learn the lessons that have made me so successful in life:
- Aim low. Real low. You'll always succeed that way.
- Always try to fit in. You'll be promoted to middle management that way.
- Never ask questions. People hate stupid questions, but they hate smart ones more.
Follow that and you'll be guaranteed to make 6 figures by the time you're 40.
Some developers get fired because:
- Heads: They are too pedantic about development practices in an organization focused on shorter term results.
- Tails: They are too focused on shorter term results in an organization focused on pedantic engineering.
- Uneven performance - productivity that tends to spike around review time but lag in the between months. Many managers aren't naive about this.
- Embattling the lead developer. Some developers take a personal disliking to the lead for whatever reason, and take a position of disagreeing with every decision very loudly.
Acquire a Men In Black mind eraser.
- Win7 is marginally faster than Vista, and it will run on far faster, more capacious hardware (on average).
- The beta/RC was a huge try-before-you-buy program, which lends itself to a more positive view of the product.
- It finally fits on a netbook, and those will be the rage once they start becoming really sexy.
- $99 just isn't what it used to be.
(In my best Special Ed impersonation)
Yaaaaaay, now we can scale out Hadoop! Yaaaaay! Yaaaay Hadoop! Yaaaaay!
I want to have a Director title. Should I learn how to brown nose, or should I learn how to backstab? Or maybe I should start with unnecessary empire building, first?
Huh? I thought Bob Dylan was singing in Chinese all this time. Must have been mistaken!
Try learning a simple assembly language or IL, like ARM or CIL. Or better yet, make up your own implementation (like, some stack-based evaluation system). Then, try writing your own language and see what you come up with. I tried this when I was taking CS and it really enhanced my practical understanding of much of the theory they threw at us.
Actually, this was exactly what they were having us do, I just didn't fully realize it because of all the jargon and terminology I found kind of above my head at the time. But the experience really did help me later think about things like Java and C++ actually work, and more importantly, why.
Wow, testy testy.
Just because a company *can* create a piece of software doesn't mean that creating that software comes without significant cost. Blizzard is not a dumb company, and I'm sure they weighed the benefits of a LAN server against the cost in time and money. Certainly they knew it would upset fans like yourself, but it was a calculated decision that just isn't worth getting that upset over.
Or are you just upset at me? I think you're reading to much into my last sentence - that was mean in jest, yet you seem to have taken it too seriously.