I told someone on some non-programming boards that I was doing a character generator (creates a character for a role playing game) in .Net primarily for the PC, but I wanted to make sure I keept it platform neutral because I would love to see how it worked on OSX. By platform neutral I mean I used XML for data storage rather than MS Access.
They lamblasted me for being anti-OSX. I was so confused. Then they told me if I really wanted to create something cross platform I'd do it in Java. This confused the hell out of me because for the most part, something done for the PC won't work on OSX. This would.
Then they went off on how none of them had the Mono Framework and I was discriminating against them. Then about how they or their friends would never put Mono on their computers and asked why I was being anti-OSX.
I let them know that despite what they chose to do, it would be available and hopefully would work perfectly on OSX. If they chose not to use it or the technology they didn't have to.
It went around in circles a bit more where I ended up being a totally heartless ***** because it came down to the fact that I wasn't interesting in learning a new programming language for my project (even though I did say if anyone knew Java I would assist their conversion or seperate construction of the Application) and how Mono wasn't an option for OSX.
The funny thing is that these people arn't anti-.Net. They'll talk up the benefits of .Net development like only a PC user could. Odd.
They also kept saying that Mono wasn't production software - though I know companies that use it for business applications and it's past v1.0.
I know it's not 100% of the .Net framework 1.1, but the way I see it, that only matters if you want it to do something that isn't implimented yet. It probobly does every basic function I'd need.
They lamblasted me for being anti-OSX. I was so confused. Then they told me if I really wanted to create something cross platform I'd do it in Java. This confused the hell out of me because for the most part, something done for the PC won't work on OSX. This would.
Then they went off on how none of them had the Mono Framework and I was discriminating against them. Then about how they or their friends would never put Mono on their computers and asked why I was being anti-OSX.
I let them know that despite what they chose to do, it would be available and hopefully would work perfectly on OSX. If they chose not to use it or the technology they didn't have to.
It went around in circles a bit more where I ended up being a totally heartless ***** because it came down to the fact that I wasn't interesting in learning a new programming language for my project (even though I did say if anyone knew Java I would assist their conversion or seperate construction of the Application) and how Mono wasn't an option for OSX.
The funny thing is that these people arn't anti-.Net. They'll talk up the benefits of .Net development like only a PC user could. Odd.
They also kept saying that Mono wasn't production software - though I know companies that use it for business applications and it's past v1.0.
I know it's not 100% of the .Net framework 1.1, but the way I see it, that only matters if you want it to do something that isn't implimented yet. It probobly does every basic function I'd need.
