tag:blogger.com,1999:blog-17681521.post75167705210737025..comments2023-11-30T10:11:42.899+01:00Comments on Eclipse and Java Blog by Michael Scharf: Good versus evil diversity - why the foundation must hire developersMichael Scharfhttp://www.blogger.com/profile/16708708879318235495noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-17681521.post-48157654302843687372023-06-23T21:16:57.526+02:002023-06-23T21:16:57.526+02:00canlı sex hattı
salt likit
heets
arkadaşlık sitesi...<a href="https://bit.ly/canli-sex-hatti" rel="nofollow">canlı sex hattı</a><br /><a href="https://bit.ly/salt-likit" rel="nofollow">salt likit</a><br /><a href="https://bit.ly/heets-heets-heets" rel="nofollow">heets</a><br /><a href="https://bit.ly/arkadaslik-sitesi" title="arkadaşlık sitesi" rel="nofollow">arkadaşlık sitesi</a><br />1M7Upelinnoreply@blogger.comtag:blogger.com,1999:blog-17681521.post-68532162984318343792009-04-08T08:01:00.000+02:002009-04-08T08:01:00.000+02:00Note sure if the foundation should hire developers...Note sure if the foundation should hire developers. I could imagine, though. I'd like to keep that apart from the foundation. I say we need to refactor the Eclipse top-level project. The influence of too few still decides about the future for many.Gunnarhttps://www.blogger.com/profile/08579442993356201374noreply@blogger.comtag:blogger.com,1999:blog-17681521.post-73783822768363135312009-04-07T21:31:00.000+02:002009-04-07T21:31:00.000+02:00"Backwards compatibility at all costs" eventually ..."Backwards compatibility at all costs" eventually leads to no forward progress because the cost of backwards compatibility becomes too high. The perl community is a good example of "no progress," whereas the php community took the opposite approach: as much backwards compatibility as possible, but not to the extent of stopping progress. Sure the result is a pain to use at times, but PHP is a lot more widely used than Perl...Bjorn Freeman-Bensonhttps://www.blogger.com/profile/12380007655974891303noreply@blogger.comtag:blogger.com,1999:blog-17681521.post-2862629410082689212009-04-07T19:26:00.000+02:002009-04-07T19:26:00.000+02:00Interesting perspective. I agree that there is the...Interesting perspective. I agree that there is the possibility of "too much of a good thing" when it comes to diversity; but I'm not sure if Eclipse projects have reached that point yet. Maybe some have, but probably not all.<BR/>I think the most important practical issue you mention is the "re-invent the wheel" syndrome; that is, there are simply too many ways to do the same things. I think a lot of that is driven by a stubborn resistance to make things public API, which in turn is driven by the "backwards compatibility at all cost" mentality. I do understand very well the motivation behind placing a premium on backwards compatibility, but I also have experienced situations where it was too strict and otherwise good ideas were abandoned or rejected because of it. That leads to many different wheels being re-invented, a sign of the bad kind of diversity of which you speak.Eric Rizzohttps://www.blogger.com/profile/08407727335073173803noreply@blogger.com