Il programma C Prog quando portato su Java si chiamerebbe JProg, una porta su C ++ sarebbe Prog ++ e una porta su Python si chiamerebbe PyProg. Questi nomi sono tutti abbastanza ovvi. Ma la porta C # si chiamerebbe IronProg, che mi sembra strana.
Perché i programmi portati su Visual Basic o C # vengono spesso chiamati Iron *?
Esempi: IronPython, IronScheme, IronRuby, ecc.
Sono loro? Ho visto principalmente cose con "N" all'inizio, ad es. "NHibernate", "nUnit", "NAnt", "Noda Time", ecc.
C'è un progetto "IronLanguages" che fa IronPython, IronRuby, ecc., ma sembra soprattutto concentrarsi sul porting dei linguaggi di programmazione su CLR.
Ecco un post sul blog che spiega il nome cita il creatore di IronPython progetto:
I'll give you the story, but I'll give you the short version 'cause it's not very good.
At the time, I had a consulting company called "Want of a Nail Software". "Want of a Nail" is based on a children's poem. It's about the importance of small things. I've always kind of believed in the importance of small things. Part of the story of IronPython's actual performance is it wasn't one big thing - Everybody wants to know "What was the one big thing?" There were some big things, but most of it was all the small things - paying attention to performance in every place.
So, that was the consulting company and "Iron" seemed to match.
There were some obvious names: Python.Net, Python#, nPython - All of those were taken. All of the URLs for those were registered.
I didn't want to reuse any of those names, so "Iron" was just kind of a name that appealed to me at a visceral level - I like the feeling of "IronPython".
There's a little bit of "Iron Chef" in it, although I'm always reluctant to admit that.
Leggi altre domande sui tag .net