LindowsOS Will Bundle AOL Client
ealar dlanvuli writes "BuisnessWeek Online is reporting that AOL/TW and Lindows have decided to work together in bundling a version of Netscape 7 with future Lindows products. One wonders if they should instead be supporting OEone and making it scream."
Man, what a piss-poor headline. I was actually excited for a second, hoping that there really would be a client for AOL *the service* bundled with Lindows. But no... it's just Netscape 7, which isn't any more functionally than Mozilla really (less in some areas).
I would have personally loved an AOL client on Linux. My family has used AOL for years, both as a primary ISP and a secondary service. I've had the same email account on AOL for years (yes, it's spam-ridden, but a lot of my friends still use it) and it would be nice to be able to access it via some method other than their (once crappy, now much better) webmail interface.
In addition to that, there's the fact that having AOL for Linux would give it another crucial app for desktop migration. Not that I'd expect it to work nearly as nicely in setting up your internet connection on Linux as it does on Windows or Mac, which is where AOL really shines, but the ability to access their full service would be nice.
But no. We get Netscape, something the whole of Unix has pretty much outgrown with Konqueror, Opera, Mozilla, and its spinoffs. Too bad, back to waiting.
"I may not have morals, but I have standards."
Lindows isn't aimed at your average Linux geek. Its core market will be people who want a cheap, functional OS (at the very least, cheap rules out MS solutions) but don't/can't/won't/ use GNU/Linux.
To misquote the oft-cited Slashdot Linux line - "I'm going to install (%distro) on my parent's home machine!" But would you really? Would you really install Red Hat or Mandrake on your parent's machine, when you know all they need is a web browser, an email client and perhaps an instant messenger client? Would you *really* take the time to install it, secure it, solve dependency issues and then *teach* them step-by-step how to use the OS until they reached the point where they weren't calling you five times a week for support?
The entire reason Lindows exists is to provide a cheap, functional and easy-to-use alternative to Microsoft on the desktop. They seem to have the first part worked out, but it remains to be seen if they can get the last two right.
Linux geeks aren't going to replace their Debian or Gentoo boxes with Lindows, because its not what most of them want (primarily). If Lindows fails to get the "mum and dad" and "I just want to do my homework and then use IRC" groups of people, than it will die a slow and painfull death.
That is why an AOL client on the Lindows desktop would be beneficial. It's a quick, easy and relatively painless way to get normal, non-tech-savvy users on the 'Net.
Of course, this is all rather academic because if you'd read the article, you'd know that the headline is BS and that the linked story talks about including Netscape 7, not AOL.
Janie took my gun...
Look:
With its AOL licensing deal, the Lindows said that consumers can enjoy the versatility of Netscape browser and communications capabilities right out-of-the-box with an icon-driven interface.
Whoa - icons! Let me get this straight... Are they saying they'll use those new, often abstract, graphic representations of commands you give to the computer? This, my friends, seem to be a browser for the 21st century. Let's all embrace Netscape 7 in all its glory.
Beware: In C++, your friends can see your privates!
Everyone has already nailed you with the "Lindows is going after Windows users", but I've got something else to add.
I would say, if someone would write a single control panel-type interface, where the important things could be configured in a centralized locations (e.g. network, software packages, display, keyboard, mouse, etc) and make it blatantly obvious that it should be used (links on the desktop, and in an obviously labeled menu) then I would put Linux up against Windows.
The problem with Linux isn't that there's no tools to configure it... the problem is that the tools often don't quite work, there are a lot of different ones (at least one for each subject) and their interfaces aren't always as easy as windows equivalent (although some do surpass their counterparts). In fact, being able to configure everything in one place, and having it work right the first time, every time, would be a substantial improvement over Windows!
If any distro got to that point, I would distribute it to every non-gamer I know (games are the big hold up, keeping people I know, from switching).
So, in case you got lost in bracket-hell, I'll say it again. With just a LITTLE work, I think Linux would be user-friendly enough to completely replace Windows.
That said, I still think more could be done with OpenBSD than Linux. Since it detects all hardware at startup, and loads drivers for hardware automatically, you would only need a very simple program that parses dmesg, then automatically reconfigures XFree86, and put up any messages, like "A new NIC was found, please type the IP address".
Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
Interesting. You're right, there it is. AOL client 7.0 sneak preview.
So my next question is how do they do this? Is the client fully native? Compiled with winelib? Just run through wine? Will this work on my debian setup?
Still, thank you for pointing this out. This is great news, especially if it can run in Mandrake and the like. Hopefully we'll know more soon.
"I may not have morals, but I have standards."
OEOne sounded good, so I figured, what the heck. I cranked up the script in lynx, and let it rip.
Well, the EULA that pops up makes Microsoft look tame.
It starts with the usual disclaimer of how they "take no responsibility for the
consequences of running this script."
That seemed pretty standard, although worded a little harsh.
It then goes through some normal install stuff, then comes the fun!
Issue 1. Your bound by the license of any other software they install, even though you don't see them.
Issue 2. Any software, or plugins they OEOne installs can ONLY be used while using OEOne's desktop, and can not be called directly.
Issue 3. Automatic communication. They can do any communication they want to, but you can shut off "MOST" of it in the pref settings. (MOST? Oh, that's nice and gray for a EULA. Stated clearly, it means that you can't shut it _ALL_ off)
Issue 4. DRM. Yup, it's in there, and they can stick in as much as they want.
Fortunately, you can hit cancel, and throw it all away. I looks to me like they are trying to complete directly with Microsoft, with restrictions, and control over my machine. I switched to Linux to get away from that crap! Sure, the screenshots looked nice, but I'll never be seeing this on MY machine.