11 ms·
Can't blame someone who tries something else instead of .net. Going back to my current legacy .net project that i hate. Except there's no way I can stealth por
by nottorp 5y ago
Can't blame someone who tries something else instead of .net.
Going back to my current legacy .net project that i hate. Except there's no way I can stealth port it to rust or anything else so i'll just try to get the changes over with.
- DeathArrow 5y agoLegacy .NET is crap. New .NET is pretty nice on the other hand.
- nottorp 5y agoI believe mine was started in VB pre .net :)
- jaywalk 5y agoOh. Oh no. I hope you've at least had exposure to recent, proper .NET code. Don't judge the platform based on that project.
- whizzter 5y agoWhile old VB was fun for whacking together things it's not really stuff one would want to maintain in the long haul. Right now I'm sometimes spending time maintaining something for a DCOM based semi-monstrosity and that does suck even if I've managed to clean out some old warts, luckily I'm also doing some more modern .NET stuff and that isn't too bad at all actually.
- darkmatterrat 5y agoHowever the people building stuff in new .NET are the same people building stuff in old .NET for the most part and you get all the same wonkyness just in .NET core.
- fmajid 5y agoI stopped reading when the author wrote with a straight face that .NET would help with their migration to Linux. That said, new technology proof of concepts should always be done on non-critical systems first, and certainly not sprung as surprises.
- littlecranky67 5y agoCan you ellaborate? .NET runs on Linux very well just a couple of years MS officially supported it, and if you have a decade worth of .NET code in your company, porting it to .NET 5 might be orders of magnitude easier than to rewrite into something else.