You know, there are many different programs in Linux that do the same thing. Gnome vs. KDE. Gnote vs Tomboy etc. ConnMan is no different, and people saying they just need to work on Network Manager have absolutely no grasp of how things work.
Related posts:
#1 by Bugsbane on June 25, 2009 - 6:11 pm
Quote
Agreed…
But who wants to give something as important as their connection to a ConnMan?
#2 by bags on June 25, 2009 - 6:40 pm
Quote
uhm, given your boldness i assumed above post was just a teaser into a more in-depth explanation of why ‘they’, ‘have absolutely no grasp of how things work’.
have you read http://blogs.gnome.org/dcbw/2009/06/25/networkmanager-and-connman/ ?
#3 by sharms on June 25, 2009 - 7:04 pm
Quote
@bags – Yes I have read that, and that really changes nothing. There are some great technical points made, but it does nothing to dispute the claim I make that in the open source world, multiple projects trying to achieve the same goal is not only common place, but healthy.
#4 by oliver on June 26, 2009 - 4:28 am
Quote
Nothing against healthy competition, if it happens on technical level. But IMO the ConnMan slides were way too aggressive towards NM, instead of just presenting ConnMans features and leaving it to the viewers to decide.
#5 by François on June 26, 2009 - 6:40 am
Quote
I agree with Olivier
ConnMan presentation was too much about why Network Manager is not good. If it’s just common to create alternative, why should you have to criticize the other solutions like that. Just explain why your software is good, and that’s it.
#6 by jldugger on June 26, 2009 - 6:44 pm
Quote
Just what is your point about Gnote vs Tomboy. They literally do the exact same thing.
#7 by sharms on June 28, 2009 - 1:37 pm
Quote
@jldugger – Gnote pushes Tomboy to get more features and faster startup / performance, and Tomboy pushes Gnote to be feature complete when this happens, causing both to be better.
Not to mention at the same time, everytime Gnote has a significant performance advantage, this will be complained about on mailing lists etc, mono devs will hear about it, and try and resolve the issue, helping that project also.