- About Scala
- Documentation
- Code Examples
- Software
- Scala Developers
Re: scala-macros vs scala-virtualized
On 14/02/2012 16:57, Daniel Sobral wrote:
Yes, it's what I keep saying to myself :) That would be great indeed, let's just hope that it will the main focus point of Scala 2.11.
CpusQtiaSg7XdyVBaeTYuZYaw [at] mail [dot] gmail [dot] com" type="cite">[...]
CpusQtiaSg7XdyVBaeTYuZYaw [at] mail [dot] gmail [dot] com" type="cite"> Macros + Interpolation make it possible to remove XML while, at the same time, providing it as a library. And, like XML, one could likewise provide JSON, etc.
Yes, it's what I keep saying to myself :) That would be great indeed, let's just hope that it will the main focus point of Scala 2.11.
-- Francois ARMAND http://fanf42.blogspot.com http://www.normation.com
scala-macros vs scala-virtualized
If the issue is whether we should be offended by such misjudgements, or whether we should be friends with such people, or alternatively if the issue was only people who are purposely trying to scare people away from scala, then that would be a valid argument.
But there is another issue, probably a more important one. A name like "macro" has the potential to easily scare away many people who simply don't know better, people who don't have much of an impression of scala yet and will now have a negative one simply due to misunderstanding.
Also, the field of advertising is all about how things impact one subconsciously, so I can't really comment but possibly that would be relevant to this. Also it could be the idea is that most people most of the time don't think into most things but walk away with whatever impression they happen to have formed. And when the conscious mind isn't deciding what impression to form, the subconscious mind is. Certainly in this case where it's not a matter of subconscious vs. conscious, but first-glance impression or skimming a screenfull vs. reading up on it properly, there could be many people out there who would pass over scala due to simple misunderstanding.
Re: scala-macros vs scala-virtualized
Case in point: in their latest episode, the Javaposse was going through an old article that was giving several reasons why "Java sucks", one of them was that it "doesn't have macros". Everybody on the Posse agreed that this was actually a good thing, that we really, really didn't want macros.
It took me a few seconds to realize that they were all (both the author of the article and the Posse dudes) talking about C-style macros, not Lisp-style ones.
For better of for worse, there are many, many more people who associate "maros" with #define and #ifdef than with Lisp macros.
-- Cédric