Twitter github

GEF moving to J2SE-1.5?

For those who are curious, GEF is planning to move to J2SE-1.5 soon. I’m not the biggest fan of moving up Java levels if there’s no good reason to as it usually crushes my dreams of having things run on the current level of embedded devices out there. For example, I bugged Ed awhile ago to consider making a certain version of EMF workable on J2ME. Some time passed and Ed actually got EMF working on eRCP… exposing EMF technology to a whole new audience. I’d imagine someone wanting Draw2D or GEF functionality on a device sometime in the future (I believe RAP people are experimenting with Draw2D working in a browser).

Please raise your concerns or praises about GEF moving to J2SE-1.5 on the bug. It’s always nice to have your voice heard.

  • Doug Schaefer

    I felt that way when we moved to Java. Most embedded devices are running C 🙂

  • Doug Schaefer

    I felt that way when we moved to Java. Most embedded devices are running C 🙂

  • Adam Cabler

    I’m selfishly happy about it – since I’m not currently doing any embedded work. I would really like the way that generics clean up my code. However, I do appreciate the limitations that comes with it.

  • Adam Cabler

    I’m selfishly happy about it – since I’m not currently doing any embedded work. I would really like the way that generics clean up my code. However, I do appreciate the limitations that comes with it.

  • Gunnar

    WT… Why does the embedded world always lag behind? We have Java 6 already. Someone should fix there VMs. Memory is not really arguable anymore these days. 😉

  • Gunnar

    WT… Why does the embedded world always lag behind? We have Java 6 already. Someone should fix there VMs. Memory is not really arguable anymore these days. 😉