In vitro meat is not fake meat, just like cultured pearls are not fake pearls. In vitro meat is produced through the same cellular process, with the same animal DNA. Anybody who did 2 minutes of research would know that in vitro meat (aka cultured meat) is never called fake meat.
I am fine with having an "Advanced" button that brings up a dialog that has 95% of the options crammed into it. That means when the user chooses to look at the options, they are first presented with the most popular options, Gnome/Mac OS X style, but then if they want, they can dive into the more advanced options.
For example, I love Mozilla's about:config page. I wish there was something intermediate between the overly simplified preferences dialog and the about:config page, but I'm still satisfied with it.
Really, I think the "Advanced" button is an excellent solution most of the time. I don't understand why it's not done more often.
That's really great for the names that are popular and/or that many people get wrong (like GNU and Linux), but I even get wrong names like "Ada", "Haskell", and "Novell".
I pronounce it "post grey S Q L", but I've been learning lately that I pronounce a lot of things differently from everybody else. (e.g. "V" for vi) This is friggin 2008, can't we get some audio recordings of how these things are supposed to be pronounced?
and figuring out its dependencies is NOT for anyone less than intimately savvy with Linux In Kubuntu 7.10, clicking a.deb package brings up a dialog. Clicking the "Install" button on that will download all dependencies and install the package. Even a normal user could figure that out.
Source packages haven't reached that level of friendliness yet, but there's still "sudo apt-get build-dep foo" for those in the know.
The problem with Gnome is not that it automatically uses lots of defaults without asking the user how they want everything to work. The problem is that Gnome often does not allow settings to be changed from those defaults.
In my experience, KDE doesn't require more input from the user than Gnome or Mac OS X, but whenever I want to make a simple change about the behavior of some feature, KDE apps are much more likely to allow me to do so easily from within the GUI. Mac OS X and Gnome rarely have more than a handful of options.
Making default decisions for the user is good. Making decisions that the user is forced to go along with is bad.
That's what gives me hope with Linux. It continues to grow noticeably better very quickly. I still don't think Linux is ready for the masses, but I think the level of computer knowledge (or support) needed is dropping fast.
Average users can do that, but they won't know on their own to do it, and it would probably be quite scary to them. If you think an average user should know they need to do something like this, you are greatly overestimating the average user.
How is a desktop icon better than just offering it automatically the first time the user tries to play an MP3?
But I don't see why they don't just offer to install it when installing the OS. That would probably get around the legal issues about as well as the current solution.
I see what you're saying. The poster you replied to said Ada "is pretty much useless for writing real-world programs", but I only feel it is probably not a very good choice for most applications.
It's called open source, and it's taking over. Anybody can download a beta of Ubuntu 8.04 and run it forever. They don't have to worry about it expiring and Canonical cutting them off.
This kind of stuff that Apple is pulling may still be somewhat acceptable now, but times are changing.
Hopefully you've at least looked at Linux (or other open source) operating systems, right? You should consider what it would be like to switch to Linux, even if you end up deciding against it.
I really don't think a programming language can be considered functional if it doesn't have closures. I believe C++0x is slated to get closures, but until then, C++ is not functional IMO.
Two big reasons that I know of: Firefox 3.0 and Mozilla 2
Most developers are concentrating on getting Firefox 3.0 finished right now. I don't know if people have tried to do too much or if the schedule was too optimistic, but some important features have had difficult getting polished up in time. Just today I read on the changelog that cross-site XHR has been removed, and there's a high chance it won't make it into Firefox 3.0.
But Opera is also dealing with that, and they're doing a lot better. The bigger reason is that Mozilla has been planning a huge refactoring, called "Mozilla 2", for quite a while (e.g. exceptions in C++ code, which were previously forbidden). Many changes needed for Acid 3 are being put off due to that. So much stuff will be changing so drastically that many developers feel it would be a waste to make changes now that will just be ripped out again right after Firefox 3.0 ships.
Mozilla 2 is expected to take at least a year, maybe two or more, so Firefox has once again been caught at a bad time. The wait for a Firefox build that pases Acid 3 is going to be even longer than that for Acid 2. Hopefully Mozilla 2 will be clean and modern enough that future changes can occur more easily.
Also, a small part of of it may be due to Mozilla not accepting bullshit like this.
Slashdot Mirror
Pleas read The iPhone SDK and free software: not a match
Considering how defensive you were, despite your ignorance, I would definitely consider you to be an Apple fanboy.
Hence the hate for Ubuntu, for allowing normal users to be comfortable with Linux.
Tell that to Canonical. https://shop.canonical.com/product_info.php?products_id=181
I've never seen anything like this before. They are pretty easy to read, so if they can't be solved easily by computers, they do look quite promising.
That would be great, but how is a bot supposed to know whether it's chatting with a human or another bot?
In vitro meat is not fake meat, just like cultured pearls are not fake pearls. In vitro meat is produced through the same cellular process, with the same animal DNA. Anybody who did 2 minutes of research would know that in vitro meat (aka cultured meat) is never called fake meat.
How does that not topple over? The balance of that doesn't sound very good.
I am fine with having an "Advanced" button that brings up a dialog that has 95% of the options crammed into it. That means when the user chooses to look at the options, they are first presented with the most popular options, Gnome/Mac OS X style, but then if they want, they can dive into the more advanced options.
For example, I love Mozilla's about:config page. I wish there was something intermediate between the overly simplified preferences dialog and the about:config page, but I'm still satisfied with it.
Really, I think the "Advanced" button is an excellent solution most of the time. I don't understand why it's not done more often.
That's really great for the names that are popular and/or that many people get wrong (like GNU and Linux), but I even get wrong names like "Ada", "Haskell", and "Novell".
I pronounce it "post grey S Q L", but I've been learning lately that I pronounce a lot of things differently from everybody else. (e.g. "V" for vi) This is friggin 2008, can't we get some audio recordings of how these things are supposed to be pronounced?
Source packages haven't reached that level of friendliness yet, but there's still "sudo apt-get build-dep foo" for those in the know.
Ubuntu tries to release every 6 months. That's why most releases end with .04 or .10 (6.06 LTS being the exception).
The problem with Gnome is not that it automatically uses lots of defaults without asking the user how they want everything to work. The problem is that Gnome often does not allow settings to be changed from those defaults.
In my experience, KDE doesn't require more input from the user than Gnome or Mac OS X, but whenever I want to make a simple change about the behavior of some feature, KDE apps are much more likely to allow me to do so easily from within the GUI. Mac OS X and Gnome rarely have more than a handful of options.
Making default decisions for the user is good. Making decisions that the user is forced to go along with is bad.
That's what gives me hope with Linux. It continues to grow noticeably better very quickly. I still don't think Linux is ready for the masses, but I think the level of computer knowledge (or support) needed is dropping fast.
Average users can do that, but they won't know on their own to do it, and it would probably be quite scary to them. If you think an average user should know they need to do something like this, you are greatly overestimating the average user.
How is a desktop icon better than just offering it automatically the first time the user tries to play an MP3?
But I don't see why they don't just offer to install it when installing the OS. That would probably get around the legal issues about as well as the current solution.
I see what you're saying. The poster you replied to said Ada "is pretty much useless for writing real-world programs", but I only feel it is probably not a very good choice for most applications.
I don't think many applications are going to find much use for early warning radar.
It's called open source, and it's taking over. Anybody can download a beta of Ubuntu 8.04 and run it forever. They don't have to worry about it expiring and Canonical cutting them off.
This kind of stuff that Apple is pulling may still be somewhat acceptable now, but times are changing.
I selected the text and dragged it to the URL bar, since I already had my right hand on my mouse.
Hopefully you've at least looked at Linux (or other open source) operating systems, right? You should consider what it would be like to switch to Linux, even if you end up deciding against it.
I really don't think a programming language can be considered functional if it doesn't have closures. I believe C++0x is slated to get closures, but until then, C++ is not functional IMO.
If child porn were legal, there probably wouldn't be very much of it on Freenet. Problem solved.
Two big reasons that I know of: Firefox 3.0 and Mozilla 2
Most developers are concentrating on getting Firefox 3.0 finished right now. I don't know if people have tried to do too much or if the schedule was too optimistic, but some important features have had difficult getting polished up in time. Just today I read on the changelog that cross-site XHR has been removed, and there's a high chance it won't make it into Firefox 3.0.
But Opera is also dealing with that, and they're doing a lot better. The bigger reason is that Mozilla has been planning a huge refactoring, called "Mozilla 2", for quite a while (e.g. exceptions in C++ code, which were previously forbidden). Many changes needed for Acid 3 are being put off due to that. So much stuff will be changing so drastically that many developers feel it would be a waste to make changes now that will just be ripped out again right after Firefox 3.0 ships.
Mozilla 2 is expected to take at least a year, maybe two or more, so Firefox has once again been caught at a bad time. The wait for a Firefox build that pases Acid 3 is going to be even longer than that for Acid 2. Hopefully Mozilla 2 will be clean and modern enough that future changes can occur more easily.
Also, a small part of of it may be due to Mozilla not accepting bullshit like this.