3 ms·

Well, we are very well aware of what you mean. With us the situation was slightly different :) We hired - because our management cares - people who actually kne

Well, we are very well aware of what you mean. With us the situation was slightly different :) We hired - because our management cares - people who actually knew what they were doing, we got in touch with the person who phisically maintain the app that was running on mono and he re-assured that his software + mono were running smoothly. We have been hacking on it for months, literally. Contributed to the original project in any possible way. But THEN mono started to give strage behaviours. Unless hacking really bad on it, we understood that there was no way to deploy it in production as it could fuck up in any moment and we could do literally nothing unless deleting a file here and there and reboot. So yeah, i'm 100% sure that things could have been done differently - better - yet this was the outcome no matter how many resources we putted on it. We never complained with the creator of the application (yet, we discussed about it with him) and for the very same reason i don't want to name the product as i'm still convinced it is indeed a good piece of software. I'm just saying that with our project, 4+ very skilled people for about 2 months ended up with nothing. Take it or leave it :)

mikeho1999 13y ago
Interesting story... but just out of curiosity, if there was already the investment made in the codebase for your application, as well as the team in place to continue with the project and maintain it afterwards, was there a consideration to switch to .NET / Windows Server? If so, I'm curious to hear the reasoning behind abandoning the project altogether and re-writing from scratch (and likely re-interviewing and hiring a different team with different skillsets) as opposed to simply moving the production environment onto Windows...
- UK-AL 13y ago
  I think a .net team could move to java relatively painlessly.
profquail 13y ago
Did you ever contact the Mono team about the issues you encountered? I've found them to be very responsive about fixing serious bugs like that. You said you just abandoned the project today -- you should still follow up with the Mono devs to let them know about your problem, since it might be a small fix on their side and it'd salvage the effort your team has already put into the project.
- jnardiello 13y ago
  Nope, we didn't go that far. Never got in touch with the mono team but indeed it's worth to try and i'll speak about this with the team tomorrow morning. :)

mikeho1999 13y ago

Interesting story... but just out of curiosity, if there was already the investment made in the codebase for your application, as well as the team in place to continue with the project and maintain it afterwards, was there a consideration to switch to .NET / Windows Server? If so, I'm curious to hear the reasoning behind abandoning the project altogether and re-writing from scratch (and likely re-interviewing and hiring a different team with different skillsets) as opposed to simply moving the production environment onto Windows...

UK-AL 13y ago
I think a .net team could move to java relatively painlessly.

profquail 13y ago

Did you ever contact the Mono team about the issues you encountered? I've found them to be very responsive about fixing serious bugs like that. You said you just abandoned the project today -- you should still follow up with the Mono devs to let them know about your problem, since it might be a small fix on their side and it'd salvage the effort your team has already put into the project.

jnardiello 13y ago
Nope, we didn't go that far. Never got in touch with the mono team but indeed it's worth to try and i'll speak about this with the team tomorrow morning. :)