Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Internet Explorer 11: “Don’t call me IE”

nczonline.net

Post reply on HN
Print view View original

161–170 of 190 posts

Re: Internet Explorer 11: “Don’t call me IE”

#161

Post by oneweekwonder »

MichaelGG wrote: post #144
bad_user wrote: post #122

Earlier quoted context omitted.

Just use something open-source - you'll get the Awesome [1] edition on any kind of chip. I never understood why some people prefer to buy licensed stuff from Oracle or Microsoft. Do you like pain? [1] http://www.codinghorror.com/blog/2009/07/oh-you-wanted-aweso...

The only good open source SQL RDBMS I'm aware of is Postgres. The moment Postgres has the feature range of SQL Server (SSIS, SSRS, SSAS), supports the same HA features without hassle, and is generally even half as easy to manage, I'll switch. Meanwhile, life's too short for me to want to become a "real" DBA.

After googling all the acronyms, I would like to know what features you believe SSIS, SSRS, SSAS and HA give you can not get from Postgres with drop in replacements.

Except maybe for that everything is already integrated and "just works".

What I'm asking is if you can specify some elements of the stack you mentioned, that is hard to replicated or unique to SQL Server?

Re: Internet Explorer 11: “Don’t call me IE”

#164

Post by deathanatos »

That User-Agent isn't really valid.

It's the "like Gecko". If you only read the BNF, then okay, it's valid. But the various sections are supposed to have semantic meaning — they're supposed to be products with optional versions and comments. Like,

  Mozilla/5.0 (Windows NT 6.3; Trident/7.0; rv 11.0)
Means the product "Mozilla" with version "5.0", followed by a comment of "Windows NT 6.3; Trident/7.0; rv 11.0". Thus their UA of…

  Mozilla/5.0 (Windows NT 6.3; Trident/7.0; rv 11.0) like Gecko
…includes the products "Mozilla", "like" and "Gecko".

Like the article mentions, "like Gecko" has been done before:

> Safari was the first browser to add “like Gecko” so that anyone sniffing for “Gecko” in the user-agent string would allow the browser through.

And they put it in a comment, not as two separate products:

> AppleWebKit/536.26 (KHTML, like Gecko)

See http://www.ietf.org/rfc/rfc2616.txt.

Re: Internet Explorer 11: “Don’t call me IE”

#165

Post by snarfy »

bsimpson wrote: post #33

I was at CES last year, and the showing of the IE team was my favorite part of the trip. They were a bunch of younger guys who basically said "We know the guys who used to work here did some terrible things in our name. We're changing that, and we're here to tell you about it." They seemed like really cool dudes. I even went over to the mall to try a Surface when they came out. Then, I realized Windows 8 is still Win…

Reminds me of the 'I contribute to the windows kernel. We are slower than other operating systems.' article:

http://blog.zorinaq.com/?e=74

"Another reason for the quality gap is that that we've been having trouble keeping talented people. Google and other large Seattle-area companies keep poaching our best, most experienced developers, and we hire youths straight from college to replace them. You find SDEs and SDE IIs maintaining hugely import systems. These developers mean well and are usually adequately intelligent, but they don't understand why certain decisions were made, don't have a thorough understanding of the intricate details of how their systems work, and most importantly, don't want to change anything that already works.

These junior developers also have a tendency to make improvements to the system by implementing brand-new features instead of improving old ones. Look at recent Microsoft releases: we don't fix old features, but accrete new ones. New features help much more at review time than improvements to old ones.

(That's literally the explanation for PowerShell. Many of us wanted to improve cmd.exe, but couldn't.)"

Re: Internet Explorer 11: “Don’t call me IE”

#166

Post by pelemele »

MichaelGG wrote: post #144
bad_user wrote: post #122

Earlier quoted context omitted.

Just use something open-source - you'll get the Awesome [1] edition on any kind of chip. I never understood why some people prefer to buy licensed stuff from Oracle or Microsoft. Do you like pain? [1] http://www.codinghorror.com/blog/2009/07/oh-you-wanted-aweso...

The only good open source SQL RDBMS I'm aware of is Postgres. The moment Postgres has the feature range of SQL Server (SSIS, SSRS, SSAS), supports the same HA features without hassle, and is generally even half as easy to manage, I'll switch. Meanwhile, life's too short for me to want to become a "real" DBA.

Everything is awesome until you stop doing general stuff. Once I started digging into more complex MDX queries in SSAS (calculated fields) the story started to be quite different. I have been doing Win dev since 1993 so I could tell you a lot of stories...

Re: Internet Explorer 11: “Don’t call me IE”

#167

Post by mrpippy »

mratzloff wrote: post #54
chadzawistowski wrote: post #35

Earlier quoted context omitted.

Windows 8 may still be Windows, but WinRT is very much the System 9 -> OS X transition. Windows 8 supports both the old Win32 APIs and the new WinRT APIs.

Well, OS X had Classic[1] for years, so it had that compatibility layer to bridge 9 to X. [1] http://en.wikipedia.org/wiki/Classic_Environment

Right. In addition, CarbonLib ran on OS 8/9, so developers could migrate their apps to Carbon but continue to build OS 9 and X apps from the same codebase.

Re: Internet Explorer 11: “Don’t call me IE”

#168

Post by Hrundi »

ksk wrote: post #113
TylerE wrote: post #75

Earlier quoted context omitted.

That's not what I remember. It was more about it having remotely-exploitable vulnerabilities without being uninstallable.

You're incorrect. And technically speaking the browser wasn't integrated with the OS (and never was), it was the rendering engine (shdocvw.dll and mshtml.dll). The Windows UI featured HTML elements that the OS rendered via this. The rendering engine is not itself connected to any TCP/IP stack, so remote exploits are impossible. But ofcource if you went to web sites with malicious HTML you could get ownzored because o…

> ...But ofcource if you went to web sites with malicious HTML you could get ownzored because of bugs in the rendering engine.

It's funny, when the Windows source code was leaked (opened?) in 2004[1], folks soon discovered a vulnerability in the BMP renderer[2].

[1] http://slashdot.org/story/04/02/12/2114228/windows-2000-wind...

[2] http://www.securitytracker.com/id/1009067

Re: Internet Explorer 11: “Don’t call me IE”

#169

Post by kryten »

MichaelGG wrote: post #150
aidos wrote: post #147

Earlier quoted context omitted.

SQL Server has some extra tools, as you've pointed out. You can probably find open source tools equally as powerful (and, by definition, more flexible) to perform those tasks. Granted, you may have to invest some time finding and learning those tools - but really, that's just life. Sometimes it's worth putting in the effort [1]. I've found that the main difference is how you work as a developer. If you're happy using…

SQL Server gives you both. They have a UI for everything, and everything you do has an option to script. So you might go through the whole wizards for replication, then when done, save off a T-SQL script. To my knowledge, there's nothing that requires the UI; it's there just to make things easier. Then on top of that, they expose an API you can use for further automation, if T-SQL isn't to your liking. Your example i…

It's not all roses. Have you ever tried scripting and versioning SSIS for example?

Probably not.

Which is why we use Spring Integration...

Re: Internet Explorer 11: “Don’t call me IE”

#170

Post by kryten »

pjmlp wrote: post #88
sixothree wrote: post #46

Earlier quoted context omitted.

Everything about Windows 8 to me just feels like a kick in the groin from Microsoft. For many years now they've claimed that .Net was the present and future of Microsoft development; yet it seems they've shoved it into the back seat and likely next into the trunk of deprecation.

There was lots of cool .NET stuff to see at BUILD 2013, not sure what you mean.

There was no cool stuff.

They fixed a load of stuff, threw new versions out and spun it as marketing.

It's not cool if you have to pay for it at a rapidly growing pace.

Post reply on HN