This is a read-only archive of the Framer Community on Facebook.

What is Framer? Join the Community
Return to index
Koen Bok
Posted Aug 22 - Read on Facebook

Poll: How would you feel about Framer switching to ES6 (actual JavaScript)?
Background: Framer currently uses a layer on top of JavaScript called CoffeeScript, to make it less intimidating and easier for beginners. But the next version of JavaScript (ES6) fixed many of these issues, so we are considering to switch to it. There is a lot more to it then I can express in this post, but I just wanted to poll the temperature and get some feedback.


Harsha Halvi

Cofeescript is easier to pick up and framer tutorials everywhere else are mostly in Cofeescript.

Øyvind Nordbø

How much switch pain are we looking at? 🤓

Kasper Andersen

Would it be possible to make an example of how a Layer and an animation would look in ES6?

Dominik Sebian

I guess it would be fine. But could you may guarantee that there is going to be a coffeescript to js converter inside of framer? So wen can translate the current project.

Aalok Trivedi

I can only speak for myself--as an intermediate coffeescripter who knows very little javascript. Would definitely be more of a burden for me, both in time to learn a new(ish) language/format AND time to actually build prototypes fairly quickly. Coffeescript makes it soo easy, but then again, it may help me in the long run?

Anton Kartashov

Kasper Andersen ↓

Jonathon Toon

I think it would be fantastic. While there is some overhead I think folks need to understand that Coffeescript IS Javascript. Conceptually everything you've written to this date is still done basically in the exact same way.

Also given that Framer allows designers to get stuck in to the implementation of actual production code, at least on the web, making the syntax almost 1:1 will close that gap even further.

Dominik Sebian

If you guys have anything to test, I would love to play around :)

Will Rice

Would much prefer ES6. From what I understand Coffeescript has essentially halted development, and ES6 has a whole lot of the good bits that made CS worth using. That being said, I write a decent amount of JS outside Framer, so it wouldn't be a huge switch for me.

Ee Venn Soh

This is awesome news! A great first step to help designers to actually learn something that is easily transferrable to other libraries and frameworks. We all like to invest time and energy in one skillset that we can see it use across many other areas.

Andrea Pedrina

Please i dont have time to learn JS

Jonathan Lazarini

Yes please ES6 👍🏻
One of the reason I don't use framerjs as it I used to do is ES6 😬

Øyvind Nordbø

I think the switch pain is worth it. Thanks to the sophisticated Framer linter and Auto-Code, we'll be fine. ;) TypeErrors will probably be a little annoying in the beginning, but the tradeoff is too big to dismiss on the account of legibility/clarity that CS provides (amongst other things), in my opinion. I think it will be way more rewarding for all parties involved, to use ES6 in the long run.

Jonathon Toon

I'm interested that people don't want Framer to change because learning Javascript is too much work. If you started using Framer with zero Coffeescript knowledge, and Javascript is practically no different, what makes you think you wont be able to pick it up just is easily (especially since the great team at Framer would re-do their source material and tutorials to match Javascript)?

Darin Dimitrov

I can't believe this is happening. Feels like Christmas. 😍

Anton Kartashov

What is pity to lose with CoffeeScript:
– "for" loop with ranges, "for…in" with iterator and "for…of" with key/value.
– ranges (array[5..], array[..10]).
– thin arrow; fat arrow in ES6 don't work with "this", you have to write word "function" :–)
– very beautiful and clean syntax with a lot of sugar.

Good things in ES6:
– "let" solves newbies' very common problem with understanding of "scoping"!!!
– ternary operator.
– classes, method properties.
– it looks more transparent.

I think, that with ES6 Framer will be complicated for beginners. On the other hand Framer would be more attractive, cause ES6 a more universal language today: you'll be able to apply your knowledge to work with the JavaScript in browser (DOM, React). Haters of CoffeeScript really got :–)

Dmitry Sholkov

I think it's worth it but a bit scary. If you guys provide good amount of learning materials to ease the switch, than I'm in. I'm talking about not just written docs but actual video tutorials with small tips around common UI interactions and syntax changes. When I was beginning learning framer I found videos easier to dive in then reading through the doc, after I got comfortable with syntax it was easier to use the documentation.

Also, I'm trying to convince some of my design peers to switch to Framer and I found it hard to recommend them any good video tutorials that is easy to follow just to get started. Most tutorials were made some time ago and don't use latest syntax (such as ".onClick" shortcuts or animate states) Who tried mentioned that it feels for them like double work: To learn old syntax first based on old tutorials and then learn shortcuts.

Dominik Sebian

Depending on how hard it is, i would like to do some tutorials to get basic stuff covered.

Douwe Homans

I believe it's better for an (experienced) programmer to learn the specifics of JavaScript then those of Coffeescript. So I believe ES6 will help them more.

Starting programmers will find learning Coffeescript or ES6 equally difficult. They will probably look at Framer documentation to learn, so as long as that documentation will be updated I think you're good.

That's my opinion and that's why I vote ES6, but Koen Bok I think you might get biased results on this poll as I believe there are a lot of novice programmers (Framer users coming from a pure design background) out there who might not even be aware that they are using Coffeescript (in Framer) now, might use ES6 in the future, and why they should or would favor one over the other....

Dmitry Sholkov

Also would be cool if someone explained for not so advanced in JS what benefits are we talking about?

Tommaso Zennaro

switching to javascript would be huge

Gregory J. Orton

ES6 BABY. No more transpiling. No more spending 30 minutes working out how to do in Coffeescript what I can do in JS in 30 seconds.

Steve Ruiz

It depends on whether you're still trying to attract designers who don't code. There's a big advantage in using immediately legible language like Coffeescript, not only for people new to coding, but to people who have spend their careers working around code without actually touching it, and who see raw code as a sign that they're in a different professional's territory. The parts that Coffeescript takes care of behind the scenes - statements and punctuation that aren't self explanatory, all in nests of curly brackets - are what previously had identified code as something I shouldn't mess with.

Daniel Lauding

Yes yes, love

Andrea Pedrina

If your target are designers (from ux, visual, ecc.) leave coffe.. Few of them are willing to learn JS since there are developers for that and its time consuming.. My 2 cents

Read the entire post on Facebook