Live data from Hacker News

CoreCLR is now open source

blogs.msdn.com

41–50 of 347 posts

Re: CoreCLR is now open source

#41
post #32
post #13

Earlier quoted context omitted.

I wish. One of the projects I am currently working on, a greenfield application, requires WindowsForms for reasons I cannot expose here.

Doesn't sound very greenfield if you're already forced to use an aging legacy technology.

The application is greenfield, the environment where it needs to run, not.

Re: CoreCLR is now open source

#42
post #14
post #11

Earlier quoted context omitted.

From their GetHashCode(): // We want to ensure we can change our hash function daily. // This is perfectly fine as long as you don't persist the // value from GetHashCode to disk or count on String A // hashing before string B. Those are bugs in your code. hash1 ^= ThisAssembly.DailyBuildNumber; I'd love to hear the story behind this one :D

I don't know the story, but the logic behind it is simple: If you want to guarantee no one depends on GetHashCode staying static between runs of an application, change it all the time.

Also is it not for hash collision protection, which can end up hurting the runtime of many algorithms, causing a DoS?

Re: CoreCLR is now open source

#43
post #3

Next step, WinForms

I think it would be more interesting and useful to have the source for WPF, given that WPF is an actual GUI toolkit implementing its own widgets, whereas WinForms is basically just a wrapper around Win32.

And WPF seems pretty slick. I've only used it as a developer who has little UI skill, but it seemed to be far better than other UI kits. The design seemed rather coherent. Too bad performance and rendering issues hurt it for the first half decade of its life.

Re: CoreCLR is now open source

#44
post #25

I am really interested to see what happens once ASP.Net is running on Linux. C# and Visual Studio are fantastic, mature tools and I think a lot of developers would enjoy using them whereas they might be hesitant at the moment due to OS lock-in on the code they are writing.

Could/Does Visual Studio run in Linux?

I'm not sure they will migrate Visual Studio. First they'd need to move WPF, which is implemented in DirectX. Second, Visual Studio and MSDN are still profitable. Third, there's the Omnisharp project that;s working on providing support for the more common IDEs on linux. In fact, there's nothing stopping people from making Eclipse and IntelliJ plugins.

Re: CoreCLR is now open source

#45
post #8

Interesting commit: https://github.com/dotnet/coreclr/commit/90ef39bc3c9886e7967... "This change fixes a potential problem in unwinding on Linux"

From the article:

Today, .NET Core builds and runs on Windows. We will be adding Linux and Mac implementations of platform-specific components over the next few months. We already have some Linux-specific code in .NET Core, but we’re really just getting started on our ports. We wanted to open up the code first, so that we could all enjoy the cross-platform journey from the outset.

Re: CoreCLR is now open source

#46

I am really interested to see what happens once ASP.Net is running on Linux. C# and Visual Studio are fantastic, mature tools and I think a lot of developers would enjoy using them whereas they might be hesitant at the moment due to OS lock-in on the code they are writing.

ASP.NET already runs on .NET with Mono, but not always the latest versions of things. Having it all open source could bridge that compatibility gap and let us fully enjoy the ecosystem, instead of having to be careful with taking dependencies all over.

Re: CoreCLR is now open source

#47
post #13

Earlier quoted context omitted.

I wish. One of the projects I am currently working on, a greenfield application, requires WindowsForms for reasons I cannot expose here.

WinForms is a pretty great UI toolkit. It's easy to use, fast, and requires very little system resources.

This. It might appear a bit clunky at first sight, and it might not provide the shiniest eye candy out of the box but in terms of development velocity to get something practical done - provided it is combined with the tooling in Visual Studio - it's really nice.

Re: CoreCLR is now open source

#48
I would be curious to see the effects of completely open-sourcing Windows. Businesses would continue to use it, because it's Microsoft and they want enterprise support. I think it would get even more love than it already does from the development community. Piracy of Windows is already rampant, so they're not really in a worse position from that (plus I think that most people who can pay for Windows do so already). Foreign governments who are concerned about NSA backdoors would have their fears allayed. Is there any way it could seriously damage their business model?

Re: CoreCLR is now open source

#49
post #11
post #7

Quick link to what I think is the most interesting class in the CLR: https://github.com/dotnet/coreclr/blob/master/src/mscorlib/s...

From their GetHashCode(): // We want to ensure we can change our hash function daily. // This is perfectly fine as long as you don't persist the // value from GetHashCode to disk or count on String A // hashing before string B. Those are bugs in your code. hash1 ^= ThisAssembly.DailyBuildNumber; I'd love to hear the story behind this one :D

IIRC, a few yeas ago appeared a denial of service attack, probably originally for Phyton, but it was ported son to other languages.

The idea is that the hash is good enough for normal list, but it's not a cryptographic hash and it's easy to find collisions. Then you can make a lot of requests with strings that has the same hash value. Now the hash operations are O(N) instead of O(~1) and everything is slower.

Using an unpredictable hash calculation makes this attack more difficult.

Re: CoreCLR is now open source

#50
post #13

Earlier quoted context omitted.

I wish. One of the projects I am currently working on, a greenfield application, requires WindowsForms for reasons I cannot expose here.

WinForms is a pretty great UI toolkit. It's easy to use, fast, and requires very little system resources.

Yes it is quite nice, but WPF/XAML is better.
Post reply on HN