Live data from Hacker News

Announcing .NET Core 1.0

blogs.msdn.microsoft.com

291–300 of 327 posts

Re: Announcing .NET Core 1.0

#291
post #267

Earlier quoted context omitted.

For me the issue comes down to whether or not Microsoft does anything useful with this data (probably not, if 20 years of NVIDIA blue screen driver failure logs, Windows 8 and OneDrive are any example of how 'big data' impacts Microsoft product quality) versus how many comments I have to read where joeblow52 is personally offended that Microsoft dares to learn what his compile time plus 999,999 other compile times, d…

How, exactly, are you thinking that Microsoft is going to fix nVidia's buggy drivers? They can collect all the data they want, but at the end of the day, it's nVidia's driver.

I worked there. Ways we solved these sorts of problems include: hardening the other side of the API/HAL when appropriate/possible, simplifying the driver model so that mere mortals could write drivers, writing our own drivers and overwriting known buggy ones for companies that couldn't get their shit together (usually network vendors), adding workarounds to the OS not to use certain features of certain cards, flying external engineers to lavish parties and our driver development labs and compatibility labs and providing one on one engineering development assistance from senior kernel developers, providing free testing of drivers for known problems before release, rolling fixed drivers into Windows updates, providing marketing funds as reward for fixing problems, and not using NVIDIA in the Xbox 360 after using them in the original Xbox as punishment because they were personally responsible for over 80% of blue screens in Windows for the preceding five years.

Sadly the motivation was often to ignore the data or watch it get spun by some jackass with the exact wrong agenda. It's just software, there's always a way to fix things if you really want to.

Re: Announcing .NET Core 1.0

#293
post #171
post #28

I'd LOVE to see some Linux web/micro benchmarks... particularly against Java, Go, Node, Python.

fwiw against Java -- http://benchmarksgame.alioth.debian.org/u64q/compare.php?lan... against Node.js -- http://benchmarksgame.alioth.debian.org/u64q/compare.php?lan... against Python -- http://benchmarksgame.alioth.debian.org/u64q/compare.php?lan...

I find the binary-tree benchmark specially disturbing, it looks like the .NET Core GC/escape-analysis has some catching up to do.

Re: Announcing .NET Core 1.0

#294

Earlier quoted context omitted.

The naming is really confusing, but then naming things is hard. As Phil Karlton famously said: There are only two hard things in Computer Science: cache invalidation and naming things.

I don't know where it came from, but I've always preferred this variant: There are only two hard things in Computer Science: cache invalidation, naming things, and off-by-1 errors.

I actually used that version in my recent book. You can see it in this section [0] of the first chapter (which is free to read, with no sign-up) that tries to explain the confusing naming.

[0] https://www.packtpub.com/packtlib/book/Application%20Develop...

Re: Announcing .NET Core 1.0

#295

I am interested in hosting a .NET web app on linux, so I read the docs: https://docs.asp.net/en/latest/publishing/linuxproduction.ht... Is there any advantage to running a reverse proxy (nginx) if you already have Cloudfront in front of your cluster, doing the https & gzip work? And, if your web app serves literally 0 static content?

>And, if your web app serves literally 0 static content? Even real time dashboards have some cacheable content. I would still want to use something like Varnish/NGINX in between.

Mobile backend, every call hits the db

Re: Announcing .NET Core 1.0

#296
post #239

Earlier quoted context omitted.

I simply don't want to be tracked in any form regardless of whether it collects my personal data. Yet it seems more and more impossible these days. It's like "If there's nothing about collecting your personal data, then you should compromise".

A router has to track you to know where to send the info you've requested.

Well, it does track, but it doesn't necessarily collect the data and use it to profiling users. I just don't like to be experimented like a little white mouse in a mouse lab, regardless of whether it's for good or bad.

Re: Announcing .NET Core 1.0

#297

Earlier quoted context omitted.

I simply don't want to be tracked in any form regardless of whether it collects my personal data. Yet it seems more and more impossible these days. It's like "If there's nothing about collecting your personal data, then you should compromise".

Sorry to tell you this 4684499, but this website and most every other website on the internet knows how many page views they have and the IP addresses that are used to get to their website, etc. ...all because they have telemetry on the server. It's how they tell if something is working or not working. Not all telemetry is bad.

At least it should be an opt-in, not opt-out.

Re: Announcing .NET Core 1.0

#298
post #289
post #228

Earlier quoted context omitted.

[Ctrl][Up] works in Vista onwards to move up a folder. It's worth knowing.

does this, since XP I think - ^↑ doesn't seem to work for me in Win 10.

Backspace is "back" not "up a folder level" as far as I am aware. This is consistent with web browsers - and indeed the conceptual meaning of "backspace" (go back 1)

Re: Announcing .NET Core 1.0

#299

Earlier quoted context omitted.

Personally, I prefer writing SQL by hand. That way I know exactly what will happen in a query. A database really is an important component of a system and shouldn't be treated like a dumb data store where you just throw in any stuff you like through an ORM and hope it sticks there somehow.

False dichotomy, you can use both together and get the benefits of both an ORM and raw sql, each when they're the better choice.

[deleted]

Re: Announcing .NET Core 1.0

#300

Earlier quoted context omitted.

Personally, I prefer writing SQL by hand. That way I know exactly what will happen in a query. A database really is an important component of a system and shouldn't be treated like a dumb data store where you just throw in any stuff you like through an ORM and hope it sticks there somehow.

False dichotomy, you can use both together and get the benefits of both an ORM and raw sql, each when they're the better choice.

Certainly. Yet there's been a tendency later to declare SQL wrong and deprecated and to incite everyone to forget about it and go with an ORM as the only way. I do not accept that. The stronger the ORM zealots are pushing the more repulsive the idea of an ORM becomes to me. But of course it's just another instrument that has its place among the others.
Post reply on HN