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


+ 1

+ 1
Add tool

HTML5 vs Ruby: What are the differences?

What is HTML5? 5th major revision of the core language of the World Wide Web. HTML5 is a core technology markup language of the Internet used for structuring and presenting content for the World Wide Web. As of October 2014 this is the final and complete fifth revision of the HTML standard of the World Wide Web Consortium (W3C). The previous version, HTML 4, was standardised in 1997.

What is 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.

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

"New doctype", "Local storage" and "Canvas" are the key factors why developers consider HTML5; whereas "Programme friendly", "Quick to develop" and "Great community" are the primary reasons why Ruby is favored.

Ruby is an open source tool with 15.9K GitHub stars and 4.23K GitHub forks. Here's a link to Ruby's open source repository on GitHub.

Lyft, 9GAG, and Asana are some of the popular companies that use HTML5, whereas Ruby is used by Instacart, Heroku, and Square. HTML5 has a broader approval, being mentioned in 3136 company stacks & 3374 developers stacks; compared to Ruby, which is listed in 2527 company stacks and 1114 developer stacks.

Advice on HTML5 and Ruby
Caue Carvalho
Needs advice


I'm a developer for over 9 years, and most of this time I've been working with C# and it is paying my bills until nowadays. But I'm seeking to learn other languages and expand the possibilities for the next years.

Now the question... I know Ruby is far from dead but is it still worth investing time in learning it? Or would be better to take Python, Golang, or even Rust? Or maybe another language.

Thanks in advance.

See more
Replies (8)
Angel Ramirez

Hi Caue, I don't think any language is dead in 2022, and we still see a lot of Cobol and Fortran out there, so Ruby is not going to die for sure. However, based on the market, you'll be better off learning Goland and Python. For example, for data science, machine learning, and similar areas, Python is the default language while backend API, services, and other general purpose Goland is becoming the preferred.

I hope this helps.

See more

I feel most productive using go. It has all the features I need and doesn't throw road blocks in your way as you learn. Rust is the most difficult to learn as borrow checking and other features can puzzle a newcomer for days. Python is a logical next step as it has a huge following, many great libraries, and one can find a gig using python in a heartbeat. Ruby isn't awful, it's just not that popular as the others.

Another reason to use python is that it is not compiled. You can muck around in the interpreter until you figure things out. OTOH, that makes it less performant. You really need to think about your use cases, your interest in lower-lever versus high-level coding, and so on.

See more
Roman Glushko
Machine Learning, Software Engineering and Life · | 4 upvotes · 12K views

I enjoy coding in Python. I think it's minimalistic and readable syntax and lang features are just unparalleled. They are perfect for prototyping and for the software engineering in general. If I'm not wrong Gitlab marked Python as #2 popular language after JavaScript. Beyond that, Python ecosystem and areas of usage are enormous. In areas like ML/DL, it's important to know Python to leverage variety of existing tools and frameworks.

Then, I have learned and worked with Golang. I use it where I think I would need a slightly better performance than in Python. Plus, relatively small and self-contained executable is a great thing to have. If you plan to write distributed systems, extend Kubernetes or do similar things I think Golang is a great choice. It's also simple and straightforward, especially when you want to do effective multithreading. Although I don't like that Golang is more low-level than Python. Sometimes I feel like I need to implement myself too much things.

Now, about Rust. It's my second try to learn Rust. First time I decided to learn Golang as I understood it in 30mins or so while I was struggling to compile/do anything meaningful there for quite a bit. So I personally don't think Rust is super easy. I have got back to learning Rust as it's going to fill one of gaps in my problem solving toolkit - let me write low-level system programs (e.g. linux kernel modules). I don't want to learn "obsolete" C/C++ (my reasons are similar to why Google has recently introduced Carbon - a replacement for C/C++ codebases). If you are not going to tight your life with system-like programming, Rust may be an overkill for you.

Finally, I have never coded in Ruby, so are not going to comment it.

See more

Since you are very experienced, picking up a language will not take you more than a week. Rust is a very new language. Many startups are still experimenting with it. Golang is very popular nowadays. You can see a lot of golang jobs in the market. The best part is, compiled code is single binary and has a minimal footprint. Rails is a compelling framework; believe me, many websites like Shopify, GitHub, GitLab, etc., are powered by the rails framework. You can also leverage the power of metaprogramming in Ruby. Python is memory and CPU intensive. It is not as performant as the other three. If you want to go into Data Science, Python is the language. Good luck, buddy. Feel free to connect with me:

See more

I'm almost same position as you. 8 years same company with c#. I tried both Python and Golang. I like working with Golang. Check this litte go doc. After reading this document and following its examples, I decided to work with "go"

See more

Because it opens endless possibilities you can do anything and everything you want to. from ai to app development to web development.

See more
A Nielsen
Fullstack Dev at ADTELA · | 1 upvotes · 8.6K views

Either Python or Golang, for all the enlightened reasons already mentionned in all advices/comments :) Enjoy!

See more

it is highly recommended to take a look at that survey

See more
fisher boy
Intern web developer at Stepway · | 9 upvotes · 72.4K views
Needs advice

Hey I'm currently an undergraduate in computer science for almost 5 years now, still left with a few courses before I complete. I know that I'm not good at programming but still I choose developer based programming career approach, I have made plans to start my career in websites, etc, for that, I have purchased books related to HTML5, CSS , JavaScript. I'm currently learning HTML5 and CSS only and after this some JavaScript I am really confident in my decision but would love to know what an expert developer advice thanks in advance.

See more
Replies (7)

Whatever you do don't go WordPress path. Developers over-there tend to ignore system limitations and hardcode and overengineer their solutions so as to please their clients. If you are a beginner probably you'll get to work on someone else's shitty code and will be asked by your boss to do "yet another impossible thing with Wordpress". And... Probably... You'll do it.

My suggestion is: think in stacks and don't start too low. Starting with HTML, CSS3 and JavaScript is too low. Start on higher levels and with something practical. You'll have time for basics some time later and it would be much easier, because you'll see those technologies are compliment to what you do and not your main objective.

My suggestion for you:

  • Android Mobile App Development path (complex enough so you won't get bored)
  • All things web3 crypto, nft, virtual reality, blockchain path (has tons of computing web development tasks)
  • Cloud computing setup and administration path (good, because you say you're not good at programming)
  • Artificial intelligence and automation (this is future, people need this)

I've also found it helpful to think of each stack as a surface (find Google Images "radar chart") . Every time you try to learn something new you start in the center, with all technology-points overlapping. You are as low as you can get and you know nothing. Your job is to expand outwards each technology so as to make a stack-surace. The more surface the better. You'll see that some technological-aspects are easier to expand than others and plan your time accordingly.

Have a good start!

See more

You can also try starting with one of the big marketing agencies. Even if you don't feel like you're ready to start as a web developer (you likely are, though, they hire at all levels) you can start as a content author or similar supporting role until you're more comfortable, then transition into a development role within the same company when you're ready.

See more
Shanover Saiyed
Software Engineer (Web) · | 4 upvotes · 19.2K views

I would recommend you to learn these quickly and get on learning a good front-end framework like Vue, ReactJs, Svelte. Pick up real world projects not just learn from books. Always keep learning about the new technologies used to develop things because IT Web development tools and their approach is growing faster than ever, you have got to keep up with those new techs and tools. Final advise, open any job portal, find your targeted job and see what requirements are their.

See more
Jose Vargas

JavaScript is an ever growing technology with lots of opportunities and great depth for both front end and back end development. I would say that JavaScript is a safe bet in terms of furthering your career as a developer in 2022 and beyond. There’s lots of tools and frameworks based on this language that you would have to make decisions on which ones you want to become an expert. I recommend you follow interesting people that you admire to draw inspiration from. Such as Ben Awad or Jeff Delaney. Check this web page recommended to me by the latter on his YouTube channel “Fireship”:

See more

I don't believe that you are confident about your decision to follow a career path as a developer. This migh be your department's fault and not necessarily yours. Most good developers are already working as developers at that age. Although your current status states that you are an intern you are struggling to find a good starting point. Since you are interested in website developmnet you can start learning programming using a mainstream CMS such as wordpress. Do you know how many companies and self employed guys make their living by customizing wordpess? But if you want to step out of the crowd then seek for junior jobs on a fintech or on a vertical market such as travel or betting. Search for online job oportunities and find out what technologies these guys use then take an online course and start learning the language. Within a month or two apply for a job as a junior and use as reference the online course.

See more

this article might help you. Web development is a combination of skills. not only developing skills but also SEO and other stuff.

See more

JS + HTML + CSS only tackles the front-end of programming. I suggest you can start to learn by finding an open API related to something you love and then creating a website for it. (E.g. movies, documentaries, music, whatever you are into) Also you can do this dude's tutorials

Later on, when you've already one a few projects, start to learn the backend side of things (database + whatever you want - C#, Python...)

See more
Needs advice


I want to generate dynamic CSS for each user with an expiry link.

I've created a cloud-based tool (Example - where people can create tables and use them on their website by pasting the HTML generated by the tool.

Now, there are a few styling options needed, which can be done using CSS. As of now, I'm asking the users to copy the CSS and paste it in the "Custom CSS" section, which is a bit hectic work as they need to change the CSS every time if I make any changes to the styling.

So, I'm just wondering if there's a way to generate dynamic CSS for each user with an expiry link.

Currently, I have around 200 users, and what's the best way to do it?

See more
Replies (2)

The best way, as usual, is a "it depends".

Still I would go to something as simple as storing the expire date+the generated css and other metadata in a table. If a user tries to access something that is expired than he's redirected to a specific page. Periodically (like once a day), a janitor process deletes the old data.

See more
Grant Steuart

Instead of having the user copy and paste the CSS directly, have them copy and paste the HTML that will include an external CSS file generated and hosted by your application. This will allow you to control when the stylesheet is updated as well as control privileges on who can request the file. Additionally, using a CDN service (e.g. Cloudflare) will allow you to cache the static assets being requested reducing overall server load.

When your server (and optionally CDN) no longer are serving the file, consider the link expired. Unique URLs can be generated using a multitude of methods but maybe consider if there is any benefit to the users if it follows the scheme: rather than something like:

See more
Needs advice

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 · | 8 upvotes · 73.3K views

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

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
pascal carrié
developper at self-employed · | 4 upvotes · 67.7K views

ruby got better and better, rails is outstanding. Listen David Heinemeier Hansson : I recommend you to read Otis Meyer and Don't bother what's they say, just enjoy programming

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

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
Ekapob Ukritnukun
Software Engineer at App47, Inc. · | 4 upvotes · 67.6K views

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
Joost Baaij
Internet creator. at Space Babies · | 3 upvotes · 50K views

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
Decisions about HTML5 and Ruby
Mark Esser
Senior Tech Recruiter at i22 Digitalagentur GmbH · | 8 upvotes · 45.4K views

A developer and project manager from our team X says the following about our use of Rails at i22:

"We use Rails to build stable and flexible backend systems. Rails is extremely good for managing data structures and quickly setting up new systems. It is the perfect base for most use cases."

I asked the same Team X member why the team prefers to work with Ruby on Rails, rather than Python and Django:

"Because Python is a scripting language and from my point of view not suitable for building stable web services. Python is for me rather good for scripts and fast small tools. Not for stable business applications. And if I want it fast I prefer Go."

See more
  • Client-Side: \ The form of our product is a web app because we would also provide a dashboard for displaying data and for some further purpose including data filtering and comparison. Hence, we would definitely use HTML5 for structuring the web, CSS3 for styling the web, and JavaScript for building the front-end logic. As for frameworks, we would use React because it is component-based that can keep our front-end code clean and organized. The virtual DOM of React also provides better efficiency in time when rendering the page. Furthermore, React has a greater number of users than Vue and Angular, thus have active communities for problem-spotting and problem-solving. We would also incorporate Bootstrap into our web app to provide an aesthetic user interface and thus to improve the user experience. The fact that Boostrap supports responsive site would also ease our workload if future adaptation for mobiles is needed.
See more


  • For our web app frontend, we decided to use TypeScript as our programming language because it supports all functionality of JavaScript and supports optional typing to the language, which can help us take advantage of OOP.
  • We chose ReactJS as our frontend library because its state management would be very handy for our single-page app. React is also component-based, which can help us improve the modularity and extensibility of the project.
  • Aside from the standard web technology HTML/CSS, we will useBootstrap to style UI components and make our web app responsive to different screen sizes.
See more
Ing. Alvaro Rodríguez Scelza
Software Systems Engineer at Ripio · | 12 upvotes · 250.7K 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 · 437.1K 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, 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

A major part of our project includes visualizing the data through graphs and charts. We chose to use d3.js since it provides a wide selection of well-designed graphics and animations. As a library, it is also easy to use and be included in our UI. JavaScript which our team has experience with was also selected to integrate graphics from d3.js into the UI, as well as to integrate the UI with the backend system. Along with JavaScript, HTML5 and CSS 3 are also selected mostly for styling and formatting the webpage. These three languages are widely used which means that more support will be available, making the implementation process easier.

See more
Labib Chowdhury
Student at University of Toronto · | 5 upvotes · 84.9K views

The key to our product relies on explainability and user experience when using our product. With this is mind, it is important to build a clean, readable web interface that a user will be able to navigate easily and quickly debug their security issues. The stack chosen for the interface of our product includes: JavaScript + React, CSS, HTML, Material UI and D3.js.

React provides us with simplicity to allow us to deliver the MVP as soon as possible. React also has multiple open source libraries to ease our development. Being able to reuse React components will help in developing the product fast as well as making the user interface modular. Since we're using React, we will also be using JavaScript, HTML, and CSS to create the frontend.

To design the UI, using a minimal approach would be the best solution. The Material UI library provides us with minimal and aesthetically pleasing React Components which would make our frontend look pleasing to the user.

Finally, our UI will consist of displaying information from our Machine Learning model in a dashboard type view. To display data in tasteful manner, we have chosen to use the D3.js library. This library is the most popular data visualization library for React with over 80k stars on Github. D3 also provides seamless compatibility with React and has a variety of features which would make the data we produce visually pleasing.

See more
Xinyi Liu
Software Developer at BigClarity · | 6 upvotes · 269.5K views

As our team will be building a web application, HTML5 and CSS3 are one of the standardized combinations to implement the structure and the styling of a webpage. Material-UI comes with all sorts of predesigned web components such as buttons and dropdowns that will save us tons of development time. Since it is a component library designed for React, it suits our needs. However, we do acknowledge that predesigned components may sometimes cause pains especially when it comes to custom styling. To make our life even easier, we also adopted Tailwind CSS. It is a CSS framework providing low-level utility classes that will act as building blocks when we create custom designs.

See more
Nathan De Pachtere
Fullstack Developer at Alpsify · | 8 upvotes · 66.5K views
Shared insights
CSS 3CSS 3HTML5HTML5JavaScriptJavaScript

Am I the only one to think that libraries like Bootstrap, Vuetify, Materialize, Foundation are too much sometimes ?

Most of the time you are loading all the library and using 10% of it. And on that 10% you are modifying 90% of it.

I feel like using grid and pure CSS / JS are enough and cleaner.

See more
Andrew Carpenter
Chief Software Architect at Xelex Digital, LLC · | 16 upvotes · 302.7K 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
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of HTML5
Pros of Ruby
  • 447
    New doctype
  • 389
    Local storage
  • 334
  • 285
    Semantic header and footer
  • 240
    Video element
  • 121
  • 105
    Form autofocus
  • 100
    Email inputs
  • 85
    Editable content
  • 79
    Application caches
  • 10
    Easy to use
  • 9
    Cleaner Code
  • 4
  • 4
  • 3
  • 3
  • 3
    Audio element
  • 3
  • 2
    Semantic Header and Footer, Geolocation, New Doctype
  • 2
    Content focused
  • 2
  • 2
  • 1
    Very easy to learning to HTML
  • 603
    Programme friendly
  • 535
    Quick to develop
  • 487
    Great community
  • 467
  • 429
  • 271
    Open source
  • 233
  • 203
  • 155
  • 138
    Powerful one-liners
  • 67
  • 57
    Easy to learn
  • 49
    Easy to start
  • 41
  • 36
  • 30
  • 20
    Fun to write
  • 19
    Diverse web frameworks
  • 12
    Reads like English
  • 9
  • 9
    Makes me smarter and happier
  • 8
    Elegant syntax
  • 7
    Very Dynamic
  • 6
  • 5
    Programmer happiness
  • 4
    Generally fun but makes you wanna cry sometimes
  • 4
    Fun and useful
  • 4
    Object Oriented
  • 3
    Elegant code
  • 3
  • 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 HTML5
Cons of Ruby
  • 1
    Easy to forget the tags when you're a begginner
  • 1
    Long and winding code
  • 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

- No public GitHub repository available -

What is HTML5?

HTML5 is a core technology markup language of the Internet used for structuring and presenting content for the World Wide Web. As of October 2014 this is the final and complete fifth revision of the HTML standard of the World Wide Web Consortium (W3C). The previous version, HTML 4, was standardised in 1997.

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 HTML5?
What companies use Ruby?
See which teams inside your own company are using HTML5 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 HTML5?
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


Oct 24 2019 at 7:43PM


Jun 6 2019 at 5:11PM


What are some alternatives to HTML5 and Ruby?
Android SDK
Android provides a rich application framework that allows you to build innovative apps and games for mobile devices in a Java language environment.
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.
The core software is built by hundreds of community volunteers, and when you’re ready for more there are thousands of plugins and themes available to transform your site into almost anything you can imagine. Over 60 million people have chosen WordPress to power the place on the web they call “home” — we’d love you to join the family.
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!
AngularJS lets you write client-side web applications as if you had a smarter browser. It lets you use good old HTML (or HAML, Jade and friends!) as your template language and lets you extend HTML’s syntax to express your application’s components clearly and succinctly. It automatically synchronizes data from your UI (view) with your JavaScript objects (model) through 2-way data binding.
See all alternatives