Been getting more and more email on the subject of Java, Mono, C++, etc.; not clear I can ever reply to all the points raised 😉 I still don’t think anyone has addressed my #1 worry however, as I tried to point out in my last blog post: forking and fragmentation are the outcome if […]
I’m trying to imagine the target demographic for this product. (This post was originally found at http://log.ometer.com/2004-03.html#21.4)
Miguel summarizes my argument as “we need to pick Java to avoid fragmentation,” I’d put it more generally “we need to pick a viable compromise,” again my attempt to summarize options people have brought up: Stick to C/C++ for the forseeable future; possibly enhanced by UNO or XPCOM or equivalent. Build a third language and […]
Miguel writes: Havoc, you are skipping over the fact that a viable compromise for the community is not a viable compromise for some products, and hence why you see some companies picking a particular technology as I described at length below. To be clear, I don’t mind if companies unilaterally choose a technology to use […]
Christian writes: As for the (l)ongoing language debate I think we need to allow for people to both use Java and C# (or any other language) that has a big enough community around it to ensure that bindings are kept up to date and follows the development of the rest of the desktop. I agree […]