Re: [eclipse.org-architecture-council] Javascript: a bug that makes me r

["Konstantin Komissarchik" <konstantin.komissarchik@xxxxxxxxxx>]

The architectural council is a misnomer as it has not power to affect architectural matters, but this isn’t even an architectural issue. 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> on behalf of Michael Scharf <eclipse@xxxxxxxxx>
Reply-To: Michael Scharf <eclipse@xxxxxxxxx>, Eclipse Architecture Council <eclipse.org-architecture-council@xxxxxxxxxxx>
Date: Thursday, June 25, 2015 at 9:30 AM
To: Eclipse Architecture Council <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.