-
Notifications
You must be signed in to change notification settings - Fork 55
Question - running on the .net core #7
Comments
Microsoft Research closed the lab that produced this work last September. The team members are now mostly at Google, and (I think) probably not in a position to develop or support Microsoft projects. When we left, both Dryad and Naiad ran just fine on Yarn clusters and worked just fine with HDFS. If you have more questions, I recommend getting in touch with someone at Microsoft. I suspect Mark Staveley could give you a definitive thumbs up / thumbs down signal. But, good to hear that you like what the lab did. |
Well since then things have moved on. I am developing 100% of the stack in Its going very well. Go can run on android and ios now. On the server side J
|
In case anyone else is interested in returning to the codebase: as Frank says, things run pretty smoothly today on YARN, but only on Windows. The problem running on Linux is that Dryad and the YARN interop layer both include managed C++. I have not been following closely, but it used to be difficult to get managed C++ to work on Linux without some porting effort, and nobody to my knowledge has tried to do that. I don’t think Mark Staveley is in a role to support this stuff any more, and I don’t know of anyone else at Microsoft who has picked it up. Someone could always fork the code… From: joeblew99 [mailto:[email protected]] Well since then things have moved on. I am developing 100% of the stack in Its going very well. Go can run on android and ios now. On the server side J
— |
Now that .net core runs on Linux and plinq is included, that means that dryad could be effectively used on a massive compute cluster.
Seems like a very nice opportunity. Can anyone of the tram comment on this ?
https://github.com/dotnet/corefx
The text was updated successfully, but these errors were encountered: