The manufacturer of the drive examined has announced that the product is being retooled and will be reintroduced later this year, presumably with actual AES encryption.
Trust is a precious resource that you must cultivate; it's not a boomerang. Never risk throwing it away.
"So we went to Bobby's party and took some beers out into the woods with this new flashlight he got, and long story short, the fire department is trying their best to turn things around . .."
How 'bout instead of giving everyone $50 when something easily preventable--on the order of duh^10, if I remember high school math well enough--they invest in some fucking backup systems for when catastrophes happen?
a game that has a story better than any movie put out in the last 30 years
Any movie? How is the ventilation in the cave you've been living in for the last 30 years?
Sounds like you've watched nothing but the latest Scary Movie sequel(s) and Jerry Bruckheimer movies. Mass Effect might be a peak for gaming, but there are tons of amazing films from the last three decades that make it look pretty average in comparison.
Apple today announced that it sold (or delivered in the case of maintenance agreements) over two million copies of Mac OS X Leopard since its release on Friday, far outpacing the first-weekend sales of Mac OS X Tiger, which was previously the most successful OS release in Apple's history.
On June 6, 2005, Apple announced that they expected to deliver over two million copies of Mac OS X 10.4 Tiger by the end of that week (June 11, 2005). Mac OS X Tiger was released at 6pm on Friday, April 29, 2005. Therefore, it took 43 days to sell two million copies of Mac OS X Tiger vs. approximately 3 days for Leopard.
Additionally, Jobs revealed in his keynote that in 90 days, Apple had shipped 5 million copies of Leopard (which of course, means retail boxes plus new machines, but Leopard undoubtedly helped sell those machines). This resulted in 20% of the installed base running the new OS in 90 days.
People will say that if you don't like it, don't buy it. They are wrong.
Then you say:
Boycott Apple now. And boycott Amazon too. Do not accept that when you buy software, you in fact license it. Assert your right to play bought media on whatever you feel like, and to buy it through open interfaces not closed proprietary software. And agitate and publicize.
I'm not a developer, but I'm really thinking this Walled Garden thing is for the birds - which makes me want one of these less and less.
Okay, don't buy one. Apple's responsibility is not to you, the hacker (I love when I get the chance to use that word in the traditional sense), but to the person who buys the device and will never do anything unsupported with it. Why? Because these people either don't want to deal with incompatibilities or problems resulting from an update, or because they can't deal with them.
Normal users don't want to "update their phone" (which is a weird concept to many consumers in the first place) and have it break in some way. Because the official SDK isn't out yet, and there are no guidelines that third-party developers are following, Apple has no realistic way to support their software across updates. Attempting to do so at this point would be a massive, stupid waste of the available time of their engineers.
"Well," you're thinking, "the users who install unsupported third-party apps would be able to deal with bugs, or understand." No, most of them are going to whine and bitch on the Internet like they do now when Apple reverts their phone to a standard, known-good state during an update. But even if I'm wrong about that, it doesn't matter. The responsibility Apple's engineers have to the customer base on the whole is to guarantee that this phone that people bought "just works".
But this presents a problem, right? It makes this amazing portable device only what Apple wants. For some, this is a real issue. You can't disagree with that, really. To solve this problem, you need a supported SDK. And that's coming. Officially. That means developers like me can write software for the iPhone and it won't vanish after an update.
Releasing an SDK means you have to support it. Putting together an SDK you can support, and that is easy for developers to use, takes time. It's not just documentation, which in of itself is a large task if you want it done right--it's API design, build toolchain design, getting the supporting websites together and ready, training your developer support people in the new stuff, etc. It's huge! But Apple is doing it.
For now, third-party software developed through unsupported means is just that: unsupported. In the near future, according to Apple, we'll have a supported means of developing software for the iPhone. And it'll be better software, because we'll have the documentation we need.
There's no "walled garden", just a device whose SDK is in beta somewhere inside Cupertino walls.
Why is a company replacing a product that they shouldn't have let out the door in the first place news?
Yes, why would you ever expect someone to fix their mistake? The nerve of these people, setting the customer right after something went wrong! They're going out of business in no time if they keep up this level of customer satisfaction.
After the consumer lashback against DRM in the audio arena forced recording studios to go MP3, Hollywood is pursuing the Bush-style I-can't-be-bothered-with-history fiasco and repeating the same mistakes. Maybe after so many billions of lost revenue, they'll finally figure it out too. DRM is a dead end.
Listen, I think DRM is a failure, too. But this post is crap.
1. There's no consumer backlash against audio DRM on a large scale. 1+ billion songs sold through iTunes proves this. Conusmers may like DRM-free songs more, but they were sucking them up by the bucketload before iTunes Plus.
2. Recording studios haven't "gone to MP3". This has nothing to do with studios. Recording studios don't use anything but lossless audio or tape machines. They send the master to the record company who then does whatever they've agreed to with the individual distribution channels. (AAC for iTunes, with and without DRM; WMA for Microsoft with DRM; MP3 for some other smaller resale channels.)
3. The moment someone in a discussion of technology introduces any part of the George W. Bush presidency as an argument or comparison, whatever point they were trying to make immediately becomes lost.
One can't rent digital data because an integral part of renting something is returning it at the end of the rental period. Some people get this, and some people don't
So you don't pay full price and can watch it for a few days or some other period of time. After that, you aren't allowed to watch anymore without paying again. Everyone who isn't a Slashdot pedant calls this "renting a movie". There's nothing wrong about describing it as a digital movie rental service, because that's just how customers are going to see it.
The project needs a top to bottom rewrite to deal with orders of magnitude more demanding usage of large numbers of tabs over days or weeks at a time.
Whenever I see statements like this, I ask myself, "Has this person ever done any real software development?" Rarely does a project--especially one like Firefox--need a "top to bottom rewrite", regardless of problems it's having. Even when applications make the transition from one platform to another, they almost never require a total rewrite.
Posts like yours sound really informed, what with phrases like "implement threading both between tab sessions and within tabs themselves". The reality is that in addition to not knowing that a stack of existing bugs doesn't mean "it's time for a rewrite", phrases like the one I quoted are more vague than they will appear to those who don't know better. What does "threading between tab sessions and within tabs" mean, exactly? What operations do you want to see performed in separate threads?
Firefox doesn't need a top to bottom rewrite, but I think your post does.
You can do all the QA in the world before releasing an operating system, and it's not going to compare to what happens when the unwashed masses get their hands on the product.
Wrong. Why do people write crap like this?
There are far, far, far more actual bugs found and resolved during development than during your.0 release. The exception to this is when you decide to do almost no testing at all and leave bugs in everywhere, at which point you've got other problems entirely.
If translucency were so great in the real world, we would be printing on onion skin and writing on glass things. But I think translucency is more to show that they can do something in 3d, done by people that have no real vision as to what to do with it.
It looks and feels awesome. It's easy to do from the engineering side.
Did I mention it looks and feels awesome? Sure, you can go overboard, but you can go overboard with anything. Translucency is pretty stylish, and last time I checked, most people like stylish things.
european carriers warn u when welcoming you on their network through an sms. this is 2007, europe, consumer friendly. cut the venom:) - if the guy did not get a welcoming sms, the phone was off - no standby, and if it was in standby and did not announced the sms, then Iphone has a serious issue. basta.
You don't know that he didn't get one and simply ignored it, thinking "screen off, cell phone off". (Which is retarded in 2007 for anyone who's ever owned a cell phone. Sorry.) He's pissed off about a huge bill that could likely be attributed to his own stupidity, and you make the leap that he's disclosed every piece of relevant information.
It is a ridiculous assumption that "since he didn't report an SMS warning, the phone was off". Hell, he could've gotten the SMS and not ignored it, but not known he got one, because he got the message while his phone was in a bag or in a place that just wasn't conducive to hearing the tone or feeling the vibration. After his screen dim time setting passed, it went back to a dim screen, and he didn't touch it until he got home.
In the end, this man spent $600 on a cell phone, in 2007, and didn't read the manual or understand that "screen not lit up" does not mean "the thing is off".
The problem was that their three Iphones were racking up a bill for data charges using foreign phone charges. The Iphone regularly updates e-mail, even while it's off, so that all the messages will be available when the user turns it on.
This is bullshit.
It doesn't sound like the unit was powered off. It sounds like the screen was off, and like my old RAZR, the unit will continue to operate in the background while the screen is off. Stupid, lazy consumer didn't bother reading the manual, which clearly discusses how to POWER THE PHONE OFF COMPLETELY and WHAT AIRPLANE MODE IS, which accomplishes the same task this guy required.
Seriously, who the fuck thinks a phone is "off" just because the screen isn't lit up? This is 2007, right? The age of the cell phone cowboy.
There's no flaw here. The vast, vast majority of iPhone users are satisfied that it will happily do its thing while the screen is off, in your pocket. Otherwise, I couldn't be notified of mail whenever I got it.
Next time, if you spend $600 on something, read the motherfucking manual. Apple goes out of their way to write clear, simple manuals for the very reason that people don't want to have to be computer scientists to understand them. Sucks to be you, dude.
There's no point in being upset about the use of the phrase "ethical hacker". Yes, we all know that being a "hacker" isn't an evil thing. But we've lost that battle in the general population from here until the end of time.
"But hacker already meant something noble! There should only be a modifier for 'evil hacking'!"
Yes, well, no one cares. No one will care. It's debatable whether or not anyone should care. When you talk to your nerd buddies, you can use "hacker" all you like in the "correct" manner and that's okay; when it's a different audience, these days, you have to make what you mean clearer than that. And that's okay. Most people just don't have time or interest to worry about the origin of the word.
In fact, I'm going out on a limb and stating that having this "ethical" modifier is a good thing for the community. Take a moment to look at the phrasing here objectively. If the masses have already decided that "hackers" are bad, and that word is locked in their minds as the dark underbelly of the Internet--terrorists whose only goal is to harm you, your family, your company, and your government--then perhaps by seeing and hearing "ethical hackers", they'll begin to understand that not only is it possible to have good hackers, but that they actually exist.
Slashdot Mirror
He started Boing Boing.
Doctorow didn't even start Boing Boing, Mark Frauenfelder and Carla Sinclair did. He wasn't even on board when it went from a 'zine to a web site.
http://en.wikipedia.org/wiki/Boing_Boing#History
The manufacturer of the drive examined has announced that the product is being retooled and will be reintroduced later this year, presumably with actual AES encryption.
Trust is a precious resource that you must cultivate; it's not a boomerang. Never risk throwing it away.
"So we went to Bobby's party and took some beers out into the woods with this new flashlight he got, and long story short, the fire department is trying their best to turn things around . . ."
How 'bout instead of giving everyone $50 when something easily preventable--on the order of duh^10, if I remember high school math well enough--they invest in some fucking backup systems for when catastrophes happen?
Fox is full of shit, but so is this:
a game that has a story better than any movie put out in the last 30 years
Any movie? How is the ventilation in the cave you've been living in for the last 30 years?
Sounds like you've watched nothing but the latest Scary Movie sequel(s) and Jerry Bruckheimer movies. Mass Effect might be a peak for gaming, but there are tons of amazing films from the last three decades that make it look pretty average in comparison.
I develop for Final Cut Pro and Motion, and the last time I installed a beta for them, they installed a component which broke QuickTime.
So the last time you installed software that was known not to be production-level, it was not production-level?
Holy. Shit.
Apple sells two million copies of Mac OS X Leopard in first weekend
Additionally, Jobs revealed in his keynote that in 90 days, Apple had shipped 5 million copies of Leopard (which of course, means retail boxes plus new machines, but Leopard undoubtedly helped sell those machines). This resulted in 20% of the installed base running the new OS in 90 days.
You were saying?
tl;dr
Did two people write your post independently?
People will say that if you don't like it, don't buy it. They are wrong.
Then you say:
Boycott Apple now. And boycott Amazon too. Do not accept that when you buy software, you in fact license it. Assert your right to play bought media on whatever you feel like, and to buy it through open interfaces not closed proprietary software. And agitate and publicize.
I'm not a developer, but I'm really thinking this Walled Garden thing is for the birds - which makes me want one of these less and less.
Okay, don't buy one. Apple's responsibility is not to you, the hacker (I love when I get the chance to use that word in the traditional sense), but to the person who buys the device and will never do anything unsupported with it. Why? Because these people either don't want to deal with incompatibilities or problems resulting from an update, or because they can't deal with them.
Normal users don't want to "update their phone" (which is a weird concept to many consumers in the first place) and have it break in some way. Because the official SDK isn't out yet, and there are no guidelines that third-party developers are following, Apple has no realistic way to support their software across updates. Attempting to do so at this point would be a massive, stupid waste of the available time of their engineers.
"Well," you're thinking, "the users who install unsupported third-party apps would be able to deal with bugs, or understand." No, most of them are going to whine and bitch on the Internet like they do now when Apple reverts their phone to a standard, known-good state during an update. But even if I'm wrong about that, it doesn't matter. The responsibility Apple's engineers have to the customer base on the whole is to guarantee that this phone that people bought "just works".
But this presents a problem, right? It makes this amazing portable device only what Apple wants. For some, this is a real issue. You can't disagree with that, really. To solve this problem, you need a supported SDK. And that's coming. Officially. That means developers like me can write software for the iPhone and it won't vanish after an update.
Releasing an SDK means you have to support it. Putting together an SDK you can support, and that is easy for developers to use, takes time. It's not just documentation, which in of itself is a large task if you want it done right--it's API design, build toolchain design, getting the supporting websites together and ready, training your developer support people in the new stuff, etc. It's huge! But Apple is doing it.
For now, third-party software developed through unsupported means is just that: unsupported. In the near future, according to Apple, we'll have a supported means of developing software for the iPhone. And it'll be better software, because we'll have the documentation we need.
There's no "walled garden", just a device whose SDK is in beta somewhere inside Cupertino walls.
Why is a company replacing a product that they shouldn't have let out the door in the first place news?
Yes, why would you ever expect someone to fix their mistake? The nerve of these people, setting the customer right after something went wrong! They're going out of business in no time if they keep up this level of customer satisfaction.
After the consumer lashback against DRM in the audio arena forced recording studios to go MP3, Hollywood is pursuing the Bush-style I-can't-be-bothered-with-history fiasco and repeating the same mistakes. Maybe after so many billions of lost revenue, they'll finally figure it out too. DRM is a dead end.
Listen, I think DRM is a failure, too. But this post is crap.
1. There's no consumer backlash against audio DRM on a large scale. 1+ billion songs sold through iTunes proves this. Conusmers may like DRM-free songs more, but they were sucking them up by the bucketload before iTunes Plus.
2. Recording studios haven't "gone to MP3". This has nothing to do with studios. Recording studios don't use anything but lossless audio or tape machines. They send the master to the record company who then does whatever they've agreed to with the individual distribution channels. (AAC for iTunes, with and without DRM; WMA for Microsoft with DRM; MP3 for some other smaller resale channels.)
3. The moment someone in a discussion of technology introduces any part of the George W. Bush presidency as an argument or comparison, whatever point they were trying to make immediately becomes lost.
One can't rent digital data because an integral part of renting something is returning it at the end of the rental period. Some people get this, and some people don't
So you don't pay full price and can watch it for a few days or some other period of time. After that, you aren't allowed to watch anymore without paying again. Everyone who isn't a Slashdot pedant calls this "renting a movie". There's nothing wrong about describing it as a digital movie rental service, because that's just how customers are going to see it.
Some people get this, and some people don't.
Evil piggies just want to cry victim.
We're supposed to take you seriously after this sentence?
The project needs a top to bottom rewrite to deal with orders of magnitude more demanding usage of large numbers of tabs over days or weeks at a time.
Whenever I see statements like this, I ask myself, "Has this person ever done any real software development?" Rarely does a project--especially one like Firefox--need a "top to bottom rewrite", regardless of problems it's having. Even when applications make the transition from one platform to another, they almost never require a total rewrite.
Posts like yours sound really informed, what with phrases like "implement threading both between tab sessions and within tabs themselves". The reality is that in addition to not knowing that a stack of existing bugs doesn't mean "it's time for a rewrite", phrases like the one I quoted are more vague than they will appear to those who don't know better. What does "threading between tab sessions and within tabs" mean, exactly? What operations do you want to see performed in separate threads?
Firefox doesn't need a top to bottom rewrite, but I think your post does.
You can do all the QA in the world before releasing an operating system, and it's not going to compare to what happens when the unwashed masses get their hands on the product.
.0 release. The exception to this is when you decide to do almost no testing at all and leave bugs in everywhere, at which point you've got other problems entirely.
Wrong. Why do people write crap like this?
There are far, far, far more actual bugs found and resolved during development than during your
Maybe the guy at Computerworld could give us seeded developers a copy of the GM before release. Apple sure didn't bother.
"Overall, Mac OS X 10.5 Leopard is perhaps the most significant update in the history of Mac OS X -- perhaps in the history of Apple
Maybe in the history of Mac OS X, but definitely not the history of Apple itself. I'd say that would be, oh, the shift to Unix.
If you're dumb enough to drive in Manhattan, you probably need a machine to park your car for you.
You cannot pirate something you are allowed to pay nothing for.
I really don't want to hear about anyone's URI hole. Ew.
If translucency were so great in the real world, we would be printing on onion skin and writing on glass things. But I think translucency is more to show that they can do something in 3d, done by people that have no real vision as to what to do with it.
It looks and feels awesome. It's easy to do from the engineering side.
Did I mention it looks and feels awesome? Sure, you can go overboard, but you can go overboard with anything. Translucency is pretty stylish, and last time I checked, most people like stylish things.
european carriers warn u when welcoming you on their network through an sms. this is 2007, europe, consumer friendly. cut the venom :) - if the guy did not get a welcoming sms, the phone was off - no standby, and if it was in standby and did not announced the sms, then Iphone has a serious issue. basta.
You don't know that he didn't get one and simply ignored it, thinking "screen off, cell phone off". (Which is retarded in 2007 for anyone who's ever owned a cell phone. Sorry.) He's pissed off about a huge bill that could likely be attributed to his own stupidity, and you make the leap that he's disclosed every piece of relevant information.
It is a ridiculous assumption that "since he didn't report an SMS warning, the phone was off". Hell, he could've gotten the SMS and not ignored it, but not known he got one, because he got the message while his phone was in a bag or in a place that just wasn't conducive to hearing the tone or feeling the vibration. After his screen dim time setting passed, it went back to a dim screen, and he didn't touch it until he got home.
In the end, this man spent $600 on a cell phone, in 2007, and didn't read the manual or understand that "screen not lit up" does not mean "the thing is off".
The problem was that their three Iphones were racking up a bill for data charges using foreign phone charges. The Iphone regularly updates e-mail, even while it's off, so that all the messages will be available when the user turns it on.
This is bullshit.
It doesn't sound like the unit was powered off. It sounds like the screen was off, and like my old RAZR, the unit will continue to operate in the background while the screen is off. Stupid, lazy consumer didn't bother reading the manual, which clearly discusses how to POWER THE PHONE OFF COMPLETELY and WHAT AIRPLANE MODE IS, which accomplishes the same task this guy required.
Seriously, who the fuck thinks a phone is "off" just because the screen isn't lit up? This is 2007, right? The age of the cell phone cowboy.
There's no flaw here. The vast, vast majority of iPhone users are satisfied that it will happily do its thing while the screen is off, in your pocket. Otherwise, I couldn't be notified of mail whenever I got it.
Next time, if you spend $600 on something, read the motherfucking manual. Apple goes out of their way to write clear, simple manuals for the very reason that people don't want to have to be computer scientists to understand them. Sucks to be you, dude.
There's no point in being upset about the use of the phrase "ethical hacker". Yes, we all know that being a "hacker" isn't an evil thing. But we've lost that battle in the general population from here until the end of time.
"But hacker already meant something noble! There should only be a modifier for 'evil hacking'!"
Yes, well, no one cares. No one will care. It's debatable whether or not anyone should care. When you talk to your nerd buddies, you can use "hacker" all you like in the "correct" manner and that's okay; when it's a different audience, these days, you have to make what you mean clearer than that. And that's okay. Most people just don't have time or interest to worry about the origin of the word.
In fact, I'm going out on a limb and stating that having this "ethical" modifier is a good thing for the community. Take a moment to look at the phrasing here objectively. If the masses have already decided that "hackers" are bad, and that word is locked in their minds as the dark underbelly of the Internet--terrorists whose only goal is to harm you, your family, your company, and your government--then perhaps by seeing and hearing "ethical hackers", they'll begin to understand that not only is it possible to have good hackers, but that they actually exist.