Changes between Version 2 and Version 3 of WhyDotNet

Timestamp:

02/25/09 13:26:01 (11 years ago)

Author:

ibboard

Comment:

--

WhyDotNet

@@ -13 +13 @@
  1. Java is a "one language, one VM" system, where as with .Net WarFoundry will be written in C# and other people can write plugins (like the [browser:IBBoard.WarFoundry.Plugin.Rollcall Rollcall plugin]) in [http://www.dotnetpowered.com/languages.aspx any .Net language] they wish.
  1. If you wrote it in Java then you could put it on PDAs if you wrote an alternate interface, since a standard app interface would be too big. Something similar should be possible with .Net as MS has the [http://en.wikipedia.org/wiki/.NET_Compact_Framework .Net Compact Framework] for WinCE PDAs and it's probably possible to install Mono on a PDA (there's mention [http://tirania.org/blog/archive/2005/Sep-20.html here] which seems to imply a standard install works fine).
+
+== Why .Net and not C++? ==
+
+ 1. I don't know C++ and I don't intend to learn it for a hobby project
+ 1. It would force everyone else to know C++ as well
+ 1. Languages with higher levels of abstraction let you concentrate more on the application and less on the memory management and other low-level details
+ 1. The app would need to be built multiple times for different architectures/GUI toolkits
+
+== Why .Net and not Python? ==
+
+While my work with Trac is getting me used to the idea of Python as a usable language (originally it looked too much like Basic) there are a few problems:
+
+ 1. As with C++, I don't know Python and you're forcing everyone who wants to contribute to use Python
+ 1. Python is new to the Windows scene and most people won't know about it, what it is or even have an installed framework. .Net is likely to be installed on a lot of Windows machines though, especially as people move to Vista/Windows 7.