Saturday, December 26, 2009
Sunday, December 13, 2009
- Works on x86, x86_64, PowerPC, ARM, SPARC, and other platforms seamlessly and without modification to source code.
- Rather complete and mostly platform independent. The runtime itself can run on Windows, Mac OS X, Solaris, Linux, and FreeBSD. Mono is extremely portable.
- Supports multiple programming languages. Mono nominally supports C#, VB.net, and Java. It can suppport Ruby, Python, PHP, etc.
- Code from multiple languages can be mixed together.
- Can be compiled ahead of time or JIT-ed depending on your needs.
- Lets ASP.net web applications run on Linux servers rather than require Windows.
- Licensed for usage with open source and proprietary applications. The core of Mono is under LGPL and most of the libraries I believe are MIT X11 licensed. There are also several libraries and toolkits licensed under the MS-PL, which is very similar to licenses like the Three-Clause BSD license.
- Rather large. The Mono runtime uses a lot of disk space, I think somewhere around 400MB?
- Uses a bit more memory than conventional optimized C/C++ programs. Note the optimized bit. If the application isn't written very well, then Mono actually uses slightly less!
- Does not integrate well into the application binary execution mechanism on any platform. This could be improved in a number of ways, but in order to remain compatible with .NET Framework, I don't think this will happen for quite some time.
- Winforms is ugly on EVERY platform. This is the unfortunate consequence of trying to make Winforms work on any platform that Mono can run on. I think its supposed to support using Windows visual styles when run under Windows, but that doesn't happen.
- GTK# doesn't quite play nice yet on Mac OS X. I can forgive this because GTK+ (which is what GTK# binds to Mono) only very recently stopped requiring X11 to work on OS X, it will take time for it to be adapted to work well under Mac OS X. Be assured that they are working on it though.
Tuesday, May 26, 2009
- The actual ratio of downloads to sales is fairly good (60:1)
- Linux and Mac downloads are on equal footing, while Windows is three times higher
- Ubuntu accounted for a majority (75%) of Linux downloads, distro neutral package accounted for 10% of Linux downloads
- Bryan is bummed about the results and conclusions
Sunday, May 17, 2009
- A new theme is set for default: Enanium
- A new extra method of security is added to auth systems: Live-ReAuth
- Enano now uses HMAC-SHA1 encoded passwords internally
- External authentication is now supported, via plugins; through this, the Yubikey plugin works
- A new simplified log interface
- The dashboard in the administrative panel has been rewritten to be a little more friendly to new users
Thursday, April 02, 2009
1. Our software comes with an installer program.
Enano CMS itself, once it is dropped into htdocs or equivalent, has a web based installer that can be used to configure Enano completely. Also, our efforts with the BitNami project allow us to say that we do have a regular installer application to run on Windows, Mac OS X, Linux, etc. for installing Enano CMS. In the future, we do plan to offer our own set of them on the project though. We also have a commandline based installation sequence that can be automated. Unless you use the BitNami installer, the only step needed to remove it is to delete the folder. The BitNami installer has a standard uninstall script/app depending on your OS. (3/3)
2. Installing or uninstalling our software does not require a reboot of your machine.
Absolutely not! Enano CMS does not require rebooting the machine because it does not have any system level components. Everything is implemented in the web script level. (3/3)
3. You can choose your locale and language at install time, and never have to see English again after that.
While Enano CMS does allow you to choose the locale and language at install time, and never require you to see English again after that, we cannot offer any languages other than English because nobody has stepped up to translate the strings. Give us a break! We are only two people and we started this project in 2006, adding translation support fairly late in the development. (1.5/3)
4. Eval versions of the latest edition(s) of our software are always available for download from the company website.
5. Our WCM software comes with a fully templated "sample web site" and sample workflows, which work out-of-the-box.
Well, not really. Enano comes with themes, yes, but that is it. Technically, Enano is a CMS with wiki features available. Enano uses the same workflow as MediaWiki, only slightly different in that it has Access Controls and other features to control what goes on. (2/3)
6. We ship a tutorial.
No, we do not. But we don't really need to either. Again, Enano is a wiki-based CMS, so anyone even remotely familiar with MediaWiki (the style of Wiki our wiki engine is based on) will be able to grasp it quite well. There is a "click here to get started" link on a fresh install of Enano though. (2/3)
7. You can raise a support issue via a button, link, or menu command in our administrative interface.
In Enano 1.0.x, no, but in our development version, 1.1.x, we most likely will. At this time, we are putting the final bits into place for 1.1.6, and a link to the page describing how to get support for Enano will likely be on the main page of the admin panel. (2/3)
8. All help files and documentation for the product are laid down as part of the install.
No way. It would make the install package way too large, and besides, Enano's documentation is also a wiki for people to contribute to. There is already a basic set of information there, but more good documentation is always appreciated (3/3).
9. We run our entire company website using the latest version of our own WCM products.
Well, we aren't a company, but we do run our entire website on the latest versions of our own software. Enano 1.0.6 is for enanocms.org and docs.enanocms.org, while nighthawk.enanocms.org and *.demo.enanocms.org use 1.1.x. When 1.1.6 is released, all sites will be upgraded to 1.1.6, even the main sites. (3/3)
10. Our salespeople understand how our products work.
Well, we don't sell anything, but we do understand how our own software works, after all, we use it all the time! (3/3)
11. Our software does what we say it does.
Absolutely! Enano doesn't claim to do what it cannot do. (3/3).
12. We don't charge extra for our SDK.
We don't charge anything for the software itself, much less the SDK, which incidentally, is part of the Enano sources. (3/3).
13. Our licensing model is simple enough for a 5-year-old to understand.
Definitely. You can get it for free and share to anyone you want under the same terms is pretty simple! Although it could be argued that five-year-olds don't know how to share ;) (3/3)
14. We have one price sheet for all customers.
Yep! We do for the software itself (FREE) and our support services (available here). (3/3)
15. Our top executives are on Skype, Twitter, or some similar channel, and: Feel free to contact them directly at any time.
Overall Rating: 40.5/45
Meme ID: 9c56d0fcf93175d70e1c9b9d188167cf
Thursday, March 19, 2009
Monday, March 09, 2009
Wednesday, March 04, 2009
Monday, March 02, 2009
Saturday, February 14, 2009
read more | digg story