111–120 of 215 posts
I frankly:
1) don't know what that is, and
2) can't even imagine what it could consist of other than a few lines of code exercising System.Net.Sockets.
Seems to me its more on the people who solve hard problems than on the current crop of .NET developers - if you are writing a complex game/MMO, AI system or what have you, and you choose to do so in Java, C++ or similar when C# might be the better option, the faults on you not the .NET community. If the whole pool of developers world wide was considered as a big pie, and a certain section of that do these 'hard probl…
https://gamedev.stackexchange.com/questions/10247/mmos-based...
I think it is important to realize that the .NET OSS ecosystem is not something that has been around for a long time. In the F# community, it truly started working as an "OSS ecosystem" only a couple of years ago - and the rest of .NET is following - and I'd say it is only starting to really exist now. Although .NET has been around for ages, people are only learning what OSS means and I think the F# community is lead…
The licenses for their operating systems have always acted to make farms of Windows machines rare. Until fairly recently, the administration approach made it painful. Microsoft had good support for client-server systems, but you did it their way, which wasn't "reactive".
Here's a quick question: Anyone know of any networking/distributed system developments that came out of a Microsoft environment?
I've been really trying to go FOSS (or even OSS) with .NET. But the community does not seem to be very open to it. They do upvote, star or otherwise applaud the effor. Yet nobody uses it. Or even makes the effort to try. My experience with the Python community is quite different. People not only accept the work provided, they actually try and use it and give feedback. It feels good to get a pull request improving som…
We've been a Microsoft shop from the start and it's obvious.
I'm reaching for a word that means "an example which is almost exactly the opposite of the concept it's used to illustrate" -- incongruous?
His main argument seems to center around a "reactive socket server middleware" being absent in the .NET ecosystem. I frankly: 1) don't know what that is, and 2) can't even imagine what it could consist of other than a few lines of code exercising System.Net.Sockets.
Re: the Akka.Net stuff, there is indeed an implementation of an Actor model framework - Orleans. Now it was developed in house at Microsoft and hasn't gotten a lot of attention from developers other than Microsoft employees, but it's there. https://github.com/dotnet/orleans
Re: the Akka.Net stuff, there is indeed an implementation of an Actor model framework - Orleans. Now it was developed in house at Microsoft and hasn't gotten a lot of attention from developers other than Microsoft employees, but it's there. https://github.com/dotnet/orleans
https://github.com/akka/akka-meta/blob/master/ComparisonWith...
I think it is important to realize that the .NET OSS ecosystem is not something that has been around for a long time. In the F# community, it truly started working as an "OSS ecosystem" only a couple of years ago - and the rest of .NET is following - and I'd say it is only starting to really exist now. Although .NET has been around for ages, people are only learning what OSS means and I think the F# community is lead…
The article accused people using .NET of not choosing to work on hard problems. I suspect that's it's the other way around. People working on hard problems have chosen other tools that they felt were more appropriate or effective at the time.
For example, if people doing hard things felt that a Linux hosting environment was most suitable for their solving hard problem, that basically ruled out .NET. Once .NET applications can be safely, reliably run on Linux, the case for using .NET becomes much stronger.