4 ms·

As a developer there's been so many times that I've gotten tired of MS solutions, and get excited about new emerging platforms elsewhere. Then I smirk when MS i

by Pigo 10y ago

As a developer there's been so many times that I've gotten tired of MS solutions, and get excited about new emerging platforms elsewhere. Then I smirk when MS incorporates that new platform's ideology. Then I'm pleasantly surprised when it turns out to be cool, and often surpassing the original. I've heard some devs claim they cherry pick from other people's work, and others that they work hard to remain progressive and relevant. I don't know if .NET Core will catch up with Node, probably not, but I respect their effort and believe competition drives the best products and technology.

cptskippy 10y ago
> I don't know if .NET Core will catch up with Node, probably not, but I respect their effort and believe competition drives the best products and technology. Comments like these always remind me of the vast the software development landscape is and how each stack is sheltered into it's own little cloister. People live and breath their stack and everything is framed against or in comparison to it.
deleted 10y ago
[deleted]
blakeyrat 10y ago
I have different priorities than you. In terms of IDE quality, debugger quality, flexibility (ability to use actual threads if you want them!), performance... in my opinion .NET Core is already so far ahead of Node.JS it's embarrassing for them. The only thing I might stack in Node.JS' favor is their NPM package manager. Maybe. Possibly.
- tigershark 10y ago
  Are you seriously saying that NuGet/paket are worse than a flawed package manager that even managed to cause a JavaScript global outage when a padding package was retired? What are your problems with NuGet and paket?
  - blakeyrat 10y ago
    Re-read my post.
  - Pigo 10y ago
    Nuget dependency management is a nightmare for my team. Mostly because there's usually only one package for a given problem, and you're always at their mercy. I suppose it's a community issue, because npm packages I seem to find few complications. Also, I always find plenty of documentation/tutorials/friendly community to help with the package, and never anyone expecting money for a out-of-date pdf generator that works with tooth-picks and bubble gum holding it together (for example). The manager in VS has gotten better, but it's still far more cumbersome than a cli.
manigandham 10y ago
> I don't know if .NET Core will catch up with Node, probably not What exactly does it need to catch up to? C#/.NET already vastly exceed anything in Node in performance, features and flexibility.
- Pigo 10y ago
  Well, for starters, a couple learning tutorials/examples that actually work for most people who try it out.
  - manigandham 10y ago
    It really seems like you're reaching if that's the complaint you have. .NET is one of the most documented platforms around. MSDN documentation covers everything[1] at a deep technical level and the official .NET docs[2] are full of tutorials and guides as well as in-depth detail. The asp.net site contains even more specific and use-case based walkthroughs with plenty of other blogs, forums, and even free video tutorials and online interactive courses. [3] 1. https://msdn.microsoft.com/library https://msdn.microsoft.com/library 2. https://docs.microsoft.com/en-us/ https://docs.microsoft.com/en-us/ 3. https://www.asp.net/learn https://www.asp.net/learn

by Pigo 10y ago

cptskippy 10y ago

> I don't know if .NET Core will catch up with Node, probably not, but I respect their effort and believe competition drives the best products and technology. Comments like these always remind me of the vast the software development landscape is and how each stack is sheltered into it's own little cloister. People live and breath their stack and everything is framed against or in comparison to it.

deleted 10y ago

[deleted]

blakeyrat 10y ago

I have different priorities than you. In terms of IDE quality, debugger quality, flexibility (ability to use actual threads if you want them!), performance... in my opinion .NET Core is already so far ahead of Node.JS it's embarrassing for them. The only thing I might stack in Node.JS' favor is their NPM package manager. Maybe. Possibly.

tigershark 10y ago
Are you seriously saying that NuGet/paket are worse than a flawed package manager that even managed to cause a JavaScript global outage when a padding package was retired? What are your problems with NuGet and paket?
- blakeyrat 10y ago
  Re-read my post.
- Pigo 10y ago
  Nuget dependency management is a nightmare for my team. Mostly because there's usually only one package for a given problem, and you're always at their mercy. I suppose it's a community issue, because npm packages I seem to find few complications. Also, I always find plenty of documentation/tutorials/friendly community to help with the package, and never anyone expecting money for a out-of-date pdf generator that works with tooth-picks and bubble gum holding it together (for example). The manager in VS has gotten better, but it's still far more cumbersome than a cli.

manigandham 10y ago

> I don't know if .NET Core will catch up with Node, probably not What exactly does it need to catch up to? C#/.NET already vastly exceed anything in Node in performance, features and flexibility.

Pigo 10y ago
Well, for starters, a couple learning tutorials/examples that actually work for most people who try it out.
- manigandham 10y ago
  It really seems like you're reaching if that's the complaint you have. .NET is one of the most documented platforms around. MSDN documentation covers everything[1] at a deep technical level and the official .NET docs[2] are full of tutorials and guides as well as in-depth detail. The asp.net site contains even more specific and use-case based walkthroughs with plenty of other blogs, forums, and even free video tutorials and online interactive courses. [3] 1. https://msdn.microsoft.com/library https://msdn.microsoft.com/library 2. https://docs.microsoft.com/en-us/ https://docs.microsoft.com/en-us/ 3. https://www.asp.net/learn https://www.asp.net/learn