Religion aside: http://wekeroad.com/2012/03/21/coffeescript-or-straight-up-js-i-suck-either-way What is better for Discourse, CoffeeScript or JavaScript? Notice, I am not particularly interested in personal preferences here. I am interested in quality and frequency of potential contributions and…

LOL you know what I mean :slight_smile: didn’t mean to troll :). There are concepts you need to understand sure but getting it to run is quite small. I don’t think so (JShint). To me, you’ll likely find some great UX people out there who know their JS and want to help. The main questions here are: …

I’m familiar with JS but not CoffeeScript or Ember. I don’t feel encumbered by CoffeeScript after looking at a few docs that explain the basic syntax differences. Ember is more of an undertaking, I haven’t yet grokked how everything at Discourse is put together.

Two points in favor of JavaScript: Every CoffeeScript developer knows JavaScript. The inverse is not true. Because CoffeeScript emits JavaScript, and any debugging you do in the browser is in JavaScript, by definition CoffeeScript developers must have at least a passing familiarity with JavaScript. …

[imagem] tomdale: CoffeeScript jeopardizes the ability to stay up-to-date with the web platform i agree with @tomdale 's second post i believe ember.js is a good choice, in terms of having a sleeker code base, yes you have to learn the framework but that shouldn’t be an issue

I am a devout CoffeeScript user, but I think the official client should probably be maintained in Javascript. Anyone can write and distribute another fully-functional front-end, or even do a fork of the current one and decompile the JS to CS. [imagem] tomdale: Every CoffeeScript developer knows…

[imagem] tomdale: CoffeeScript jeopardizes the ability to stay up-to-date with the web platform. Parts of CoffeeScript require new syntax that is incompatible with features coming in ES6 and ES7. By using CoffeeScript, you are locking yourself into always using ES4. One of the principles of TC39…

Hmm, I may have to backtrack on my original opinion after giving this more consideration. While I have been able to figure out how things work without too much issue despite not having a deep familiarity with either CoffeeScript or Ember, the combination does introduce a level of friction that make…

While we’re deep in bikeshedding zone, The pretext in the responses seem to be that enough hypothetical proficient Ember.js devs are going to be dissuaded from contributing to Discourse at such a substantial rate that it’s worth getting rid of Coffeescript. And that it ostensibly outweighs the ben…

CoffeeScript has significant whitespace. So instant no. It makes it a pain in the butt to parse. It’s annoying. Most people (except for Python developers) don’t like it. Due to being difficult to parse, you will have problems when you try to refactor. Not to mention the problems of re-indenting eve…

Is it better for Discourse to use JavaScript or CoffeeScript?

Dev

anotherchris (Chris S.) Fevereiro 15, 2013, 11:03pm 14

TypeScript!

Tumbleweed

It’s still Javascript, but sadly the compiler is Windows only and a bit VS centric.

Tópico		Respostas	Visualizações
Coffeescript vs Javascript Development	1	914	22 de Setembro de 2016
Choice of tech stack for discourse if started in 2020 Development	8	2119	28 de Maio de 2024
Case study of an amateur plugin author Development	11	188	4 de Maio de 2026
Are there any plans to migrate Ember.js to React.js in Discourse? Development	7	205	27 de Julho de 2022
WYSIWYG Plugin (again) Feature completed	28	9714	12 de Março de 2025

Is it better for Discourse to use JavaScript or CoffeeScript?

Tópicos relacionados