Catch up on stories from the past week (and beyond) at the Slashdot story archive


Forgot your password?

Comment Re:Next post: how to jailbreak it. (Score 1) 231 231

My take is that it's an "oh, crap! my machine isn't working and the instructions for fixing it are on the net!" feature. That, or a pre-emptive strike in case of a virus some day. Boot into safari mode, browse the internet for the wisdom it contains, maybe connect to for an update, etc.

Comment Re:'Bout time (Score 1) 917 917

It's not so much the iphone is poorly designed, or other phones are poorly designed. The fact is (or seems to be...), there's a hard problem to solve in the smart phone arena and Apple, like others, have so far failed to solve the problem. So, they haven't designed a flaw into the device; instead, they've failed to design a solution to an inherent problem that nobody else has solved either.

Comment Re:The others (Score 1) 917 917

It's not quite the same thing. It's more like the CEO of a car company saying "all cars allow some road noise in, it's a problem for the whole industry". It's not so much that Apple has done anything wrong, but more like they've failed to fully solve a problem that everyone else has also failed to solve.

Comment Re:DRM, restrictions, outcry (Score 1) 610 610

The point that I think people are missing is that the fanboys were right to a degree -- the devices didn't *need* whatever feature-of-the-day was hot at the time. If the device needed it and didn't have it, people wouldn't have bought the device. Yet, the devices continued to sell. Now, as for the device being better with feature-of-the-day -- yes. The iPad would likely be better with multiprocessing for all apps, for instance. Does it *need* it, a million plus people say no.

Comment Re:people don't want to fiddle (Score 1) 1067 1067

I disagree. I've met very few people outside of techie circles who want a custom option or two. Kids, yeah. Geeks, yeah. My mom? Sisters? Cousins? People I interact with in professional offices (doctors, lawyers, etc). Not so much. They want to do what they want to do (doctoring, lawyering, planting gardens, sharing information with friends). None of that -- in the strictest sense -- requires "using a computer". The computer is just a device they have to use in order to do what they really want to do. Outside of computer geeks, nobody wants to "use a computer". They just don't. They want services that a computer provides, but as soon as a better device comes along that provides those services they'll drop the computer like a hot potato. I've met orders of magnitude more people like that than I have people who want options and ports and freedom to compile their own code.

Comment Re:easy. (Score 2, Insightful) 842 842

Working 60 hours is a choice. You can choose to work for companies that don't expect that, or you can choose to work for companies that do. Not all software companies are sweat shops.

Me? I rarely work more than 40.0 hours. Often it's more like 38 or so, depending on how you count. Though to be honest I spend a few hours here and there on some weekends, and also several after hours thinking about work. And I always work extra hours when extra hours are necessary to get the job done. But my butt is rarely in the office chair more than 40 hours a week.

"It might help if we ran the MBA's out of Washington." -- Admiral Grace Hopper