21–30 of 109 posts
> Not having a debugger is actually a liberating experience because it forces you to code in a different way. Not having a debugger is like living in the stone age. Personally, the the ability to inspect application state at runtime is non-negotiable.
While I agree with some of these points the biggest one for me is client adoption. All clients assume everything is run in Linux. I don't even know why this mindset is so popular. When we develop something and the client wants to host it I can guarantee (more or less) that the platform is Linux and they want to know why the software we have written doesn't work on Linux. I know there is Mono but I always use IIS to r…
Actually most of the Linux guys I know, can only manage a specific distribution.
They aren't even aware how commercial UNIXes work or how POSIX is not as standard as they think it is.
The fact is, that it is just impossible to know everything across multiple systems.
> Not having a debugger is actually a liberating experience because it forces you to code in a different way. Not having a debugger is like living in the stone age. Personally, the the ability to inspect application state at runtime is non-negotiable.
While I agree with some of these points the biggest one for me is client adoption. All clients assume everything is run in Linux. I don't even know why this mindset is so popular. When we develop something and the client wants to host it I can guarantee (more or less) that the platform is Linux and they want to know why the software we have written doesn't work on Linux. I know there is Mono but I always use IIS to r…
> All clients assume everything is run in Linux. I don't even know why this mindset is so popular. Might be on your part of the globe. On my little world, we have enough Windows only clients to keep us busy.
Our clients are normally ones who have come from a small background and are growing quite rapid, this customer is almost certainly on some type of Linux offering.
It's probably a mix of the clients we target and the geographical location.
Some really good criticisms, but I do wonder how long ago this developer left .NET. .NET is now heavily async based. WPF may have started it years ago, but async has been a keyword in the language for quite awhile! (I haven't used a proper lock in ages. Event queues are where it is at! Or pick your favorite paradigm, heck the framework comes with thread pools built in that it'll juggle for you!) In regards to .csproj…
For me, VS is the strongest pull of the .Net platform after C# the language. It doesn't take me long in another IDE/language to sigh and wish for something to work as well as VS.
However, I am one of the few that would never use resharper. There are no refactoring features in the world that make a good trade for laggy typing.
Earlier quoted context omitted.
> All clients assume everything is run in Linux. I don't even know why this mindset is so popular. Might be on your part of the globe. On my little world, we have enough Windows only clients to keep us busy.
We are based in the UK. I don't know if it's the clients and the type of work we are filling but we seem to be migrating a lot of people from Wordpress so typically they expect everything to still run on Linux. Our clients are normally ones who have come from a small background and are growing quite rapid, this customer is almost certainly on some type of Linux offering. It's probably a mix of the clients we target a…
Some really good criticisms, but I do wonder how long ago this developer left .NET. .NET is now heavily async based. WPF may have started it years ago, but async has been a keyword in the language for quite awhile! (I haven't used a proper lock in ages. Event queues are where it is at! Or pick your favorite paradigm, heck the framework comes with thread pools built in that it'll juggle for you!) In regards to .csproj…
I recently had to spend a lot of time with csproj files. They look and behave rather a lot like Ant/Maven. This is not a point in their favor. Ant/Maven was loved and then subsequently hated by a lot of java developers. XML is an extremely verbose syntax to have to deal with. But the real killer is one of lockin. Yes you can use msbuild to do things with them but the syntax is really designed not for a developer to r…
> traditional Windows devs are typically only good at Windows and get lost very quickly outside of their comfort zones, which is not true for Linux devs Strongly disagree. I've watched scores of Linux-only developers try to do things on windows machines, stumble over small things, and then proceed to blame windows instead of realizing they simply lack experience.
Long time user of both nix and Windows here: At least around here it seems anyone can be a Windows dev/admin while becoming a *nix admin often takes some dedication. And to this day the amount of busywork that Windows admins and devs find acceptable still amuses me and not in a good way.
As a counterexample. My Linux servers, when presented with 4 NICs and multiple VLANs, doesn't know what to do with them. I had to edit the iptable. Something that I still haven't needed to do to any of our Windows server.
Different strokes for different folks.
While I agree with some of these points the biggest one for me is client adoption. All clients assume everything is run in Linux. I don't even know why this mindset is so popular. When we develop something and the client wants to host it I can guarantee (more or less) that the platform is Linux and they want to know why the software we have written doesn't work on Linux. I know there is Mono but I always use IIS to r…