Ruby VS CoffeeScript

Ruby Reviews

CoffeeScript Reviews

Ruby mentions (3)

• A full-stack serverless application with AssemblyLift and Next.js

  The counter function is written in Ruby. Since Ruby is an interpreted language, AssemblyLift deploys a customized Ruby 3.1 interpreter compiled to WebAssembly, which executes the function handler. Since the interpreter is somewhat large, the cold-start time of a Ruby function tends to be larger than that of a Rust function. Our counter is being run in the backround, so we're fine with it being a little bit laggy... - Source: dev.to / over 1 year ago

• Why is no one promoting ruby?

  But, in general I was told use rubyapi.org unless you _really_ want to stick with the ruby-lang.org docs for all you do (which is fine) or to dig more into some object hierarchy, etc. Source: almost 2 years ago

• Looking for pwsh (core/open source, v7) integration w/ rbenv, asdf

  [2] 'rbenv' - https://github.com/rbenv/rbenv - Ruby version management utility. Run something like rbenv install 3.1.1 to install that version on your system (requires related project ruby-build), then rbenv local 3.1.1 in your code's directory to specify that for any ruby command in that directory only, you want to use version 3.1.1 that you installed through rbenv. Does other useful stuff too. Only does Ruby,... Source: about 2 years ago

CoffeeScript mentions (25)

• Ask HN: Why don't browsers just build a non-JS interpreter?

  JS isn't perfect, but it's good enough. And there is ongoing effort to make it even better. Also, many other languages compile to JS (without WASM). Notably: - https://www.typescriptlang.org/ - https://coffeescript.org/ - https://clojurescript.org/ - https://www.transcrypt.org/ I wrote https://multi-launch.leftium.com, which is only 6% JS. The majority is Svelte (65%) + TypeScript (27%). ( - Source: Hacker News / 4 months ago

• Vanilla+PostCSS as an Alternative to SCSS

  As a front-end web developer, do you still use CoffeeScript or jQuery? Unlikely, as TypeScript, ES/TC39 and Babel (and the retirement of Internet Explorer thanks to @codepo8 and his EDGE team) have helped to transform JavaScript into some kind of a modern programming language. - Source: dev.to / about 1 year ago

• Why React isn't dying

  On the other hand, companies choose React because that's where all the developers are. If you want to build something that can be maintained years from now, you better not choose the next hype train that goes straight to nowhere (remember CoffeeScript ?). You want something battle tested that has stood the test of time, where you won't have trouble finding developers to scale once you need to. And nobody ever got... - Source: dev.to / over 1 year ago

• Civet: The CoffeeScript of TypeScript

  Http://coffeescript.org/#expressions this comes from Lisp and makes a lot of things easier. Obviously this was not implemented in ES6 because it would break compatibility and there is also some problems with implicit returns that made the feature a bit weird I wonder if a syntax like this for JS would work: const eldest = if (24>41) { escape "Liz" } else { escape "Ike" } with "escape" working like a mix of "break"... - Source: Hacker News / over 1 year ago

• Civet: The CoffeeScript of TypeScript

  Coffeescript[1] was a flavour of JS syntax meant to look similar to Ruby syntax. You just compiled it back to JS. It was nice for working on Rails projects since it made everything feel more “cohesive”. I assume this project is here for older Coffeescript[1] projects who want to start using typescript, and need access to interfaces/types that were present in old CS files. [1] https://coffeescript.org/. - Source: Hacker News / over 1 year ago