Slashdot Mirror


AOL To Finally Switch To Mozilla?

pitabutter writes "Sounds like AOL is joining the list of companies making the internal switch to Linux, taking their default browser choice along with them. Oddly, second article in a short time linking AOL and Red Hat. " As with all things with AOL/Mozilla, I'll actually believe it when the darn thing ships - but the internal switch to Linux is something that I've also heard from people.

149 of 383 comments (clear)

  1. Does that mean... by codexus · · Score: 5, Funny

    that I'll be using the same browser that AOLers use. I'll be too ashamed and switch to Konqueror :)

    --
    True warriors use the Klingon Google
    1. Re:Does that mean... by Ewan · · Score: 2

      Nope, Konquerer is a completely independant browser, it can use the gecko rendering engine from mozilla, but it doesn't by default.

      Galeon is the cut-down mozilla browser.

      Ewan

    2. Re:Does that mean... by 10Ghz · · Score: 2

      "... except Konqueror is based on Mozilla. D'oh!"

      No it isn't. Check your facts.

      --
      Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
  2. publicity? by Transient0 · · Score: 2

    I don't suppose AOL will make a big deal of it when they do actually change over, eh?

    I have to admit that i'm pretty keyed up on the IBM/Linux publicity. It would be pretty cool if AOL with throw a Linux shout-out in a couple of their infernal TV ads.

    1. Re:publicity? by skt · · Score: 2, Insightful

      I am sure that when they do switch their internal browser, they might mention 'new and improved AOL 8!!', but that's about it. The end users (especially AOL users), don't care what rendering engine they are using to view web pages. And they certainly don't care that AOL is making an internal switch to linux. AOL marketing is smart, that's why they are "#1" :P

    2. Re:publicity? by opkool · · Score: 5, Insightful

      Well.

      From now on, for a website to be defined as "AOL friendly", they will need to be "mozilla friendly". If they are not (now they only need to be "designed for IExplorer"), AOL viewers will complaint about those "pesky webpages makers that cannot get a webpage done right" and will not use them (hint: think web-commerce, web-services....)

      Because AOL users represent the biggest piece of the internet consumers pie (at least, in the USA), all those websites will need to adapt and become "AOL (mozilla) compliant" ( = W3C compliant?? ) or (economically) die.

      Now, with many websites turning into paysites, if AOL people cannot see your website in a proper and appealing way (font types, font syzes, table rendering, html extensions.... all those things that makes a website "designed for IExplorer" .... and mostly unfriendly to mozilla/W3C) they will start to see that their projected visitors/revenue fall down because of lack of standards adherement.

      So, I say that this is good for us, W3C-compliant browsers (mozilla, Konqueror...)

    3. Re:publicity? by IGnatius+T+Foobar · · Score: 4, Insightful
      Now, with many websites turning into paysites, if AOL people cannot see your website in a proper and appealing way (font types, font syzes, table rendering, html extensions.... all those things that makes a website "designed for IExplorer" .... and mostly unfriendly to mozilla/W3C) they will start to see that their projected visitors/revenue fall down because of lack of standards adherement.
      And that's a beautiful thing.

      I'm a die-hard Linux advocate, but as soon as AOL 8.0 is released, I'm going to begin strongly recommending AOL to Mac and Windows people who need a dial-up ISP. AOL is pushing a standards-compliant browser, and that's good for the whole of the Internet. AOL also continues to push RealPlayer, which isn't all that great, but it's better than the alternative (Windoze Media everywhere) and will at least keep the market divvied up until an open standard for digital media can be adopted as well.

      As the webmaster of xiph.org so elegantly wrote, "The Internet exists today and continues to move forward despite, not because of, corporate self-interest; critical mass passed the point of no return long before Microsoft and Netscape tried to salt the earth of their rivals. " Open standards are very important, and it's good to see that someone as big as AOL is going to cause the Internet to be a bit more standards-based. Obviously they're doing it to suit their own ends, of course, but they're doing it.
      --
      Tired of FB/Google censorship? Visit UNCENSORED!
    4. Re:publicity? by ncc74656 · · Score: 2
      From now on, for a website to be defined as "AOL friendly", they will need to be "mozilla friendly". If they are not (now they only need to be "designed for IExplorer"), AOL viewers will complaint about those "pesky webpages makers that cannot get a webpage done right" and will not use them (hint: think web-commerce, web-services....)

      FWIW, the last time I reworked a website, there was no difference between IE and Mozilla that needed to be handled. Nutscrape 4 had major problems with CSS, but the beta Mozilla that was available at the time rendered the site nearly identically to IE.

      (If an AOLer whines about my site, I'd be inclined to tell him to bugger off and get a real Internet connection. Then again, I'm not running a site that tries to make money.)

      --
      20 January 2017: the End of an Error.
    5. Re:publicity? by GreyPoopon · · Score: 3, Interesting
      Because AOL users represent the biggest piece of the internet consumers pie (at least, in the USA), all those websites will need to adapt and become "AOL (mozilla) compliant" ( = W3C compliant?? ) or (economically) die.

      This is interesting. I just hit the "Submit" button on an opinion that takes it from the other point of view. I indicated that AOL may face a risk of departing customers if too many web pages don't work. This all brings up an interesting question: Is AOL's large install base enough to whip the noncompliant web sites into shape? Do you think they'd start working on this problem in advance of a Mozilla-based delivery? What's the right approach to make sure the web sites change rather than the AOL customer base?

      --

      GreyPoopon
      --
      Why is it I can write insightful comments but can't come up with a clever signature?

    6. Re:publicity? by flacco · · Score: 2
      Now, with many websites turning into paysites, if AOL people cannot see your website in a proper and appealing way (font types, font syzes, table rendering, html extensions.... all those things that makes a website "designed for IExplorer" .... and mostly unfriendly to mozilla/W3C) they will start to see that their projected visitors/revenue fall down because of lack of standards adherement.

      I am clapping my hands with glee at the thought of all those dick-head "IE only" web designers frantically scrambling about trying to get their web pages standards-compliant.

      MS drone: "But - but I used FrontPage! That's from MICROSOFT! I thought Microsoft WAS the Internet! What's going on???"

      Boss: "Shut up you WORM! I don't know what happened, but if you don't fix our website FAST and get our numbers back up, YOU'RE FIRED!"

      Hehehehehe....

      --
      pr0n - keeping monitor glass spotless since 1981.
    7. Re:publicity? by Arker · · Score: 2

      Do you think they'd start working on this problem in advance of a Mozilla-based delivery?

      According to the article:


      The only thing that might delay -- not stop, just delay -- AOL's change from Explorer to a Mozilla-based browser is allowing time for some of AOL's largest and most important "partner sites" to do away with any Explorer-specific features they have been using in place of W3C standards.
      --
      =-=-=-=-=-=-=-=-=-=-=-=-=-=-
      Friends don't let friends enable ecmascript.
    8. Re:publicity? by flacco · · Score: 2
      I indicated that AOL may face a risk of departing customers if too many web pages don't work.

      I don't think so. For starters, commercial web designers follow stories like these, and those that are using IE-only crap will start working some long weekends to make sure their customers (internal or external) don't have broken websites. Or go out of business / get fired - their choice.

      On the other end of the spectrum, if you're the typical AOL user and suddenly your cousin's Limp Bizkit websitez be goin all shiznit on you, are you going to blame Great Mother AOL, or your three-bongloads-a-day cousin? I don't think they'll start firing off angry missives to Steve Case about the deplorable lack of support for non-standards.

      --
      pr0n - keeping monitor glass spotless since 1981.
  3. Doesn't this say it all? by wackybrit · · Score: 4, Interesting

    As far as an AOL client for Linux, one Linux-using AOL employee says, "How many Linux people do you know personally who would sign up for AOL if we had a Linux client? I don't know a single one, myself. I have an account with another ISP I use at home with my Linux box, and probably wouldn't use AOL from home even if I could."

    'Linux people'? It's no surprise that Linux won't make it onto the average desktop with that sort of attitude.

    Their reckoning is that.. all Linux users are nerds so they don't need to use such a crappy ISP. That might be true now but if AOL doesn't offer a Linux client then they're implying that they think Linux will continue to remain a nerd interest.

    With support like that from the biggest companies in the world, who needs enemies?

    1. Re:Doesn't this say it all? by IamTheRealMike · · Score: 4, Interesting
      'Linux people'? It's no surprise that Linux won't make it onto the average desktop with that sort of attitude.

      Actually (hides face in shame) I would have loved an AOL Linux client a while ago. My family used AOL at the time because a) it was cheap and b) it worked freecall with the UK cable network. An AOL client would have been great - unfortunately there wasn't one of course so we had to leave AOL and switch to NTL World which are pretty bad, worse even than AOL!

      So while they may have a point now, the makeup of 'Linux people' is changing, and is moving further away from the geek demographic all the time. thanks -mike

    2. Re:Doesn't this say it all? by Surak · · Score: 5, Interesting

      With support like that from the biggest companies in the world, who needs enemies?

      I'll make a prediction right now...Do I have to say it? Oh, I guess I do...

      AOL/TW will buy Red Hat. They're looking to break free of Microsoft, especially since Microsoft basically screwed them over with XP. They will finally make good on a Mozilla/AOL client, they will release versions for Linux and Windows and continue with the strategy that Linux is the cheapest way to get AOL into every household in America.

      People buying computers just to get on the Internet (there's still a lot of those) will buy Linux machines (without really knowing why) that have AOL installed on them. Microsoft will slowly lose their grip on the consumer desktop market...

      They'll continue to own the commercial market until the same twits who insist on the use of Windows in the commercial market because it "looks just like what i've got at home" will have Linux at home, and then they'll want that because it "looks just like what I've got at home."

      Boom, Microsoft's stranglehold on the desktop fails, Linux takes over and utopia finally sets in.

      Whatcha think? Too far fetched? :-P

    3. Re:Doesn't this say it all? by An+Onerous+Coward · · Score: 3, Interesting

      Worse, they're implying that AOL is for non-geeks only.

      I browsed Google for solutions for folk who want to use AOL. While I did find a listing for AOL Tunneling Client for UNIX on linux.org, the web page that it links to seems to have disappeared. Perhaps the WINE project offers another ray of hope.

      It seems like the best solution would be for AOL to switch from its proprietary internal protocols to TCP/IP and family. With packet filtering, they should be able to maintain just as much control over the user environment as they do now, while making it easier to support "non-standard" clients.

      And while they're at it, I'd like them to switch to IPv6. Plus I want world peace and a pony.

      Seriously, there are a thousand good reasons to switch to TCP/IP. What advantages do they gain by sticking with what they have?

      --

      You want the truthiness? You can't handle the truthiness!

    4. Re:Doesn't this say it all? by blakestah · · Score: 4, Insightful

      I dunno abour your predictions, but AOL switching to a Gecko rendering base will do wonders for web standards compliance.

      And an AOL-linux client will be a big seller too, but at the OEM level. Grandma will buy a box set up to connect, with a user interface she would never know is linux if you asked her. It will have an AOL interface - and a linux engine.

    5. Re:Doesn't this say it all? by DrXym · · Score: 2

      Until a distribution such as Red Hat / Mandrake becomes a mass-market, consumer friendly operating system there is little chance of having AOL. Can you imagine the support calls AOL would be getting if they shipped on Linux now? Hell, how many people alone would call up complaining that they put the AOL CD into the drive but no CD appeared on their desktop?

    6. Re:Doesn't this say it all? by CokeBear · · Score: 2
      If that was the plan, why not buy Apple and license Mac OS X?

      There are already more Mac OS X installations than all flavors of Linux.

      --
      Reality has a liberal bias
    7. Re:Doesn't this say it all? by 4of12 · · Score: 2

      'Linux people'?

      Well, hey, I'm a Linux people and I dont' have AOL as my ISP. But am I concerned? No.

      AOL doesn't need the niche nerd market. It's not where profits are. Nerds basically do their own tech support and only call with such technical complaints that would require staffing your support center with ubernerds paid 6 figures. No, that is not a market that AOL wants. It's proof they have half a brain.

      What is more encouraging however is that they're beta deploying Linux to find out how it would play in Peoria, what does it need? It still needs things and that's fine. But it shows that Linux is being evaluated for a business purpose other than because some nerds think it's cool, some zealots think it's the moral thing to do, etc.

      I think this is a great move. Shoot, if AOL poured a few million into WINE, they really could distribute AOL 9.0 that upgrades not just the client application, but the underlying OS at the same time. Imagine 40 million bulk mail upgrades like that!

      --
      "Provided by the management for your protection."
    8. Re:Doesn't this say it all? by Waffle+Iron · · Score: 2
      If that was the plan, why not buy Apple and license Mac OS X?

      Maybe because they have the wisdom to stay out of the hardware business?

      Plus, AOL would need to put their OS on piece-of-crap machines. Apple engineers would puke if they had to work with anything less than 1337 hardware. (Disclaimer: I like crappy hardware.)

    9. Re:Doesn't this say it all? by liquidsin · · Score: 4, Interesting

      I'd like to take that one step further though. I'd like to see AOL/TW buy RedHat and develop it into AOL-OS (or some such named product). All the power of linux, all the ease-of-use of AOL - which is to say, damn simple. Eventually, phase out the Windows version entirely. You want AOL? Gotta use AOL-OS. But that's a good thing, since it's cheaper than Windows and, with all that AOL/TW cash behind a linux distro, way more stable. Now THAT'd be cool...I'd almost use AOL for that ;)

      --
      do not read this line twice.
    10. Re:Doesn't this say it all? by BrerBear · · Score: 2, Insightful


      I am sure the open source community sees nothing wrong with this? If AOL puts millions of dollars into anything, it will be proprietary and they will own all the rights. Amazes me how so many of the so called open source supports simply don't see that they would be merely changing one monopoly for another.


      Yeah, just like AOL made Mozilla closed source and proprietary after putting millions in development costs into that.

      Oh wait, never mind.

    11. Re:Doesn't this say it all? by Amazing+Quantum+Man · · Score: 2

      With IE commanding over 90% of the market,

      Yeah, but if AOL goes Gecko, then that number should instantly drop to about 60%.

      --
      Fascism starts when the efficiency of the government becomes more important than the rights of the people.
    12. Re:Doesn't this say it all? by laserjet · · Score: 2

      I keep hearing that OS X has the largest Unix user base, but I don't believe it. Can you prove it?

      I am not attacking you, I just want to know where you get your numbers.

      --
      Moon Macrosystems. Sun's biggest competitor.
    13. Re:Doesn't this say it all? by Amazing+Quantum+Man · · Score: 2

      No it wouldn't. Haven't you ever heard AOL'ers complain about the automatic update whether they want it or not? (I know my dad did at one point).

      --
      Fascism starts when the efficiency of the government becomes more important than the rights of the people.
    14. Re:Doesn't this say it all? by Fjord · · Score: 2

      I'll make another prediction: people will start switching back to Netscape slowly but surely. The reason? You can't install IE6 on Win 95. That's a pretty large install base to just cut off like that. New features will go into Gecko and run on 95. Business will switch back and thus people at home will switch back.

      --
      -no broken link
    15. Re:Doesn't this say it all? by Surak · · Score: 2

      I believe Apple will take over the desktop -- not Linux.

      How? OS X only runs on expensive, proprietary hardware. Until OS X runs on cheap commodity hardware, forget about it.

      Remember Apple has the largest Unix user base right now with OS X. Linux on the desktop is a non-starter vs. OS X

      Show me the statistics that prove this. Most people who say this are counting every single Macintosh owner as an OS X users. This is simply not true. Most of the Macs that are shipping even today dual boot OS 9 and OS X. Many Mac users I have talked to never go into OS X...they use OS 9 or 8.x or even in some cases 7.x.

    16. Re:Doesn't this say it all? by Graymalkin · · Score: 2

      A Linux utopia brought about by a bigger monopoly than Microsoft? What in the fuck are you thinking? Wow great it is a Linux kernel and an entirely AOL-ized environment on top of it, not GNU tools, just the Linux kernel between the AOl environment and the hardware. That would be just awesome. You go from Windows to AOL-OS. The great caveat is in order to use AOL-OS you need to be an AOL/TW subscriber for x dollars a month. Man I certainly can't wait to live in your retarded Linux utopia. Please let it come soon!

      --
      I'm a loner Dottie, a Rebel.
    17. Re:Doesn't this say it all? by flacco · · Score: 2
      AOL/TW will buy Red Hat. They're looking to break free of Microsoft, especially since Microsoft basically screwed them over with XP.

      I'm not sure it would be in their best interest to buy Red Hat, unless it was a defensive move to prevent someone else from snatching it up.

      It seems like it would be more in their interest to have an independently healthy Red Hat, and contract their services.

      --
      pr0n - keeping monitor glass spotless since 1981.
    18. Re:Doesn't this say it all? by geekoid · · Score: 3, Funny

      Does it even occur to them to think "why do these people hate AOL, and what can we do to attract them?"

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
    19. Re:Doesn't this say it all? by flacco · · Score: 2
      A Linux utopia brought about by a bigger monopoly than Microsoft? What in the fuck are you thinking?

      The people using "AOL-OS" as you put it are not likely people who have the cluefulness to investigate an alternative OS on their own. Even if they are entirely unaware of their "OS/browser switch", it will alter the technology demographics in a very favorable way.

      Diverse implementations of standard protocols is a very VERY good thing. Anyone who wants to reach the 35million or so AOL subscribers cannot just assume every Internet-connected moron with a credit card will be running IE on Windows (we'll leave passport/.net discussion for another day).

      I'm not saying I would prefer the reverse to be true - that is, the Windows/IE market share decimated to 10% and AOL's share at 90%. I would rather have a number of competing providers with roughly equal market share. That would FORCE them to adopt open standards, and would force content providers who want to reach a full audience to adhere to open standards as well.

      999 cuts to go.

      --
      pr0n - keeping monitor glass spotless since 1981.
    20. Re:Doesn't this say it all? by TandyMasterControl · · Score: 2
      People People People! This talk of AOL buying Redhat is nuts.
      Why the hell would AOL buy Redhat when they can redistribute/install branded versions of the Linux OS for cheap or free?
      Redhat is a business supporting Linux for other businesses. They put a brand name on commodity software, mostly free stuff floating about the .org TLD , and sell it as a tested configuration for which businesses may purchase support. As a sideline they develop aspects of the OS and related services.
      This is not AOL's sphere of banditry at all. People do not look to AOL for support services in any area of software, and AOL market exclusively to consumers, not businesses. Surely AOL management understands that Redhat's business does not fit in theirs, is not congruent nor complemetary.

      AOL has scooped up quite a number of smaller companies whose products are used to acessorize the AOL client and to make it look like AOL invented the internet to a gullible public. In what way would owning Redhat fit that pattern and further that image? Unlike Nullsoft or Mirabilis Redhat makes nothing that helps children and grandmas share pr0n or stolen music or impress each other with the fact that they are so computer literate they can actually chat online. Redhat complements the AOL client and impresses the AOL installed base in no way.

      AOL buying Redhat would possibly be the death of Redhat longterm since many talented people would leave, and it constitutes no advantage to AOL marketing in the shortterm.


      I agree with posters below who say that AOL could market a internet appliance and web services accessed with the appliance and that they could do it with Linux. (They would need to BRAND the thing themselves, not under a partner 's name like they did before with Gateway, and they'd have to advertize it on TV) But actually owning Redhat Software outright is not a prerequisite for success with what is basically a hardware venture, and since a takeover by AOL would probably weaken Redhat instead of strengthen them, it would be a huge waste of money to acquire what they can already get much more cheaply. AOL farming support contracts for Linux webterminals to Redhat is a viable ecology; AOL buying Redhat is death by smothering for Redhat and a selfdefeating investment for AOL.

      --
      Johnny Quest has two Daddies.
    21. Re:Doesn't this say it all? by Jay+L · · Score: 2

      Seriously, there are a thousand good reasons to switch to TCP/IP. What advantages do they gain by sticking with what they have?

      Most new content areas ARE served via (tunnelled) HTTP to the web browser. For the longest time, though, the advantage of the proprietary forms language was speed. AOL's forms engine, while primitive by today's standards, can render screens on slower computers a LOT faster than IE or Mozilla can, and in many fewer bytes. The protocol was designed when 2400-baud modems were the vanguard of speed.

      As for the functional areas, the AOL proprietary protocol has one HUGE advantage over straight TCP/IP - it does NOT require the client to know what server it's talking to. That means things like scaling, stateful routing, server upgrades, failovers, etc. can all be done invisibly to the client. Even today, this isn't really possible on the internet; rotating DNS has many limits, and you can't guarantee that someone hasn't cached an IP address. IP-based protocols like Oscar still have to layer all these features over TCP/IP.

    22. Re:Doesn't this say it all? by blakestah · · Score: 2

      If AOL rolls out a Gecko-based client, it will take a long long time to do so. Further, they will then have to migrate 24 million accounts from IE to (likely less-functional) Netscape 6.x.

      This is AOL. You will upgrade and be assimilated whether you like it or not.

      As to commanding the web to rewrite - the web rewrites for its readership, provided they exist in adequate percentages. No one ever commanded anything. Authors write for their audience - always have, always will. A few years back when IE and Netscape both had market share, people had to write and validate independently for both.

      If AOL really makes this move, it will mean the same situation will return. Web authors will need to validate for Mozilla and IE. And for other than Microsoft web users, this is a "good thing."

  4. Well they could contribute to the redhat community by Romancer · · Score: 2


    Well AOL could actually contribute to the Red Hat community that is still using 56k dial-up.

    AOL could ship their CDs with the Red Hat distro on them so people will actually put them in their computers before toasting them. :)

    --


    ) Human Kind Vs Human Creation
    ) It'd be interesting to see how many humans would survive to serve us.
  5. A step... by Heem · · Score: 3, Insightful

    It's definately a step in the right direction. Remember all those suckers that use AOL may not mean anything to us, but that number of people not using MSIE is sure to change the way the web looks to those of us who also hate MSIE. Web pages that work in the browser that we use by default.. Won't be long before other ISP's that ship their 'own' browser switch over to a Gecko based browser - And without any real stats, i'd guess that 80% of internet users think that they have to use the browser that comes on their ISP's CD or else it won't work. So how long till MSIE uses Gecko, and claims it as their own? MSIE 8.0?

    --
    Don't Tread on Me
    1. Re:A step... by bfree · · Score: 5, Funny
      How long until MS uses Gecko? I think that will be sometime after:
      1. They are split apart
      2. They adopt Free Software and Open Standards across the board
      3. 95%+ of websites will ONLY render with the mozilla engine
      4. RMS is appointed General/Technical/Absolute Manager
      5. MS buys AOL
      6. Hell freezes over
      Seriously it will take a massive shift in MS for this to happen and it would probably be one of the least significant things which would appear from such a transition (I imagine a GPL WordViewer would be about top of the list and the biggest thing we could see). MS detests free software (or open software or anything that might prevent their control) and would pay a massive price rather than lose control of the internet browsing experiences of the web. I would actually expect it to be far more likely that MS will become more aggressive in locking out other browsers than IE wherever possible (think IIS, Frontpage and all the MS controlled sites). Hell they conned Tony "The Stooge" Blair into handing over large wadges of cash for the new government public internet portal which is completly IE dependant! Ah well let the battle commense again.
      --

      Never underestimate the dark side of the Source

    2. Re:A step... by WheelDweller · · Score: 2, Insightful

      Well, yeah if you look deep enough, the web will be aware of the truth. But just glancing..."every" browser claims to be Mozilla, doesn't it?

      :)

      Like:
      Mozilla/4.0 (compatible; MSIE 5.0; AOL 7.0; Windows 98; DigEx

      and

      Mozilla/5.0 Galeon/1.0.3 (X11; Linux i686; U;) Gecko/20020205

      --
      --- For a good time mail uce@ftc.gov
    3. Re:A step... by bfree · · Score: 2

      Your point? They released some open source software to run on their computers for compatibility and to eat into a market, if they "break" the underlying OS hooks for XP/YP/ZP/2003 then they have no obligation to continue with these tools. This software is in no way comparable to them replacing a major piece of their own written technology with a more free version and especially it does not loosen their control over ?everything digital?

      --

      Never underestimate the dark side of the Source

    4. Re:A step... by epsalon · · Score: 2

      Only in a transition phase. Don't forget that all AOL/TW partner sites will be modified to be Gecko-friendly. Then, there will remain just a few sites that don't support Mozilla, and AOL would pressure those sites into complaiance.

  6. This is a good thing why ? by Tha_Zanthrax · · Score: 3, Insightful

    "Woohoo, one more big company using the penguin !!"

    I like Linux and I am not to keen on Micros~1 and I like to see more Linux-use like this, but as with most large companies which switch to Linux AOL already was using UNIX and is replacing that with Linux. It's another step in the right direction, to bad BillG isn't loosing any money/customers here.

    The AOL-client is switch to Mozilla, with which they are replacing MSIE :). For the average home-user this might go by unnoticed ot they will fear the change.

  7. Taking the benefits and giving nothing back. by wackybrit · · Score: 2

    In the article there's constant bleating about how a Linux client wouldn't be 'economical' blah blah etc.. well, aren't they going to save a stack of money by using Linux on the back-end?

    It seems to me like they're taking all of the benefits of Linux and open-source and giving NOTHING back whatsoever.

    What a wonderful community spirit.

    (I know it's bad form to reply more than once to a topic, but hey..)

    1. Re:Taking the benefits and giving nothing back. by great+throwdini · · Score: 2, Insightful

      It seems to me like they're taking all of the benefits of Linux and open-source and giving NOTHING back whatsoever.

      Yes, note this quotation from the piece:

      "It's still easier to optimize eveything when we finally control both the server and the client, and can make them work as smoothly together as possible."

      Now, should this control be established, AOL may still give something back, but I think that one quotation cuts to the heart of the real matter: control.

    2. Re:Taking the benefits and giving nothing back. by Guillermito · · Score: 4, Insightful

      Didn't AOL buy Netscape? Hasn't Netscape
      contibuted most of Mozilla code?
      So I think AOL gave Mozilla back.

    3. Re:Taking the benefits and giving nothing back. by DrXym · · Score: 4, Insightful
      Of course AOL are giving something back. They're giving Red Hat a huge stack of money. Red Hat can do what they like with it.


      Besides which, is funding Mozilla for nearly 4 years to the tune of hundreds of millions of dollars nothing either?

    4. Re:Taking the benefits and giving nothing back. by cananian · · Score: 3

      Um, Hello? AOL is *funding* mozilla. Or haven't you noticed? I don't think that's exactly 'giving nothing back'. Mozilla *rocks* -- and the source is free! What more could you ask for?

      --
      [ /. is too noisy already -- who needs a .sig? ]
    5. Re:Taking the benefits and giving nothing back. by EllisDees · · Score: 2

      It seems to me like they're taking all of the benefits of Linux and open-source and giving NOTHING back whatsoever.

      And what would you call that whole 'Mozilla' thing?

      --
      -- Give me ambiguity or give me something else!
  8. Th new desktop! by jackb_guppy · · Score: 3, Funny

    We have GNOME and KDE.

    Now we will have AOL!

    That right AOL.

    At one point Netscape was quoted to say, "They were the next desktop". Other than office tools (StarOffice?), AOL has most of the needs in place. They have user base. Now with AOL Anywhere, a little java... They are a virual desktop on all platforms.

    The OS today, is nothing more than the MACRO KERNEL of tomorrow.

  9. Less IE specific content (hopefully) by cheekymonkey_68 · · Score: 5, Interesting

    I don't care if they're just doing this to save money, the end result could benefit all web users so its "a good thing" tm and the only people this will hurt are those companies making IE only sites

    This could mean that web developers might finally be allowed to write html conforming sites, rather than the current notion of supporting the current two generations of IE and thats it.

    Perhaps the bean counters will start to think of making websites more accessible when a large minority of users suddenly don't use IE.

    Like it or not AOL users make up a significant number of internet users (30% in the US for ex), and if AOL uses Mozilla for the client it can only increase web standards compliance... hopefully we'll start to see more sites that don't purely rely on Microsoft's interpretation of the html standards and actually try to reach the widest possible audience by making standards compliant web sites.

    From the article:-

    The only thing that might delay -- not stop, just delay -- AOL's change from Explorer to a Mozilla-based browser is allowing time for some of AOL's largest and most important "partner sites" to do away with any Explorer-specific features they have been using in place of W3C standards.

    A browser shift by AOL is going to leave an awful lot of companies that assume their Web sites only need to work with Explorer scrambling to rewrite their code so that they don't lose AOL's 30 million-plus subscribers, or about 30% of all U.S. Internet users.


    1. Re:Less IE specific content (hopefully) by sammy+baby · · Score: 2
      ... hopefully we'll start to see more sites that don't purely rely on Microsoft's interpretation of the html standards and actually try to reach the widest possible audience by making standards compliant web sites.

      I agree with the gist of what you're saying, but it's important that Netscape get its share of the blame for the lack of standards-based sites. Sure, part of the reason that you see so many "IE-based" sites out there is because Microsoft bundled the damn thing with Windows, but the Netscape 4.x series was pretty much an unmitigated disaster for standards compliance. When there's only one widely used browser with decent standards compliance anyway, using the non-standard features of that browser doesn't seem like such a bad thing anymore.

      (Note - the linked article mentions the WaSP's annoyance with Netscape. I didn't really agree 100% with WaSP's opinion on the subject back then, but it's indicative of how bad the situation was.)

    2. Re:Less IE specific content (hopefully) by Fjord · · Score: 2

      The difference being that the nonstandard features in IE are there to protect their operating system monopoly. Case in point: you can't install IE6 on Win95. This is a way to force an upgrade to get newer features (even standards based ones), but still have your nonstandard application run.

      Netscape has no such motivations so their extensions act in a more benign fashion: giving more power to the users and developers instead of locking them into a separate purchase.

      --
      -no broken link
    3. Re:Less IE specific content (hopefully) by sammy+baby · · Score: 2
      Netscape has no such motivations so their extensions act in a more benign fashion: giving more power to the users and developers instead of locking them into a separate purchase.

      As has been remarked elswhere: the vast majority of active development on Mozilla is done by employees which draw paychecks cut (ultimately) by AOL-TW. This isn't an accident: AOL would love to have a platform with which to compete against Microsoft, and Netscape is just a piece of it.

      I do, however, remember five years ago when Netscape was bragging about how they would be able to reduce Windows to, essentially, a platform on which you'd run Netscape, which would be the be-all end-all. Sun (via Java) and Netscape were looking to make Windows irrelevant as a platform: there was nothing altruistic about their motives then, although I'm sure that more than a few developers had the "we're going to revolutionize the world" mindset.

      In any case, your distinction is disingenuous, to say the least: when Microsoft adds features to their product, it's "embrace and extend" Orwellian-Borg tactics, but when Netscape does it, it's because they're nice folks who just want us to be happy developers. Rather than mudslinging, lets just reward the guys who get the standards right by using their product.

  10. Re:umm, whats the big issue here? by Arker · · Score: 4, Insightful

    The main reason to care is this - if AOL does go to Gecko instead of IE (which would be a very smart decision for a number of technical and business reasons you'd know about if you read the article) then 30% of web users will no longer be using MSIE - and those bastards that write their webpages in MSHTML are going to be scrambling to fix their pages.


    Now that would be freakin cool!

    --
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Friends don't let friends enable ecmascript.
  11. Re:Well they could contribute to the redhat commun by An+Onerous+Coward · · Score: 2, Interesting

    Maybe not. By the sound of the article, the people at AOL don't want to have to do tech support for a Linux client. Without a Linux client, anyone using the Internet is someone who is using another ISP.

    Also, the boxed Red Hat 7.2 distro contains no fewer than 7 CDs (2 install disks, 2 source disks, Star Office, some Loki demos, and a documentation CD). Even if they limited it to just the first two, it still means tripling the already vast amount of plastic being distributed, and I don't think they'll go for that.

    Finally, given the expertise differential between "installing the AOL Client" and "reformatting or repartitioning the HDD and installing Red Hat Linux," it's a bad idea. I think there are too many people out there who would wreak havoc on their current system if some Red Hat CDs dropped into their laps. It wouldn't be good for thousands of people to think of Linux as "that software that ate my computer."

    --

    You want the truthiness? You can't handle the truthiness!

  12. ThreeThings I Want To Know... by great+throwdini · · Score: 4, Interesting
    1. We all seem to know that AOL on Wintel utilizes the Microsoft rendering engine. What does AOL for MacOS use?

    2. Has AOL ever used a rendering engine for either platform other than the one(s) used now?

    3. If AOL has switched in the past, what was the motivation then?

    (Finally, a reason to use my +1 bonus.)

    1. Re:ThreeThings I Want To Know... by leviramsey · · Score: 3, Interesting
      We all seem to know that AOL on Wintel utilizes the Microsoft rendering engine. What does AOL for MacOS use?

      I'd presume the IE Mac rendering engine, but that's a guess.

      Has AOL ever used a rendering engine for either platform other than the one(s) used now?

      AOL's original browser was Mosaic-based, IIRC. It blew goats (I think it had table support, but not much else).

      If AOL has switched in the past, what was the motivation then?

      AOL switched to IE back when Netscape owned about 70% of the market. Microsoft got the IE rendering engine to #1, and AOL got desktop placement in Windows (remember the Online Services program group in Windows?)

    2. Re:ThreeThings I Want To Know... by SuperCal · · Score: 3, Informative

      AOL for Macs up to ver 4 used MSIE for Mac. I assmue the same for higher, but I do not know this for a fact. Befor IE bacame intergrated with AOL's client AOL did not ship with a Browser. Was very late in support of the web, there was a great deal of speculation that AOL felt threatened by the web because it was simular to what AOL thought was its greatest asset... A GUI. Slowly AOL begain pointing its users to netscape as it became apparent that this web thing wasn't going away. I think there was even a CD or two that provided netscape. (I beleave this was all happening around ver 2 and 3 of the AOL client). Finally AOL fully embraced the web though a Deal with MS. AOL agreed to promote IE by intergrating it with AOL's client and AOL got prime placement on windows descktop. so to recap... 1 MacOS AOL uses IE (or did) 2 AOL promoted Netscape, but never required it. 3 AOL switched to IE because of a marketing deal.

      --
      Business News and Resources: www.usasource.net
    3. Re:ThreeThings I Want To Know... by babbage · · Score: 3, Interesting
      1. We all seem to know that AOL on Wintel utilizes the Microsoft rendering engine. What does AOL for MacOS use?

      I can't give a completely technical answer to this one, but I do know that for both OS9 , your Mac's system folders end up containing a whole slew of MS specific code:

      % ls /System\ Folder/Extensions/MS\ Library\ Folder/
      total 2568
      -rw-r--r-- 1 chris unknown 112644 Mar 25 1998 MS C++ Library (PPC)
      -rw-r--r-- 1 chris unknown 189123 Mar 25 1998 MS Container Lib (PPC)
      -rw-r--r-- 1 chris unknown 611367 Mar 25 1998 MS Internet Library (PPC)
      -rw-r--r-- 1 chris unknown 119930 Mar 25 1998 MS Preferences Library PPC
      -rw-r--r-- 1 chris unknown 33232 Mar 25 1998 MS Variant Lib (PPC)

      I thought I came across similar stuff on the OSX directories, but a quick search isn't turning up anything obviously originating from MS. Presumably it's all just part of the Internet Explorer app, and not (obviously?) exported as a globally available library.

      Also note that the Mac versions of IE are for the most part a completely separate codebase from the Win32 versions, with different developers and everything. There is some cross-pollination between the two branches, but not to the point where you can consider them to be identical. The Mac version has some very nice features that still haven't made their way to the Windows branch, and it has other features (auto-virus mode comes to mind :) that still haven't been exported to Macland yet.

      2. Has AOL ever used a rendering engine for either platform other than the one(s) used now?
      Can't address the Mac on this one, but as another commenter noted, AOL first tried to ignore the web, then it tried to implement support for it in a very broken way. The browser for AOL 3 or so was really bad -- probably (in my opinion) to get AOL users to think that the web wasn't worth all the hype, and that they should stick to AOL (that and, to be fair, it was probably just difficult to get a solid browser put together quickly, which would explain why they went on to just embed IE and then later buy out Netscape).
      3. If AOL has switched in the past, what was the motivation then?

      As noted, their inittial attempts to get a browser within the AOL client were just really, really awful. Their web client crashed all the time, couldn't render things, felt slower than the rest of the AOL service, etc. (Note that, apparently at around this time, AOL switched to HTTP as their main internal network protocol, instead of whatever propietary protocol AOL was using before that. Thus going to the web from within AOL meant having to do some kind of protocol translation to make it work, so this made the service degrade even beyond the poor quality of the browser they were offering at the time. Citation for this is in "Philip & Alex's Guide to Web Publishing", where he talks about what a surprisingly good webserver AOLServer is, noting that it has been tuned to support the millions of concurrent AOL users...)

      Anyway, as noted by another commenter and in great detail in the MS antitrust Findings of Fact document, AOL entered a contract where they would use IE for five (?) years in return for a guaranteed place on the Windows desktop (and no longer having to devote resources to coming up with a viable browser of their own), and MS would get instant access to AOL's millions of users. AOL hedged their bets for the future by buying out Netscape, but they kept IE around even after the contract expired in the hope that MS would allow some sort of new agreement along the lines of the earlier one. As it has become clear that MS doesn't feel they need to co-exist with AOL anymore, AOL in turn seems to be considering playing their Netscape trump card now -- "if you don't need us then we don't need you either."

      Sooner or later I assume they will -- must -- switch to Netscape: otherwise they will have wasted their investment in that company and continued to support their biggest rival in the process. The more interesting question to me is whether they really are willing to switch to some kind of [Red Hat based?] AOLinux. Part of me really wants to see this happen -- it would be nice to see some significant competition to MS on the shelves at BestBuy and Circuit City (above & beyond Apple's 5%, where you can even find that in the first place). But at the same time, I'm not comfortable with the idea that everything on their machines -- from the kernel up to the user level AOL client -- would have been bolted together as a monolithic whole by one corporation. Even if the guts are open source, I'm sure that the high level stuff would certainly be proprietary. Macintosh can claim to be internally open too, but the more interesting high level stuff is still proprietary. On a hypothetical AOLinux, you're only likely to have as much access to the Linux stuff as their high level interface allows you to have, and seeing as this is AOL we're talking about, I can't see them giving you much access there. At least MacOSX gives you the Terminal to work with (and through that, all the BSD subsystem). What will AOLinux let you use? If this goes the way I'm fearing it could, it could be at least as bad as the current Windows situation, because it would mean that of the three systems you'd be able to buy at that Circuit City -- AOLinux, Mac, and Windows -- all three would be for the most part vertically integrated, with one vendor supplying the bulk of the user and system level software on each platform. This could serve to Balkanize each sub-market, and I'm not clear who if anyone would gain by such a situation, aside from *maybe* those three vendors.

  13. The problem may be Time Warner by yerricde · · Score: 3, Interesting

    It seems to me like they're taking all of the benefits of Linux and open-source and giving NOTHING back whatsoever.

    The real reason why AOL(tw) won't release an America Online for PC Linux: there'd be no way to stop a kid with a debugger (easier to obtain on Linux than on Windows XP) from breaking into the Time Warner content because the machine owner is root and the publishers can't do jack about it. (SSSCA aims to change that.)

    --
    Will I retire or break 10K?
    1. Re:The problem may be Time Warner by helixblue · · Score: 2

      Seeing as AOL already supports UNIX (in the US anyways, they support MacOS X)... which comes with gdb on the Developer Tools CD, this is pretty silly :)

  14. there's some truth to that by mrsbrisby · · Score: 5, Insightful

    it truly would be nice to have an AOL client for Linux. But they really only have two options:
    1. support ONLY UNMODIFIED RPM-ONLY REDHAT BOXES (or xxx other distribution)
    2. build an all-in-wonder static library that has the dialer, gecko, vpn client, and everything all built-in.

    no linux user really wants either option, but it does sound off a big reason why companies are reluctant to bring desktop-software to linux: there are too many variables.

    There is a good reason that "Reinstall Windows" is in the 90th percentile of all support responses. It's a simple answer, and by having nobody who can actually repair a broken windows machine, it's the best answer.

    But linux systems can be repaired so long as they still kick (and sometimes: even past that point). So there's two options for us:

    1. we can adopt some kind of sane configuration system. [i think freshmeat had an article about the unix configuration nightmare, so don't expect the answer to this to begin with the word "just"]

    2. we can all adopt a single limiting platform for desktop use, and do all our hacking in every other system.

    If people really believed point #2 was a possibility, I think we would have a lot more desktop presense already. But #1 has the most promise. If people weren't so angry as to say "configuration like XXX is too YYY" instead of saying "configuration like YYY is unreliable because ZZZ" we might actually key someplace.

    And everyone would have to adopt it. Gnome moves somewhat forward with gconf, but don't think it's the end-all. we'd have to have dialup and network configuration, and X configuration and everything in a similar engine. In this case, we can ditch gconf completely, or we can build wrappers to do just this.

    1. Re:there's some truth to that by Reziac · · Score: 2
      Ahem... *I* fix Windows rather than reinstalling. In fact once I start actually using a particular Windows box for real work, I never reinstall Windows (and have had Windows setups in excess of 6 years old, in heavy use, without a single reinstall). Whatever goes wrong can nearly always be fixed. You just have to know what you're doing.

      Gee, sounds kinda like fixing a wonked Linux box, eh??

      --
      ~REZ~ #43301. Who'd fake being me anyway?
    2. Re:there's some truth to that by HiThere · · Score: 2

      I believe he was talking about responses from the help desk to a phone call. A knowledgeable user will rarely call MS for help (though many seem to spend a lot of time searching through their site). So most of the calls that they get are from "novices" (with varying amounts of time experience). So they opt for a simple answer for three reasons:
      1) it saves them time, and
      2) it's something the local user can actually be expected to do.
      3) it lets the first level of the help desk be run by people who operate off of a checklist (i.e., by cheap people).

      There are actually decent reasons for these choices. I don't like them, and don't want them on my system, and consider that they aren't made to my advantage, but in this area the choices that MS made are probably about as good as feasible for the average user. And it allows less skilled people to use computers. Admittedly, it tends to prevent them from ever becoming anything but unskilled users, but that is often preferred by the end-user, his/her management, and definitely by MS.
      .

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    3. Re:there's some truth to that by Reziac · · Score: 2

      Yeah, you're right when it comes to the helpdesk end of things, sad as it may be it's practical reality. But the fellow I replied to seemed to think that the ONLY solution to a Windows foulup is a reinstall, but that conversely it somehow makes more sense to merely FIX a mangled linux setup. Which struck me as a double standard (like I'm so surprised at encountering that here? :)

      --
      ~REZ~ #43301. Who'd fake being me anyway?
    4. Re:there's some truth to that by Reziac · · Score: 2

      I've fixed some pretty seriously mangled Winboxen (most recently one that had suffered random deletia courtesy of the owner's kids). You can't always get 'em back to pristine condition, but they can generally be got into good-enough working order, and in much less time than it would take to reinstall Windows, reinstall all the apps, and backup/restore all the user data (don't forget, it's NOT just a matter of reinstalling the OS!) The DOS prompt is your Loyal Ally, and REGEDIT is your Friend :)

      But my point wasn't really that anyway. Rather, that this guy was assuming that no one could, let alone would *want* to merely fix a hosed Winbox, but they'd always want to fix a hosed linuxbox and that would be somehow SO much easier.

      Gee, I guess that's why no one would (or could?) tell me how to get back into my late RedHat setup after it arbitrarily decided it no longer knew my login password? Good thing I never used it for any real work.

      Ya see, I know as much about fixing linux as the average Windows users knows about fixing Windows. So what's my solution? Nuke linux and reinstall it!! But I'd never do that to a misbehaving Winbox, because I know how to fix Windows.

      Point being, what you consider "fixable" depends largely on your knowledge base. The average person knows no more about fixing a hosed linux box than they do about fixing a hosed Winbox, but *that* doesn't have any bearing on whether or not either CAN be fixed.

      So (what the heck was the original topic anyway? :) it doesn't really matter if the average AOLer is using a Winbox or an AOLinux box -- helpdesk will still tell 'em "Reinstall!" even tho you and I both know that's overkill, regardless of the base OS.

      --
      ~REZ~ #43301. Who'd fake being me anyway?
    5. Re:there's some truth to that by Fjord · · Score: 2

      The difference, I've found, is that there are a more resources devoted towards fixing a problem on open source problems than there are on closed source ones (I make the destinction because I've found stuff to fix cygwin setups pretty easily). Most closed source apps you can't even get an error code, it just crashes. Open source ones often fail with a reason. This makes it easier to find the fix online. Try to figure out why windows is crashing and you'll be searching for a while.

      I can fix my broken installs on linux without knowing what I'm doing. All I need to know is the URL for google. Windows has so much arcana that it is more difficult to work with in this way. It's just easier to reinstall.

      There was one time when we had a huge rollout of a J2EE app that had a specific time it had to be out because the ad in the WSJ was going to be out at that time. The day before the rollout, the client called us up and told us that they had changed the URL in the add to point to their main domain (the comms between us and them was very crappy). We tried going through the config files for iPlanet to switch it to the new domain name, but something wasn't working (we were grepping for the old domain and not getting anything, but it still would do absolute redirects to the old domain). I looked at our admin and said "How long would it take to reinstall everything" "3 hours" (he knew well since he had done it 4 times prior). "How long do you think it will take us to figure out how to switch this over" "It could take all night". He knew what I was getting at.

      This was on a solaris box with a Netscape-Sun Alliance product, but it underlines the issue. The fact is that I have tried to admin my Windows boxes the way I admin my linux box. I've been adminning windows at home way longer than linux (I came from 3.1, whereas I've only used linux at my job for 2 1/2 years and at home for 1 1/2). But it's a big f'ing wall. My wife had a problem where outlook express would crash in some DLL. Uninstall/reinstall OE: it would work for a week and then start again. Use the recovery CD to reinstall windows: it worked for a month and started crashing again. Result: wipe and install windows xp. Now OE works fine, but IE6 sends an error report or 2 daily and it couldn't be on the same workgroup as our roomie's Win 95 machine for some reason unknown to the troubleshooter.

      At least I have backup scripts on my linux box that will effortlessly backup everything on the other machine.

      So, no. It really isn't anything like fixing a wonked Linux box.

      --
      -no broken link
    6. Re:there's some truth to that by SurfsUp · · Score: 2

      it truly would be nice to have an AOL client for Linux. But they really only have two options:
      1. support ONLY UNMODIFIED RPM-ONLY REDHAT BOXES (or xxx other distribution)
      2. build an all-in-wonder static library that has the dialer, gecko, vpn client, and everything all built-in.


      3. Open the specs and let us build a client for them.

      Not that I'd use it personally, but other folks might.

      --
      Life's a bitch but somebody's gotta do it.
    7. Re:there's some truth to that by Reziac · · Score: 2

      Where were you when I was arguing with the beast? Thanks, saved for reference.

      --
      ~REZ~ #43301. Who'd fake being me anyway?
    8. Re:there's some truth to that by Reziac · · Score: 2

      LOL! Nope, that just made it shake its head harder! :)

      Oh well, it gave me an excuse to wipe linux off this machine.. next time it'll have its own dedicated box. I am not a fan of duel^H^H dual booting.

      Tho [heresy alert!] on brief exposure to FreeBSD, I found I prefer it to linux. :)

      --
      ~REZ~ #43301. Who'd fake being me anyway?
    9. Re:there's some truth to that by Reziac · · Score: 2

      Probably depends somewhat on what you're used to, as well. When I go searchng for *NIX info, it looks more like arcana to me than Winfo ever does :)

      As to stuff like crashes in some unknown DLL -- maybe it's something in my personal assortment of crossed wires :) but after a few such incidents, I often start to see a pattern and if sufficiently motivated, can usually pin down what's causing it. Of course, sometimes there is no solution except to get rid of whatever conflicts.

      In my experience, everything gets easier to fix/maintain, and 100x more stable, if you don't install *ANY* M$ software other than Windows itself!

      BTW I also came from DOS/Win3.1, and that's where I got this notion that fixing Windows beats reinstalling it. My old Win3.11 setup (which had so much stuff installed that Windows itself was maxed out) was retired at age 8 years, having been moved around a bunch but was NEVER reinstalled. (It also went as long as 18 months in *heavy* use, without a single crash.)

      Hell, I've got a WinME box (yes, it IS for laughing at, why do you ask? :) that is 2 years old, has every kind of crap installed, and hasn't had a redo yet. That may be a record. :)

      You can bet if I ever have a *NIX box that's expected to do real work, I will be just as resentful of any thought of reinstalling it :)

      --
      ~REZ~ #43301. Who'd fake being me anyway?
    10. Re:there's some truth to that by dublin · · Score: 2

      Point being, what you consider "fixable" depends largely on your knowledge base.

      This is a VERY valid point. After many years of amassing a great deal of knowledge about Windows, Linux, and various Unixes, I have finally reached the conclusion that once they start to act flaky, it's ALMOST ALWAYS easier and quicker to simply reinstall the OS than to figure out what obscure setting, library, etc. got broken. (Not that one shouldn't find root causes, but let's face it, much of the time it's just not worth the effort.)

      Linux and Windows are both quite difficult to administer in very different ways. Those of you that have never used a real production-quality OS (Solaris and DEC/Compaq Tru64 are, AIX, IRIX, & HPUX aren't, IMO) really don't know how stable and easy to run those systems can be.

      I like and use Linux routinely, but it's not a panacea - my most recent Linux reinstall was caused by doing an upgrade via Debian's vaunted apt-get mechanism: I didn't bother to even figure out what apt-get did to completely scrog the OS - it was obviously very bad and quite clear that reinstalling from an old Mandrake CD I had lying around would be much quicker and easier. (No, I won't touch Debian again for another year or two.)

      By the same token, bit rot munches my Win98 to the point that I have to start over from scratch about every six to eight months. Again, I *could* probably fix it given the time, but I've got beter things to do, so reinstalling makes sense, at least until we get OSes that deliver real stability.

      --
      "The future's good and the present is nothing to sneeze at." - Roblimo's last ./ post
    11. Re:there's some truth to that by Reziac · · Score: 2

      You mention the bitrot problem.. in my own systems, I seem to avoid this, but I don't do a lot of installing/uninstalling either -- those being THE major factors that eventually make Windows flakey. (Using ToniArts' Easycleaner on the Registry after every uninstall helps a lot.)

      Generally I try stuff out on an expendable rig, and it only goes on the production machine when I'm sure of its behaviour. And then only if I trust the uninstaller. As a general rule, if some app doesn't use a current version of InstallShield, I don't install it. AND I don't install upgrades or patches unless they address some problem that is affecting MY system. We all know how they often break more than they fix!

      This here Win95 install is almost 3 years old, NO reinstalls, close to 100% stable, and *never* BSODs (you see, I'm spoiled too -- I *expect* high reliability from the OS!) But I've followed my own rules religiously as to how it's maintained and what does or doesn't get installed. I thump on my clients mercilessly til they learn these rules, which keeps their boxes in good shape too.

      Tho my WinME box (which has the unpleasant duty of being the software test rig) is now almost 2 years old and with every sort of crap dumped on it, is still stable! The only thing that crashes it is the sucky new WinHelp system. Apparently I sacrificed that black chicken at the exact right point of the moon cycle. :)

      I gather bitrot is just as much a problem with linux, what with all the different minor versions of everything in sight. That's a problem with anything that's constantly in development!

      What factors do you find make linux flaky over time? other than mismatched libraries and the like.

      --
      ~REZ~ #43301. Who'd fake being me anyway?
    12. Re:there's some truth to that by Reziac · · Score: 2

      There used to be a site that you could plug Windows error codes into and get a meaningful result back, but I've lost the URL :(

      But I think you're right about the cultural aspect (kinda ties back into the notion of an AOLinux, eh? :) Windows is =expected= to be opaque and intractable, so you're told "Don't waste your time fixing it, just reinstall!" -- This of course offends the ear of anyone who believes in stability and long uptimes.

      Conversely *NIX users =expect= to hear an exact fix, frex "Just install the obfust beta, using rpm -x /nd4 /35r -DNr with the gchunk v6.0.12.099 library installed in d5 mode while running as root, and everything will be fine." -- Commandline obviously made up to be as nonsensical as possible, to emphasise how arcane such things look to a WinUser.

      Also, as with anything, one needs to know where to look and how to extract what you want from the appropriate search engine. I've not had great luck with the linux help searches, but I haven't used them a lot either. I will say that M$'s latest incarnation of their knowledge base seems specificially designed to prevent anyone from finding needful results! :(

      BTW, anyone have any idea how to get a linux router and a Netware 3.2 server to collectively allow access to the Wildcat 4.2 BBS that runs on the Netware server?? We have this fantasy about doing this for telnet access to the BBS...

      --
      ~REZ~ #43301. Who'd fake being me anyway?
    13. Re:there's some truth to that by Reziac · · Score: 2

      Well, that'll teach you to RTFM before you mess with gchunk :)

      Actually, that sort of cryptic nonsense is what generally turns me off linux :( And mind you, I grew up with DOS, so the commandline isn't foreign territory.

      We really do need something like AOLinux (see, I even remember the nominal topic :) for raw *NIX beginners -- with a config manager that looks and acts enough like the Windows-familiar Control Panel and Device Mangler to avoid scaring 'em off, but that at the same time SHOWS the user exactly what it's doing, so they can learn the commandline aspects if they're so inclined. KDE has the GUI part more or less right, but it doesn't let me see what I just did, so how am I supposed to learn what's going on under the hood, if I don't have the time or inclination to put weeks of study into it?

      I learned all my HTML essentially that way -- via a WYSIWYG editor that has a very useable simultaneous raw HTML interface (would you believe AOLpress? a damned nice if aging editor.) "Oh, I made this here structure, and it actually wrote that there code in the document? That's simple enough. I can do that myself."

      [Side note, if anyone from the Netscape code team is listening -- any chance of getting the AOLpress source released so someone can update it and fix a few bugs, pleeeeez? It certainly can't hurt AOL to do this, since it was always freeware and they've stopped supporting it anyway. I've used Frontpage, Dreamweaver, and Pagemill, but when I just want to get a standard web page built with minimal hassle, I always wind up going back to AOLpress. I'd like to make the same beg for the Netscape 3.x codebase, too. Still my *preferred* browser.]

      As to the BBS -- thanks, that link is exactly the info we've been looking for!! I don't actually admin the server (I'm the sysop-at-large, and my buddy is the Real Sysop who actually runs the place) so I'm not sure what protocols it supports. Forwarding to the BBS, not sure what you mean?

      Wildcat5 supports telnet out of the box, but Steve doesn't want to switch over to the requisite Win32. He's a Novell and DOS dude all the way, and hates Windows of every species.

      --
      ~REZ~ #43301. Who'd fake being me anyway?
    14. Re:there's some truth to that by Reziac · · Score: 2

      True, AOLinux would probably default to hiding everything -- but ISTM it would probably be overall much simpler and more focused (after all, the =only= job it would really NEED to do is connect to AOL) which might be more attractive for relative beginners, both at the user level and at the programming end -- might be easier to hack a nice control interface onto. Sometimes the wheel that's already invented takes too much power to turn. :)

      As to my concept for controls (GUI to do the work, but also displaying what it really did) -- yeah, that could be broadly applied and doubtless would make many such operations less opaque. It croggles me that the usual coding philosophy is that you are only allowed to have one or the other!

      I've only messed with RH6, since out of the disties I had to hand at the time, it's the only one that would play nice with this S3Trio video card. Someone lately gift me with recentish SUSE and Mandrake, so maybe I'll try those next, just for variety. :)

      --
      ~REZ~ #43301. Who'd fake being me anyway?
  15. Re:Well they could contribute to the redhat commun by Lumpy · · Score: 2

    it would have to be a really old, or special compressed distro as redhat takes 2 full cd's now.

    unless thay start sending DVD's.. but then everyone would have to have DVD drives and they are less common in pc's than burners. (burners outsell dvd read only drives 10 to 1 while regular CD drives outsell DVD drives 20 to 1.. stats collected by a friend of mine at a computer superstore)

    If someone could get me a RH7.2 cd that default installed KDE that was on one CD I would kiss them! as I desperately need a distor that is super easy and fit's on one CD to give away.

    --
    Do not look at laser with remaining good eye.
  16. AOL switching to Mozilla... by Jason+Levine · · Score: 2

    This is definitely good news, but not just because a decreased IE browser share will give incentive for both MS and the Mozilla development crews to improve their browsers. Perhaps, with more people using Mozilla, Netscape 4.x users will finally upgrade.

    I develop three different websites and I can't tell you all the headaches NS 4.x has given me. If you think IE is bad, try coding for NS 4.x. And it's not as if I can say "Very few people use that browser so I can ignore it." I get about 5-6% NS 4.x traffic, that makes it small enough to be annoying but big enough to make me have to address it. (By comparison NS 6.x comprises less than 2% of my traffic.)

    I have no problems with someone using a non-IE browser so long as it conforms to standards. And yes, as non-conforming as some think IE is, it is more compliant than NS 4.x.... Maybe not more than NS 6.x, but it seems like a lot of people aren't upgrading. Anything that gets people to ditch that awful browser (be it for IE, Mozilla, NS 6.x, or some other up-to-date browser), is a good thing for web developers everywhere.

    --
    My sci-fi novel, Ghost Thief, is now available from Amazon.com.
    1. Re:AOL switching to Mozilla... by Jason+Levine · · Score: 2

      There are a few problems with a "Test on NS 4.x, assume it works on everything else" strategy. First of all, I've found things that work with NS 4.7 that don't work with NS 4.0x. Should I now test with every sub-version of NS 4.x just to make sure it works across the board?

      Secondly, blindly assuming that a site tested with NS 4.x will just work with IE 4.x/5.x/6.x and NS 6.x and Mozilla can lead to the site not displaying correctly under non-NS 4.x browsers. For example, you can use the LAYER tag to position elements on the page in NS 4.x. It's a tag the NS developers invented in an attempt to make it the CSS standard. However, support for the LAYER tag was dropped (in favor of DIV) in NS 6.x (and was never present in IE). You could design a site using LAYERs that will display perfectly in NS 4.x, but won't display right in any other browser. You should always test your site against as many browsers as possible (or at least against the most commonly used browsers).

      Finally, NS 4.x is 1998 technology. (Maybe 1999 with some of the newer revisions.) It's 3 to 4 years old. Why should a developer limit his site building to old technology just because 5% of his audience refuses to upgrade? Especially when using CSS can reduce download times and make a site look much better.

      I'm not saying that web sites should be inaccessible to NS 4.x users, but you can use CSS for IE 4.x+/NS 6.x/Mozilla and still make it degrade nicely for NS 4.x. It's that "degrading nicely" part that can be a pain simply because NS 4.x won't just ignore CSS. It will try to render it and will fail miserably. When it was first released, NS 4.x was the top of the heap, now it's just an old pain that refuses to go away.

      --
      My sci-fi novel, Ghost Thief, is now available from Amazon.com.
    2. Re:AOL switching to Mozilla... by lkaos · · Score: 2

      I guess I am one of the 5-6% percent :)

      I've used NS4.x since it came out and I've also followed Mozilla since NS first released the code oh so long ago. Currently, I have the lastest version of Mozilla installed 0.9.x something or other but I still choose to use NS4.x to browse for one reason.

      Most sites who use the 'newer' features of HTML look horrible. In fact, I didn't even release I had CSS shut off on NS4.x until recently and aftering turning them on, I quickly realized why I had them off. Website designers really need to design pages better. The biggest problem with CSS is that people assume that everyone is going to be on a 800x600 screen it seems and I can't friggin read anything anywhere.

      It's painful. Give me a text-only site _any_ day to the new breed of flash/shockwave/CSS sites. They just plain suck.

      --
      int func(int a);
      func((b += 3, b));
    3. Re:AOL switching to Mozilla... by laserjet · · Score: 2

      Finally, NS 4.x is 1998 technology. (Maybe 1999 with some of the newer revisions.) It's 3 to 4 years old. Why should a developer limit his site building to old technology just because 5% of his audience refuses to upgrade? Especially when using CSS can reduce download times and make a site look much better.

      This, of course, is a personal opinion. Obviously you know that you can design a site for whatever brower you like. I'll tell you why I design for NS4.

      First, I use NS4 quite a bit. I work on HPUX systems, and NS4.7 is the standard. Most of the time I use Mozilla for HPUX when avaialable, but NS4 is always there.

      Second, NS4, as you point out, is OLD technology. It doesn't do CSS, it doesn't do nested tables very well, it doesn't render very quickly. But, being old technology is a plus too.

      Third, even if 5% of web users are using NS4, that is 5% I don't want to alienate. If you get 1000 visitors to your online shopping site, do you want to tell 50 of the to "go away" just because they use the wrong browser? Why not keep ALL of your customers?

      It is not that hard to accomodate all browsers. Flash, CSS, all that stuff is not needed. I shoot for the lowest common denominator, and can still help out everyone, make a decent looking site, and not alienate any customers. That is why when I create a site, I test with NS4, Mozilla, IE4, and IE5. I want NO ONE, not even 5%, to be turned away just to make a page look better of load a little quicker.

      --
      Moon Macrosystems. Sun's biggest competitor.
    4. Re:AOL switching to Mozilla... by Jason+Levine · · Score: 2

      Third, even if 5% of web users are using NS4, that is 5% I don't want to alienate. If you get 1000 visitors to your online shopping site, do you want to tell 50 of the to "go away" just because they use the wrong browser? Why not keep ALL of your customers?

      Actually, I mentioned having a web site "degrade nicely" for NS 4.x. This means that IE 4.x+/NS 6.x/Mozilla users can get some nice CSS-enabled pages, but NS 4.x users will still see a decent, useable site. They won't get the browing experience I'd prefer them to have on my site, but they won't be turned away either.

      To expand your analogy, suppose I were to get a 1% traffic rate from NS 3.x users. Should I make sure my site is designed to NS 3.x specifications so as not to turn away the 10 in 1000 NS 3.x visitors?

      And what about cross-platform testing? A page on Windows might not look the same on a Mac or Linux even if you're using the same browser. There's not enough time in the day to test all the browser-platform combinations.

      That's why I have what I call my "5% rule." If a browser (or platform) is consistantly below 5% of my traffic, I'm not going to spend my time testing and tweaking my site for it. NS 4.x has, so far, barely managed to avoid falling under the 5% mark so I still test on it, but I really do hope it goes away soon. A 7% NS 6.x crowd would be better to design for than a 5% NS 4.x crowd and a It is not that hard to accomodate all browsers.

      Actually, it can be. CSS code that works properly in IE 5.5 doesn't look right in NS 6 and looks downright awful in NS 4.7. A site that looks fine in NS 6 and IE 5.5 might still have issues with NS 4.7. Then there's the cross-platform issue addressed above. And even if you were to leave CSS out of the picture, NS 4.x doesn't handle percent widths properly and has problems with input box sizes. Supporting NS 6 with a site designed for IE 6 isn't too much of a problem (assuming you're not relying on IE-specific tags), but supporting NS 4.x on a site designed for a 5.x+ level browser can be.

      Flash, CSS, all that stuff is not needed.

      I'll agree that Flash isn't needed (although it can be useful in some cases), but CSS is quite handy. I can use it to position elements exactly where I want them (eliminating complex and slow-to-load table structures), assign an easily updateable global style, and replace some image effects with quicker-loading text effects.

      I shoot for the lowest common denominator, and can still help out everyone, make a decent looking site, and not alienate any customers. That is why when I create a site, I test with NS4, Mozilla, IE4, and IE5. I want NO ONE, not even 5%, to be turned away just to make a page look better of load a little quicker.

      I agree that you must test on as many browsers as possible, but at what point do you stop testing? If NS 4.x were to fall to 4% of your traffic, would you still design the site to be viewable for those users? 3%? 2%? At some point you shift your "target browser(s)" up a version number or two while making all reasonable attempts to have your site degrade nicely for those using the older browsers.

      Instead of catering to a small group using an old browser, I shoot for the most commonly used browser(s) while making sure that the rest of my audience can still browse my site. I won't turn anyone away knowingly, but I'm also not going to waste time testing my site on every browser out there. If I did, I'd never complete a single web page.

      --
      My sci-fi novel, Ghost Thief, is now available from Amazon.com.
  17. new slogan by monkey_jam · · Score: 3, Funny

    Americans On Linux

    substitute Assholes for americans where you see fit..

  18. Alternative to re-installing by Walles · · Score: 2, Interesting
    There is a good reason that "Reinstall Windows" is in the 90th percentile of all support responses. It's a simple answer, and by having nobody who can actually repair a broken windows machine, it's the best answer.

    Something I've been pondering (a little) is that since Linux boxes are fixable (regardless of distro), why couldn't this fixing be automated? Have a program that diagnoses the problem by trying to dial out, run traceroute, start X, and / or whatever, then when an error is encountered "check" (for some definition of checking) relevant config files or whatnot for errors, maybe asking the user some questions in the process.

    Granted, this would be a task in full parity with making something like Linuxconf or XST, but if somebody did, imagine what it would do to the support costs!

    --
    Installed the Bubblemon yet?
  19. AOLinux by Alien54 · · Score: 3
    The only way AOL could provide a cost-effective Linux client, given its "total support for free" policy, would be to market a real, full-featured personal computer (as opposed to an "Internet appliance") that runs Linux and is preconfigured for AOL. The target market for this computer would not be sophisticated Linux users, but current AOL subscribers who want to replace their current boxes, and it would need to be a very low-cost item to succeed in that market

    The best way to acommplish this would be to have their own branded verion of Linux.

    AOLinux.

    Then they won't have to worry about all of the other distros. And it can have a stripped down feature set so that they do not have to support every widget on planet earth.

    Extra bonus brownie points for tweaking the Nose of Microsoft.

    --
    "It is a greater offense to steal men's labor, than their clothes"
  20. Interesting Comment on the Newsforge article by Christopher+Whitt · · Score: 2, Interesting
    In the followup comments on the site, an AC wrote


    That is why I am not sure I wanted to see this article just yet, even though I consider it interesting and very good news. Premature talk may scuttle these kinds of strategic decisions. Eg. You-Know-Who might step up his FUD or make AOL management an offer they cannot refuse: "If you use Mozilla, we cannot promise the AOL browser works on future Windows versions , but here's an IE licensing deal that solves such problems...".


    That's a pretty interesting point. I'm not business expert, but this sounds plausible. It would be a shame if talks fell through because of fallout from the rumor-mill.

    On the other hand, I'd say that this is no news to Redmond. The bad blood between them is probably deep enough that the AOL->Gecko outcome is inevitable. Not to mention the money sunk into Netscape over the last few years...

    Everybody here is talking about the boon to web compatibility if this happens. I sure hope it does!

    Christopher
  21. AOL for Linux??? by fruey · · Score: 2, Interesting
    Perhaps one of the world's many stalwart Linux entrepreneurs will eventually convince AOL management that an AOL-branded, consumer-priced Linux box is a good idea. Otherwise, AOL will probably stick to the current corporate operating system pattern: Linux in the server room, Windows or Mac on user desktops -- except that AOL-ized desktops will run the AOL browser and its Mozilla rendering engine instead of Microsoft Explorer.

    Who wants AOL for Linux? What is going on? A proprietary dial-up, authentication and content delivery system? Pulllease.

    If AOL offered a dial up account using PAP or CHAP and just TCP/IP access with a browser that went to their homepage and allowed you to see their premium content, this may be a good thing for any AOL content junkies

    But I can already use AOL Instant Messenger, and MSN, and Yahoo! through Linux, why would I need anything else?

    AOL are right not to create AOL for Linux. Linux users should be following Internet standards and not some proprietary bullshit.

    Windows users can have AOL for all I care. Give me a proper ISP any day of the week.

    --
    Conversion Rate Optimisation French / English consultant
    1. Re:AOL for Linux??? by lkaos · · Score: 2

      This brings up a good point. For AOL to support Linux, they would have to add another authentication mechanism to the kernel. This likely means a kernel module. Unfortunately, since they are a proprietary protocol, the module would have to be binary-only.

      Supporting binary modules alone between the various kernel modules is enough of a hassle to make them not want to support Linux.

      If AOL opened up their protocol then I, for one, would support a project to add support for the protocol to Linux. Whether it sucks or not, it's good for Linux.

      --
      int func(int a);
      func((b += 3, b));
  22. Re:am i the only one... by DrXym · · Score: 3, Insightful
    Who says it crashes more? AOL hates support calls (read the article) so perhaps they're switching to Gecko because they can make it crash less than IE.


    Think about it. Microsoft is a mortal enemy of AOL. If AOL discovers a crash bug in IE, how much effort do you think MS would put into fixing it? At best I bet the bug would end up in a big pile of other bugs from other big customers and no particular effort would be made to fix. Hell, I bet MS could turn around and say they won't fix it.


    Now think what the situation would be with Gecko. AOL can modify their own copy of the source if they need but they also have a direct line to the Netscape developers. It means the action time on bugs is going to be dramatically less than with IE and more bugs will be fixed.

  23. Re:umm, whats the big issue here? by DrXym · · Score: 2
    I recall someone from AOL saying that partner sites are contractually obliged to support all versions of the AOL client - Windows AND Mac which of course means that most sites are likely to be pretty browser-neutral anyway. Hell, I bet all but a few are totally ready to switch to Gecko right now. There can't be many sites that are so profitable that they will turn away even 3% of their customers for "not using the right browser".


    The issue is not with the big guys. It's with the home user / enthusiast dorks who've decided for whatever reason to code their sites in VBScript, ActiveX and proprietary DHTML. These people will kick up a stink, but frankly they've made their bed and now they'll have to lie in it. Boo hoo for them.

  24. Re:Bullshit by gfxguy · · Score: 2

    As an AOL/Time-Warner employee (not directly AOL, however), I have available FREE AOL, if I want it, but choose to pay for a standard ISP.

    Am I an elitist? I'm not alone. I'd guestimate 90% of the people here do NOT use AOL, and I'm not just talking about computer nerds, and I'm the only one here that I know of that even uses Linux at home.

    I've also not heard any mention in these parts about switching to anything else - we run Windows almost exclusively, even though I've often thought (outloud) that being such MS haters, AOL could do a lot of financial damage to MS by internally switching to something else - without even asking our customers to switch, AOL/TW employs tens of thousands of people - switch them over to Linux, save the company millions of dollars, and take that profit away from MS.

    But Nooooooo....... We're not even allowed to order a "bare-bones" machine, we have to order one that comes with Windows preinstalled.

    --
    Stupid sexy Flanders.
  25. AOL Should Buy Hardware Vendor by billtom · · Score: 3, Interesting

    While lots of people talk about AOL shipping a Linux install on their ubiquitous CDs I don't really see that happening (because of the support nightmare of grandma calling up because she can't view the powerpoint presentations she had from her grandkids).

    But what I do think that makes sense is AOL buying a hardware vendor and bundling Linux, Mozilla, an AOL client, and staroffice into a microsoft free solution.

    Gateway would make a good choice becuase they're not doing so well (primarily because they're not Dell), but they've got good brand recognition. Then we'd start to see the "AOL Computer by Gateway" (with Linux probably not mentioned at all).

    AOL would make it clear that this wasn't a Windows computer and that Windows software wouldn't run on it, but AOL has enough money to keep at it until they've sold enough units for software vendors to start supporting it. The target audience would be new computer users and heavy AOL users who are buying a new computer.

    In my view the only way that Linux can succeed on the desktop is if the computer comes pre-installed with Linux. Installing a second OS is something that the average user is just never going to do. And AOL/TW has deep enough pockets to make a go of it.

    1. Re:AOL Should Buy Hardware Vendor by Spoing · · Score: 2
      While I'm in agreement that a Linux-based AOL-branded computer (not just a browser) could work, there is one real snag.

      1. AOL would make it clear that this wasn't a Windows computer and that Windows software wouldn't run on it, but AOL has enough money to keep at it until they've sold enough units for software vendors to start supporting it.

      This won't work. Example: My little sister runs Linux. I setup and configured it for her. She has StarOffice and all the other apps. I put games and game demos on the machine. I've offered to install any type of software she wants.

      Overall, she's happy and content with the machine, and has been using it for almost 3 years now.

      Her main complaint? She can't open Windows programs in email. She is really upset about this, and mentions it often.

      Yes, I've mentioned that this is a Bad Idea. I've mentioned this multiple times. She's still confused that she can't open Windows programs in her email.

      Well, I finally installed Wine for her, and gave her directions on how to use Wine to run those attachments. Yes, I gave her another warning. No, she does not listen.

      Now, say AOL sells this computer to 10% of thier customers, and only 10% of those want to run those Windows attachments...sure, the net would be a safer place...but calls to AOL would go up substantially.

      This is all guesswork on my part, though I'd like to know how well the AOL-branded browser computers went for AOL. So far, the whole internet appliance business seems to have slowed to a crawl.

      --
      A firewall can not protect you from yourself. Turn off what you do not need. Do not use the firewall to do your work.
  26. Yay! more compliant websites by unsinged+int · · Score: 2, Insightful

    "A browser shift by AOL is going to leave an awful lot of companies that assume their Web sites only need to work with Explorer scrambling to rewrite their code so that they don't lose AOL's 30 million-plus subscribers, or about 30% of all U.S. Internet users." I think this is the first real effect we'll notice from all this. Standards compliance means fewer times that I have to say, hmm, doesn't work in Konq...lets try Mozilla...no, hmm...let's try Opera...no, hmm... darn now I have to go get my Windows computer.

  27. Re:Maybe when it WORKS. by EllisDees · · Score: 4, Insightful

    Following standards is not 'retarding your code'. When this switch occurs, a large portion of web pages will have to switch from sloppy MS-only HTML to W3C compliant HTML. Are you honestly saying that this is a bad thing? Is it just because you are lazy and don't want to have to fix your old code?

    --
    -- Give me ambiguity or give me something else!
  28. why not an AOL distribution? by /tmp · · Score: 2, Insightful

    probably asking for it by saying this but, why doesn't AOL just release an AOL dist. of linux? If they had their out dist. they could support AOL on linux and would not have to worry about supporting umpteen thousand linux distros. They would support their own (it could just be a customized version of RH etc..) with the AOL access built in. No reason to sell stripped down "internet appliances" there are probably millions of old pc's that would work great with a stripped down version of linux installed. So when your parents/grandmother is looking to get on the net so they can use email just toss in an AOL-linux cd and install an old box that was replaced by a newer system and poof! grandma is on the net for short $$ and AOL gets another customer. Or they could partner with these companies you see selling $399 boxes at bestbuy etc. to preinstall their AOL client OS instead of Windows and cut back the cost of a new pc even further by not cutting MS a check for each box they sell. (they could almost give these boxes away if they got a 3 years of AOL usage contract signed) Sounds like a win-win to me.

    AOL already mails out millions of cd's to everyone and their brother so getting the dist. out would not be a problem. And if a user calls in with a problem on their pc you could have a very simple fix/restore procedure that would fix corrupted files etc right off the cd (or off a main AOL server since they would have the source). I dare say it just might be a support person's dream. Possibility of getting files destroyed could be minimized because the user would never use the box as root.(root would only be used during upgrading or support fixes, not normal use)

    This of course would not be a distro for most that read slashdot. but for someone that really does not care what is inside the "funny beige box" I think it would work out pretty good. And they could release the source to the client that gets embedded so if somebody really wanted to use AOL on their own Linux box they could hack away but get no support of course.

    probably never happen...

  29. Re:Maybe when it WORKS. by aallan · · Score: 3, Insightful

    Until Gekko can play as fast and loose with HTML as the IE rendering engine...

    HTML is a standard, playing fast and loose with a standard is a bad thing, not a good thing, ask anyone who builds bridges for a living. So the fact that Gecko fails to render non-standards compliant HTML is a good thing. The only problem I have with Gecko is how slow it is compared to the old Navigator 4.x engine...

    Al.
    --
    The Daily ACK - Eclectic posts by yet another hacker
  30. AOL "Mozilla" client on Mac first by RayChuang · · Score: 3, Insightful

    Personally, I think it'll be some time before AOL delivers a client program for their service that uses a web browser derived from Mozilla 1.0 code--at least for Windows users. The reason is that given that Internet Explorer has been tightly integrated into Windows since Windows 98, putting on another browser may end up causing customer confusion, to say the least.

    However, that could be different if the final settlement in the US v. Microsoft case requires a Plain Jane version of Windows XP. In that case an AOL client that uses Mozilla 1.0 code makes way more sense.

    In my personal opinion, the most likely place that AOL may try to use Mozilla 1.0 code as part of the AOL client program is on the Macintosh, where Apple at least since the late 1990's has offered the choice of Netscape and Internet Explorer as your default web browser. I wouldn't be surprised that AOL cuts a deal with Apple that on new Macs if you install the AOL client the web browser based on Mozilla 1.0.x code becomes the default web browser for the whole system.

    --
    Raymond in Mountain View, CA
    1. Re:AOL "Mozilla" client on Mac first by Spoing · · Score: 2

      When you logon to AOL, you fire up AOL's software. That another browser might be on the system is not an issue for an AOL user; they'll never see the other browser, and I doubt that they will notice a new one is being used in AOL 8.0. Instead, they will notice that AOL itself has been upgraded...and probably nothing more specific.

      --
      A firewall can not protect you from yourself. Turn off what you do not need. Do not use the firewall to do your work.
  31. Re:Well they could contribute to the redhat commun by Genom · · Score: 2

    Not necessarily...

    They could simply pare down the standard RH distro to one CD, with just enough to get the base system installed, get X up and running, and get the user on the network (dialup or ethernet) - then download the rest. Kindof like a Debian net-install.

    For all I know, RH may have this ability already, and all AOL would have to do would be the paring down to one CD.

    If they make sure there's an installer on the CD for people who already have a RH/rpm-based install, that would cover most of the bases. Of course, this would leave deb and tgz-based distros out of the mix - but those could be optional downloads if they decided to provide them.

  32. Server side Sun is the real looser by Spoing · · Score: 2
    On the server end, this is another example of one Unix cannibalizing another.

    What I'd like to see is more information on converting from Windows to Unix-style systems. Except for Apple joining the Unix camp, the percentage of Windows and Unix systems seems to be fairly static.

    --
    A firewall can not protect you from yourself. Turn off what you do not need. Do not use the firewall to do your work.
  33. hey, hey.. by Hooya · · Score: 2

    now i may actually want to do something with those cd's that keep coming in my mailbox instead of using them as coasters.

  34. What choice do they have? by dinotrac · · Score: 2

    AOL has had the opportunity to watch Microsoft screw anybody and everybody who got in their way.

    Microsoft is pushing MSN.
    Microsoft is pushing .NET.
    Microsoft is pushing Passport.
    Microsoft is pushing Windows Media Player.
    etc.

    If you are AOL, and Microsoft makes your browser engine, you have got to be concernede that you will be on the wrong side of some little "oops" like the one that recently made Quicktime plugins go poof, or made DR DOS go poof, or what have you.

    AOL needs to break free of IE as a matter of self preservation.
    The world will then be a better place for all of us.

  35. AOLinux with ads! by jawtheshark · · Score: 3, Interesting
    Okay, you don't like ads...I don't like ads, but guess what: I learned something recently. Joe User does not care!
    See, I have this network at home which I administer like a tyrant: only programs that I approve will be installed. Nothing else is allowed unless I think it's usefull and I checked it's integrity (spyware and the like).

    Now, why do I tell you this. Simple: my sister is a real music fan and wants to access file sharing software like Morpheus, Kaazaa and the like. So I did my homework and downloaded Gnucleus (which works insanely well). I told her: look, here is a client without ads that does everything you need. Spread the word to your friends about it. Her reply was simple: my friends do not care about the ads, they are not interested in alternatives. Same thing when she subscribed for an hotmail account: I told her, you'll be spammed to hell and I subscribed her to a better account. She did drop her hotmail account but under protest, because that was what she knew. Another instance is ICQ, 2000 and 2001 clients come with ads. I kept the 99b version until it stopped working correctly. I didn't want the 2000 and 2001 versions because of the ads...she again did not care.
    Most people don't care about ads, not about spyware....even if they underestimate spyware.

    So *if* AOL would bring out AOLinux with a default windowmanager that looks like Windows 98/W2K/XP and that has an ad in the corner: I'm all for it because the normal user will take it, use it and accept the damned litte ad.

    --
    Ahhh...the great dumpster continuum. Many a free computer will be found there. -- sowth (748135)
    1. Re:AOLinux with ads! by emc · · Score: 2, Informative

      I have this network at home which I administer like a tyrant: only programs that I approve will be installed.

      Please look here underAdministrative Fascist.

    2. Re:AOLinux with ads! by flacco · · Score: 2
      Okay, you don't like ads...I don't like ads, but guess what: I learned something recently. Joe User does not care!

      I learned something about myself recently. It's not the ads per se that I so despise. It's the ANIMATION that drives me insane. I don't mind glancing at a static ad for one of those goddamned X10 cameras. But if, while trying to focus on an article, my attention is forced to fight the lure of a dancing clown juggling AT&T logos, I get REALLY pissed off.

      Bringing this back on-topic - That's another reason Mozilla is great. I can TURN OFF the animations, but still accept images from the ad servers used by /. and other sites whom I want to support with my eyeballs.

      Now if we could do the same with Flash animations I might start using the Flash plugin again.

      --
      pr0n - keeping monitor glass spotless since 1981.
    3. Re:AOLinux with ads! by flacco · · Score: 2
      Please look here underAdministrative Fascist [gnu.org].

      So, if you were responsible for a few hundred desktops and a dozen servers, you wouldn't mind users installing whatever they wanted on your company's systems?

      Now,when I say "users" I mean "computer illiterates.". And by "responsible", I mean "if anything goes wrong you have to fix it, whether it's the user who thought he'd try to install his own ISA modem in his PC (which has no ISA slots), the guy who thought it might be cool to set up a Wolfenstein server and invite everyone on his floor to play, the receptionist who won't stop crying because she can't get rid of comet cursor and the Yahoo toolbar that have taken over her browser, and the executive who thought it might be a nice idea to upgrade to Office XP while everyone else is still using Office 97."

      If it weren't for company-wide standards and controls on computing resources, I guarantee you workplace violence statistics would be WAY higher.

      --
      pr0n - keeping monitor glass spotless since 1981.
  36. Ignorance means corporate death. by hkmwbz · · Score: 3, Insightful
    You have some excellent points here.

    Basically, many webmasters are ignorant, or even arrogant enough to ignore standards compliance. Those who fail to see that standards compliance is the way forward, will have painted themselves into a corner. The cost of completely re-doing a site which has been carefully written specifically for IE and all its non-standard extensions and quirks, could potentially lead to more dot.com deaths. This is a good thing! People who don't care enough to inform themselves don't deserve to do business. Am I being harsh? Perhaps, but being an avid user of alternative browsers, I am tired of fighting with arrogant web designers who don't understand what they are doing.

    Finally, we will see who has the foresight or the insight to survive this.

    Grim predictions aside (I may have been a bit negative above), this naturally benefits users of alternative browsers. Mozilla and Opera will both be able to display more pages than before, and their user base will probably grow rapidly because of this. After all, the feature sets of these browsers are far superior to IE from a user's point of view (disclaimer: This is a personal opinion based on my personal preference. Ok? Please, no browser wars).

    Note that I am not even bashing IE here. The good news is that this can be cheaper for online companies in the long run, since it will pay off to write standards compliant code, rather than writing specifically for only certain browsers. MSIE 6 has decent standards compliance. The problem is the proprietary extensions used so extensively instead of the W3C counterparts.

    This becomes even more important now that handheld devices are becoming more and more popular. We will see a significant increase in the number of devices used by consumers, and these devices will be using alternative browsers as well.

    It basically boils down to this: The browser market is diversifying, and if AOL decides to go with Gecko, this will speed up this process. It will not be a nice transition. Many may find that they have major problems due to "IE-centric" code on their sites.

    AOL may not be doing this because they desperately want to get rid of IE or because they want to support alternative browsers (who knows, there may be many reasons, perhaps these play in as well). Nevertheless, for once, it would seem that the consumer - the user - benefits from such a drastic move.

    If AOL are indeed planning to move from MSIE to Gecko, that is...

    --
    Clever signature text goes here.
  37. It fails to render STANDARDS compliant HTML. by solios · · Score: 2

    Say I have a table that's 100% high, and inside of that, an image that's 80 pixels high and another table that's 100% high.
    Now, in theory- and under IE and other browsers, in PRACTICE, this second table would consume the remainder of the height inside of the first table, less the 80 pixels of the image. This is really simple math. This doesn't break ANY standards. This is, in fact, something that's reasonably important to certain design implementations,

    And mozilla pukes on it.

    How's that being standards compliant, if you implement "the standard" for the first table and ignore it for the second? You're using your happy little argument as an excuse to code poorly.

  38. real or not? by Tom · · Score: 3

    Even after reading the article, I'm not sure whether or not this is real.

    Remember: AOL has done well with Windos, which is the OS of choice for most morons out there (and a couple non-morons) mostly because "it came with the 'puter".

    There are a variety of reasons why they should/could switch, but also many why they should not. Maybe, just maybe, this was an intentional leak to put some pressure on M$ and get another "put us on the desktop" deal?

    I would absolutely love to see the web move back to a "best viewed with any browser" attitude, and AOL switching to Mozilla/Gecko would ensure at least a parity.
    Just lets not break open the champagne just yet, hm?

    --
    Assorted stuff I do sometimes: Lemuria.org
  39. You mean the AOL Web Terminal by swb · · Score: 5, Insightful

    I would imagine that this is a lot closer than anyone would care to think:

    I imagine a 15" flat panel display with a keyboard and a mouse. The display base houses 56K and G.lite modems, 10/100 ethernet and mainboard. The whole thing runs on a low-end x86 platform off of a ATA flash disk. It runs a customized Linux kernel with the AOL software as the only environment. As a bonus a printer can be connected and they include some truly basic AOL apps, a word processor and a checkbook program.

    The likely hurdle is the cost of 15" LCDs and the tanked out economy, although the latter should be helping the former. I imagine an Asian manufacturer could build them for about $350 each and AOL could probably sell them at cost w/3 mos. free AOL.

    It's basically WebTV with a good display, and I know tons of people that would buy it because all they want is web+email, they don't care about all the other crap. It fits on that little "desk" by the phone in the kitchen, requires no configuration and cuts AOLs tech support costs significantly.

    It hasn't worked before because the people doing it were trying to provide a generic solution. Coupled with AOL it *has* to work, and AOL will need to do it anyway since MS will be bundling XBoxen in the future as web terminals connecting to MSN.

    1. Re:You mean the AOL Web Terminal by swb · · Score: 2

      Linux is the new tinkerer's OS, and if it became untinkerable, what would be the point? Who would buy it?

      That portion of the market that doesn't want to tinker with something?

      The idea here is that AOL needs to come up with an AOL-only hardware platform that enables people who don't want the complexity of a computer to use their services.

      To do this they need to make the smallest possible investment in a hardware design and the smallest possible investment in a non-Windows operating environment. Linux fits the bill for this. The GUI toolkits are there enough to build in the basic AOL software services, although multimedia might be a challenge.

      It's not a question of supplying a general purpose computer to everyone -- that market is owned by other people. It's a question of supplying the basic hardware to access their software services for people who don't own or want a computer.

      Microsoft is already getting ready to enter that market with future XBoxes. AOL will see less growth unless they can provide an equivilent to an XBox+MSN service.

  40. Evaluation: Dubious by HiThere · · Score: 2

    Why Red Hat? Corel would probably be a lot cheaper, and would get them an office suite for the new platform besides. It may need a bit of patching right now, and updating for new libraries, but it's pretty close.

    OTOH, they might, e.g., buy Lindows, and help everyone feel at home.

    Or buy Stormix (if they can find who owns the rights). That one would be real cheap, and is known to work well.

    I don't see them forking out the cash to purchase Red Hat. All they'd be buying is the name, and in the market that they would be targeting, Red Hat is a completely unknown name.

    Or they could just do what Mandrake did. Fork off of a Red Hat distribution, and start developing it.

    Or they could stay out of the systems market entirely, and just decide that it would be nice to work closely with some particular systems distributor.

    But even with AOL/TW support MS won't loose it's monopoly until there is decent competition in the office suite business. That's why Sun has been pushing Open Office. Build 641 seems to work pretty well on Win95, but on Linux it crashes without useful diagnostics on even a one page document (with, be it admitted, a bit of fancy formatting).
    .

    --

    I think we've pushed this "anyone can grow up to be president" thing too far.
  41. Here's my $0.02... by Teferi · · Score: 5, Insightful

    AOL is *not* going to release a nicely packaged Linux client.
    No. Period. It doesn't make business sense for them to encourage people to switch operating systems and deal with the flak that'll result.
    So, what I'm predicting is AOL looking into building its own custom distro - definitely the AOL client, which, I am told, already exists on a Gateway 'internet appliance' machine, probably a stripped-down-to-the-bones base system and KDE, and a hacked-up version of StarOffice or KOffice with perfect MSOffice compatibility.
    They'll offer this as a standalone OS solution to OEMs. *Not* retail; the people who go out and buy their own OSes aren't AOL's market. AOL's market are the people who buy a computer for light web surfing, IMing, and word processing - sure, they wouldn't mind if every geek in the world used their product on Linux, but we're not their primary market.
    They can tout their OS as being 'Linux-powered' in the same sense that Mac OS X is touted as 'UNIX-powered', hype the stability, etc, etc. They have the advantage that this is an almost entirely closed software platform, so they'll be able to achieve stability greater than that of AOL on Windows. They'll advertise innate security, and so on.

    And it will work, unless MS strongarms the hell out of all the OEMs; in light of the continuing antitrust trial, that would not be in their own interest.
    It's not a victory for Linux - though that's a practically meaningless phrase - it's not a victory for 'Open Source' or 'Free Software' - ditto. It *is* a *small* victory for open standards, which Gecko complies to quite well.
    Don't get any hopes up about AOL replacing its proprietary protocol suite, though, or about them releasing source. They know exactly what they want - a closed software platform that they're not dependent on archenemy MS for, and if they do what it seems they will, they'll get it.

    It occurred to me that such a closed platform would be an excellent way for AOL/TW to enforce DRM on their platforms. Without a way to install new apps besides 'AOL-certified' ones (you bet there won't be any other way - why the hell would they include a terminal app? Their market doesn't care about a CLI), it'll be easy for them to enforce copyright. Not spinning conspiracy theories, just found that interesting...

    --
    -- Veni, vidi, dormivi
  42. Re:am i the only one... by Lendrick · · Score: 2

    On my system (Win 98 SE), IE 5 crashes several times a week. The Mozilla nightly I use crashes maybe once a week, and Moz 0.9.8 is almost perfectly stable.

    Maybe I have a corrupt file somewhere, I dunno. Also, there might be a bug fixed in IE6, which I don't want to download because I don't want it taking over my computer like every previous version of IE has done.

  43. AOLindows? by wytcld · · Score: 2

    A machine that was Linux-based, AOL-optimized, and could run a subset of Windows apps would about do it. Considering the cost-of-acquisition of a new customer for AOL, it could sell these machines at a loss and still come out ahead as compared with spamming the world with coasters. If it can also run AOLindows-compliant games and apps (particularly some of the Adobe and Macromedia stuff, as well as Quicken and tax software) - without requiring those companies to do much more than be sure their stuff installs cleanly under Wine - then it's like: Do you want to pay $1000 for a new Windows machine; or would you rather pay $600 for the same hardware (that's -$200 AOL loss leader, -$200 Microsoft licenses) and still be able to run everything you, average home user, could need?

    And the next time Microsoft is selling a Windows upgrade, offer an AOLindows conversion kit for free, and offer some cool new AOL features that don't work under Win. ("We're sorry, but feature X can't be separated from the OS.")

    With the AOL user base, companies would pay to have their stuff certified AOLindows compliant. It's a sure win if it gets out of the starting gate.

    ____

    --
    "with their freedom lost all virtue lose" - Milton
  44. Cross-platform interoperability by llamalicious · · Score: 2

    This isn't just a good from the "let's get away from everything microsoft" viewpoint.

    Think of what this means for cross-platform AOL clients:
    Mac support: OS9, OSX.x
    Linux support (no client yet, but the switch to gecko should reduce the amount of work to be done in porting)

    Think about what it means for advancing the real W3C standards:
    A standards compliant rendering engine used by the largest single percentage of Internet users out there...?

    This is all good stuff.

    Well aside from AOL taking over my RoadRunner connection in the near future, and controlling everything on cable.

    Now, if we can all just agree to stop using any version of Netscape 4.x, I'll be a happy programmer.

  45. It would help if you learned the f**ing standard by flimflam · · Score: 2

    It will render what you want just fine as long as you put in the right DTD. (I just tried it). If you don't know what you are doing, then just don't use the strict DTD. Anyway, the standard isn't really that hard to understand, and documentation is freely available -- you should try reading it sometime.

    --
    -- It only takes 20 minutes for a liberal to become a conservative thanks to our new outpatient surgical procedure!
  46. And it also funded Mozilla development coordinatio by HiThere · · Score: 5, Insightful

    And AOL also funded Mozilla development coordination. Many of the top Mozilla developers and coordinators were paid to do this by Mozilla. When everyone was jumping up and down on Mozilla for taking too long for the re-write, AOL continued to support them.

    AOL isn't a dedicated member of the community, but they sure are a supporting member! They may be (are!) doing this for their own reasons, which we should attempt to understand, but for the last several years some reasonable fraction of their purposes have been in synchrony with our needs.

    It is, of course, also true that AOL is not a separate company. That's why some people write it AOL/TW, and the TW half is dominant at unpredictable times (of its choice). Even were AOL to be composed of comitted GPL supporters, the TW management could issue a directive, and that would determine the direction. So don't hang you hat or heart on them. But they supported Mozilla as open source before Konqueror was working at all, and before Gnome was usably stable. So don't sell them short, either.
    .

    --

    I think we've pushed this "anyone can grow up to be president" thing too far.
  47. The REAL good news by Hieronymus+Howard · · Score: 3, Insightful

    This line in the article is probably going to benefit the 'ordinary' Linux user most:

    We hear that every hardware vendor who approaches AOL is now being asked, "How is your support for Linux?" before they are even allowed to make a sales presentation

    This could force hardware vendors to provide good Linux support. If so, then we should thank AOL for this, regardless of what we otherwise think of them.

    HH

  48. Re:Believe When Seen, Not Heard by electroniceric · · Score: 2

    You're on the right track, but I think it's even simpler than that.

    'Roblimo' hung this weekend with some friends who are engineers at AOL. Some beer got drunk (this beer was not free as in beer). They got to talking about how much that haaaaate that bad ole Micros~1. The evening got later, some more beer got drunk, and someone mentioned having seen a Mozilla poster in the office of that VP he'd never talked to.
    "Yeah!" said Roblimo, "AOL's going Mozilla! I'll take your dazed and drunken smiles as a yes." he continued. So the well-intentioned Roblimo wrote diligently through the night to brings this news to the world:

    "I'm just positive AOL's switching to Gecko, and right away"

  49. Comment removed by account_deleted · · Score: 4, Insightful

    Comment removed based on user account deletion

  50. AOL using Mozilla by gorehog · · Score: 2, Insightful

    So much to discuss!

    Everyone seems to be looking at this as if it is a major corporate war. I'd like to point out that AOL has had Netscape for a while now, has owned ICQ for a while now, and is owned by Time Warner, who supplies cable modems to their customers. They were talking about buying Red Hat a while ago.

    Well...it sounds to me like there must be some locked doors that say "Confidential" on them somewhere in the AOL/Time Warner hierarchy.

    Answer a few questions here, and intentions become clear.

    1)Is AOL switching over their desktops to Linux? Or is it only their servers? Or...was there any mention of switching to linux at all? I propose that if they switch to Linux internally, and in specific ways it is to develop a "pilot project" for AOL on Linux.

    2)Combine these three elements in a mixing bowl and hand it to a bunch of developers. a)high bandwidth b)AOL-idiot friendly philosophy c)The ability to distro Linux on a single cd. This, folks, would imply the ability to create a pseudo-network computer out of almost any old 80x86 machine out there. (NEW AOLinux! Install it on your old PC! Just install, run and be online!) If the developers at AOL can automate the Linux install they might try to make it transparent. ie: Install Linux and AOL in one fell swoop. Automate the patching process utilizing high bandwidth. They would not even need to specifically ally with hardware vendors, just say that new components should be Linux compatible.

    3) As for the switch to Mozilla...IF IF IF it does happen then yes, it is a shot fired at MS. AOL knows that they need to slowly make MS look more and more buggy and inconvenient, and this is one way to do it. Already it will be hard for people to obtain cheap/free copies of MS with XP's new licensing. Many people brought MS home from the office (making it FREE, not pirated *wink wink*). By taking AOL's enormous user base away from IE compliant browsers they will force a shift in browsing habits and web design methods.

    Will AOL/Time Warner start a full fledged war against MS? No. The consumers wont stand for it. It'll be too confusing for them. There's not enough alignment among the Linux players and not enough consumer products (read: Games, home office, video editing) for a full scale war for consumer hearts. Time-Warner is doing something else though, the are setting up MS for a fall. They are moving quietly, slowly. Like ninja. They are obtaining the properties, developing the technology, and shifting the terrain while microsoft is fighting anti-trust. If TW/AOL is interested they will need to release and idiot-proof, AOL ready Linux that is Linux-in-the-wild compliant.

    That product, distro'd cheaply, and as a replacement for XP could mean something.

    Heh, of course, then imagine AOL hackers at work. hey folks? If AOL does support linux in the above mentioned manner, please, dont hack 'em. Linux on the desktop could use the support they could give.

  51. Re:Well they could contribute to the redhat commun by laserjet · · Score: 2

    Licorys linux is super easy, has KDE 2.something, and fits on one CD. you should try it.

    --
    Moon Macrosystems. Sun's biggest competitor.
  52. Re:Evaluation: Dubious by Surak · · Score: 2

    Decent competition in the office suite community? Name ONE reason anyone would switch from MS Office. ONE. And don't say cost, because as we all know Office comes free on PCs. :-P

  53. In hindsight (BeOS?) by ghost. · · Score: 3, Interesting
    It's all hindsight now, but comments like:

    AOL/TW will buy Red Hat. They're looking to break free of Microsoft...

    Why Red Hat? Corel would probably be a lot cheaper...

    make me wonder if AOL perhaps missed an opportunity by not buying Be. Seems to me BeOS would have fit the bill for all this talk of an AOL web/email only consumer box, and could have been purchased for a song. Am I overlooking something here?

    Cheers.

    --
    Bush is a cylon.
  54. Re:When not If by GreyPoopon · · Score: 2
    Of course AOL will have to eventually switch to Mozilla - considering how much they hate MS...

    I'm sure they eventually will. It would make sense to use technology for which they have the source code. My guess is that the single biggest thing stopping them (besides the work required to switch over) is the fear that the Mozilla flavor of their product will have trouble with web sites that contain either broken or IE-only coding and don't work properly in Mozilla. To much trouble in this area could send some of their customers to MSN. I think switching will be a tad risky.

    --

    GreyPoopon
    --
    Why is it I can write insightful comments but can't come up with a clever signature?

  55. Revenge of "AOL-friendly"? by jesser · · Score: 2

    I hope the reputation of the phrases like "This site is AOL-friendly" and "AOL users click here" doesn't slow web developers from making their sites compatible with Mozilla. I still see sites complain about the "AOL browser's" weak support for png, so I hope AOL can find a way to prevent web developers from confusing the ancient AOL browser with a Gecko-based AOL browser (embedded Mozilla).

    --
    The shareholder is always right.
  56. Fixing windows by PaxTech · · Score: 2
    I agree that it CAN be fixed, but often the time it will take to fix a borked Windows setup is much longer than if you just slick the box and reinstall. When I used to be an NT support monkey, we had a unattended scripted reinstall that would slick, reinstall NT, and reinstall all the user's apps in about 30-40 minutes. Roaming profiles kept (most) of the user's settings as well.

    The general rule of thumb was that you tried to fix it for about 20-30 minutes.. If it was going to take longer, you'd be better off reinstalling.

    --
    All movements for social change begin as missions, evolve into businesses, and end up as rackets.
    1. Re:Fixing windows by Reziac · · Score: 2

      That's great if you're supporting an office where all the Winboxen are fundamentally alike, and where you can count on good backups. It's not so great when your clientele are private parties with a personalized assortment of software (but no bloody backups!) that would take literally days to get back in shape from scratch. In that case, beating Windows into submission is more cost-effective. (My real secret: Windows is afraid of me :)

      So yes, I am considering "what's more cost effective, fix or reinstall?" If I were supporting a corporate network, I'd doubtless become a big fan of Ghost and scripts in a hurry. :)

      --
      ~REZ~ #43301. Who'd fake being me anyway?
  57. Re:Must be able to handle non-standard HTML by aallan · · Score: 2

    By maintaining an ivory tower postion, where only so-called standards-compliant HTML gets rendered, and ignoring the web-wide reality of broken HTML generators, common HTML errors, and commonly used HTML extensions, we embark on a losing strategy.

    Perhaps its because I am looking out from the ivory tower, see my web page if the email address doesn't make it immediately obvious, but there isn't anything on the web that I actually want to use that doesn't render perfectly happily in Navigator 4.x. So why am I loosing anyuthing at that point?

    But at the end of the day, the browser which just "works" for Joe Business is the one which wins. Simple as that. No arguments about standards. No lectures about speach and beer. It either works, or it doesn't.

    Why has the web got anything to do with what business wants? The commerical end of the web may be driving cutting edge development, for somewhat dubious values of cutting edge and development, but its certainly not the interesting bit. Amazon is nice, I like ordering by books online, but I don't particularly want to order my groceries online, or clothes or much else. In most cases I want to be able to pick the thing up and look at it before I buy it so I'd never buy it online. The bulk of the rest of the commerically orientated web is advertising. I don't volunteer to read advertising, so I don't look at it.

    Time to get away from theory and have a look at real-world practice.

    Your priorities aren't my priorities, your real world doesn't necessarily correspond to mine. I'll use the web for what I want, you use it for what you want, but don't expect me to care if browser specific junk makes vast sections that I don't care about un-navigatable.

    A case in point is the receent Slasdot story concerning the development of sites only in Flash (no HTML content at all). This breaks lots of things you probably take for granted, like search engines. You're saying this is a good thing because its obviously what bussiness wants? I'm not convinced.

    Al.
    --
    The Daily ACK - Eclectic posts by yet another hacker
  58. Re:Server Platform by Glytch · · Score: 2

    Performance is based almost completely on hardware and only in minor ways on the operating system.

    Absolutely! After all, operating systems like MS-DOS certainly do everything that one needs on modern PCs.

    Dumbass.

  59. Re:Must be able to handle non-standard HTML by aallan · · Score: 2

    Actually, you make my point. Netscape 4.x does render pages that are not in strict conformance with . This is a good thing for users.

    Considering how long Netscape 4.x has been around I guess I could argue along the lines of decfacto standards, but I conceed the point, but only partially. There aren't very many other browsers around that won't render something that 4.x will render, but there are a whole bunch around that won't render stuff that is IE specific (by definition).

    Personally, I think Flash is trash, but that is beyond the scope of the argument.

    Actually I think Flash is the arguement, or at least its a prime example of what the arguement is all about. I can't think of anyone that has come up with a good use for Flash yet, but its everywhere because business seems to value appearance over content.

    The bulk of the extensions to HTML which aren't rendered well, or at all, by the Gecko engine (lets get back to the point here) are just that, they deal with the appearance rather than the actual content. The web, or at least HTML as designed, is nothing to do with the appearance. Its the entire point its supposed to be information which can be rendered in different ways. I agree the vast bulk of the web is broken, but I think its broken in a different way than you seem to think.

    If people really want to render something that looks like a printed page into a browser (of some kind) they should go off and invent something to do it and stop trying to bend and pevert HTML to do it.

    Al.
    --
    The Daily ACK - Eclectic posts by yet another hacker
  60. Re:umm, whats the big issue here? by Arker · · Score: 2

    I recall someone from AOL saying that partner sites are contractually obliged to support all versions of the AOL client - Windows AND Mac which of course means that most sites are likely to be pretty browser-neutral anyway.

    Ummm no. That would be nice, but it's just not true. At the moment the Windows and Mac clients both use MSIE.


    This is definately an issue with the big guys, it's precisely big corporations which think they can get away with telling their customers what browser to use. Just go down the list of AOL partner sites with Netscape and try to use their login functions and the like if you don't believe me.

    --
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Friends don't let friends enable ecmascript.
  61. Where did you learn to fix Windows? by swillden · · Score: 2

    I think the big difference between Linux and Windows in this respect is that with Linux nothing is hidden from the knowledgeable user. By looking at the available documentation and code on my Linux box I can figure out how to fix absolutely any problem.

    With Windows, sources of information on the details are rarer (yeah, there's a lot of stuff on the MS web site, but there's a lot of stuff not covered, as well) and you have no recourse to the source code. From what I've seen the way you learn how to fix a Windows box is to either (1) take a bunch of classes from MS or (2) hang out with a bunch of guys who took bunch of classes and/or know people at MS.

    Is there another way? I ask primarily out of curiosity, since I don't foresee myself going back to a Windows platform anytime soon, and I'm quite enjoying the reprieve from tech support for my neighbors, relatives, etc., since I started saying "Oh, your Windows mahchine doesn't work? Sorry, I use Linux, don't know anything about Windows." ;-)

    --
    Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    1. Re:Where did you learn to fix Windows? by Reziac · · Score: 2

      You make linux sound like DOS -- where nothing is hidden, all can be found (including source code :) and everything can be beaten into submission by any knowledgeable user!

      As to learning to fix Windows -- actually, I've always approached it as "a big ugly DOS shell in drag", rather than as an opaque GUI that no one understands. LIST (yes, the old DOS util) is my main tool for fixing Windows because it lets me snoop everywhere; I missed it dreadfully during my foray into linux. (Midnight Commander was helpful, but it just wasn't the same.) If I had a tool like LIST, I'm sure I would like and understand linux a lot better. (Maybe someone could adapt the public domain source for LIST 6.0 that's on Simtel.)

      Anyway my method has been mostly hunt and peck. I don't have any magic system, and when advice from elsewhere doesn't solve a problem, I'm prone to invent techniques as I go along. Frex, moving Windows to another drive letter -- conventional wisdom is that this is impossible, and your only option is to reinstall. Why, when all you need do is export the registry to text, do a global S&R for the drive letter, restore the registry, move the files to the new drive, do a few twiddles from DOS as may be required, and reboot?? Maybe that gives you an idea how I approach it -- doing stuff like that seems obvious to me :)

      I suspect I treat Windows a great deal like you would treat linux. :)

      --
      ~REZ~ #43301. Who'd fake being me anyway?
  62. AOL has to be careful not to piss people off, too by swillden · · Score: 2

    There are a lot of comments here to the effect of: "Yeah, cool, if AOL switches to Mozilla, 30% of the population of the web will suddenly require Mozilla compatibility and all those stinking IE-only pages will get fixed!"

    There's something to that, but don't forget AOL's point of view: "If we switch all of our users over to Mozilla, we're going to have millions of customers who are annoyed that since they installed AOL 8.0 their favorite web sites don't work." This will create a huge number of support calls and may incent some people to switch service providers. AOL support has the option of telling customers to minimize "AOL" and click on "that funny-looking blue 'e'" so they can use their web sites, but AOL prefers that most of their users not know they have the option of surfing without all the AOL goodies and ads.

    Not that AOL doesn't have the power to get all of the sites fixed (they clearly do), but they've had their share of black eyes in the past and aren't eager to get another one.

    --
    Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
  63. Re:Evaluation: Dubious by Brendan+Byrd · · Score: 2

    Sure: MS Office doesn't have a Linux version :)

  64. Re:umm, whats the big issue here? by DrXym · · Score: 2
    MSIE for Windows and the Mac are totally seperate products. The Mac version is a reasonably standards compliant browser and isn't tainted by the proprietary crap that goes into the Windows version.


    Besides, AOL also produce various set top boxes, PC appliances including one based around Linux & Gecko which no doubt their partners are also required to support.

  65. Re:umm, whats the big issue here? by Arker · · Score: 2

    MSIE for Windows and the Mac are totally seperate products. The Mac version is a reasonably standards compliant browser and isn't tainted by the proprietary crap that goes into the Windows version.

    Both the Mac and Windows version are "reasonably standards compliant" in the sense that they will render standard compliant HTML reasonably well. That's not the problem at all. The problem is that they also support lots of non-standard code, which MS encourages people to use instead.


    Besides, AOL also produce various set top boxes, PC appliances including one based around Linux & Gecko which no doubt their partners are also required to support.

    Umm produced, past tense, and there was only one the best I remember. It was never made in large quantities, and never sold very well, and was discontinued long ago.


    --
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Friends don't let friends enable ecmascript.
  66. Re:Evaluation: Dubious by WNight · · Score: 2

    Cost.

    Office comes free on OEM PCs, the kind marketted to people who don't know hardware from software and to whom an OS is a "start button".

    Office PCs come bare and the IT department installs everything the employee is going to need.

    Usually when installing a PC the software costs are more than the hardware.

    Most companies do IT in an ad-hoc way, buying a new computer (whatever is cheapest) to replace a dead one, or for a new employee. These companies are hopeless, but they'll likely die because they do this half-assed stuff in other areas too.

    Companies that are on the ball upgrade all PCs every few years, buy some spares, and do it from a dealer who will guarantee being able to sell them identical hardware until their next upgrade point. They decide on a software package, do one perfect install, and ghost all the rest in machine that support hot-swap IDE drive bays. I've been there, working on that kind of thing.

    The company was willing to spend a few dollars for quality parts, and was willing to trim in other areas because every dollar saved on a PC was $100k+ when spread across every PC worldwide.

    If they could save $200 on Office XP ($600 new, assume 1/3 of list, for a large site-license) times 100k PCs it's going to be worth some training and getting used to a slightly different interface.

    Actually, the funny thing is that MS's anti-piracy measures have caused more demand for non-MS products than anything else recently. I've had clients ask for non-MS (free specifically) internet terminals, for free office suites, etc. All because they either fear the BSA, or actually purchased a computer themselves and noticed the huge cost of the software.

    Had MS kept their mouth shut they wouldn't have lost these people. It might not be much, but when people realise you can live without MS software it'll just get easier.

  67. Re:AOL has to be careful not to piss people off, t by Todd+Knarr · · Score: 2

    Counter-point: if AOL announces the change-over, no web site out there can afford to not work with Mozilla when the change occurs. You simply can't afford to tell 30% of your user-base "Sorry, we don't want your business.". If they're under the gun, I suspect the web designers will scramble to accomodate this large chunk of their user-base. It's not like they don't have the tools available, after all.

  68. Re:AOL has to be careful not to piss people off, t by geekoid · · Score: 2

    "that web site isn't Internet compliant"
    is pretty much all they'll have to say. Most people can find another site that gives them what they want, and bigger site will comply, and fast.
    Imagine you own a large Web Business.
    Suddenly 30 million people can't buy your stuff because your not compliant, what do you do?
    hmmmm.
    That proplbably here more about this in more public areas of the media as time goes buy. sort of a heads up.
    I hope every "web-master" whose site is non compliant gets fired when people can't utilize the site they where hired to create.
    and by fired I mean 'hit by a truck'.

    --
    The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
  69. Maybe We'll See AOL_Linux CD's? by reallocate · · Score: 2, Interesting

    AOL is justified in being wary of offering a Linux client that sucks them into providing support for a myriad variety of Linux distributions. But... you can fit a lot of stuff on a CD. How about giving folks an option by rolling out an AOL version of Linux with the AOL client? If you want a Linux AOL client plus AOL support, you get to run AOL Linux. Sounds reasonable to me.

    --
    -- Slashdot: When Public Access TV Says "No"
  70. Re:Maybe when it WORKS. by aallan · · Score: 2

    Also, I don't know where these IE specific webpages exist...don't think I've ever seen one.

    Thats a joke right? Just about anything produced by MS Frontpage with the default output preferences will be IE specific HTML, which while it might get rendered by Netscape, it won't be rendered "correctly".

    Al.
    --
    The Daily ACK - Eclectic posts by yet another hacker
  71. Comment removed by account_deleted · · Score: 2

    Comment removed based on user account deletion

  72. Re:I hear NTL World is good by wackybrit · · Score: 2

    Bah, just be lucky you can actually GET broadband in your area. Where I am, deepest parts of Lincolnshire, no ADSL till at least 2008 (according to BT), and it's too remote for cable to make it within the next few years.

    Good thing that I'm planning to move within the next couple of years to someone with broadband ;-)

  73. Re:Must be able to handle non-standard HTML by SurfsUp · · Score: 2

    A case in point is the recent Slasdot story [slashdot.org] concerning the development of sites only in Flash (no HTML content at all). This breaks lots of things you probably take for granted, like search engines. You're saying this is a good thing because its obviously what bussiness wants? I'm not convinced.

    Right, and it breaks cut n paste, and I can't turn off the animations. For starters, there's a lot more wrong than that.

    I appeciate the graphics and the efficiency, but I resent the loss of control and flexibility. I guess the problem mainly lies in the the players. I don't see why search engines can't dive inside the flash files and index the text, as with pdf's.

    Oh, and having Shockwave continue to control the format is a bad idea for the public. I suppose if that doesn't get resolved we'll see a truly open knockoff pretty soon. SVG is a step in the right direction, if the patent issues get worked out.

    --
    Life's a bitch but somebody's gotta do it.
  74. Mod parent up! by opkool · · Score: 2

    I really would like to have mod points, so I can mod up the parent (the comment #3145234, by hkmwbz)