But we don't see someone stepping up to provide up-to-date JavaScript
support using Xtext or LiClipse either. All I see is the basic tragedy
of
the commons issue here combined with the fact that desktop IDE is not
what
companies want to invest in right now. Short of radically
restructuring
Eclipse Foundation with a higher revenue stream and ability to hire
developers, I don't see a solution here.
-----Original Message-----
From: Michael Scharf [mailto:michael@xxxxxxxxx]
Sent: Thursday, June 25, 2015 8:02 AM
To: Konstantin Komissarchik; 'eclipse.org-architecture-council'
Subject: Re: [eclipse.org-architecture-council] Javascript: a bug that
makes
me really sad....
On 2015-06-25 15:58, Konstantin Komissarchik wrote:
The architectural council is a misnomer as it has not power to affect
architectural matters,
but this isn't even an architectural issue.
You are right, it is not an architectural issue. But maybe the
architecture
of the eclipse IDE makes it difficult to provide a solution. I also
know
that there are other javascript solutions that are better than this.
But
eclipse ships with a project that is essentialy dead since many years.
If JavaScript would be any rarely used language, it would not really
matter,
but JavaScript is one of the most important language for many
projects.
So, we have tools (Xtext) that can generate IDEs for even obscure
DSLs, but
Javascript support is stuck in the last century.
Architecturally we have different worlds for language support, the
hand
written ones, the Xtext language support, LiClipse with declarative
language
support, Doug with a great idea of jet another Antlr4 based multi
language
support etc. Lots of different architectures that compete with each
other...
Yes, that is a Bazaar, not a Cathedral but for many users eclipse
appears to
be a Cathedral they can download, just to realize that inside there is
a
Bazaar. For a Bazaar, little architecture is needed. For a Cathedral,
architecture is vital. Eclipse once started with a great
architecture...
Those who know me (hello Doug), know that about once a year, I ask my
self,
what does the architectural council have have to do with architecture.
But
like every year, I get over it ;-)
Michael
It's a feature request to support newer versions
of Javascript. Better Javascript support at Eclipse would be clearly
beneficial, but so far no company has put forth resources on
sufficient
scale to achieve this.
- Konstantin
*From:*eclipse.org-architecture-council-bounces@xxxxxxxxxxx
[mailto:eclipse.org-architecture-council-bounces@xxxxxxxxxxx] *On
Behalf Of *Doug Schaefer
*Sent:* Thursday, June 25, 2015 6:43 AM
*To:* Michael Scharf; eclipse.org-architecture-council
*Subject:* Re: [eclipse.org-architecture-council] Javascript: a bug
that
makes me really sad....
I suppose that's almost an existential question on the role of the
Eclipse Architecture Council. At times, I feel the projects have too
much
power, the power to make decisions that adversely affect the Eclipse
product
as a whole. And I'm sure this extends just beyond the IDE.
But Eclipse is built as a meritocracy. And really the only people who
have the power to change things like this are the ones contributing
the
code to that project. We can try and influence them to make the right
decisions, and I think we are in our right to do that. But that would
require the Architecture council be more vocal about technical matters
and
earn the respect of the projects so they'll have some incentive to
listen.
Doug.
*From: *<eclipse.org-architecture-council-bounces@xxxxxxxxxxx
<mailto:eclipse.org-architecture-council-bounces@xxxxxxxxxxx>> on
behalf of Michael Scharf <eclipse@xxxxxxxxx
<mailto:eclipse@xxxxxxxxx>>
*Reply-To: *Michael Scharf <eclipse@xxxxxxxxx
<mailto:eclipse@xxxxxxxxx>>, Eclipse Architecture Council
<eclipse.org-architecture-council@xxxxxxxxxxx
<mailto:eclipse.org-architecture-council@xxxxxxxxxxx>>
*Date: *Thursday, June 25, 2015 at 9:30 AM
*To: *Eclipse Architecture Council
<eclipse.org-architecture-council@xxxxxxxxxxx
<mailto:eclipse.org-architecture-council@xxxxxxxxxxx>>
*Subject: *[eclipse.org-architecture-council] Javascript: a bug that
makes
me really sad....
Hi,
I am excited about mars being out. But there is a bug,
that makes me really really sad. The most popular eclipse
package is JavaEE and it contains JavaScript. But eclipse
supports only JavaScript 1998.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=223131
The most annoying problem is that modern versions of javascript
allow keywords if they are part of a data structure:
promise.catch(function(){...});
var foo {
default: 42
}
Many libraries use `throw` and `catch` as methods on objects
and this causes a lot of errors and the rest of the file cannot
be parsed.
I know there are a lot of different javascript solutions out
there that work better than this. But, the out of box experience
with eclipse is, well suboptimal.
Is there anything the architecture council can do about this?
Michael
---------------------------------------------------------------------
This transmission (including any attachments) may contain
confidential
information, privileged material (including material protected by the
solicitor-client or other applicable privileges), or constitute
non-public
information. Any use of this information by anyone other than the
intended
recipient is prohibited. If you have received this transmission in
error,
please immediately reply to the sender and delete this information
from your
system. Use, dissemination, distribution, or reproduction of this
transmission by unintended recipients is not authorized and may be
unlawful.
_______________________________________________
eclipse.org-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-council
IMPORTANT: Membership in this list is generated by processes internal
to the Eclipse Foundation. To be permanently removed from this list,
you must contact emo@xxxxxxxxxxx to request removal.
