× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



My only problem with .Net (apart from its fan-boys) was that it was Windows specific and I did not see any point for people who were considering moving away from the "proprietary" IBM i platform to move to yet another "proprietary" system.

.Net Core is a different matter - but other than as a porting target it is hard to imagine that it will gain an enormous amount of headway. Considering that you need Javascript knowledge no matter what language you choose, node.js is a pretty compelling choice for many - although I confess I dontt like it much for what I've seen so far.

Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Jan 10, 2018, at 7:07 PM, John Yeung <gallium.arsenide@xxxxxxxxx> wrote:

On Wed, Jan 10, 2018 at 4:11 PM, Jon Paris <jon.paris@xxxxxxxxxxxxxx> wrote:
Seriously though - you can't be the only .Net fan out there so why isn't it being done?
Surely it doesn't need IBM to do it just as Python didn't originally. IBM was late to
the game with that.

From a technical standpoint, I suspect .NET Core is a bigger effort to
port than Python. And .NET Core is pretty new. Sure, .NET isn't new,
but .NET Core is a major refactoring of the original .NET, which was
highly Windows-specific. In contrast, Python is just one language, is
a relatively small language at that, and its reference implementation
has always been POSIX-centric (and specifically designed to be simple
to understand and maintain, rather than optimized for any particular
underlying platform).

I feel there are probably cultural issues at play as well. Python was
designed to be multiplatform, and has been roughly as successful as
Java in terms of meeting the write-once-run-anywhere ideal. It has
also seemed to attract a fair number of fanatical followers from
pretty early on, well before becoming mainstream. Meanwhile, Microsoft
has only recently begun to embrace other platforms (even later than
IBM). The whole concept of .NET on non-Windows is pretty foreign to a
lot of people, both fans and detractors of .NET alike. Even if someone
were to really, really love .NET the way the staunchest Python fans
love Python, they are most likely thinking "great, now I have the best
tools in the world to develop on Windows!"; not "how do I bring these
awesome tools to other platforms?".

As one measure of the level of fanaticism we're talking about: The
third-party Python port was to QSYS.LIB. With ILE C. (I don't know
exactly how far back ILE goes; maybe the original iSeriesPython even
used non-ILE C?) This is a noticeably greater undertaking than porting
to PASE. Yet it was done by one dedicated individual.

But I absolutely agree with you that (1) IBM was late with its Python
and (2) there is enough interest and enough value in the .NET Core
proposition that it *ought* to be ported to PASE, whether that's by
IBM or by some interested third party.

John Y.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.