For all you IE lovers out there

Do you understand how things make it in to the standards? Do you know the origins of JS?

Because your comments suggest you don't. Browser developers basically have an idea, put it forward and then implement it, go look at the number of webkit and moz prefixed tags that are supported by Chrome/FF/Safari or the Safari HTML5 demos on Apple's site that only allow you to view them with Safari. But no one picks up on them, MS pushing tech and items they want in the standard != IE6 style standard compliance issues.


Questioning?

What do you think this is.

Any way, this is the initial post I was refering too. It is moving in a different direction to the flow of the thread.

If you read my posts just above where you entered this thread, you will catch on to the flow.

Also how can you say it isnt, when it is! Maybe your the one that needs questioning eh?

Care to quantify us with a reason as to why you argue, 'it isnt'?

As well as that I'm here to be educated, as well as educate others, so please tell me, im all ears, and Im not being sarcastic, if you believe me or not.
 
Last edited:
Questioning?

What do you think this is.

Any way, this is the initial post I was refering too. It is moving in a different direction to the flow of the thread.

If you read my posts just above where you entered this thread, you will catch on to the flow.

Also how can you say it isnt, when it is! Maybe your the one that needs questioning eh?

Care to quantify us with a reason as to why you argue, 'it isnt'?

Because things that horrible broken in IE6 like positioning, alpha blending on PNGs, non compliant ECMAScript implementation etc don't exist anymore. IE9 is the most compliant to ratified standards released to date. Yes it has quirks but then so does Opera and I've written CSS that works flawlessly in Safari only to break FF, it's the nature of the beast.

The new bits being talked about at MIX and TechEd are MS trying to innovate and bring some of their ideas to the standards, just like Google, Mozilla and co.

Most of the comments I see about IE10 "trying to force new standards on the web" are from, quite frankly, morons looking to jump on MS for anything.

Much like a lot of your posts in this thread it seems little more than hating, your talk of patch management is a good example. You seem to be under the impressions that all known flaws in OSS are patched immediately, this is far from the case I would bet my mortgage on there being a list of known and reported zero day exploits sat in the private bug trackers of FF/WebKit. This is because of the risk of not fixing v the risk of fixing in a panic that anyone with even a tiny amount of experience of shipping software will understand.

They only patch once month because it allows focused development of solutions that can be developed, tested and deployed without the need to patch the patch immediately. All these things are important when you're working with such a large userbase. It takes time to analyse, code, qa and manage a fix.

The modern development practices and the SDL from MS are seen in industry as examples of best practices and what other strive towards.

I may sound like a fanboy but I don't use IE, total Chrome lover, and I spend 70% of my time in OSX but I think credit where credit is due to the MS.
 
That puts the onus on you, rather then me.

I don't think you understand how to debate. You make a claim, you substantiate it. If you can't substantiate it, then that's a flaw in your argument. The same happens under cross examination. Someone attacks your argument, you defend it. If you can't then you need to either explain why it's irrelevant or admit it's a flaw.
 
trolling ^

Not nesserarly as this is not an inqusition.

I did not title this thread, "Spanish Inquisition of the Opeth Disciple"

A debate is where two sides, put forward argument.

No argument is put forward when some people assume someone doesnt know what they are talking about.

Such as this:
It does smack of someone who's just discovered what open source means, and somehow now contributes to some projects (despite having a visibly high frequency of spelling and grammatical errors). And has come here to tell everyone how awesome open source is and how bad and flawed closed source is.

And I have been substantiating my claims.
 
Because things that horrible broken in IE6 like positioning, alpha blending on PNGs, non compliant ECMAScript implementation etc don't exist anymore. IE9 is the most compliant to ratified standards released to date. Yes it has quirks but then so does Opera and I've written CSS that works flawlessly in Safari only to break FF, it's the nature of the beast.

The new bits being talked about at MIX and TechEd are MS trying to innovate and bring some of their ideas to the standards, just like Google, Mozilla and co.

Most of the comments I see about IE10 "trying to force new standards on the web" are from, quite frankly, morons looking to jump on MS for anything.

Much like a lot of your posts in this thread it seems little more than hating, your talk of patch management is a good example. You seem to be under the impressions that all known flaws in OSS are patched immediately, this is far from the case I would bet my mortgage on there being a list of known and reported zero day exploits sat in the private bug trackers of FF/WebKit. This is because of the risk of not fixing v the risk of fixing in a panic that anyone with even a tiny amount of experience of shipping software will understand.

They only patch once month because it allows focused development of solutions that can be developed, tested and deployed without the need to patch the patch immediately. All these things are important when you're working with such a large userbase. It takes time to analyse, code, qa and manage a fix.

The modern development practices and the SDL from MS are seen in industry as examples of best practices and what other strive towards.

I may sound like a fanboy but I don't use IE, total Chrome lover, and I spend 70% of my time in OSX but I think credit where credit is due to the MS.


Ok I can see some logic here... at least its better than just bashing my understanding, with out providing any bases for your views ;)

Not nice when the tables are turned is it? :p

There may be an element, of marketing, media manipulation and anti IE sentiment, however, this will take a long long time, for Microsoft to rescue, as its well entrenched and not soon forgotten.
 
Last edited:
...We understand you're bitter about something MS related but you don't half go on and on about it whilst posting some drivel :o

Time to go back in your box until IE10 I think.
 
Yea, but its dropping fast. Hence the statement.

And its only a sigficant market share, based on the fact it comes bundled with Windows, hence the whole court case, and the outcome being the the little app microsoft pushed out asking users if they want to install another browser.

But it's not "dropping fast", certainly since the beginning of this year the percentage drop appears to be in line with Firefox's loss, the only browser making any gains is Chrome.

http://gs.statcounter.com/#browser-ww-monthly-201101-201105
 

God some people won't let it rest.


Website said:
"These are very difficult to exploit," said Andrew Storms, director of security operations at nCircle Security, in a March interview. "Last year, it was 'Oh my gosh,' but it turned out to be not so easy to exploit these because it required users to browse to the malicious location and open the file, and the attacker to plant a [malicious] DLL and a bad file. That's quite a few steps."


It's not that easy to do it requires a hell of a lot of things to happen - it's not just an open system. Of course, if someone has full access to the computer, they can exploit anything - because it's done internally. They key here is to get it done over the internet which is not so easy it requires the person to go to the website, access the vulnarability, probably turn off there AV, etc.








M.
 
Last edited:
Oops....

Chrome Pwned...

...the exploit shown is one of the most sophisticated codes we have seen and created so far as it bypasses all security features including ASLR/DEP/Sandbox (and without exploiting a Windows kernel vulnerability), it is silent (no crash after executing the payload), it relies on undisclosed (0day) vulnerabilities discovered by VUPEN ....
 
Oops....

Chrome Pwned...

...the exploit shown is one of the most sophisticated codes we have seen and created so far as it bypasses all security features including ASLR/DEP/Sandbox (and without exploiting a Windows kernel vulnerability), it is silent (no crash after executing the payload), it relies on undisclosed (0day) vulnerabilities discovered by VUPEN ....

OMG Chrome is **** and really insecure. Lets all just use Firefox instead...
 
Back
Top Bottom