Poll extension...
-
It seems only about 15% of us consider .NET Core as platform for development, the question is why? 1. Either no interest in multiplatform 2. Or does not consider .NET Core as a good choice for that Any opinions?
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
-
I am so glad I write in C still. I can remain blissfully ignorant of all this latest must have technology. Imagine the time spent learning COM, all wasted. Java too, gone by the wayside. Good old C, it lasts forever! :)
-
I am so glad I write in C still. I can remain blissfully ignorant of all this latest must have technology. Imagine the time spent learning COM, all wasted. Java too, gone by the wayside. Good old C, it lasts forever! :)
C IS good, indeed... Maybe C++ a bit better... But there are lines of development you can not use them... Not without spitting blood at least...
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
-
I use C++ in MFC for writing test apps and the odd cpl applet, but so much of what I do is process based that C really is the best language.
-
It adds a lot of cruft. Complicates server deployment. Or at least: that is how it feels.
... such stuff as dreams are made on
More complicated. But can be automated... You may be interested in my article about .NET Core (the second one)...
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
-
C IS good, indeed... Maybe C++ a bit better... But there are lines of development you can not use them... Not without spitting blood at least...
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
Of course, fortunately I dont go anywhere near those lines of development! :)
-
Of course, fortunately I dont go anywhere near those lines of development! :)
Lucky you! :laugh:
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
-
It seems only about 15% of us consider .NET Core as platform for development, the question is why? 1. Either no interest in multiplatform 2. Or does not consider .NET Core as a good choice for that Any opinions?
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
3. Does not write .NET apps but uses [insert your favorite language] for cross platform applications For me, it is C++ with cross platform frameworks like Qt and C, C++, and Perl for console applications.
-
3. Does not write .NET apps but uses [insert your favorite language] for cross platform applications For me, it is C++ with cross platform frameworks like Qt and C, C++, and Perl for console applications.
It is actually 2. - you consider your current cross platform solution better (or good enough)...
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
-
Lucky you! :laugh:
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
Benefits of working in the kernel, it hasnt really changed in decades, seriously.
-
More complicated. But can be automated... You may be interested in my article about .NET Core (the second one)...
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
-
It is actually 2. - you consider your current cross platform solution better (or good enough)...
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
I think it would be a good choice if I would write .NET apps (and have not used many methods that are not supported by .NET core).
-
I was thinking in terms of updating .NET itself, when there are dependencies between all the applications and the core. Maybe you cover that too, but I saw no link Köszi :)
... such stuff as dreams are made on
It does not cover .NET Core updates, as I do not consider it as a developer problem. It is about hosting the very same compilation on different platforms... ASP.NET Core: compile once, host everywhere[^]
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
-
I am so glad I write in C still. I can remain blissfully ignorant of all this latest must have technology. Imagine the time spent learning COM, all wasted. Java too, gone by the wayside. Good old C, it lasts forever! :)
[Poem - Write in C](http://www.poppyfields.net/filks/00259.html) :)
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack. --Winston Churchill
-
[Poem - Write in C](http://www.poppyfields.net/filks/00259.html) :)
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack. --Winston Churchill
:)
-
[Poem - Write in C](http://www.poppyfields.net/filks/00259.html) :)
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack. --Winston Churchill
or even better ... with music :-D : [htps://www.youtube.com/watch?v=1S1fISh-pag](https://www.youtube.com/watch?v=1S1fISh-pag)
-
It seems only about 15% of us consider .NET Core as platform for development, the question is why? 1. Either no interest in multiplatform 2. Or does not consider .NET Core as a good choice for that Any opinions?
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
No requirement, a purely windows shop so "everywhere" is .Net :-D
Never underestimate the power of human stupidity RAH
-
It seems only about 15% of us consider .NET Core as platform for development, the question is why? 1. Either no interest in multiplatform 2. Or does not consider .NET Core as a good choice for that Any opinions?
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
I like .NET and I'm excited about .NET Core although I haven't used it for a production app as yet. Having said that, up until recently there was a lot of stuff missing. Given than Java is more mature and has better performance, there's always the question in the back of my mind "why don't I just do this in Java?".. and that's the first hurdle Microsoft is going to have with developers when it comes to cross platform web development. Personally I'll stick with it, but I'll probably need to learn Java as well just to hedge my bets on where future opportunities are going to be.
Now is it bad enough that you let somebody else kick your butts without you trying to do it to each other? Now if we're all talking about the same man, and I think we are... it appears he's got a rather growing collection of our bikes.
-
It seems only about 15% of us consider .NET Core as platform for development, the question is why? 1. Either no interest in multiplatform 2. Or does not consider .NET Core as a good choice for that Any opinions?
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
Well, there's 2 issues at play here. First, Java already does that, so most people that had a vested interest in cross-platform applications are most likely already following that route. Secondly, MS hasn't helped the situation by failing to wrap the .NET world under a coherent umbrella. They just tack a new word onto it, pass it to a team, and let them do whatever they feel like. The division between .NET Standard and .NET Framework is a great example of this: there is no reason whatsoever that all modern .NET isn't .NET Standard, except different teams have their fingers in the pie.
"There are three kinds of lies: lies, damned lies and statistics." - Benjamin Disraeli
-
Well, there's 2 issues at play here. First, Java already does that, so most people that had a vested interest in cross-platform applications are most likely already following that route. Secondly, MS hasn't helped the situation by failing to wrap the .NET world under a coherent umbrella. They just tack a new word onto it, pass it to a team, and let them do whatever they feel like. The division between .NET Standard and .NET Framework is a great example of this: there is no reason whatsoever that all modern .NET isn't .NET Standard, except different teams have their fingers in the pie.
"There are three kinds of lies: lies, damned lies and statistics." - Benjamin Disraeli
True .NET is late to the party, but all latest (and alive) .NET versions implements .NET Standard 2.0 (the latest too)... so there is an improvement there...
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
