Linked by Thom Holwerda on Mon 1st Oct 2012 22:55 UTC
General Development "Everyone seems to have a replacement for JavaScript - Google even has two. Now Microsoft has revealed that Anders Hejlsberg has been working on a replacement and it has released a preview of TypeScript. TypeScript is open source - Apache 2.0 license - and a superset of JavaScript. As you would expect from a Hejlsberg language it incorporates type checking, interfaces and lots of syntactic sugar."
Thread beginning with comment 537242
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:

The DOM issues are mostly browser specific problems.
You still have to battle beast of Redmond on a daily basis if you have to serve the public at large though.

Nice giant swaths of missing features...
Especially the extremely useful CSS3 stuff.

But worse is its random bugs with canvas... yuck..

And with the latest version of IE for XP being IE8... Talk about random bugs... IE8 is the new IE6.
Thank god we don't have to deal with IE6 or IE7 as much anymore... IE7 was God's punishment for me complaining about IE6 for so long :-D

Somewhat related: if you want to make the world a better place for all us web-developers, spread the word that people stuck on IE7 or IE6 can install Chrome Frame without admin rights on their machines!
It won't break anything because it's only triggered if the website they visit specifically tells it to be enabled.

Maybe HTML5 will bring about world peace in another 5 years ;)

Reply Parent Score: 2

lucas_maximus Member since:

There is nothing wrong with IE8. Until Firefox 3.0 (I think) it was doing a better job of being Standards compliant.

Also what nobody mentions is that if you add an XML element to an XHTML document, every browser except IE will happily ignore that whether or not the namespace is declared at the top of the document or not, and render it even though it is invalid XML.

There is a lot of stuff IE gets wrong, but other browsers do lots of shitty things as well (until I think Chrome 12 or 13, if you were rendering a legend tag with display:block, it wouldn't render correctly unless you added a padding to the fieldset).

As for the missing CSS 3.0 features most of these weren't actually finalised or proposed by the time IE9 was beta. Chrome and Firefox have a very different release schedule than Internet Explorer and why there is always a discrepancy in features.

Reply Parent Score: 5

intangible Member since:

Even simple things like zebra striping in IE8 don't work (via nth-child, or any :nth selectors), selection::, :not, border-radius, TONS of css issues when styling tables (tbody scrolling took so long to only barely work in ie ;) ), opacity issues (have to use the IE filters hacks).

Though IE8 is miles ahead of IE7. In IE8, it usually just doesn't support the feature, in IE7 and IE6, it would botch it terribly instead of letting you gracefully fallback. I can live with having to support IE 8 for a while longer. In the corporate world it'll be common for a while since it's the last IE browser for XP ;) (that's what I meant by "the new IE6"... it's here for a while)

My biggest issue is knowing that when IE6 became the dominant browser by default (was good enough at the time and Netscape faded and Mozilla was being crazy), MS completely disbanded the IE team and basically held back web development for years with the monstrosity that became so entrenched.

Never again.

Edited 2012-10-02 06:47 UTC

Reply Parent Score: 2

Savior Member since:

There is nothing wrong with IE8. Until Firefox 3.0 (I think) it was doing a better job of being Standards compliant.

That doesn't really add up: Firefox 3.0 came out in 2008, IE8 in 2009.

Reply Parent Score: 2