|Re: [cross-project-issues-dev] Freemarker|
The decision to leverage JDT tooling was pragmatic but it's really slow. When you type something you have to wait for the underlying Java to get created, built, messages to appear and relayed.
If anything goes wrong you have the problems that the net effect is a cascade of JDT and Xtend idiosyncracies.
Refactoring just doesn't work.
Debugging is unpleasant because you get to see large numbers of synthetic variables in the Variables View.
Got to line can fail since some Java problems do not appear in the Xtend so you cannot got to the relevant line to fix them. You have to manually open the Java file, locate the context of the error and manually navigate back to the corresponding point in Xtend.
Personally I really dislike the syntax incompatibilities with Java although I could live with, perhaps even like, the extra type inference. Migrating to Xtend took much longer than I expected because of stupid things like changing casts to "as". Subsequently I have had to reverse the same changes in order to regain control. My current practice is to minimise my Xtend usage and avoid as many non-Java syntaxes as possible.
I find the flattening of getXX() as xx very dangerous since you get new occlusion hazards with respect to function parameters.
But ''' and guilemets are great.
On 22/10/2013 15:35, Sebastian Zarnekow wrote: