3 ms·
Partially agree. When I choose a technology for my project, I have to prove to my supervisor that technology is a good fit. In case of Mono.Touch, its usage lea
by solomatov 13y ago
Partially agree. When I choose a technology for my project, I have to prove to my supervisor that technology is a good fit. In case of Mono.Touch, its usage leads to too many risks. What if Mono.Touch is bought by evil company like Oracle (see what happened to MySQL) or decides to abuse its user base by imposing crazy fees? What if the company fails, and who is going to maintain the solution in this case etc? In case of current license, the risks related to these questions are just too high.
- cageface 13y agoDon't you work for JetBrains? Couldn't the same thing be said for your tools? I love them but they're not cheap.
- solomatov 13y agoThe situation is very different here. The core IntelliJ is open source. There're plenty of open source alternatives. So if the license is changed, there're a plenty of options to migrate project to alternative IDEs. In case of Xamarin, there's no such choice. Only Xamarin can compile C# to iOS, and if the license changes, the whole project implemented with the tool is locked in. The only option is to rewrite the whole project with alternative technology. I think, LGPL open source core SDK + paid IDE + paid additional libraries would be a much better choice which mitigates the risk. But Xamarin for some reason decided to choose a different path.