Skip to main content

No, Mach-II Is Not Dead

No, Mach-II is not dead. Far from it. I'm not sure why this seems to come up every six months or so, but I think Sean Corfield covers things pretty well so I just wanted to add a few thoughts to his blog post.


First, Mach-II isn't dead, it's actually growing by leaps and bounds. Not only do we see more uptake and great activity on our Google Group, but we're very close to an official beta release of Mach-II 1.5 which adds a ton of great features. We also already have several things on the roadmap for Mach-II 2.0.


Next, we've expanded the community aspects of Mach-II by making the source code publicly available via Subversion, and adding more members to the Mach-II team other than Peter and myself, including Kurt Wiersma as our resident geek (hey, that's the title he wanted), Dave Shuck as our community manager, and Kyle Hayes as our designer.


Finally, we have a new web site that's about to launch, lots of new documentation in the works, and a lot of other cool stuff in the works that we're not quite ready to talk about yet. In short, we've been working very hard over the last few months, so there's no need to fear for Mach-II's demise. If anything we're more active with Mach-II than we've been at any time in the past, and in my opinion version 1.5 is the most significant release of Mach-II since it was created.


We're committed to Mach-II. Everyone involved with Mach-II uses the framework heavily, there are a lot of large implementations of Mach-II projects, and we already have a roadmap in place for well into 2008. So rather than speculate that it's dead simply because we haven't updated the web site in a while, if you're interested in Mach-II, please join the Google Group. It's the best place to get the latest information about Mach-II, and given the active discussion there you'll see Mach-II is anything but dead.

Comments

Popular posts from this blog

Installing and Configuring NextPVR as a Replacement for Windows Media Center

If you follow me on Google+ you'll know I had a recent rant about Windows Media Center, which after running fine for about a year suddenly decided as of January 29 it was done downloading the program guide and by extension was therefore done recording any TV shows.

I'll spare you more ranting and simply say that none of the suggestions I got (which I appreciate!) worked, and rather than spending more time figuring out why, I decided to try something different.

NextPVR is an awesome free (as in beer, not as in freedom unfortunately ...) PVR application for Windows that with a little bit of tweaking handily replaced Windows Media Center. It can even download guide data, which is apparently something WMC no longer feels like doing.

Background I wound up going down this road in a rather circuitous way. My initial goal for the weekend project was to get Raspbmc running on one of my Raspberry Pis. The latest version of XBMC has PVR functionality so I was anxious to try that out as a …

Running a Django Application on Windows Server 2012 with IIS

This is a first for me since under normal circumstances we run all our Django applications on Linux with Nginx, but we're in the process of developing an application for another department and due to the requirements around this project, we'll be handing the code off to them to deploy. They don't have any experience with Linux or web servers other than IIS, so I recently took up the challenge of figuring out how to run Django applications on Windows Server 2012 with IIS.

Based on the dated or complete lack of information around this I'm assuming it's not something that's very common in the wild, so I thought I'd share what I came up with in case others need to do this.


This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.

Assumptions and CaveatsThe operating system is Windows Server 2012 R2, 64-bit. If another variant of the operating system is being used, these instructions may not work properly.All of the soft…

Setting Up Django On a Raspberry Pi

This past weekend I finally got a chance to set up one of my two Raspberry Pis to use as a Django server so I thought I'd share the steps I went through both to save someone else attempting to do this some time as well as get any feedback in case there are different/better ways to do any of this.

I'm running this from my house (URL forthcoming once I get the real Django app finalized and put on the Raspberry Pi) using dyndns.org. I don't cover that aspect of things in this post but I'm happy to write that up as well if people are interested.

General Comments and Assumptions

Using latest Raspbian “wheezy” distro as of 1/19/2013 (http://www.raspberrypi.org/downloads)We’lll be using Nginx (http://nginx.org) as the web server/proxy and Gunicorn (http://gunicorn.org) as the WSGI serverI used http://www.apreche.net/complete-single-server-django-stack-tutorial/ heavily as I was creating this, so many thanks to the author of that tutorial. If you’re looking for more details on …