Not all of us on the Posse are SWT bashers :) I always thought a next- generation toolkit could have been built with something like swing on top of java2D and SWT.
But I guess JavaFX's scene graph is the now new new thing. On Apr 8, 12:01 pm, Lhasadad <[email protected]> wrote: > Guys, > > Listened to latest podcast and have got to say that the SWT bashing > got old pretty quick. I agree with you that using an internal API is > likely to get you into trouble. that was just a poor choice the > Eclipse SWT developer made. As you pointed out it works with an > environment variable tweaked (its possible that the developer intended > that it always be tweaked on Linux and someone missed doing that until > now). you guys have lived in the real world and you know how this > happens. > > I worked with early Java and I know the pains our GUI god when through > to work with AWT and early Releases of Swing. The early development > of eclipse was looking for more performance than was available in > those releases and they saw a problem and found a solution. In the > end they very likelyhelped drive the Sun through a little competition > to improve the implementation of Swing to get much better performance > out of it. At the end of the day everyone benefited. we got a strong > IDE that helped moved Java adoption in the enterprise space. we all > won there. Can we just call a truce at this point and not sing in > glee when small problem appears in someones library as long as the > respond and fix it quickly? > > Can we let it go? > > Thanks -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
