Slashdot Mirror


Google Brings SVG Support To IE

stelt writes "Scalable Vector Graphics (SVG) is in most graphical tools. It is used heavily in many big projects, such as KDE and Wikipedia. But Internet Explorer's lack of built-in support for SVG was keeping it away from mainstream use on the web. Google is fixing that now with a JavaScript drop-in named SVGWeb. They've posted a quick, one-minute overview, a longer and more detailed presentation, and you can read about it on the project page."

233 comments

  1. Incompatibility Problems by Anonymous Coward · · Score: 2, Insightful

    How long before a new version of IE develops incompatibility problems with this extension?

    1. Re:Incompatibility Problems by rvw · · Score: 3, Insightful

      How long before a new version of IE develops incompatibility problems with this extension?

      How long until Google or someone else hacks around this?

    2. Re:Incompatibility Problems by Jurily · · Score: 3, Insightful

      It would be easier for them to just add SVG support.

      Can we get rid of IE already, please? Just stop caring about it, and use open standards. If they won't adapt, tough luck.

    3. Re:Incompatibility Problems by Runaway1956 · · Score: 1

      A more accurate question would be, "How long until Microsoft enforces incompatibility with the web again?"

      --
      "Windows is like the faint smell of piss in a subway: it's there, and there's nothing you can do about it." - Charlie Br
    4. Re:Incompatibility Problems by webheaded · · Score: 5, Insightful

      I'm sorry, but I see this response a lot and I honestly have to say...have you ever actually run a website before? Alienating your potential audience over something like this is not really the best way to go about things. Yeah, maybe put up a notice somewhere about it, but really, telling them to just screw off is not actually a solution. It just makes your site look like crap to all the people using IE. The people that still use IE6 and such aren't the type of people to know or care why your site is broken...they just think you have a broken site.

      I completely understand your hate of IE...I can't tell you how many times I've had to go "fix" my website designs because of IE6...it drives me completely insane. On the other hand, you simply cannot ignore these things. Being a good web designer means you unfortunately need to compensate.

      --
      "Those who would sacrifice essential liberties for a little temporary safety deserve neither liberty nor safety." - BenF
    5. Re:Incompatibility Problems by nametaken · · Score: 2, Insightful

      I'm totally down with that... but my boss wouldn't be. I still have to make sure our sites work in IE and FF. :(

    6. Re:Incompatibility Problems by BillGod · · Score: 0, Troll

      Internet Explorer's lack of built-in support for SVG was keeping it away from mainstream use on the web.

      Since when is IE NOT mainstream? They have over 90% of the market? I get it.. they don't follow the rules and IE sux and everyone should use firefox or opera but to call IE not mainstream is if nothing else a bit odd.

      --
      MISSING - Sig file. 2 years old black and white and very funny. If found please email me.
    7. Re:Incompatibility Problems by Kjella · · Score: 1

      Not until Firefox makes significant impact on large corporate installations. I work with quite a few large companies as a consultant and it's IE, IE and then some more IE. A few have Firefox optionally installed but always the blue E. The only good news I do have is that when they do have Firefox installed, it's normally a fairly recent version since they have IE as fallback and don't have to worry about backwards compatibility for Firefox.

      --
      Live today, because you never know what tomorrow brings
    8. Re:Incompatibility Problems by Anonymous Coward · · Score: 1, Interesting

      I work for a large US national lab and for a period of about two months they blocked IE7 and forced you to go to either firefox or IE8 to surf the web. (and yes, it was suggested in that order.)

    9. Re:Incompatibility Problems by V!NCENT · · Score: 3, Insightful

      Yeah, and if everybody keep thinking that then IE will never go away. Just display the message "Your are trying to view this webpage with a non-standard browser. Please use Mozilla Firefox, Google Chrome or Opera." Seriously, is that so hard? Even Google did this trick with YouTube for IE6. Well... if Google can do that then why can't you?

      --
      Here be signatures
    10. Re:Incompatibility Problems by Fallen+Seraph · · Score: 2, Informative

      Internet Explorer's lack of built-in support for SVG was keeping it away from mainstream use on the web.

      Since when is IE NOT mainstream? They have over 90% of the market? I get it.. they don't follow the rules and IE sux and everyone should use firefox or opera but to call IE not mainstream is if nothing else a bit odd.

      Ok, now try READING the summary instead of skimming it.
      They're saying IE's lack of built-in support for SVG was keeping SVG from mainstream use.

    11. Re:Incompatibility Problems by Lord+Bitman · · Score: 4, Insightful

      I'll agree you don't want to alienate your audience just because they're using a broken browser, but that is not what being a "good" web designer is about.

      --
      -- 'The' Lord and Master Bitman On High, Master Of All
    12. Re:Incompatibility Problems by majesticmerc · · Score: 1

      It would be easier for them to just add SVG support.

      Can we get rid of IE already, please? Just stop caring about it, and use open standards. If they won't adapt, tough luck.

      I care about Internet Explorer because even though I do want to code to standards, I don't want to alienate over 60% of my audience.

    13. Re:Incompatibility Problems by derGoldstein · · Score: 2, Interesting

      On the other hand, you simply cannot ignore these things. Being a good web designer means you unfortunately need to compensate.

      That depends on what audience you're targeting. If you're building a website for a government institution, then yes, you need to support IE, including IE6. If, on the other hand, you have commercial considerations, and can deliver a real *web app* by dropping IE, then you have some thinking to do. Maybe you could just drop IE6 -- if youtube can do it then it's probably a safe move. But if you know that you can provide a really significant improvement in usability by supporting only modern/compliant browsers, then being a "good web designer" would be to tell IE users that in order to fully experience this particular site, they need a better platform.

      --
      Entomologically speaking, the spider is not a bug, it's a feature.
    14. Re:Incompatibility Problems by Jurily · · Score: 1

      I care about Internet Explorer because even though I do want to code to standards, I don't want to alienate over 60% of my audience.

      So, if those people suddenly couldn't use half their favorite websites properly, and all of them had a disclaimer saying "This site only uses international standards. If you have problems, please try another browser.", how long would it take for most of them to do so?

      IE had an impact on web developers for way too fucking long. It's about time we change that. BTW, last I heard IE8 actually has some decent standards support, so it might not be that hard to switch. And even Microsoft thinks IE6 needs to die already.

    15. Re:Incompatibility Problems by eugene2k · · Score: 1

      All the web-designers really need to do to get rid of IE is use this:

      <!--[if IE]>
      <H1> You are using a non-standard compliant browser. This web-site requires a standards-compliant browser such as <a href="http://getfirefox.com">Mozilla Firefox</a> or <a href="http://opera.com">Opera</a></h1>
      <![endif]-->

      Sadly, web-designers try to stay compatible with IE which in turn makes it good enough for to view the web most people.

      --
      Apple has "Mac vs PC", Microsoft has "Laptop Hunters", Linux has recession
    16. Re:Incompatibility Problems by Hurricane78 · · Score: 5, Insightful

      Sorry, I once worked on a site, where we got 16 million visits *a day*! And that's only for the top country.

      And your attitude is the very reason we are in this situation.
      You always cave in, when you fear you could lose some users. It's so pathetic.

      No, don't make links non-underlined! We will lose users!
      No, don't stop supporting that browser! We will lose users!
      No, don't change the design! We will lose users!
      etc, etc, etc.

      It's the knock-out argument for all change.

      And while others innovate, you keep running behind them, always trying to catch up.
      While your user base turns into the most stubborn, spoiled and dumb that is possible.
      They will totally dominate you instead of you dominating them.

      If you ever read something about leadership, you will understand, that you can only lead, if you do what *you* want, and stand behind that, not caring what the mob/crowd thinks.
      Because they will *want* to follow you, if you are a role model, *knowing* what is right.
      Of course this won't give you *all* users. Because when you're greedy and want them all, it's pretty much guaranteed that you will be left with even less than if you would have just let those follow you, that want you for what you are.

      Yes, it's the same thing as in love and friendship relationships.

      And as always, this time it's the leaders again, who will drop support for the IE first. Those sites, where people don't go because the sites are trying to do it right for everybody, but because they're so cool and worth so much to them, that people will do anything to still be able to use their site.
      And soon you will follow them. When you notice that half your user base is already lost to them.

      --
      Any sufficiently advanced intelligence is indistinguishable from stupidity.
    17. Re:Incompatibility Problems by TheRaven64 · · Score: 1

      And they're fixing this with a plugin? I'm confused, because the last time I ran IE was several years ago and back then it supported SVG just fine, via a plugin from Adobe. The only limitation was that, because it was a plugin, the SVG had to be in a separate file, you couldn't mix SVG and XHTML in the same XML document. You also couldn't use SVG for site layout and properly embed HTML in it, as you can in a browser that supports SVG natively. So, what advantage does a new Google SVG plugin over an old Adobe SVG plugin? I'd be very surprised if Google supports more of the (massive and crazy) SVG spec than Adobe.

      --
      I am TheRaven on Soylent News
    18. Re:Incompatibility Problems by Anonymous Coward · · Score: 0

      These are also the type of people who will listen to a pop-up that tells them that their computer is infected with viruses and that they need to install some fake anti-virus program to fix it. So you have a simple solution to getting them to upgrade: a pop-up that tells them that their computer is broken and needs IE8/Firefox/Chrome to fix it. Use their ignorance for their own good.

    19. Re:Incompatibility Problems by Anonymous Coward · · Score: 0

      Most "good" web designers I know alienate everybody.

    20. Re:Incompatibility Problems by Anonymous Coward · · Score: 1, Funny

      There could be a warning. Like googlemaps does when it feels your browser crumble under the javascript load. Only browser-specific. Something like:

      "Slow? That's because of all the emulation layers. Your browser doesn't implement current web standards."

      "Does this page look broken? We've done our best to adapt it to IE, but maybe you should switch to a browser that displays standard HTML out of the box."

    21. Re:Incompatibility Problems by agnosticnixie · · Score: 1

      Windows, not IE, IE is down to 60% and losing ground. And that ignores the mobile market (dominated by Opera, Safari and Fennec, I think more or less in that order).

    22. Re:Incompatibility Problems by Mad+Merlin · · Score: 4, Informative

      Since when is IE NOT mainstream? They have over 90% of the market?

      Welcome to 2009, IE has ~60% usage and falling: http://en.wikipedia.org/wiki/Usage_share_of_web_browsers

    23. Re:Incompatibility Problems by Onymous+Coward · · Score: 2, Interesting

      They have over 90% of the market?

      90%? What? That's a bit odd. Really, it's <70% and dropping like a rock.

      See for yourself here. (Requires SVG-capable browser.)

    24. Re:Incompatibility Problems by ClosedSource · · Score: 1

      The problem is that some website developers don't understand what they were hired to do. Their job isn't to pick the winners and losers in the browser market, but to maximize the number of visitors to their employer's site.

      Only in the wacky world of web culture would providing content for the most common tool be considered an annoying afterthought in favor of also-ran tools. It's not about which browser is best, it's about which browser makes your company more competitive.

    25. Re:Incompatibility Problems by ClosedSource · · Score: 1

      "So, if those people suddenly couldn't use half their favorite websites properly, and all of them had a disclaimer saying "This site only uses international standards. If you have problems, please try another browser.", how long would it take for most of them to do so?"

      That's very unlikely to happen simply because a competitor would come along and say "Switch to our site and you can continue using the browser you already own".

      Besides, I thought not having a choice is MS's rap.

    26. Re:Incompatibility Problems by agnosticnixie · · Score: 1

      The most common tool is soon going to be the also ran vs the plethora of standards compliant browsers. They're pretty much equal at this point.

    27. Re:Incompatibility Problems by joaommp · · Score: 2, Interesting

      So true.

      I'm currently in the process of developing a few websites. IE is a pain in the nikta because of the way it renders the stuff. However, it has been quite more pleasing in some javascript details (doing client based XSLT transformations, for example, is working better in IE than in Firefox, which fscks up everything and adds elements not in the XML or the XSL).

    28. Re:Incompatibility Problems by Fallen+Seraph · · Score: 4, Informative

      Well for one thing, Google's plugin can automatically or programatically switch between embedding using flash and embedding it natively. Additionally, Adobe has discontinued their support for the SVG plugin for IE, since Adobe owns Flash now. This Google plugin also works on ALL browsers using JavaScript, and Flash for rendering. So the user doesn't have to install a separate plugin for SVG, like IE had to, and it brings more support for SMIL, which Firefox can't do natively yet, as well as the HTML5 audio and video elements, which Microsoft currently have no plans to support.

      This has the potential to do things like allow you to use the HTML5 video tag indiscriminately, and have it render natively where it's supported, and have it default to Flash where it's not. And finally, if you've ever done a lot of work with SVG, you'd notice that the Adobe plugin often renders scenes in drastically different ways than native implementations. Basically, it was to SVG what IE6 was to the web: a broken implementation. Google's project is still in it's early incarnation and already surpasses the Adobe plugin. Hopefully in the next year or so, it'll match native implementations well enough to allow web developers to use SVG and SMIL, and not have to worry about legacy browser compatibility.

      And if you'd watched the one minute video running through it, you'd know most of this :P

    29. Re:Incompatibility Problems by Fallen+Seraph · · Score: 1

      Sadly, web-designers are forced by their clients and managers to try to stay compatible with IE which in turn makes it good enough for to view the web most people.

      Fixed that for you...

    30. Re:Incompatibility Problems by Anonymous Coward · · Score: 0

      And people will go to your competitor faster then you can say "Firefox".

    31. Re:Incompatibility Problems by ClosedSource · · Score: 1

      When the balanced is tipped, it makes business sense to reevaluate, but we haven't reached that point yet. Even if IE disappeared, you won't be able to design a web page that can be viewed on the other browsers and look the same. Per browser testing will always be necessary for serious work.

    32. Re:Incompatibility Problems by agnosticnixie · · Score: 1

      1. The balance is sufficiently tipped - it doesn't require suppression but a) relevance of users (the corporate world is far from being the only relevant force, or as monolithically into MS' lockin as portrayed) and b) rough parity for the balance to be tipped
      2. Yes, but not to the extent of requiring huge numbers of dirty hacks to keep compatibility with a 6 years old browser.

    33. Re:Incompatibility Problems by westlake · · Score: 1

      90%? What? That's a bit odd. Really, it's 70% and dropping like a rock.

      I see no significant change in market share for IE or Firefox in the better part of a year. Top Browser Share Trend.

      The take-up of IE8 has been faster than Firefox 3.5. Top Browser Share Trend.

    34. Re:Incompatibility Problems by westlake · · Score: 2, Insightful

      I once worked on a site, where we got 16 million visits *a day*!

      Which is what your employer is paying you to deliver.

      If those numbers go down because you are too "principled" to support IE - he will find someone a tad more flexible.

    35. Re:Incompatibility Problems by Onymous+Coward · · Score: 2, Insightful

      "No significant change"? WTH.

      I guess that blue line may look "level" if a person doesn't think about it much.

      But upon closer inspection you'll realize that it shows an 8% drop over the year. The same happened in 2007-2008. Just three years more of that kind of drop and you'll lose another quarter of the market.

      No, IE doesn't have 90% as GP tried to say. And IE is in fact dropping like a rock (PNG version for those with outdated browsers).

      People are learning that IE just isn't cool anymore. And I'm glad of it.

    36. Re:Incompatibility Problems by Ythan · · Score: 2, Insightful

      Youtube doesn't support dial-up either, that doesn't mean you shouldn't.

      There are plenty of free libraries you can use to retain IE6 compatibility with your website. Yes it's quirky and a pain in the ass but if you can't offer at least basic functionality for IE6 users then you're doing something wrong. The anti-IE6 movement just means that there are a lot of developers out there who are too lazy or inexperienced to deal with an older browser. They should take more pride in their work IMHO.

    37. Re:Incompatibility Problems by Anonymous Coward · · Score: 1, Insightful

      "This site requires Adobe Flash Ten. You may download it HERE."

      "This site requires Google SWGWeb. You may download it here."

      What's the difference?

    38. Re:Incompatibility Problems by Creepy · · Score: 1

      speaking of IE6, one of the best SVG viewers available was Adobe's, but support for that died with IE6. Well, I shouldn't say died - I know of several enterprise level products that depend on it, and that is why many corporations are stuck using IE6. Unfortunately, a lot of implementations of SVG are incomplete - in fact, I don't think any are fully compliant

    39. Re:Incompatibility Problems by shentino · · Score: 1

      It's just a game of hardball.

      Youtube is a mega-popular site, so it has enough might to make right that way. Other sites may not have that kind of clout.

      And of course, MS's insanely huge market share, especially in the corporate sector, for IE will mean sites have to kowtow to it, which creates a positive feedback loop.

      This is a war, and I've got the sinking feeling that there will need to be a few casualties (in the form of sites being snubbed by fussy users sticking with IE, and/or users getting fed up with getting the bird for using IE) before MS gets bothered enough to get with it and start following standards.

    40. Re:Incompatibility Problems by SpecBear · · Score: 2, Insightful

      A year ago you were earning $75K/year. Now business has slowed and you're earning $68K/year. Would you say that the recession has had no significant effect on your income?

    41. Re:Incompatibility Problems by ClosedSource · · Score: 1

      I don't get your "relevance of users" argument.

      From a business perspective the most relevant users are those that have the greatest probability of contributing to a company's bottom line.

      Since you haven't explained who this group of "relevant users" are I can't determine if they are or are not.

    42. Re:Incompatibility Problems by binkzz · · Score: 1

      I dare say current interoperability management is nothing compared to how it was in the days of NN3, IE3, NN4 and IE4 with their respective Mac and PC versions, and their own, almost completely separate JavaScript engines.

      --
      'For we walk by faith, not by sight.' II Corinthians 5:7
    43. Re:Incompatibility Problems by Hurricane78 · · Score: 2, Interesting

      Ha. You have NO idea!

      First of all, that company is dead and gone, because they did what they did. So yeah, very wise of them... ^^

      Second, it's not the page views. It's the clicks on ads that are worth money. Page views *cost* money!
      My former employer wanted money. Not page views per se.

      Third, making stuff run in IE took so much time, that by stopping to do it, we would actually have made money!

      Fourth, I left the company to found my own, because I found them to be literally to fuckin' stupid to understand the Internet. Hell, the boss of content used AOL to surf the web! And their "design" team simply tried to clone Apple, every time they came up with "something new". I mean, when I started there, the local "development team" rejected my recommendation to make a library out of the design (HTML tables snippets back then) so we could quickly update it, because, and I quote "Functions are too complicated."... Yes, they meant the concept of calling functions in a server-side language like PHP! I'm not kidding!

      So you really got no idea! ^^

      --
      Any sufficiently advanced intelligence is indistinguishable from stupidity.
    44. Re:Incompatibility Problems by Anonymous Coward · · Score: 0

      I like how you equate spoiled with "not knowing what SVG is". Spend some time away from the computer. There are a lot of hard-working, intelligent people that are not going to understand the difference between browsers until you explain it to them.

      OR you could wax philosophical about leadership in an attempt to rationalize the sales you lost because you were stubborn about a few lines of code. FFS.

    45. Re:Incompatibility Problems by upuv · · Score: 1

      I don't want to nit pick but I will.

      No where in the links provided did it show that the "take-up" of IE8 was faster than Firefox 3.5. It does show that IE8 has a larger market share than Firefox 3.5 but it is definitely not being adopted/taken-up faster than Firefox 3.5.

      As a matter of Fact the data shows that the "take-up" is fastest with Firefox3.5.

    46. Re:Incompatibility Problems by Anonymous Coward · · Score: 0

      Your reference does not support your assertion. 67% is not ~60%. And that 67% is only the lowest source, Net Applications. OneStat puts it at 80%.

    47. Re:Incompatibility Problems by Jugalator · · Score: 1

      How long until Google or someone else hacks around this?

      Given how often Microsoft updates IE for major changes *cough*, I'd say this won't be a problem, no.

      IE 7 did minor but important changes, and IE 8 is something like an exception. Otherwise I think the lastr major engine/standards update was with, uh, IE 4?

      --
      Beware: In C++, your friends can see your privates!
    48. Re:Incompatibility Problems by Eudial · · Score: 1

      Sure 67% is ~60%. An 11% error is well within the error margin where similarity (~) is appropriate.

      --
      GAAH! MY PRINTER IS ON FIRE!!! PUT IT OUT! PUT IT OUT!
    49. Re:Incompatibility Problems by Anonymous Coward · · Score: 0

      How long before a new version of IE develops incompatibility problems with this extension?

      How long until Google or someone else hacks around this?

      Then MS will "develop" and incompatibility... then google will do a workaround... then MS will "develop" an incompatibility... then google will...

      At least one of the names has changed, but this seems familiar for some reason.

    50. Re:Incompatibility Problems by Anonymous Coward · · Score: 0

      They will totally dominate you instead of you dominating them.

      You know, if you think your job is to *dominate your users*, then perhaps your job title shouldn't be "web developer".

      Then again, maybe your 16-million-hits-a-day website is... different from the ones I've worked on.

    51. Re:Incompatibility Problems by SoupIsGoodFood_42 · · Score: 1

      It's not a question of how hard it is, it's about alienating users. Some of us actually design/develop websites for a living. That means we deal with people in life who aren't nerds and who aren't involved with the politics of the web, don't want to be, and shouldn't have to be. Why should I tell my clients that I plan to reduce their number of potential customers because I have an issue with the way MS does business? Is it really that important that we need to make the issue heard outside of the IT industry and at a cost to the client? MS is slowly losing this war, we don't need to be so hostile.

    52. Re:Incompatibility Problems by Anonymous Coward · · Score: 0

      THANK YOU

      People need to get that idea across - IE accounts for only 40% of users of my site, the rest are FF and Safari, plus Chrome is rising. IE 6 is only 4%, thank god - I can almost ignore it soon.

    53. Re:Incompatibility Problems by Anonymous Coward · · Score: 0

      Youtube doesn't support dial-up either, that doesn't mean you shouldn't.

      The lesson to learn from this is that every website is different. Those who think "you must always support IE6" are just as wrong as those who think "I should do whatever google does".

    54. Re:Incompatibility Problems by Doggabone · · Score: 1

      Yeah, and if everybody keep thinking that then IE will never go away. Just display the message "Your are trying to view this webpage with a non-standard browser. Please use Mozilla Firefox, Google Chrome or Opera." Seriously, is that so hard? Even Google did this trick with YouTube for IE6. Well... if Google can do that then why can't you?

      Easy to do, and if it fits the clients profile to do that - and they're cool with it. But if I want to get paid, the site better work in IE6 the way the client wants it to.

    55. Re:Incompatibility Problems by Lennie · · Score: 1

      last one before 7 would be 6, it broke lots of stuff.

      --
      New things are always on the horizon
    56. Re:Incompatibility Problems by Lennie · · Score: 1

      They were also hired to do so in as little time as possible. Some webdevelopers have claimed 80% of their time is spent working around IE. I'm not sure if 80% is a really good number, but atleast 60% is actually very realistic.

      --
      New things are always on the horizon
    57. Re:Incompatibility Problems by Kagetsuki · · Score: 2, Informative

      That's BS, the Adobe SVG viewer is terrible. Perhaps at the time it was good, but now it still remains basically the only SVG plug-in for IE and I have yet to see it render any SVG properly other than the SVGs created by Adobe software.... Not to mention if you include a script in your SVG the Adobe plug-in will immediately lock up or just crash on loading.

    58. Re:Incompatibility Problems by Anonymous Coward · · Score: 0

      The people that still use IE6 and such aren't the type of people to know or care why your site is broken...they just think you have a broken site.

      The number of people that come into my shop with winfixer, windows antivirus 2009 and personal antivirus (read: spyware!) tells me that all you would need to do is have a popup tell them firefox it is a required addon to the 'internet' on there computer.

    59. Re:Incompatibility Problems by V!NCENT · · Score: 1

      Look at it from this way; with IE's marketshare there will also be websites for IE only. That would be uhm... schools included. It has bigger implications than you might imagine.

      --
      Here be signatures
    60. Re:Incompatibility Problems by easyTree · · Score: 2, Funny

      This is a war, and I've got the sinking feeling that there will need to be a few casualties (in the form of sites being snubbed by fussy users sticking with IE

      If you can't beat 'em, join 'em - I mean, do you really want someone who uses IE6 using *your* website? :D

    61. Re:Incompatibility Problems by V!NCENT · · Score: 1

      State on your website: "I develop websites according to the latest standards. If you want have additional legacy support for IE6 then extra costs due to extra work."

      Secondly; Google has the largest user base... ever. So Google would be alienating the most people out there on the web. It clearly doesn't hurt their business at all.

      Don't be so paranoid.

      --
      Here be signatures
    62. Re:Incompatibility Problems by V!NCENT · · Score: 1

      "Internet Explorer is out of date. Please upgrade to the latest version by going here: http://www.microsoft.com/windows/internet-explorer/default.aspx We're sorry for the inconvenience."

      These tactics ALWAYS work with these kind of people.

      --
      Here be signatures
    63. Re:Incompatibility Problems by easyTree · · Score: 1

      I don't remember typing this but it looks veeerrrry familiar :D

    64. Re:Incompatibility Problems by Anonymous Coward · · Score: 0

      Don't say "non-standard", people don't understand or care about that. Say the browser is old and doesn't support features that have become commonplace and are required for your site, then give them a link to update their browser.

    65. Re:Incompatibility Problems by civilizedINTENSITY · · Score: 2, Insightful

      Its amazing to see someone refering to IE6 and suggesting that someone other than microsoft did something wrong. Wake up, face reality, and realize where the "too lazy" to do it right tag really belongs. "Take more pride in their work." In context, thats rich!

    66. Re:Incompatibility Problems by civilizedINTENSITY · · Score: 2, Informative

      I always thought that Adobe implemented a poor SVG to prevent SVG competing with Flash.

    67. Re:Incompatibility Problems by civilizedINTENSITY · · Score: 1

      "...because I have an issue with the way MS does business..."

      While a good case can be made regarding the way Microsoft goes about doing business, the fact of the matter is really that they can't ever seem to be standards compliant. They are always playing catch up, and what works isn't linear. Different things break in different places as you move up the IE version numbers. This isn't about them being thieves (as you seem to think), its about the lack of competence displayed by IE. Basicly it comes down to coding for 4 main browser groups: IE6, IE7, (soon to be IE8), and the rest of the web.

    68. Re:Incompatibility Problems by civilizedINTENSITY · · Score: 1

      I think what he meant by relevance of users is that just because IE6 has almost 15% market share, that doesn't mean that 15% of your customers use IE6. Large corporations are tied to IE6 so its used at work, during the week, but its share goes down on weekends when people surf from home. If it so happens that your web site isn't visited much by people at work, say, but rather caters to people surfing from home, then it might be that IE6 is less than 1/2 of a percentage point of your customers. From a purely financial perspective if it costs more to support them that they bring in in revenue, then they aren't really customers. They are parasites. At least, thats how I interpreted his relevance remark.

    69. Re:Incompatibility Problems by civilizedINTENSITY · · Score: 1

      In what reality does 15% equate to "most common tool". That and the "also-ran" indicate you are trolling.

    70. Re:Incompatibility Problems by civilizedINTENSITY · · Score: 1

      ..."and don't have to worry about forwards compatibility to Firefox", there, fixed that for you.

    71. Re:Incompatibility Problems by rbanffy · · Score: 1

      If no IE-only user ever came to my site again (http://www.dieblinkenlights.com/blog_en) I would experience a 15% drop in unique visitors and an about 88% reduction of bounces.

    72. Re:Incompatibility Problems by sgbett · · Score: 1

      Same old argument, so here again is my tired response.

      85% of our users are IE
      74% of those are IE6

      over 90% of our hits come from N3 which is the NHS Network. These people *can't* change their browser. If I don't support them I can kiss goodbye to contract renewals.

      That's not paranoid, that's business.

      --
      Invaders must die
    73. Re:Incompatibility Problems by BenoitRen · · Score: 1

      Since when should people take pride in adding tons of hacks and work-arounds for one particular web browser? If anyone's lazy, it's the ones who don't bother to make a website standards compliant in the first place.

    74. Re:Incompatibility Problems by Anonymous Coward · · Score: 0

      These statistics hide some important "clumping" in the user base.

      For example, for our Web Application we have found that we must have good IE6 support because a large proportion of our users (actually - our Customer's Customers) are accessing the application from work, where IE6 is the only option for them because they are in a managed environment.

    75. Re:Incompatibility Problems by DaVince21 · · Score: 1

      IE has been Windows' standard browser for years and years. It's not that easy to just "phaze" it away.

      If you mean standards-compliant, then I'd have to agree, but company sites definitely can't afford to do this (disgruntled customers, and less of them).

      --
      I am not devoid of humor.
    76. Re:Incompatibility Problems by Doggabone · · Score: 1

      "Internet Explorer is out of date. Please upgrade to the latest version by going here: http://www.microsoft.com/windows/internet-explorer/default.aspx We're sorry for the inconvenience."

      These tactics ALWAYS work with these kind of people.

      For remarkably small values of "ALWAYS". I have clients who not only refuse to encourage their customers to upgrade their browser, they refuse to upgrade from IE6 themselves. Knowing that much of my billable time is specific to IE6 issues, they'll pay that premium willingly - or, not hire me at all.

    77. Re:Incompatibility Problems by V!NCENT · · Score: 1

      And why is that?

      --
      Here be signatures
    78. Re:Incompatibility Problems by noundi · · Score: 2, Informative

      How long until Google or someone else hacks around this?

      Given how often Microsoft updates IE for major changes *cough*, I'd say this won't be a problem, no.

      IE 7 did minor but important changes, and IE 8 is something like an exception. Otherwise I think the lastr major engine/standards update was with, uh, IE 4?

      IE 8 is MS trying desperately to hang on when browser benchmarking is this moments hot topic, with the competing browsers pushing new version with higher and higher benchmark scores. They have never release a follow-up browser so quickly before. There's nothing new and of value in IE 8 that hasn't already been seen in other browsers. What goes for IE 7, well let's be honest here, it can't be compared to IE 6 as calling IE 6 a browser should be prohibited by law.

      --
      I am the lawn!
    79. Re:Incompatibility Problems by badkarmadayaccount · · Score: 1

      Mod parent up.

      --
      I know tobacco is bad for you, so I smoke weed with crack.
    80. Re:Incompatibility Problems by Keynan · · Score: 1

      First, quit trying to use lazy as an insult on /. it's a compliment here. Lazy is a highly positive trait in an industry were you build automation.

      Second, IE 6 is so far behind that modern CSS, while at the same time holding so much of the market share that it not only makes the initial build more difficult; it makes all the advancements of web tech over the last 5-10 years pointless because you have to hack around it.

    81. Re:Incompatibility Problems by SoupIsGoodFood_42 · · Score: 1

      Google can afford to loose many customers if it wants to. Not all my clients can afford to do so.

      As for putting a quote like that up on my site, it doesn't seem very professional. When I talk to my clients these issues get raised when they are relevant. No need to overload clients with details they don't yet understand before I even talk to them.

    82. Re:Incompatibility Problems by SoupIsGoodFood_42 · · Score: 1

      And I agree with you. Maybe you missed my point? I don't believe in forcing clients to understand the IT world. So issues such as noncompliance are something I don't bring up unless it's an issue in their case. They usually have more important things to do than ponder about the openness of the web, no matter how important either of us think that is.

    83. Re:Incompatibility Problems by Assembler · · Score: 1

      One solution that's becoming popular is to send IE6 users to the mobile version of the page, optionally with a screenshot of what the site would look like in a better browser.

  2. good by Errtu76 · · Score: 1

    Now Microsoft doesn't need to do it anymore. Is this a good thing then? Nice move on Google's part though.

    1. Re:good by rvw · · Score: 4, Insightful

      Now Microsoft doesn't need to do it anymore. Is this a good thing then? Nice move on Google's part though.

      It's a bad thing that Google needs to fix basic functionality in a competitor's product. But it shows one more time why Google is good and why Microsoft is mediocre.

    2. Re:good by Anonymous Coward · · Score: 0

      I see what you did there!

    3. Re:good by moosesocks · · Score: 1

      You can say what you want about the Google Library project, but the important thing to note is that it's finally gotten people in the mainstream industry to begin talking about the merits/drawbacks of extended copyright terms, and more importantly, compelled a number of very high-profile players to join the Internet Archive's "open" effort to digitize out-of-print books.

      It might be convoluted, but the Google Library effort will be a very good thing if it fails, thanks to the dialogue that it's spurred.

      --
      -- If you try to fail and succeed, which have you done? - Uli's moose
    4. Re:good by nametaken · · Score: 1

      Is SVG support really considered basic functionality in a web browser? Gif and Jpeg, I'd call those basic functionality for sure.

    5. Re:good by Anonymous Coward · · Score: 3, Interesting

      As a website builder, svg is more then just pictures, if i had it available to me i would create entire websites using it. ( xhtml+svg )

      why?

      because then i can finally present people with websites that look exactly the same everywhere and fill your entire browser screen.
      dynamic design, dynamic fonts, dynamic everything. no more fixed layout design.

      While i don't thing this new plugin is going to be the holy grail, it love to see them push in the right direction :)

    6. Re:good by jopsen · · Score: 1

      Is SVG support really considered basic functionality in a web browser? Gif and Jpeg, I'd call those basic functionality for sure.

      Okay... But in a modern webbrowser, yes!
      Especially, when you advertise for your browser by saying that it is more compatible than it's competitors...

      I know MS is pure evil, and doesn't care... But isn't just a little embarrassing when your competitors patches your browser using Javascript and Flash...

    7. Re:good by TheRaven64 · · Score: 2

      If having a plugin means Microsoft doesn't need to implement it, then the existence of the several-year-old plugin from Adobe has been doing that already. Looking at the project page, it seems like using this in IE means that the entire SVG part of the site ends up being rendered in an SVG-supporting browser implemented in Flash. Umm, yay?

      --
      I am TheRaven on Soylent News
    8. Re:good by BikeHelmet · · Score: 1

      Is SVG support really considered basic functionality in a web browser? Gif and Jpeg, I'd call those basic functionality for sure.

      Is CSS2 support basic functionality?

      SVG is older than CSS2.

    9. Re:good by Anonymous Coward · · Score: 0

      As a mediocre human being, I object to being associated with Microsoft!

    10. Re:good by SoupIsGoodFood_42 · · Score: 1

      As someone who worked for a national statistics website, I can tell you that SVG would be immensely more useful and user friendly for doing graphs. A single image doesn't contain extra info such as being able to hover over a single bar for a precise value (not only useful, but also more accessible). That's just one example. Trying to do that extra stuff with HTML is a bit of a hack and still far from ideal compared to SVG. Not to mention the most obvious feature: scalability. Not only does it mean less work for content creators, but also increased functionality and accessibility. Wikipedia is good example. An SVG diagram can be viewed on the page, but can also be downloaded and incorporated into a printed document, or perhaps incorporated into a sideshow and projected into a huge wall, where it will still look crisp and clear to read.

      I'd call that basic functionality if the goal of the website is to be an information resource.

    11. Re:good by DaVince21 · · Score: 1

      So did I. Because I'm not blind.

      --
      I am not devoid of humor.
  3. Lame. by iYk6 · · Score: 5, Informative

    From the project page: "No downloads or plugins are necessary other than Flash ..."

    1. Re:Lame. by Bj�rn · · Score: 3, Interesting

      Yes rendering is done by Flash. But since Flash is installed in about 95% of computers that is not much of a problem. Not that I'm a big fan of Flash though.

      --
      Never express yourself more clearly than you are able to think. --Niels Bohr
    2. Re:Lame. by Anonymous Coward · · Score: 2, Funny

      Well according to Adobe (Yes, Adobe) Flash Content works on 99% of the browsers. I imagine Slashdotters to be the 1 remaining percent though =D

    3. Re:Lame. by RiotingPacifist · · Score: 1

      indeed, I suspect the overlap between the 5% without flash and IE users is minimal.

      --
      IranAir Flight 655 never forget!
    4. Re:Lame. by Anonymous Coward · · Score: 0

      I would disagree. I would argue that, other than the Lynx users, most people without Flash are I.E. users because, just like they don't know enough to install a new browser, they don't know how to install a plugin.

    5. Re:Lame. by Anonymous Coward · · Score: 0

      Surely a pure Javascript rendrer would be a better option? you try...

    6. Re:Lame. by westlake · · Score: 1

      From the project page: "No downloads or plugins are necessary other than Flash ..."

      Which means that the SVG support could just as well be integrated into Flash itself - the one plug-in every browser must support.

      No matter how loudly the geek in the back row moans and groans in complaint.

    7. Re:Lame. by cbiltcliffe · · Score: 1

      Just click on the yellow bar that's saying...

      "DON'T click herE!1! It could KILL your compuTER!!!!1!!!!1"

      That's what they usually do to install the latest WinAntivirus, so they should be able to install plugins the same way.... :-)

      --
      "City hall" in German is "Rathaus" Kinda explains a few things......
    8. Re:Lame. by Anonymous Coward · · Score: 0

      Yeah, you're right. They should have chosen Silverlight, obviously...

    9. Re:Lame. by condition-label-red · · Score: 1

      If this works out, it allows one to move away from static image rendering on server-side just so IE will "see" the SVG document. *THIS* is a big win!

      --
      Lorem ipsum dolor sit amet, consectetuer adipiscing elit.
    10. Re:Lame. by Anonymous Coward · · Score: 0

      How lame is that? It works with every computer that matters.

    11. Re:Lame. by derGoldstein · · Score: 4, Funny

      Oh cool, so I can install Flash, explorercanvas, and now SVG Web, and I'll finally have a browser that is half-way up to date.

      Google: Please release V8 as a plugin for IE, along with CSS compatibility. Actually, scratch that -- please release Chrome as a plugin for IE.

      --
      Entomologically speaking, the spider is not a bug, it's a feature.
    12. Re:Lame. by iYk6 · · Score: 2, Interesting

      I am part of the 95% of users with Flash, but I don't like it. I use Firefox, so I shouldn't have to enable Flash to view SVG documents, but the same could be said for watching videos and navigating a website.

      My concern is that many websites that use SVG will require Flash on all browsers, not just the ones using IE.

    13. Re:Lame. by Yvanhoe · · Score: 1

      To be more precise : the people worried about flash installed on their computers usually don't use IE. So this is a non issue.

      --
      The Wise adapts himself to the world. The Fool adapts the world to himself. Therefore, all progress depends on the Fool.
    14. Re:Lame. by derGoldstein · · Score: 1

      You haven't been keeping up to date with the *hip* phishing sites. They'll have an arrow pointing to that yellow bar and saying "Hi! Look at the shiny pictures! Do this and that with that yellow bar to see more shiny pictures!"

      (*and by "shiny pictures" I mean porn)

      --
      Entomologically speaking, the spider is not a bug, it's a feature.
    15. Re:Lame. by Anonymous Coward · · Score: 0

      Maybe you should RTFA, or rather view the presentation.. It is javascript for browsers that DO NOT have native SVG support; You add it to your page and SVG just works, the page itself doesn't change at all.

    16. Re:Lame. by doti · · Score: 1

      Lame? Not for *this* reason.

      Remember we are talking about people that still use IE.
      What's reliance on Flash compared to that?
      Besides, every user running IE has flash enabled already anyway.

      (I didn't RTFA, but I suppose it uses this Flash-based SVG renderer only if the browser doesn't support SVG natively.)

      --
      factor 966971: 966971
    17. Re:Lame. by jopsen · · Score: 1

      Google: Please release V8 as a plugin for IE, along with CSS compatibility. Actually, scratch that -- please release Chrome as a plugin for IE.

      Yes... let's make a javascript accelerator for IE using Flash :)

    18. Re:Lame. by jopsen · · Score: 3, Informative

      My concern is that many websites that use SVG will require Flash on all browsers, not just the ones using IE.

      Quote from the quick start:

      By default we use the Flash based renderer on Internet Explorer while using the native SVG support on other browsers like Firefox and Safari.

      You can override this manually, but why would anyone do that for other purposes than debugging...?

    19. Re:Lame. by jopsen · · Score: 1

      The plugin uses native SVG support if available.

    20. Re:Lame. by derGoldstein · · Score: 1

      You already can, to some degree. Write the functions within Flash (in actionscript, which is also ECMAScript), and send the arguments to the functions that are within the .swf file. It's been done to hide/obfuscate/compact code (though it's not compiled, it's byte code, so it's not really hidden). This way the Flash VM does the processing, not the browser. You'd really need significant separation in functionality in order to improve performance (something that could be done entirely within javascript, and not require access to the browser/DOM), but it's possible.

      --
      Entomologically speaking, the spider is not a bug, it's a feature.
    21. Re:Lame. by Bj�rn · · Score: 1

      You can override this manually, but why would anyone do that for other purposes than debugging...?

      For at least two reasons, incompatibility between various browsers, or missing functionality in some browser. Firefox doesn't support SVG defined fonts yet, for example. Hopefully this is just a passing phase.

      --
      Never express yourself more clearly than you are able to think. --Niels Bohr
    22. Re:Lame. by swilly · · Score: 1

      Flash video works on my Linux box, but Flash audio doesn't. Am I considered in the working or non-working set?

    23. Re:Lame. by BikeHelmet · · Score: 1

      From the project page: "No downloads or plugins are necessary other than Flash ..."

      And how do you propose you get the rendering done in IE6? If you have an SVG compatible browser, you don't need this... which means not lame.

    24. Re:Lame. by maxume · · Score: 1

      There are hooks for implementing scripting languages, so you don't have to go quite so far out on a limb to pull in an alternative javascript engine:

      https://wiki.mozilla.org/Tamarin:ScreamingMonkey

      --
      Nerd rage is the funniest rage.
    25. Re:Lame. by Anonymous Coward · · Score: 0

      Google: Please release V8 as a plugin for IE, along with CSS compatibility. Actually, scratch that -- please release Chrome as a plugin for IE.

      Yes... let's make a javascript accelerator for IE using Flash :)

      If that ends up being too slow, I'm sure they code a nice Flash accelerator in javascript

    26. Re:Lame. by iYk6 · · Score: 1

      From TFA: "If native SVG support is already present in the browser ... you can override this and have the SVG Web toolkit handle things instead."

      I realize that reading the article (project page) is a lot to ask for Slashdot readers. I don't usually read them; this time was an exception because I was actually interested. But really, you should read the article before telling others to RTFA.

    27. Re:Lame. by vertigoCiel · · Score: 1

      You can override this manually, but why would anyone do that for other purposes than debugging...?

      Because their user-agent sniffing doesn't work well for more obscure browsers. I'm using Camino, a lightweight gecko-based browser for OS X, and the demo page defaults to Flash, when it actually runs better with the native SVG option.

    28. Re:Lame. by jopsen · · Score: 1

      For at least two reasons, incompatibility between various browsers, or missing functionality in some browser. Firefox doesn't support SVG defined fonts yet, for example. Hopefully this is just a passing phase.

      True, but I doubt that Firefox doesn't want to support SVG... So if more websites starts using SVG, the rendering in various browser will probably be improved..

    29. Re:Lame. by pbhj · · Score: 1

      I use links2 and don't have flash support .. you insensitive sod.

    30. Re:Lame. by badkarmadayaccount · · Score: 1

      Mutually meta-circular interpreters FTW!

      --
      I know tobacco is bad for you, so I smoke weed with crack.
  4. Funny thing by Anonymous Coward · · Score: 2, Interesting

    IE used to have SVG support via an Adobe plugin. Then they bought the Flash crap and suddenly the SVG plugin went away. Can't have competition I guess.

    1. Re:Funny thing by foniksonik · · Score: 4, Insightful

      That plugin was always slow and only supported a very limited subset of svg.

      --
      A fool throws a stone into a well and a thousand sages can not remove it.
    2. Re:Funny thing by British · · Score: 2

      The Adobe Flash plug-in was terrible. I had to use it when I was testing a SVG drawing ap. One problem noted was that nothing showed up until it was entirely loaded. For larger images, this was frustrating, as it made it slower than Flash.

      I wish SVG would have taken off, but sadly, it didn't.

    3. Re:Funny thing by gaspar+ilom · · Score: 1

      I beg to differ on you view of events: The incremental improvements to Flash were going fine when Macromedia was not owned by Adobe. AS3, JIT compiling, and the more advanced "displaylist" rendering were all well on their way to delivery w/ Macromedia. This continuous improvement has ceased -- and now, Flash 10 is a far more buggy, memory-leaking POS than anything that preceded it.

      And I think it's Adobe's mis-management that's responsible.

  5. Good news for Microsoft by Anonymous Coward · · Score: 5, Funny

    But Internet Explorer's lack of built-in support for SVG was keeping it away from mainstream use on the web.

    Yes! Internet Explorer may finally be ready for mainstream use.

    1. Re:Good news for Microsoft by mgblst · · Score: 1

      Someday soon, it will even be ready for the desktop.

  6. Flash-based... by argent · · Score: 4, Interesting

    It's not bad performance, and useful for applets, but you don't want to use it for layout unless having dozens of little flash applets all over the page turns you on.

    1. Re:Flash-based... by PouletFou · · Score: 1

      At least, web developers can now use SVG without worrying about browser support for IE. If the page is viewed with a svg supporting browser, the svg rendering will be done by the browser, otherwise it will be done by flash. It's up to anyone to choose his browser.

    2. Re:Flash-based... by Anonymous Coward · · Score: 0

      you don't want to use it for layout unless having dozens of little flash applets all over the page turns you on.

      Excessive use of flash is the only thing that works for my impotency so I stand by this move.

    3. Re:Flash-based... by Ilgaz · · Score: 1

      If I told you Flash is actually a vector graphics plugin originally?

      This is what Flash is, originally
      http://www.4dm.com/files/tech/blue.htm (Flash plugin needed), it is "future splash".

      Look to CPU usage having just that original flash open in browser, ou will be surprised. Flash is doing its own job, what it was originally designed for.

    4. Re:Flash-based... by argent · · Score: 1

      In other words, this means you can use SVG for situations where you are only using it in one or two places on the page.

      For people who are looking to use SVG in layout (eg, to replace bitmapped images in borders) this is not useful.

    5. Re:Flash-based... by Yvanhoe · · Score: 1

      But from Google's point of view it is a perfect move : now people will see SVG enabled sites as rendering correctly, while blaming the slowness of IE

      --
      The Wise adapts himself to the world. The Fool adapts the world to himself. Therefore, all progress depends on the Fool.
    6. Re:Flash-based... by argent · · Score: 1

      I think you're missing the point: what this will do will be to allow people who want to use SVG for a single applet (or maybe a few applets) in their web page to use SVG where they previously couldn't... but people using image files for framing and other details of layout (like, say, slashdot) will still have to keep on using them, because it's not practical to have dozens of flash applets on the page.... and most of their viewers will still be using IE.

    7. Re:Flash-based... by argent · · Score: 1

      If I told you Flash is actually a vector graphics plugin originally?

      It wouldn't make a difference. There's also been Postscript and Tcl plugins. I've been watching people try to use plugins to fix the lack of structured graphics in HTML for years, and except for the case where you have one or two graphical areas in the page it doesn't help. You have to drop back to putting rounded curve bitmaps on the corner of boxes (tables or frames or divs, same thing) and more complex graphical constructions are just not done.

      http://www.4dm.com/files/tech/blue.htm (Flash plugin needed)

      A single plugin in the page.

      Look to CPU usage having just that original flash open in browser, you will be surprised.

      Goes up from 10% to 24%, and the applet is 40k. Now imagine Slashdot using 40k flash applets instead of 166 byte PNGs for the rounded corners of boxes.

    8. Re:Flash-based... by LS · · Score: 1

      Is there something inherently bad about having dozens of little flash applets all over the page? That's how HTML layout works, but in this case just happens to be rendered by an external component. Unless there is some known inefficiency caused by having multiple flash elements on a page then what's with the implied negativity?

       

      --
      There is a fine line between being a cultivated citizen and being someone else's crop. - A. J. Patrick Liszkie
    9. Re:Flash-based... by argent · · Score: 1

      Is there something inherently bad about having dozens of little flash applets all over the page?

      Because each flash applet is a new instance of the flash engine.

      Unless there is some known inefficiency caused by having multiple flash elements on a page

      One might say that, yes. If one were to understate the matter for ironic intent.

    10. Re:Flash-based... by LS · · Score: 1

      Do you have some information or links to back this up? Are you sure there's a new instance of the engine for each element on the page? Even so, do you have some idea of the design of the engine and the overhead introduced by each instance? Also, how does it compare to DOM elements in performance? We are talking about Flash on IE here - I'm aware of Flash's poor performance on Linux.

      LS

      --
      There is a fine line between being a cultivated citizen and being someone else's crop. - A. J. Patrick Liszkie
    11. Re:Flash-based... by badkarmadayaccount · · Score: 1

      Why? Because the page is going to be littered with Flash applets? LOL, there are sites that are ONE BIG Flash applet.

      --
      I know tobacco is bad for you, so I smoke weed with crack.
    12. Re:Flash-based... by badkarmadayaccount · · Score: 1

      What if the Flash applet is zero size, and draws on a bunch of canvas tags, or dynamically generates images?

      --
      I know tobacco is bad for you, so I smoke weed with crack.
    13. Re:Flash-based... by argent · · Score: 1

      The overhead of one big flash applet is significantly lower than many small ones.

    14. Re:Flash-based... by badkarmadayaccount · · Score: 1

      Citation?

      --
      I know tobacco is bad for you, so I smoke weed with crack.
    15. Re:Flash-based... by argent · · Score: 1

      The result derives from first principles.

      Each applet requires a separate instance of each and every data structure required to instantiate the Flash execution and display content. This overhead exists independently of the payload.

      Displaying the same content as N instances of the flash execution environment requires more resources than displaying it as a single instance of the flash execution environment.

    16. Re:Flash-based... by badkarmadayaccount · · Score: 1

      Single zero size flash applet, dynamic embedding of bitmaps via DOM manipulation interfaces would fix that overhead.

      --
      I know tobacco is bad for you, so I smoke weed with crack.
  7. Would be nice if it worked though... by KazW · · Score: 1

    Using Firefox 3.5 on Kubuntu 9.04 64 bit = no love, only "browser native svg" rendering works on the demo page, none of the samples work.

    --
    Geeks don't grock information, they grep it.
    1. Re:Would be nice if it worked though... by KazW · · Score: 1

      Never mind, it just took forever to load the flash at the online demo.

      --
      Geeks don't grock information, they grep it.
    2. Re:Would be nice if it worked though... by JackieBrown · · Score: 1

      It doesn't work with Konqueror on my system (Debian AMD64 KDE 4.3)

      I tried disabling netescape plugins so I could try native as well. No joy

  8. So could this be... by Anonymous Coward · · Score: 0

    the year of IE on the desktop?

    1. Re:So could this be... by cbiltcliffe · · Score: 0, Redundant

      But Internet Explorer's lack of built-in support for SVG was keeping it away from mainstream use on the web.

      I parsed that sentence the exact same way, intially, assuming it was a joke from the poster.

      Then I realized after a few seconds that it's not Internet Explorer that was kept away from mainstream web use, but SVG that was kept away from mainstream web use _by_ Internet Explorer....

      --
      "City hall" in German is "Rathaus" Kinda explains a few things......
  9. Could this be ... by Rambo+Tribble · · Score: 2, Insightful

    ... the long-awaited dawn of SVG animation challenging Flash, (and Silverlight)?

    1. Re:Could this be ... by TheRaven64 · · Score: 1

      Just in case Flash wasn't slow enough for you, now you can use an SVG viewer written in Flash! Maybe this is Google's way of making Chrome seem much faster than IE; make IE run a plugin inside another plugin for stuff Chrome does natively...

      --
      I am TheRaven on Soylent News
    2. Re:Could this be ... by Zaiff+Urgulbunger · · Score: 1

      Might be! One thing that I noticed was that where AFAIK you currently need to run Adobe tools to create flash animations, this provides an viable alternative... maybe?! Obviously performance will be better where there is native support, and it's worth noting that this works on iPhone whereas Flash doesn't.

    3. Re:Could this be ... by Rambo+Tribble · · Score: 1

      Actually, SWiSH has long offered an alternative, albeit still proprietary, to Adobe. Some have reported good success running some versions of that software under Wine. A trial version is available to test compatibility. Although it is very narrow in its focus, wink offers some .swf authoring capabilities in an OSS tool.

  10. An interesting link.. by Seth+Kriticos · · Score: 4, Interesting

    Despite the video being very very dry, there was an interesting link in the middle of the presentation: http://downloadstats.mozilla.com/

    That site features real time download statistics for FF3.5. The interesting part is, that the map at the top is rendered in real SVG combined with canvas (for the dots).

    About this flash based library: it's strange. At the demo page the native rendering of SVG failed and only the flash version worked on my FF 3.0.x.. Not a problem with my browser though, as the site I mentioned at the top as well as Wikipedia SVG's work fine. Something is not right with this library, but interesting non the less.

    1. Re:An interesting link.. by D+Ninja · · Score: 2, Informative

      Interestingly enough, the "use your mouse to zoom" on that map does not zoom within Google Chrome.

    2. Re:An interesting link.. by Anonymous Coward · · Score: 0

      There is no svg in that page. It is all canvas.

    3. Re:An interesting link.. by Anonymous Coward · · Score: 0

      the map at the top is rendered in real SVG combined with canvas (for the dots)

      Nice, but where's the SVG part in "SVG+Canvas world map"? I don't see any SVG nodes in the live DOM, nor SVG constructors in http://downloadstats.mozilla.com/js/moz.stat.map.js . And those sparkline s would be just as nice in SVG, with the additional benefit of being accessible over the DOM.

    4. Re:An interesting link.. by Henk+Poley · · Score: 1

      Neither in Safari/Mac 4.0.3

  11. Actual Link to the Demos by Anonymous Coward · · Score: 1, Informative

    The summary misses the actual link to the demos. Here it is:
    http://codinginparadise.org/projects/svgweb/samples/demo.html

  12. Re:Slow city! by Anonymous Coward · · Score: 0

    Wrong. The on-demand rasterization of the SVG document tree elements is done using eigenvalue calculations on full-markov matrices, making it quite fast.

  13. Becoming AOL by geophile · · Score: 4, Insightful

    Microsoft is becoming AOL. A crappy, proprietary, expensive, unreliable impediment to getting onto the internet. Their applications have plateaued, and open-source desktop and web-based competitors are improving rapidly. They'll hang on longer, but they've begun their long decline.

    1. Re:Becoming AOL by Anonymous Coward · · Score: 0

      AOL never had big business by the balls. You're wrong. Sorry.

    2. Re:Becoming AOL by binkzz · · Score: 1

      Actually, because of Open Source, Internet Explorer has improved dramatically. With Google implementing this and canvas, Microsoft will have a much harder time to control web standards. They don't want SVG support, or canvas support, they want people to use SilverLight. But thanks to having a choice of browser, they can't force their changes on everyone anymore, like they did with IE4 to IE6.

      This is why monopoly stifles innovation.

      --
      'For we walk by faith, not by sight.' II Corinthians 5:7
    3. Re:Becoming AOL by upuv · · Score: 1

      You have points. But like others have pointed out it's all about the server room. That's the money maker. Vendor lock in the server room is a GOLD MINE. ( I speak of Large Enterprise. )

      Microsoft was making steady progress in the server room. They actually had products that IT managers would say OK to. So we started to see this bleed of Wintel servers sneek in. Then something happened. All of a sudden not a single "new" wintel system has come near any of the many Enterprise server rooms I have had the pleasure of working with. Sure you see some upgrades and in some cases expansions but nothing new. So what was this meteoric event?

      VISTA.

      In my many many years of working in IT I have never ever seen a product release from a company cause such an instant reaction.

      And your right Open Source is kicking Microsofts butt in the server room. The adoption of Linux based systems in the server room is amasing. Just a few years ago if you mentioned Linux you got that look from the CIO. ( Oh no not another OpenSource nut job ). Now from the CIO we hear "So how can I make this Linux + Java + Green"?

      I personally think Microsoft is looking at a very steep decline. I also think they have started on that decline. However they have this thing called Install base. This is a massive anchor that has saved them many times. It's this install base that will let Microsoft hold at the edge or just inside the edge of decline for a very long time. Vista has eaten up some years already. IE has been nothing but a termite eating at the foundations. Basically Microsoft has to come up with a winning play soon. Or it's going to get much much hard to climb out. This massive install base is shrinking relative to the total market size for some time now. Another flop and it could be lights outs.

      Oh and something to make everyone laugh. www.zune.com. I've left crayons in the sun that made better logo's

    4. Re:Becoming AOL by GF678 · · Score: 1

      Microsoft is becoming AOL. A crappy, proprietary, expensive, unreliable impediment to getting onto the internet. Their applications have plateaued, and open-source desktop and web-based competitors are improving rapidly. They'll hang on longer, but they've begun their long decline.

      I think one of the reasons why I have a problem with Slashdot commenters is because they have delusions that simply aren't being seen in the real world. Microsoft is stronger than ever these days, and Windows 7 is only going to continue their domenance. I don't see businesses leaving their technologies for anything else anytime soon.

      It's very important to not have Slashdot as your only source of tech news, otherwise you can become deluded just like this poster. Microsoft are fucking BIG. We've been suggesting their decline for years. Why do people still believe in this myth?

    5. Re:Becoming AOL by Anonymous Coward · · Score: 0

      oh i know dude! its totally time for the year of linux on the desktop! critical mass will be achieved by september! righteous!

      Really? This post reads like a 100% troll and it gets modded to +5 because it predicts the doom of the big evil Microsoft. Shame on you, moderators.

    6. Re:Becoming AOL by Anonymous Coward · · Score: 0

      not to detract from the normal fare of a slashdot post, but i'd LOVE some hard data on the deployment stats to verify that.

  14. Did you install a 3rd party plugin lately? by Ilgaz · · Score: 1

    Try to make a user to install any plugin in age of 2009 or better, an OS vendor to include it on their default OS install. Please try and see what happens.

    One of the coolest things Google did is Google Earth plugin, perfect for directions and I tested it on one of the sites I manage for 2-3 days. Do you know what I had in return? Mails accusing me of installing spyware/virus to their systems ironically from @gmail.com! I ended up waiting for some kind of flash implementation and rm -rf 'ed all.

    BTW, you are bitching about Flash for what reason? Being 3rd party plugin, abused right? Just watch how your cool, open SVG is used once the advertising agencies/designers figure it has 90% reach.

    1. Re:Did you install a 3rd party plugin lately? by drinkypoo · · Score: 0

      Flash sucks ass on Linux, because Adobe apparently hates Linux or something. The same sites run at maybe a tenth to a hundredth the speed on Linux that they do on Windows on the same hardware. I have never understood how Flash could consume 180+MB and 85% of a Core 2 Duo for a little motorbike game anyway... and I'm talking about on Windows here. But a lot of flash stuff that just flies along on Windows is unusable on Linux. Most of it is crap software, but so is flash.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  15. Campaign donor-independent formats by SgtChaireBourne · · Score: 1

    Yes rendering is done by Flash. But since Flash is installed in about 95% of computers that is not much of a problem. Not that I'm a big fan of Flash though.

    Flash is not a campaign donor-independent file format.

    --
    Beta is broken and the link to classic doesn't work. Stop wasting our time or there won't be anybody left here.
  16. DNR in MS next set of EULAs by Anonymous Coward · · Score: 0

    A terminally sick patient in Hospital will often have a 'DNR' (Do Not Resucitate) notice placed over the bed to avoid them suffering needlessly. Shouldn't the same be done for I.E?

    More than just IE needs that. If Gates wants to be truly philanthropic, he'll require that all new Microsoft EULAs to require the agreeing party become full organdonors and wear a DNR Medical Alert bracelet or necklace. That way the MSCEs would not be a total waste of oxygen.

  17. Know your user base by Temujin_12 · · Score: 2, Interesting

    When discussions of supporting various versions of browsers come up, it is important to know what browsers are actually visiting your site. Earlier this year IE6 users to one of my sites dipped below 10%. Since then, it has now been ~3% for the past month.

    Now I no longer stress about IE6. I'll check it to make sure the site is at least functional and usable in IE6. But I no longer strive for pixel-perfect compatibility. It's simply not worth it.

    You can spend the extra hours getting it to work for all browsers and end up using hacks and mangling your HTML/CSS to do so, but if all of that work is only for a small percentage of your user base, it is not worth it.

    --
    Faith is a willingness to accept something w/o complete proof and to act on it. Reason allows you to correct that faith.
  18. Misleading Headline by Anonymous Coward · · Score: 0

    "Google Brings SVG Support To IE"

    The project is hosted at google code, but this is not a google project, is it?

    1. Re:Misleading Headline by orta · · Score: 1

      I thought that, but one of the project owners has a google.com email address

      --
      my band is more brutal techno punk than yours
  19. Boon for SVG deploability by mjrauhal · · Score: 1

    Now, I'm among the first to go "meh" about their use of Flash. But.

    This SVG kludge certainly improves the chances of web sites deploying, where applicable, SVG solutions instead of going directly for Flash (which is SVG's main proprietary vector graphics competitor on the web). After all, if your SVG/SMIL etc will play in Flash, suddenly your installed base of capable viewers is at least that of Flash.

    'course, more quality SVG tools are needed also but this is an important step towards more openness on the web.

  20. "Nothing to download"? by Anonymous Coward · · Score: 0

    Do they think we're stupid? Or is Google redefining words now?

    OK, actually I think this is great, just bitching about semantics.

    Or maybe it's not so great. MSIE shouldn't be artificially kept alive.

  21. SVG support in other browsers isn't very good by moosesocks · · Score: 1

    As much as I like the *idea* of SVG, it doesn't seem to work particularly well, even in browsers where it is "officially" supported.

    Safari tends to choke on complicated images, and cannot zoom in on full-size SVG images, making it quite useless for reading maps and the like. Additionally, I've noticed that most current platforms do not include any sort of utility to view/edit/rasterize SVG images outside of the web browser. Firefox 3.5 seems to work fine, but I seem to recall older versions having issues. Here's a reasonably complex image to try for yourself.

    Should we just focus on the Canvas element instead? Many browsers already have partial support, with a better/standardized specification on the way in HTML5. Some Javascript trickery should be able to add full support to older browsers.

    --
    -- If you try to fail and succeed, which have you done? - Uli's moose
    1. Re:SVG support in other browsers isn't very good by TeXMaster · · Score: 1

      As much as I like the *idea* of SVG, it doesn't seem to work particularly well, even in browsers where it is "officially" supported.

      Indeed. Of all the browsers that support SVG, for example, Opera is the only one that accepts SVG images from background-image CSS attributes. See this for example.

      Safari tends to choke on complicated images, and cannot zoom in on full-size SVG images, making it quite useless for reading maps and the like. Additionally, I've noticed that most current platforms do not include any sort of utility to view/edit/rasterize SVG images outside of the web browser. Firefox 3.5 seems to work fine, but I seem to recall older versions having issues. Here's a reasonably complex image to try for yourself.

      The image renders perfectly in Opera, and also in FF 3.0.12 (Iceweasel branding). The rendering is very slow, and faulty, on Konqueror.

      Should we just focus on the Canvas element instead? Many browsers already have partial support, with a better/standardized specification on the way in HTML5. Some Javascript trickery should be able to add full support to older browsers.

      There are many possible employments of SVG that have absolutely nothing to do with Canvas, so no. Fix SVG. (This is not to say that Canvas shouldn't be properly implemented too.)

      --
      "I'm never quite so stupid as when I'm being smart" (Linus van Pelt)
    2. Re:SVG support in other browsers isn't very good by ledow · · Score: 1

      You want to use a better browser.

      Opera 9.54 rendered it in no time at all (nowhere near the download time, for instance), allows you to zoom in /out, pan, etc. immediately once it's loaded. SVG is obviously dependent on the number of objects and size of the rendered image, whereas bitmaps are pretty much only reliant on the size of the rendered image, so complex scenes *will* take longer to draw. But with decent code, it shouldn't be a problem at all and vector-based-desktops are the up-and-coming thing.

    3. Re:SVG support in other browsers isn't very good by rliden · · Score: 1

      Even FF 3.5 doesn't render the graphic properly for me. In the legend the type below the line "For legibility all 'streets' and 'st' markers" is garbled. Why doesn't this work 100% of the time? Isn't there a standard (W3C, etc) that could be referenced?

      --
      Don't think of it as a flame, more like an argument that does 3d6 fire damage.
    4. Re:SVG support in other browsers isn't very good by moosesocks · · Score: 1

      Should we just focus on the Canvas element instead? Many browsers already have partial support, with a better/standardized specification on the way in HTML5. Some Javascript trickery should be able to add full support to older browsers.

      There are many possible employments of SVG that have absolutely nothing to do with Canvas, so no. Fix SVG. (This is not to say that Canvas shouldn't be properly implemented too.)

      Let me revise my earlier statement: I feel that the Canvas element is potentially quite a bit more important, given the obvious advantages it has for navigation elements, UI controls, and dynamic content. HTML5 and CSS3 should eventually greatly reduce the number of images used in web layouts, especially if we finally get support for proper gradients in CSS.

      SVG is ideally suited for static vectorized images, and not much else. There is indeed a use for this, although this is not something that is encountered all that frequently, and can already be achieved by simply linking to a PDF.

      --
      -- If you try to fail and succeed, which have you done? - Uli's moose
    5. Re:SVG support in other browsers isn't very good by TeXMaster · · Score: 1

      Should we just focus on the Canvas element instead? Many browsers already have partial support, with a better/standardized specification on the way in HTML5. Some Javascript trickery should be able to add full support to older browsers.

      There are many possible employments of SVG that have absolutely nothing to do with Canvas, so no. Fix SVG. (This is not to say that Canvas shouldn't be properly implemented too.)

      Let me revise my earlier statement: I feel that the Canvas element is potentially quite a bit more important, given the obvious advantages it has for navigation elements, UI controls, and dynamic content. HTML5 and CSS3 should eventually greatly reduce the number of images used in web layouts, especially if we finally get support for proper gradients in CSS.

      SVG is ideally suited for static vectorized images, and not much else. There is indeed a use for this, although this is not something that is encountered all that frequently, and can already be achieved by simply linking to a PDF.

      I'm afraid I still have to disagree. First of all, SVG is not only for static content, since you can do animations with it.

      Also, once you considering linking to a PDF as viable, you're thinking about situations where the content format has little if anything to do with the support capabilities _of the browsers themselves_, whereas I'm thinking about graphic that is an integral part of the webpage.

      Moreover, SVG+CSS is much more appropriate (not to mention backwards-compatible) than Canvas for most UI styling.

      Finally, support for SVG is already in a _much_ more advanced state than Canvas, HTML5 and CSS gradients. Polishing the remaining bugs would be much faster (and should have higher priority) than implementing things which are not even well-defined standards yet.

      --
      "I'm never quite so stupid as when I'm being smart" (Linus van Pelt)
    6. Re:SVG support in other browsers isn't very good by Lennie · · Score: 1

      Their is ExplorerCanvas. Maybe that will help. :-)

      --
      New things are always on the horizon
    7. Re:SVG support in other browsers isn't very good by Lennie · · Score: 1

      Forget what I mentioned, it's based on SilverLight I think. I don't think the openweb will improve if more people download SilverLight.

      --
      New things are always on the horizon
    8. Re:SVG support in other browsers isn't very good by Lennie · · Score: 1

      Ahh, their is more than one implementation, this one is ok:

      http://code.google.com/p/explorercanvas/downloads/list

      --
      New things are always on the horizon
  22. JavaScrpit + IE = Barf by dagamer34 · · Score: 1

    Last I checked, IE had crappy JavaScript performance.

    1. Re:JavaScrpit + IE = Barf by jensend · · Score: 1

      It's still crappy with IE 8, but considerably less so. IE 8 has about half the JS speed of FF 3.0, while IE 7 was more like 1/8 as fast. With modern CPUs you can do quite a good deal with JS on IE 8 before you run into major performance problems.

  23. New God (Re:Incompatibility Problems) by Informative · · Score: 0

    You need to switch to a new god. Bill has fallen out of favor.

  24. it's an experimental alpha by Anonymous Coward · · Score: 0

    It's still an experimental alpha at this stage, according to the project page. Promising though

  25. fixed it for you by fadir · · Score: 1

    Last I checked, IE was crappy.

  26. Google code XForms as well by leighklotz · · Score: 1

    This would be a good fit with the Ubiquity XForms implementation hosted on Google Code as well. It's aimed adding in-browser MVC (model-view-controller) support to IE, Firefox, Opera, and Safari, based on another W3C recommendation, XForms 1.1.

    For example, see this tutorial on how to style hints on triggers (multi-modal word for "buttons") declaratively. (This is from the SVN trunk so it will load all the JavaScript implementation files individually rather than as a single library.)

  27. content creation by edxwelch · · Score: 1

    I don't think browser support is the only thing holding up SVG use. What about content creation tools? Do they have anything as good as the Flash IDE? Or are you ment to hand write the SVG code?

    1. Re:content creation by Zaiff+Urgulbunger · · Score: 1

      Inkscape not good enough for ya?!

  28. No reason Microsoft couldn't do it by FirstTimeCaller · · Score: 3, Insightful

    If you look at Silverlight (or XAML or XPS) you'll see a lot of things that resemble SVG. It would be trivial for MS to support SVG, but they choose not too. The probably don't want anything to compete with Silverlight adoption.

    --
    Wanted: witty unique signature. Must be willing to relocate.
    1. Re:No reason Microsoft couldn't do it by upuv · · Score: 1

      Does anyone else get that feeling that Silverlight is going to be the next ActiveX nightmare?

    2. Re:No reason Microsoft couldn't do it by Anonymous Coward · · Score: 0

      not at all, Silverlight is basically a better Flash. Security is better, features are better. While being a better flash is about the equivalent to being a better OS than Windows 95 any improvement in that particularly crap space should be welcome.

    3. Re:No reason Microsoft couldn't do it by Anonymous Coward · · Score: 0

      I'm not sure how you get from "a lot of things that resemble SVG" to "trivial for MS to support". Just because the output has similar features doesn't mean the back-end is anything alike.

      Nothing that any of these web standards do, on its own, is conceptually hard. Almost all of them do variations of the same thing: put text or simple graphics on the screen, from an XML (or XML-like) text description language. There's even open-source libraries for text parsing, graphics rendering, and so on. (So it should be even trivialer for open-source browsers! Yet somehow Firefox and KHTML/Webkit still have mediocre SVG.)

      Implementing these standards isn't about some new experimental algorithm. It's all about getting a million little details right. That's not trivial.

    4. Re:No reason Microsoft couldn't do it by upuv · · Score: 1

      I would counter point this however.

      - OS specific. ( Moon light can't count as it will never be up date with Silverlight )
      - Browser bias'd. ( Again cross browser support is lets just say suspect. )

      This is conversation is actually fairly mute. As html 5 + new gen Javascript engines are making application add-ons increasingly pointless.

    5. Re:No reason Microsoft couldn't do it by FirstTimeCaller · · Score: 1

      I'm not sure how you get from "a lot of things that resemble SVG" to "trivial for MS to support". Just because the output has similar features doesn't mean the back-end is anything alike.

      Except that you can take SVG data, change the formatting slightly (e.g. with a Perl script), feed it into XamlPad and get your vector output displayed. I'd say that was fairly trivial.

      --
      Wanted: witty unique signature. Must be willing to relocate.
    6. Re:No reason Microsoft couldn't do it by Anonymous Coward · · Score: 0

      The word is "moot" dammit, not "mute". There is a bit of a difference.

    7. Re:No reason Microsoft couldn't do it by badkarmadayaccount · · Score: 1

      The reverse process, along with http://xmlvm.sf.org/ on the server side might prove interesting.

      --
      I know tobacco is bad for you, so I smoke weed with crack.
    8. Re:No reason Microsoft couldn't do it by Anonymous Coward · · Score: 0

      It's another case of the left hand not knowing what the right hand is doing -- no reason why SVG couldn't be supported via Silverlight.

  29. Get a clue by westlake · · Score: 2, Interesting

    Microsoft is becoming AOL. A crappy, proprietary, expensive, unreliable impediment to getting onto the internet. Their applications have plateaued, and open-source desktop and web-based competitors are improving rapidly. They'll hang on longer, but they've begun their long decline.

    The true Slashdot geek can't post about Microsoft without his brain dissolving into mush. Fantasy rules and reality is an intrusion.

    Listen to one of your own:

    And then there's Microsoft. The company prints billions of dollars worth of profits each quarter from its Windows franchise, yet for years it has been quietly developing its next big operating system. And no, I'm not referring to Windows 7.

    Microsoft has created a bridge "between personal productivity and line-of-business applications," one that stitches together Microsoft's "desktop" dominance with its cloud ambitions.

    It's called SharePoint, and with over 100 million seats and $1 billion in revenue, the odds are that your company already has it installed.

    Microsoft CEO Steve Ballmer long ago declared that "SharePoint is the definitive operating system or platform for the middle tier," and I don't think he's using the term "operating system" lightly.

    Increasingly, SharePoint is the center of the Microsoft universe, at least, for enterprise computing. SharePoint serves as the hub for Microsoft's suite of operating systems, applications, and third-party software. It is a content application server, of sorts, one that provides the platform upon which so much of Microsoft's value is now being built.

    I've disparaged SharePoint in the past for its tendency to lock customers into its proprietary repository. But let's be clear: a large number of companies seem perfectly happy to make that trade-off and are actively using SharePoint at the heart of their intranets, extranets, and Web sites.

    Microsoft, Google, and VMware redefine the OS


    Matt Assay is vice president of business development at Alfresco, a company that develops open-source software for content management.

    He was even blunter when speaking to The New York Times:

    SharePoint is saving Microsoft's Office business even as it paves the way for a new era of Microsoft lock-in. It is simultaneously the most interesting and dangerous Microsoft technology, and has largely caught its competitors napping."

    Microsoft's SharePoint Thrives in the Recession

    1. Re:Get a clue by jeanph01 · · Score: 1

      Google help reinvent the paradigm... I agree that sharepoint is a lock-in tool but the google approach is to put documents in the cloud. Right now there is so much IT departments everywhere that cost so much to business. Imagine in 5-15 years. Corporations will have the smallest It dept possible, their only job will be to make sure that the net connection to Google is working.

    2. Re:Get a clue by Lennie · · Score: 1

      Have you actually tried to use it ?

      I'll never do it again.

      it reminds me of their Office email client and the magic 8 ball: outlook not so good

      --
      New things are always on the horizon
    3. Re:Get a clue by mspohr · · Score: 1
      My (very large) organization has Sharepoint installed and it is worthless. I can never find what I need (even stuff that I have put there). Nobody uses it except admin people who are told to use it.

      This is typical Microsoft software that is buggy, has a lousy user interface but is sold to the clueless drones who run most IT departments and they love it because it is easy to administer but it is worthless for any actual work.

      This is typical of large dinosaur organizations. They are slowly dying and being replaced by more agile competitors. Sharepoint is only a symptom of the problem. I am happy to see large dinosaur organizations adopt Sharepoint. It will help move these organization to a better place (the graveyard). Don't ever go to work for an organization that uses Sharepoint. It is a sign of terminal bureaucratic rot.

      --
      I don't read your sig. Why are you reading mine?
  30. Re: from the particular to the general by John+Dowdell · · Score: 2, Informative

    "Flash sucks bleep on Linux, because Adobe apparently hates Linux or something. "

    No, your assumption is mistaken... in fact, Linux is becoming more important to Flash over the next year, as smartphones and televisions introduce new configurations.

    For performance which is slower than other machines, first try checking for background processes or browser chokepoints... that's easier than checking for hardware which creates the difference.

    Then look into the Player betas, feedback process. If we can make your slowdown happen in the shop too, then we'd want to try to ameliorate that situation within the common Player, thanks.

    jd/adobe

  31. Google hosts SVG conference Oct. 2-4 by Anonymous Coward · · Score: 0
  32. Give me a break by snowwrestler · · Score: 2, Insightful

    Sorry, I once worked on a site, where we got 16 million visits *a day*! And that's only for the top country.

    Yeah, we've all "worked on" big sites. It's quite another thing to be financially accountable for a big site. You'll find it's a little less easy to cast away 10% of your users overnight when your profit margin is only 1% to 3%.

    The proper way to build a big site is to build to standards and then add exception handling for any significant user bases. Over time some of these will shrink below the "who cares" limit and you can get rid of that exception. Obviously those limits will vary per site and audience.

    Your rant about leadership is fine, but you do not lead your customers, you serve them. You lead your employees, and then, yes, you sometimes make decisions that are necessary but not popular.

    --
    Build a man a fire, he's warm for one night. Set him on fire, and he's warm for the rest of his life.
  33. If Every Website in the World... by Nom+du+Keyboard · · Score: 1

    If every website in the world would check the browser being used and if they were using a feature that IEx didn't support inserted a message: YOUR BROWSER DOESN'T SUPPORT SOME OF THE FEATURES OF THIS WEBSITE - SOME ITEMS MAY NOT DISPLAY CORRECTLY then Microsoft would get the word. Until then, MS has successfully made this issue Everybody Else's Problem.

    --
    "It's the height of ridiculousness to say for those 9 lines you get hundreds of millions."
  34. SVG dosn't matter anymore. by Kaenneth · · Score: 2, Interesting

    I liked SVG, back in 2004/05 I wrote an interactive map application using SVG and what's now known as AJAX in IE5.

    I read that Adobe was on the standards commitee for SVG, and piled tons of unneeded crap into the spec to try and make it a 'Flash Killer', but once they aquired Macromedia they stopped caring... and they were the only one that did.

    There may never be a full implementation of the SVG spec, it's just too cumbersome, and outdated at this point.

    1. Re:SVG dosn't matter anymore. by Kagetsuki · · Score: 2, Interesting

      That's bullshit, I just developed an application in SVG because the devices it will be run on do not support flash, but they can run Firefox. It runs like a charm, and on an actual computer it runs faster than flash. SVG may seem to have been outdated, but perhaps that's just because the steam behind it ran out for a few years -untill now-. Safari, Firefox, and Opera each have very competent implementations of SVG, and the fact that you don't need to deal with a plug-in and can tightly integrate SVG with HTML/etc. gives it an easy advantage over Flash in my mind. If you say SVG doesn't matter, what do you think does? Flash???

    2. Re:SVG dosn't matter anymore. by evanspw · · Score: 1

      I don't suppose you could point to some websites using SVG so one could check it out?

      --
      Interstitial spaces are filled with cream.
    3. Re:SVG dosn't matter anymore. by badkarmadayaccount · · Score: 1

      Ever heard of wikipedia?

      --
      I know tobacco is bad for you, so I smoke weed with crack.
  35. mainstream use on the web by Anonymous Coward · · Score: 0

    >But Internet Explorer's lack of built-in support for SVG was keeping it away from mainstream use on the web.

    Yeah, IE is a marginal browser used by few.

  36. Supporting IE6 means withholding features by Rix · · Score: 4, Insightful

    Even supporting IE at all means withholding features. That can make sense for supporting IE 7/8, which hold about 40% of the browser market.

    IE6 only holds about 15% of the browser market, and requires extreme measures to support. If Google, a 150 billion dollar corporation, can't be bothered to support it in something as simple as a webmail client or video portal, why should the little guy struggle to support it in a complex web app?

    1. Re:Supporting IE6 means withholding features by Fred_A · · Score: 1

      Even supporting IE at all means withholding features. That can make sense for supporting IE 7/8, which hold about 40% of the browser market.

      IE6 only holds about 15% of the browser market, and requires extreme measures to support. If Google, a 150 billion dollar corporation, can't be bothered to support it in something as simple as a webmail client or video portal, why should the little guy struggle to support it in a complex web app?

      While a number of companies retain IE6, in my case I just make sure it more or less works (i.e. no major loss of functionality) on the sites I build. If it doesn't display "just so", well tough. I don't check them for Mosaic users either. (I never even build any Gopher compatibility in for traditionalists).

      I understand that companies have to protect their investment in crappy software (duh), but *some* pressure has to be applied *somewhere*. Or in 15 years we'll still be stuck with that damn thing.

      OTOH of curse, it might end up with :

      IT guy : Our users complain that they cannot display web sites, nothing works on IE6 any more
      PHB : Good, productivity will increase !
      IT guy : But a lot of them need the web to work
      PHB : Tell them to order paper catalogues
      IT guy : Uh, they're ordered through a web interface...

      --

      May contain traces of nut.
      Made from the freshest electrons.
  37. Right on time! by Kagetsuki · · Score: 1

    I was actually just about to start porting an SVG applet I wrote to IE, and was not looking forward to it. After about 10 minutes of fiddling with this google project I got it up and running in IE! Google probably saved me at least a few days of work this week, and probably quite a bit more in the future! Thank you google!

  38. But... by DaVince21 · · Score: 1

    But it's IE, and JavaScript is slow in IE!

    --
    I am not devoid of humor.
  39. That's fine for static pages by Rix · · Score: 1

    But webapps with lots of javascript have more to worry about than just looking a bit funky.

  40. Re: from the particular to the general by drinkypoo · · Score: 1

    Flash is more or less usable for me on one machine since the release of fb 10b for amd64. But when I went from Windows XP to Linux (tried several) on my poor little Aspire One with an Atom processor, flash went from mostly pretty good to barely usable. Most other things are at least in the ballpark, if not better (useful boot time is much better, for one.)

    --
    "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  41. IE? Try Office by TheStonepedo · · Score: 1

    I applaud Google's efforts to bring us all toward standards-compliance, but hope this tweak will be brought to MS Office rather than stopping at MSIE.
    Most companies have vector graphics of their logos for printing company swag, yet their email signatures still use image-based logos that add hundreds of kilobytes to the simplest one-line correspondence.
    So long as big boss wants email signatures that look like business cards and IT guys want uniform installations of Windows+IE+Office any move toward standards-compliance which Microsoft will embrace is a godsend.

    --
    I'll be your candy shop of infinite deliciousity if you'll be my discotheque of endless rump-shaking.
  42. And you didn't do the superman trick? by tjstork · · Score: 1

    16 million visits a day...man, all you had to do is flash an occasional link to your site, what, 1 in a 1000 times? Man oh man...

    --
    This is my sig.