Voting: Unterschied zwischen den Versionen

Aus Java Student User Group Austria - Java + JVM in Wien Österreich / Vienna Austria
Wechseln zu: Navigation, Suche
(owZFZsriEASDPwlz)
(fwCcCKIyUqOHpv)
Zeile 1: Zeile 1:
Wow. You are really off base: But brneaikg the year long no-Java-mention embargo on his blog by introducing JavaFX is a sad reminder that Sun does, indeed, care very little about Java. Jonathan Schwartz mentioned Java 76 times in 54 blog posts over the past 12 months:May 27th  2 timesMay 31st  7 timesJul 25  3 timesAug 17  3 timesOct 4  onceOct 23    onceNov  8  8 timesNov 13  12 timesNov 28    onceDec 9    onceJan 14  4 times, Intel partnership optimizing Java on intelMay 4  twiceMay 8  30+ timesMay 15  3 timesYes, there was a 3 month quiet period before JavaOne, which is to be expected, you save up your good stuff for when it's most relevant.Coming from the position of  Leader of the Java World  to CEO, I'm surprised he didn't try to shed the I'm really a nerdy developer  image that one COULD put on him (no one does).How important is Java to Sun?  Read the posts. For example, on May 4th, when Jonathon was discussing the most recent revenue numbers, he mentioned a new large OEM Java Licensee and 200,000 more uses added to the Java Enterprise System.
+
in your post that this should be ootgrhonal from a compiler perspective but I'm not sure how it can be). Yours is a simple case, but I could see this type of thing getting out of control for more complex cases. Other developers would have to accept your view and program accordingly. In other words, extending any language via macros or macro-like constructs is a catch 22 situation.Brings me back to the days using assembler and people having their own toolkits of macros. They were usefull and all but they almost always degenerated into their own minilanguages and impacted development and maintenance.It seems that the purpose of any source language(with all it's shortcomings) is to provide a baseline grammar and syntax to allow everyone to communicate with. If you go down the path of  You say POTAYTO, I say POTAHTO with source view representations, it's only going to cause confusion in the long run.Anyway, I'll still use your plugin if you post it

Version vom 16. Dezember 2012, 07:44 Uhr

in your post that this should be ootgrhonal from a compiler perspective but I'm not sure how it can be). Yours is a simple case, but I could see this type of thing getting out of control for more complex cases. Other developers would have to accept your view and program accordingly. In other words, extending any language via macros or macro-like constructs is a catch 22 situation.Brings me back to the days using assembler and people having their own toolkits of macros. They were usefull and all but they almost always degenerated into their own minilanguages and impacted development and maintenance.It seems that the purpose of any source language(with all it's shortcomings) is to provide a baseline grammar and syntax to allow everyone to communicate with. If you go down the path of You say POTAYTO, I say POTAHTO with source view representations, it's only going to cause confusion in the long run.Anyway, I'll still use your plugin if you post it