|
|
|
|
|
by md5person
2199 days ago
|
|
What's wrong with having to pay for software? Or learning to accept that some software is proprietary? Or even with learning to use the right tool for the job, even if that "right tool" may sometimes come at a cost? Students are required to pay for their education at MIT. Were the costs of this course offset with the costs of the non-free software used in an otherwise "standard course"? People put immense effort into developing software. Is asking for compensation for one's time and effort somehow wrong? And in many cases, proprietary/commercial software really does outperform the equivalent FOSS/Libre solution. Why are we teaching people to reach out for the suboptimal tools in these situations? |
|
> The freedom to study how the program works, and change it so it does your computing as you wish.
That is particularly important for students of computer science -- what better way to see how all kinds of software works than by reading and modifying its source code?
I'm surprised if a "standard course" doesn't mostly use free software. Mine certainly did, I remember only a single module where we used a commercial software package (something for hardware simulation). I've never felt that this has limited me in any way. One module had us modifying the Linux kernel.