Need advice about which tool to choose?Ask the StackShare community!

Lua

1.4K
830
+ 1
156
Ruby

28.3K
18.2K
+ 1
3.9K
Add tool

Lua vs Ruby: What are the differences?

Lua: Powerful, fast, lightweight, embeddable scripting language. Lua combines simple procedural syntax with powerful data description constructs based on associative arrays and extensible semantics. Lua is dynamically typed, runs by interpreting bytecode for a register-based virtual machine, and has automatic memory management with incremental garbage collection, making it ideal for configuration, scripting, and rapid prototyping; Ruby: A dynamic, interpreted, open source programming language with a focus on simplicity and productivity. Ruby is a language of careful balance. Its creator, Yukihiro “Matz” Matsumoto, blended parts of his favorite languages (Perl, Smalltalk, Eiffel, Ada, and Lisp) to form a new language that balanced functional programming with imperative programming.

Lua and Ruby can be primarily classified as "Languages" tools.

"Fast learning curve" is the top reason why over 19 developers like Lua, while over 590 developers mention "Programme friendly" as the leading cause for choosing Ruby.

Lua and Ruby are both open source tools. It seems that Ruby with 15.9K GitHub stars and 4.25K forks on GitHub has more adoption than Lua with 1.26K GitHub stars and 436 GitHub forks.

Airbnb, Instacart, and StackShare are some of the popular companies that use Ruby, whereas Lua is used by Shopify, Close, and Thumbtack. Ruby has a broader approval, being mentioned in 2530 company stacks & 1140 developers stacks; compared to Lua, which is listed in 55 company stacks and 23 developer stacks.

Advice on Lua and Ruby
Needs advice
on
JavaScriptJavaScript
and
RubyRuby

I'm new to development, and I've been studying JavaScript and Ruby concurrently, but I'm to a point now where I should really be focusing my effort into learning one language. I'd like a solid foundation and understanding, so that I can move forward with confidence. Everywhere I go, I keep hearing that RoR is a dying breed. However, I really have enjoyed Ruby and Rails...a LOT. Its approachable, fun, and readability is great. I just don't want to set myself up for failure by saddling myself in with a stack that will take me nowhere. What is your opinion on the future of RoR and would it be foolish for me to invest too much time in learning it over others?

See more
Replies (6)
Julien DeFrance
Principal Software Engineer at Tophatter · | 7 upvotes · 63.3K views
Recommends
RubyRuby

Ruby on Rails is far from being dead. In fact, this is a very popular choice in early-stage startups, given how fast and easily it allows them to launch their product and iterate on it.

Even at more mature companies, you'll still find a ton of opportunities. Not for internal tools or legacy codebases, but for actual production workloads: web apps, APIs, etc...

Some may tell you that Ruby doesn't scale, but is it really Ruby that doesn't scale, or the code they wrote?

Languages have trends. Sometimes, recruiters will try to take you one way or another to meet their own agenda. Don't always listen to what you hear. Long live Ruby! Long live Rails!

See more
Recommends
RubyRuby

You can’t directly compare RnR and Javascript, since the first is a framework (Ruby would be the language), and Javascript is a language. RnR even uses quite an amount of Javascript. I think that Ruby, and Rails, are design by improving on previous languages, and shifting the perspective from speed to readability and general developer friendliness. Opposed to that, Javascript did not have any design goals at all, and seems to be repeating the errors of all language designs that existed before. “Knowing Javascript” would not be a selling point to me when hiring someone, there should be mentioned specific javascript frameworks. And I’d always try to find someone who has experience in multiple languages. So my advice is to to learn RnR first, you get a head start, Javascript will just come along with it. And you can distinct yourself from other people that claim web development knowledge because they have done one javascript tutorial :-)

See more
Ekapob Ukritnukun
Software Engineer at App47, Inc. · | 4 upvotes · 57.8K views
Recommends
JavaScriptJavaScriptRubyRuby

I know I'm cheating by recommending both, but that's because I don't think you can go wrong either way.

I've been working with RoR full-time for the past 3.5 years and I really enjoy it. Compared to JavaScript, it's so much easier to read which is amazing from a team collaboration perspective. As for the perception that it's dead, when I recently started looking for new opportunities, I received probably an average of 10-15 calls a week from recruiters looking for people with RoR experience. Also, if you look around for average wages of developers of different languages, Ruby is fairly high up there (higher than JavaScript if I recall correctly), probably because there are fewer of us around and we can command a premium.

However, that said, if your goal is to find a full-time engineering position quickly, then JavaScipt certainly is the flavor of the month and any product with a frontend component will need it. Even our enterprise SaaS platform which didn't use a frontend framework (React, Angular, Vue, etc...) required us to integrate JS packages and write custom ones. JavaScript is probably more versatile than Ruby at the moment and it seems like new frameworks are being written for it all the time, but remember that Ruby was also the preferred language by almost all companies 5-10 years ago.

At the end of the day, I would go with the language that you enjoy writing the most as you'll be using it a lot in your workplace. If you aren't having fun at work, that's a lot of time spent suffering.

See more
pascal carrié
developper at self-employed · | 4 upvotes · 57.9K views
Recommends
RailsRailsStimulusStimulus

ruby got better and better, rails is outstanding. Listen David Heinemeier Hansson : https://corecursive.com/045-david-heinemeier-hansson-software-contrarian I recommend you to read Otis Meyer https://www.informit.com/store/practical-object-oriented-design-an-agile-primer-using-9780134445601#largeCover and https://eloquentjavascript.net/ Don't bother what's they say, just enjoy programming

See more
Leonardo Ribeiro
Software Developer Consultant at Scalable Path · | 4 upvotes · 57.7K views
Recommends
JavaScriptJavaScriptRubyRuby

One of the things that we I often hear since I started programming, is that languages will die. Ruby and JavaScript are both one of the most popular languages today. And popular languages just doesn’t go to the top and die.

So, F*** what people say about languages dying. Go ahead and learn both, or choose one to learn. But also learn data structures, design patterns and testing. This is basic for awesome developers and a lot are missing that.

See more
Joost Baaij
Internet creator. at Space Babies · | 3 upvotes · 40.2K views
Recommends
at

Yo Matt,

I've been in the Ruby on Rails game for twenty years. For the last ten, Rails has been declared deceased. ;) But in reality, Rails is still going strong. The jobs are highly paid and fun. All the pros you list are valid. Yes it is a beautiful language, the OO makes sense, it's dynamic and expressive, and the ecosystem is top shelf. What's to dislike? There are a lot of Rails websites out there. And new ones get created every day too.

Now, to address the elephant in the room....

Ruby is quirky. Since the syntax is pretty different from PHP, and core developers being opinionated, some people just see drama. When Node.JS got slightly usable, they moved over to that. Node.JS is very c/PHP-like after all in its syntax. Many engineering managers will just select the ecosystem that is biggest. Node.JS is a lot bigger. But if you don't care about going a little off the beaten path sometimes, Ruby in my opinion still, after all this time, gives me joy when I use it.

Also important: to this day, I can build everything I want. Ruby, Rails and many gems are being actively maintained. Security vulnerabilities are discovered and corrected. New developments still find their way into the language. For myself, I know that the anemic JS standard library would just frustrate me to no end.... every wheel is invented time and again. Ruby's standard library isn't as voluminous, but it's a lot more diverse and useful.

See more
Needs advice
on
JavaJavaLuaLua
and
PythonPython

I am trying to make Roblox game which requires Lua. I quite don't want to go with Lua just because other tools just might let me do more projects later on. I heard that Python is most similar to Lua, but I am still not sure which tool to use. Java, I think it will help me with many stuff later on for websites, projects, and more!

See more
Replies (2)
Rafey Iqbal Rahman
Recommends
LuaLua
at

Since you are trying to make a Roblox game, you have no other option than to use Lua, since Roblox only allows coding in Lua. Yes, you've heard right, Python is identical and as easy as Lua, although Lua is easier than Python. Beginning from Lua and then escalating to Python is recommended. Java is only helpful when you are creating a heavy, big-budget, enterprise-level product, otherwise, Python would suffice.

See more
Recommends
TypeScriptTypeScript

If you really hate lua check out roblox-ts, a tool that compiles typescript code into roblox lua. https://github.com/roblox-ts/roblox-ts

See more
Decisions about Lua and Ruby
Ing. Alvaro Rodríguez Scelza
Software Systems Engineer at Ripio · | 12 upvotes · 213.1K views

I was considering focusing on learning RoR and looking for a work that uses those techs.

After some investigation, I decided to stay with C# .NET:

  • It is more requested on job positions (7 to 1 in my personal searches average).

  • It's been around for longer.

  • it has better documentation and community.

  • One of Ruby advantages (its amazing community gems, that allows to quickly build parts of your systems by merely putting together third party components) gets quite complicated to use and maintain in huge applications, where building and reusing your own components may become a better approach.

  • Rail's front end support is starting to waver.

  • C# .NET code is far easier to understand, debug and maintain. Although certainly not easier to learn from scratch.

  • Though Rails has an excellent programming speed, C# tends to get the upper hand in long term projects.

I would avise to stick to rails when building small projects, and switching to C# for more long term ones.

Opinions are welcome!

See more
Timm Stelzer
VP Of Engineering at Flexperto GmbH · | 18 upvotes · 377K views

We have a lot of experience in JavaScript, writing our services in NodeJS allows developers to transition to the back end without any friction, without having to learn a new language. There is also the option to write services in TypeScript, which adds an expressive type layer. The semi-shared ecosystem between front and back end is nice as well, though specifically NodeJS libraries sometimes suffer in quality, compared to other major languages.

As for why we didn't pick the other languages, most of it comes down to "personal preference" and historically grown code bases, but let's do some post-hoc deduction:

Go is a practical choice, reasonably easy to learn, but until we find performance issues with our NodeJS stack, there is simply no reason to switch. The benefits of using NodeJS so far outweigh those of picking Go. This might change in the future.

PHP is a language we're still using in big parts of our system, and are still sometimes writing new code in. Modern PHP has fixed some of its issues, and probably has the fastest development cycle time, but it suffers around modelling complex asynchronous tasks, and (on a personal note) lack of support for writing in a functional style.

We don't use Python, Elixir or Ruby, mostly because of personal preference and for historic reasons.

Rust, though I personally love and use it in my projects, would require us to specifically hire for that, as the learning curve is quite steep. Its web ecosystem is OK by now (see https://www.arewewebyet.org/), but in my opinion, it is still no where near that of the other web languages. In other words, we are not willing to pay the price for playing this innovation card.

Haskell, as with Rust, I personally adore, but is simply too esoteric for us. There are problem domains where it shines, ours is not one of them.

See more
Andrew Carpenter
Chief Software Architect at Xelex Digital, LLC · | 16 upvotes · 268.9K views

In 2015 as Xelex Digital was paving a new technology path, moving from ASP.NET web services and web applications, we knew that we wanted to move to a more modular decoupled base of applications centered around REST APIs.

To that end we spent several months studying API design patterns and decided to use our own adaptation of CRUD, specifically a SCRUD pattern that elevates query params to a more central role via the Search action.

Once we nailed down the API design pattern it was time to decide what language(s) our new APIs would be built upon. Our team has always been driven by the right tool for the job rather than what we know best. That said, in balancing practicality we chose to focus on 3 options that our team had deep experience with and knew the pros and cons of.

For us it came down to C#, JavaScript, and Ruby. At the time we owned our infrastructure, racks in cages, that were all loaded with Windows. We were also at a point that we were using that infrastructure to it's fullest and could not afford additional servers running Linux. That's a long way of saying we decided against Ruby as it doesn't play nice on Windows.

That left us with two options. We went a very unconventional route for deciding between the two. We built MVP APIs on both. The interfaces were identical and interchangeable. What we found was easily quantifiable differences.

We were able to iterate on our Node based APIs much more rapidly than we were our C# APIs. For us this was owed to the community coupled with the extremely dynamic nature of JS. There were tradeoffs we considered, latency was (acceptably) higher on requests to our Node APIs. No strong types to protect us from ourselves, but we've rarely found that to be an issue.

As such we decided to commit resources to our Node APIs and push it out as the core brain of our new system. We haven't looked back since. It has consistently met our needs, scaling with us, getting better with time as continually pour into and expand our capabilities.

See more
Thomas Miller
Talent Co-Ordinator at Tessian · | 16 upvotes · 140K views

In December we successfully flipped around half a billion monthly API requests from our Ruby on Rails application to some new Python 3 applications. Our Head of Engineering has written a great article as to why we decided to transition from Ruby on Rails to Python 3! Read more about it in the link below.

See more
Mike Fiedler
Enterprise Architect at Warby Parker · | 3 upvotes · 120K views

When I was evaluating languages to write this app in, I considered either Python or JavaScript at the time. I find Ruby very pleasant to read and write, and the Ruby community has built out a wide variety of test tools and approaches, helping e deliver better software faster. Along with Rails, and the Ruby-first Heroku support, this was an easy decision.

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Lua
Pros of Ruby
  • 38
    Fast learning curve
  • 24
    Efficient memory usage
  • 24
    Very easy to embed in C programs
  • 18
    Open source
  • 14
    Good for game scripting
  • 7
    Simple Language
  • 7
    Supported in most game engines
  • 6
    Syntax is amazing
  • 6
    Pretty simple to learn
  • 6
    Quick to code
  • 4
    D
  • 1
    Can be used for a wide variety of development
  • 1
    Coroutines
  • 601
    Programme friendly
  • 535
    Quick to develop
  • 487
    Great community
  • 467
    Productivity
  • 429
    Simplicity
  • 271
    Open source
  • 233
    Meta-programming
  • 203
    Powerful
  • 155
    Blocks
  • 138
    Powerful one-liners
  • 67
    Flexible
  • 57
    Easy to learn
  • 49
    Easy to start
  • 41
    Maintainability
  • 36
    Lambdas
  • 30
    Procs
  • 20
    Fun to write
  • 19
    Diverse web frameworks
  • 12
    Reads like English
  • 9
    Rails
  • 9
    Makes me smarter and happier
  • 8
    Elegant syntax
  • 7
    Very Dynamic
  • 6
    Matz
  • 5
    Programmer happiness
  • 4
    Generally fun but makes you wanna cry sometimes
  • 4
    Fun and useful
  • 4
    Object Oriented
  • 3
    Elegant code
  • 3
    Friendly
  • 3
    There are so many ways to make it do what you want
  • 3
    Easy packaging and modules
  • 2
    Primitive types can be tampered with

Sign up to add or upvote prosMake informed product decisions

Cons of Lua
Cons of Ruby
  • 3
    Nooby
  • 2
    Not widespread
  • 7
    Memory hog
  • 7
    Really slow if you're not really careful
  • 3
    Nested Blocks can make code unreadable
  • 2
    Encouraging imperative programming
  • 1
    Ambiguous Syntax, such as function parentheses

Sign up to add or upvote consMake informed product decisions

What is Lua?

Lua combines simple procedural syntax with powerful data description constructs based on associative arrays and extensible semantics. Lua is dynamically typed, runs by interpreting bytecode for a register-based virtual machine, and has automatic memory management with incremental garbage collection, making it ideal for configuration, scripting, and rapid prototyping.

What is Ruby?

Ruby is a language of careful balance. Its creator, Yukihiro “Matz” Matsumoto, blended parts of his favorite languages (Perl, Smalltalk, Eiffel, Ada, and Lisp) to form a new language that balanced functional programming with imperative programming.

Need advice about which tool to choose?Ask the StackShare community!

What companies use Lua?
What companies use Ruby?
See which teams inside your own company are using Lua or Ruby.
Sign up for StackShare EnterpriseLearn More

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with Lua?
What tools integrate with Ruby?

Sign up to get full access to all the tool integrationsMake informed product decisions

Blog Posts

Nov 20 2019 at 3:38AM

OneSignal

PostgreSQLRedisRuby+8
8
4160
Oct 24 2019 at 7:43PM

AppSignal

JavaScriptNode.jsJava+8
5
823
Jun 6 2019 at 5:11PM

AppSignal

RedisRubyKafka+9
15
1255
GitHubDockerReact+17
35
32605
What are some alternatives to Lua and Ruby?
Python
Python is a general purpose programming language created by Guido Van Rossum. Python is most praised for its elegant syntax and readable code, if you are just beginning your programming career python suits you best.
JavaScript
JavaScript is most known as the scripting language for Web pages, but used in many non-browser environments as well such as node.js or Apache CouchDB. It is a prototype-based, multi-paradigm scripting language that is dynamic,and supports object-oriented, imperative, and functional programming styles.
Arduino
Arduino is an open-source electronics prototyping platform based on flexible, easy-to-use hardware and software.
Java
Java is a programming language and computing platform first released by Sun Microsystems in 1995. There are lots of applications and websites that will not work unless you have Java installed, and more are created every day. Java is fast, secure, and reliable. From laptops to datacenters, game consoles to scientific supercomputers, cell phones to the Internet, Java is everywhere!
Golang
Go is expressive, concise, clean, and efficient. Its concurrency mechanisms make it easy to write programs that get the most out of multicore and networked machines, while its novel type system enables flexible and modular program construction. Go compiles quickly to machine code yet has the convenience of garbage collection and the power of run-time reflection. It's a fast, statically typed, compiled language that feels like a dynamically typed, interpreted language.
See all alternatives