I'm leaning more and more towards making a "wait-and-see" recommendation about node to our shop. This isn't so much about node per se. It's more about: (a) the circumstances in the shop where I work, and (b) Microsoft making ASP.NET 5 open source and multi-platform.

Learning that ASP.NET 5 has become open source and multi-platform changes my perspective entirely. My shop already has a lot of experienced .NET developers, and we already use .NET for all of our web and mobile development. My shop could probably afford to wait a year or two and see if ASP.NET 5 gets ported to the IBM i. If ASP.NET 5 does get ported to PASE, then it would make so much more sense for my shop to use ASP.NET 5 rather than node. If ASP.NET 5 doesn't get ported to PASE, we could still use .NET running in IIS and the .NET Provider to do all of our web and mobile development. It wouldn't be the same path we're already on today.

Maybe in a year or two, we would be able to compare a slightly more mature node against a slightly more mature open source ASP.NET 5 and make a decision that's better for us than we can make today.

Kelly Cookson
IT Project Leader
Dot Foods, Inc.
1.217.773.4486 ext. 12676
kcookson@xxxxxxxxxxxx


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.