Just because you're used to a CLI doesn't make it better. Why would I want to read a bunch of documentation, mess with command line options, then read whole block of text to see what it did?
I'd much rather sit back in my chair, click something, and then see if it worked. Don't make me read a bunch of man pages just to do a simple task.
In essence, the question here is whether it's okay for the user to be lazy and use a GUI, or whether the programmer should be too lazy to develop a GUI.
Apple sells to geeks, and geeks tend to have Apple products AND products from other companies.
I'm sure if you look at sales of netbooks, you'll find that most of them are purchased by geeks who can't stand being without a computer and want something small and light for travel purposes. Many of these geeks will also own Apple products. Why? Because they're geeks.
Twitter needs to focus on their core service. It frequently goes offline, like many social services did when their growth was faster than expected (Friendster, LiveJournal, etc.)
The lessons of other social networks should be a clue that focusing on infrastructure stability needs to be a priority. People will get used to a crappy interface -- just look at MySpace -- but will not put up with unstable service for long.
Slashdot Mirror
Yes, but only this film:
http://www.imdb.com/title/tt0115964/
I never got the leet speak in spam thing. Sure, it might get past the filter, but who can read it? Are they trying to sell drugs to script kiddies?
I wonder if you can run Duke Nukem Forever on the XO.
This will make the "xray" threads on /b/ waaay more interesting.
For years we've heard predictions about how we'll run out of addresses "this year." Yet we haven't.
I assume that's partly because my toaster doesn't have an IP, but it's also got to be because of NAT.
And yet, Macs *are* capable of uploading viruses to alien ships.
Just because you're used to a CLI doesn't make it better. Why would I want to read a bunch of documentation, mess with command line options, then read whole block of text to see what it did?
I'd much rather sit back in my chair, click something, and then see if it worked. Don't make me read a bunch of man pages just to do a simple task.
In essence, the question here is whether it's okay for the user to be lazy and use a GUI, or whether the programmer should be too lazy to develop a GUI.
That makes a hell of a lot more sense than the article summary.
Wait... you actually LIKE Xcode?
So far I've never met anyone who didn't have the urge to jump off a building after being forced to use it.
Any serious application is going to take weeks if not months to QA. 24 hours is meaningless.
Even Larry Ellison thinks Larry Ellison is a dick.
Let's also not forget that there's no way to "return" an app or even to politely ask for your money back. If the app doesn't work, you're screwed.
I can see why piracy is an attractive option.
Yes, but all those records were scratched up by hip-hop DJs in the mid 80's.
That's why we need to start making records again.
Slashdot has ads?
I'm not sure people with leather phone fetishes are enough to keep Nokia in business.
They used to have a lot more. 44% is way, way down from a couple years ago.
The smartphone apps never went down as far as I could tell.
And a true geek knows the difference between "their" and "there."
A rod of applause to you.
Apple sells to geeks, and geeks tend to have Apple products AND products from other companies.
I'm sure if you look at sales of netbooks, you'll find that most of them are purchased by geeks who can't stand being without a computer and want something small and light for travel purposes. Many of these geeks will also own Apple products. Why? Because they're geeks.
Are there any aspects of Java that aren't unnecessarily complicated?
Go try and tell a computer newbie what JRE is, its relation to Java, and why they need to install it.
At least Google isn't as bad as Sun.
One day I was on Java 1.4, and then next thing you know, POOF, I'm on Java 5!
I thought TurboText from Borland was better.
The mouse, ethernet, OOP... who cares? Isn't LambdaMOO enough of a reason to celebrate PARC?
Twitter needs to focus on their core service. It frequently goes offline, like many social services did when their growth was faster than expected (Friendster, LiveJournal, etc.)
The lessons of other social networks should be a clue that focusing on infrastructure stability needs to be a priority. People will get used to a crappy interface -- just look at MySpace -- but will not put up with unstable service for long.