On 3 November 2017 at 03:19, Brett Cannon wrote:
> On Wed, 1 Nov 2017 at 16:17 Lukasz Langa wrote:
>>
>> I find this sad. In the JavaScript community the existence of Babel is
>> very important for the long-term evolution of the language independently
>> from the runtime. With Babel, JavaScript p
On 2 November 2017 at 23:42, Victor Stinner wrote:
> (Email resent, I first sent it to Nick privately by mistake.)
Oops, I didn't even notice that. Reposting my reply below.
> 2017-11-02 2:53 GMT+01:00 Nick Coghlan :
>> The piece that we're currently missing to make such workflows easier to
>> m
On Wed, 1 Nov 2017 at 16:17 Lukasz Langa wrote:
> I find this sad. In the JavaScript community the existence of Babel is
> very important for the long-term evolution of the language independently
> from the runtime. With Babel, JavaScript programmers can utilize new
> language syntax while being
(Email resent, I first sent it to Nick privately by mistake.)
2017-11-02 2:53 GMT+01:00 Nick Coghlan :
> The piece that we're currently missing to make such workflows easier to
> manage is an equivalent of JavaScript's source maps (...)
Code objects already have a instruction pointer => line numb
On 2 November 2017 at 09:16, Lukasz Langa wrote:
> I find this sad. In the JavaScript community the existence of Babel is
> very important for the long-term evolution of the language independently
> from the runtime. With Babel, JavaScript programmers can utilize new
> language syntax while being
I find this sad. In the JavaScript community the existence of Babel is very
important for the long-term evolution of the language independently from the
runtime. With Babel, JavaScript programmers can utilize new language syntax
while being able to deploy on dated browsers. While there's always
