5 ms·

Yes, I'm glad of it too. I no longer need Windows to develop nor host, while keeping on a platform which is hard to beat (for my requirements). This isn't cha

Yes, I'm glad of it too. I no longer need Windows to develop nor host, while keeping on a platform which is hard to beat (for my requirements). This isn't change for the sake of it, it's to keep .NET relevant. VS and Windows have become pain points.

copperx 8y ago
What kind of requirements fit .NET best? I'm trying to decide between .NET and Rails 4 for a new project.
- jenscow 8y ago
  I chose core over node, because it has a better standard library with less 3rd party reliance. On my last project, dealing with the multiple layers of dependencies with node became troublesome. (static vs dynamic has equal balance, in my experience) However, if it where not for Linux support (and Rider), I would have gone with node.
- oblio 8y ago
  REST API + frontend framework => .NET
  - abledon 8y ago
    Greater than or equals..... ?
    - jbigelow76 8y ago
      How soon we forget. That is obviously a CoffeeScript fat arrow function, after you're done adding the Rest API to the front end you callback to the .NET framework to execute it.
      - sk5t 8y ago
        Looks like a Scala type alias to me.
- int_19h 8y ago
  Start by asking yourself whether you like static typing.
dgritsko 8y ago
VS is a pain point? It remains one of the best IDEs out there IMO. What are your specific issues with it, aside from needing to run it on Windows?
- horsawlarway 8y ago
  I think VS is painful. It's slow to open. It crashes frequently. It's hard to extend. It's absolutely AWFUL on system resources. Its settings are a complete clusterfuck (admittedly, mainly because it tries to be/do absolutely everything). I also think VS is actually a bad teaching tool for new developers. It simply tries to hand-wave/magic away parts of the system you're working on that REALLY matter. It's like VS is stuck in the era where the idea of opening a configuration file in a text editor is "uncouth". Which is frankly insane, since navigating the frustrating and byzantine guis it throws up instead is an absolute nightmare. Worse, you really need to care about those config files and settings, having them hidden helps nobody. Basically, I think VS Code is a better IDE (yes, IDE, not editor) in every way. It takes more work to get off the ground, but it's literally miles away a better experience.
  - tluyben2 8y ago
    I have no clue why VS is so bad. You would hope that as a commercial and primary development tool for a company as large as MS, they would be able to make it stable and fast. It's horrible. But so is XCode... I guess both try to cram in too much features and developers will (have to in many cases) use it anyway.
  - nightski 8y ago
    Then use VS Code? But as a .NET developer of over 15 years now I disagree. VS Code is currently using 1,200 MB of ram on my machine while Visual Studio is using 1,700 MB. I have a much larger project open in visual studio. Out of the 64 GB of ram on my machine, this isn't even a factor. What kind of machines are you running on where this is actually a problem?
    - acct1771 8y ago

copperx 8y ago

What kind of requirements fit .NET best? I'm trying to decide between .NET and Rails 4 for a new project.

jenscow 8y ago
I chose core over node, because it has a better standard library with less 3rd party reliance. On my last project, dealing with the multiple layers of dependencies with node became troublesome. (static vs dynamic has equal balance, in my experience) However, if it where not for Linux support (and Rider), I would have gone with node.
oblio 8y ago
REST API + frontend framework => .NET
- abledon 8y ago
  Greater than or equals..... ?
  - jbigelow76 8y ago
    How soon we forget. That is obviously a CoffeeScript fat arrow function, after you're done adding the Rest API to the front end you callback to the .NET framework to execute it.
    - sk5t 8y ago
      Looks like a Scala type alias to me.
int_19h 8y ago
Start by asking yourself whether you like static typing.

dgritsko 8y ago

VS is a pain point? It remains one of the best IDEs out there IMO. What are your specific issues with it, aside from needing to run it on Windows?

horsawlarway 8y ago
I think VS is painful. It's slow to open. It crashes frequently. It's hard to extend. It's absolutely AWFUL on system resources. Its settings are a complete clusterfuck (admittedly, mainly because it tries to be/do absolutely everything). I also think VS is actually a bad teaching tool for new developers. It simply tries to hand-wave/magic away parts of the system you're working on that REALLY matter. It's like VS is stuck in the era where the idea of opening a configuration file in a text editor is "uncouth". Which is frankly insane, since navigating the frustrating and byzantine guis it throws up instead is an absolute nightmare. Worse, you really need to care about those config files and settings, having them hidden helps nobody. Basically, I think VS Code is a better IDE (yes, IDE, not editor) in every way. It takes more work to get off the ground, but it's literally miles away a better experience.
- tluyben2 8y ago
  I have no clue why VS is so bad. You would hope that as a commercial and primary development tool for a company as large as MS, they would be able to make it stable and fast. It's horrible. But so is XCode... I guess both try to cram in too much features and developers will (have to in many cases) use it anyway.
- nightski 8y ago
  Then use VS Code? But as a .NET developer of over 15 years now I disagree. VS Code is currently using 1,200 MB of ram on my machine while Visual Studio is using 1,700 MB. I have a much larger project open in visual studio. Out of the 64 GB of ram on my machine, this isn't even a factor. What kind of machines are you running on where this is actually a problem?
  - acct1771 8y ago