@Sander_Boer wrote:
Hi,
This is a question for the core developers. I had a talk with steve baer a couple of years ago and I remember him being enthousiastic about rhinocommon in particular and dotnet in general.
I took this as futureproofing rhino, a multiplatform future. Osx was on the rise and work was being done to get rhino mac ready.Now a couple of years later I think it is safe to say that rhino mac has been a struggle and it feels like developing with dotnet has not helped in that regard. Like, at all.
Now, I regularly have dicussions with microsoft fanbois about dotnet and I do a fair bit of c# myself in grasshopper and unity. I can see the appeal of more readable code, but fundamentally al the friction points are still there, f.i. include hell and build spaghetti to name but two. Especially building and linking is very opaque now.
The reason I bring this up is because dotnet feels more and more of a lock-in and I worry about the path microsoft is taking, windows 10S being the latest shenanigan.
My question to the devs is this: did dotnet pay off ? I don't mean did it work, but is developing with dotnet a path into the future? Or should one take serious steps in being multiplatform like f.i. blender has done ? I bring this up bc when I develop an app I notice a great demand for multiple platforms. Mac and win being a main concern, but mobile and web coming in as close seconds. I have used lightweight libs like oryol and raylib with great ease, a pleasure compared to f.i. qt.
So, again, dotnet/rhinocommon: "OMGbestDecisionEVErrr! Msvc 4eva!" or "meh, seemed like a good idea at the time" ?
Thx.
Sander
Posts: 1
Participants: 1