211–219 of 219 posts
Earlier quoted context omitted.
And for more IE-related humor, I recommend the following webcomic: https://www.webtoons.com/en/challenge/internet-explorer/list...
I clicked to laugh at a meme for a second and ended up reading an intriguing action packed drama about anthropomorphized web tech. This is awesome! Thanks for sharing :)
I actually just discovered the same comic also has a voice-over: https://youtu.be/8rygV_MeudA
Earlier quoted context omitted.
Imagine having a piece of software where you have 95% global market dominance, a near complete monopoly. And then decide not to update said software in the slightest (other than security fixes) for 6 straight years. Kind of mind blowing.
that was the point. The entire point of IE was to embrace and extinguish the nascent web. With Netscape being cross-platform and the rise of Java, MS was feeling the threat to their Windows platform. Apple is doing a similar thing with Safari. Their App Store is their money maker. It's the whole reason they force Firefox and Chrome to use standards-lagging and neutered WebKit on iOS. Google doesn't like the web, eith…
"Google hasn't been a perfect ally to the Web, but Google's incentives do align far better than Apple's ongoing opposition.
Apple can be ruthless because the Web is a competing platform for them—versus Google's situation where the Web is critical to revenue. Both companies are just acting in their own business interests (even if Google's interests happen to align with what I view as "good").
That's why Safari spent a decade Grover Norquisting the Web. No one told them to—and I'd bet most of them even believe they're saving the Web. But Apple's incentives have long been against the Web, and that won't change unless the incentives change.
Of course, even if Google's incentives are more aligned, they're… messy… and certainly not perfect. So, it is smart to maintain informed suspicion of Google's influence over the Web. That stated, I do see Chromium itself as a very strong hedge."
Earlier quoted context omitted.
Now we have Safari...
The situation with Safari is nothing like what we had back in the IE6 days. It was like developing for multiple platforms, not just a multiple browsers. Thats not to say Safari isn’t dragging it’s heals, but it looks like Apple are finally ramping up development speed. I gather they have been expanding the Safari dev team, and the latest announcements at WWDC look really good. I actually use Safari as my primary brow…
There's only one reason Web Apps are not currently viable on mobile, and unless you're down in the trenches building these apps these issues are invisible.
// One last time remembering IE6 var request = new ActiveXObject("Microsoft.XMLHTTP");
* html { _background:black !ie; }
Earlier quoted context omitted.
And people flock to vsCode and other offerings from MS like IE never happened. People really need long term memory...
Microsoft's leadership and strategy has evolved under Nadella, at least enough to produce quality products like VSCode, and 'good enough' products like WSL. I say this as someone who has historically been very anti-Microsoft, that used to do all my work in Linux. Modern Windows with VSCode, running WSL, is something the Microsoft of the IE6 era would never have produced.
At least Ballmer didn't try to milk me for my data.
I started my career 2008 building real estate and stock news websites. Back then, sooooo much of my days were spent making things "IE compatible" using techniques like: - creating sprite sheets of transparent png corners and sides that one could arrange in a table around an element to create drop-shadows and rounded corners - putting single pixel, transparent gifs at the end of floated containers because clearfix use…
> (...) Microsoft makes different browsers. They are not. They just took Chrome and added their logo and theme around.
Just like Apple's Safari is built on WebKit. You wouldn't say that other vendors like Sony just took Safari and put their logo on the browser for the browser on PlayStation.
It's the same engine, not the same browser.
Earlier quoted context omitted.
Probably getting you a kerberos ticket (which would subsequently be available to other services like explorer). Hitting it with another browser (which need to be configured to use Kerberos) probably led to an NTLM auth in response to the Negotiate header. NTLM isn’t a global credential and doesn’t get a kerberos ticket.
Both Firefox and Chrome can get the kerberos ticket themselves, but it is necessary to whitelist sites that can use spnego. For Firefox, the settings are separate for ntlm and spnego, so one can be disabled and the other whitelisted. Interestingly, Edge for Linux doesn't support spnego at all.
The lack of support for spnego in edge for linux isn’t entirely surprising though I am curious what the excuse is.