Permalink
Browse files

Update README.rst

  • Loading branch information...
1 parent 7903732 commit 8a795c4b4457b5f15bd2cb328c961e4b143bb7d6 Ed Ceaser committed Jan 30, 2012
Showing with 3 additions and 8 deletions.
  1. +3 −8 README.rst
View
@@ -131,14 +131,9 @@ The client has full readline support, including command history and tab completi
Why not Procon?
---------------
-* Procon is not easy to run crossplatform. It currently relies on having the .NET CLR installed in some form. Most
-non-Windows servers do not have a CLR environment unless they install Mono, which is not a common package on most
-server OS distributions.
-* Procon is not very lightweight or componentized. It is both a layer server as well as a GUI that includes features
-such as a map viewer, plugin downloader, etc. I think a more modular architecture where the server is a headless,
-daemonizable process with no UI provides for a more flexible and easier to manage system.
-* Easier Plugin / Module API. Procon handles plugins by using a very strange C# runtime compilation stage, which makes
-writing and testing plugins very difficult.
+* Procon is not easy to run crossplatform. It currently relies on having the .NET CLR installed in some form. Most non-Windows servers do not have a CLR environment unless they install Mono, which is not a common package on most server OS distributions.
+* Procon is not very lightweight or componentized. It is both a layer server as well as a GUI that includes features such as a map viewer, plugin downloader, etc. I think a more modular architecture where the server is a headless, daemonizable process with no UI provides for a more flexible and easier to manage system.
+* Easier Plugin / Module API. Procon handles plugins by using a very strange C# runtime compilation stage, which makes writing and testing plugins very difficult.
General Roadmap
-------

0 comments on commit 8a795c4

Please sign in to comment.