Announcement

Collapse
No announcement yet.

CodeWeavers Is Working On A New Web Browser

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    Originally posted by r1348 View Post
    You seem to forget the hugely wide deployment of ActiveX for intranet CMS systems in enterprises, which is what CodeWeavers is aiming at. Very often the Windows -> Linux migration is ruled out by companies because the cost of porting from ActiveX to whatever open standard you choose is higher than just buying new Windows licences and sticking to ActiveX. By trying to eliminate this extra cost that is holding back Linux in enterprise, CodeWeaver is actually helping the adoption of Linux, other than of course seeking for private profit, as any company.
    You completely missed the point. I am arguing precisely OPPOSITE to your statement. That this behavior NEEDS TO BE TERMINATED.
    If you bring balmer shit compatibility to Linux, there is no longer a strong motivation to fix the software to no longer need balmer shit, hence it is NEVER fixed, and balmer shit doesn't ever die.

    It doesn't matter if the customer is home or enterprise users, the effect is IDENTICAL.
    Why should ENTERPRISE customers insist on their software suppliers building software that is compatible with Linux if hacks can make balmer shit work adequately on Linux? This is a BAD policy.

    Comment


    • #17
      Originally posted by droidhacker View Post
      You completely missed the point. I am arguing precisely OPPOSITE to your statement. That this behavior NEEDS TO BE TERMINATED.
      If you bring balmer shit compatibility to Linux, there is no longer a strong motivation to fix the software to no longer need balmer shit, hence it is NEVER fixed, and balmer shit doesn't ever die.

      It doesn't matter if the customer is home or enterprise users, the effect is IDENTICAL.
      Why should ENTERPRISE customers insist on their software suppliers building software that is compatible with Linux if hacks can make balmer shit work adequately on Linux? This is a BAD policy.
      I don't think most of it is from 3rd party software suppliers. It's in-house crap.

      So, a manager goes to his boss and says we have 3 options:

      1. Stick with Windows so we can run IE6 for our crap internal software.
      2. Pay our developers 5 million dollars to rewrite it properly, so we can switch to linux.
      3. Buy CodeWeavers for 100,000 dollars and we can switch to linux.

      I think you can guess which option the manager will choose (well, it will be either 1 or 3), and I don't see anything wrong with CodeWeavers trying to fill that niche.

      Comment


      • #18
        Disregarding ActiveX, lots of Israeli websites require IE to render properly. I cannot image how these websites were written to break in every other browser so terribly.

        Doubly so for government and Ministry of Education websites. We cannot even register our children for kindergarten without IE. There is nobody to complain to, it is all legal. Arguments about "availablility to everybody" are a joke, because everybody can pirate Windows.

        Comment


        • #19
          Originally posted by dotancohen View Post
          We cannot even register our children for kindergarten without IE. There is nobody to complain to, it is all legal. Arguments about "availablility to everybody" are a joke, because everybody can pirate Windows.
          This is the kind of thing I'm talking about, but it's even worse in the B2B and G2B spheres, where it's presumed every business is running Windows on every desktop.

          Saying stuff like

          Originally posted by droidhacker
          this behavior NEEDS TO BE TERMINATED.
          If you bring balmer shit compatibility to Linux, there is no longer a strong motivation to fix the software to no longer need balmer shit, hence it is NEVER fixed, and balmer shit doesn't ever die.
          is only valid in ivory towers and your mom's basement. In the real world, Windows has a 90% market share, and it's not a matter of laziness, spite or anything else that causes developers to only have Windows versions of their programs, or that they use Windows-only technologies to build their websites. It's money. Posting online diatribes about it with copious caps won't solve the problem. Having executives say "I want the entire executive board to have iPads, so any product we buy has to work in the iPad browser or have an iPad app available", as sad as that may be, will help. (So will Android tablets and POS terminals, etc., but to the non-technical folks out there, "tablet" is still sadly synonymous with "iPad".)

          And if a company adopts Wine-based products like this to run legacy Windows products they already own and Windows-only websites they have no choice but to use, when the next vendor comes calling, the guy who made the Wine decision so he could move the entire company to Linux on the desktop isn't going to order the Windows version. He's going to say "We're a Linux shop. What's your Linux support like?" It makes the annoying Windows-only sales calls end abruptly and if more than about 5% of companies do that, it'll make vendors do things differently.

          I say this from direct experience. Unfortunately, my direct experience also says that only smaller businesses with a technical culture and good continuity -- and 800-pound-gorillas like Google -- can make such a migration stick, but it is happening.

          Comment

          Working...
          X