In this lesson, you have seen some reasons why open source software can offer advantages over proprietary software. You can now list the freedoms that you should look for in a piece of software and know why vendor lock-in is expensive in the long term. It can be avoided by using open standards during development.
This week, we covered the emerging technology trend of openness which is becoming increasingly important to web-enabled businesses. Openness goes beyond simply making your code available - it has as much to do with a "development ethic" than anything else. Whether or not you agree with the directions assumed by a culture of openness, I am sure you can see how it is having an impact in the near term on how systems are created and how vendors adapt to new technology.
In the next lesson, we will delve deeper into system development nuts & bolts by focusing on different opportunities that various programming languages can afford. Choosing languages is often a luxury (existing legacy systems may force one option over others), but it is important to understand the capabilities of different languages when making those decisions.
Tell us about it!
If there is anything in the lesson materials that you would like to comment on, or add to, feel free to post your thoughts in the General Questions Discussion Forum in Canvas. For example, what did you have the most trouble with in this lesson? Was there anything useful here that you'd like to try in your own work? While you are there, feel free to post your own responses and comments if you are able to help out a classmate.