5 ms·
Saying that mono failed for your project and that you're not going to touch it again is like saying that opensource failed for your project and you're not touch
by knocte 13y ago
Saying that mono failed for your project and that you're not going to touch it again is like saying that opensource failed for your project and you're not touching it again.
Mono is a project which has a lot of different pieces of technology underneath. Please tell us the part that didn't work for you, because you cannot attribute low quality to the whole project just by testing a small part. (i.e.: was your project a web app or a desktop app? how did you host it? did your team have any Unix expertise or were just a bunch of Windows devs expecting to become Linuxers overnight?)
And most importantly, what version of Mono did you use? (Most people that complain end up saying that they just used the mono that their 4 year old distro supplied, which is a version even older than 4 years.)
- jnardiello 13y agoThat is not the case. Team with a dedicated Unix devops engineer and a windows dev consultant, all other are skilled unix devs. We have been debugging like beasts and we are probably and realistically one of the best technical teams in the country. We ran everything on Mono 3.0, which we was chosen for specific reasons and weare very aware that is a 1.5yrs old distro. The last specific problem would maybe be sorted upgrading to last release (we don't know) but we already know that new issues would rise as the pattern keeps being the same.
- turnip 13y ago"we are probably and realistically one of the best technical teams in the country" yet were unable to debug 2 months worth of new code on a mature platform, that lesser people have no troubles with.
- knocte 13y agoYou still haven't said the type of the app (web, desktop?), and in case of web, what technology you chose to host it (this is actually the root of many issues that people wanting to host Mono apps face, and it's kind of unrelated to Mono stack).