Applets were always the answer. Amazing how badly a technology can fail because of start-up time.
152 karma · joined June 22, 2012
I kind of liked quantum foam as a possible way of explaining gravity observation that are not explained by the amount of visible matter and thus attributed to 'dark matter', because 'matter' is the only thing we know that would cause gravity. This tells me I shouldn't get too excited about that possibility.
In my experience, you can be more productive in Java than in any other language, because it has by the best tools and libraries. However, don't use reflection, don't use cloning, avoid automatic (de)serialization, don't doc needlessly, don't separate interface and implementation when you don't have to, use refactoring and code generation, don't feel bad about code duplication.
Most of all, always consider that coding is cheap. Changing a constant? Easy, not hard. Changing interfaces? Easy, not hard. Introducing an alternative implementation? Easy, not hard. Changing names? Easy, not hard. Adding new types? Easy, not hard. You don't need to think about easy things in advance, think about the problem instead.
In old school or new school C, there's every reason to minimize the use of malloc and it's easy to avoid.