Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Why we still build with Ruby

getlago.com

Post reply on HN
Print view View original

31–40 of 94 posts

Re: Why we still build with Ruby

#31

Post by tekknolagi »

ksec wrote: post #20

I am hoping we have even more surprises in Rails World in two weeks time. And may be a glimpse of ZJIT? It is not just Ruby and Rails has gotten faster, CPU performance and core count has been getting cheaper. One thing I forgot to post last time in the GitHub CEO step down thread. I am hoping Microsoft won't force GitHub to move away from Ruby Rails. I remember there were some noise early on during the acquisition M…

Re: ZJIT: all development is happening in the open in the zjit folder of the ruby/ruby repo. You can follow along!

Re: Why we still build with Ruby

#32

Post by AlienRobot »

doublerabbit wrote: post #8
rafark wrote: post #4

Earlier quoted context omitted.

It’s the same thing with php. I would say it’s probably because they are languages from the 90s, but then you have python and JavaScript which are from the same era too and people never question their relevance or “modernity”. All of these languages (even java) have been in constant development since then and all of them have modern features. Why are some considered modern and some outdated when they are all basicall…

PHP typically required a web-server, system administration which is old fashioned. No one wants to do that which is fine as it keeps me employed. When Ruby made western presence it was clunky. No one knew what it was and it got stuck with that personality. It had an ecosystem too but never hooked in to the western world. Java is tainted by Oracle and seen as "business". And it's also weird how Postgres has made an up…

How is it possible that we have this many programming languages and every single one is worse than the other?

Re: Why we still build with Ruby

#33

Post by tonyhart7 »

vindin wrote: post #2

I don’t understand why Ruby and Rails get a reputation for being outdated or “legacy.” Over the last several years both have seen massive numbers of contributions, both in improvements and new features. I’d be surprised if any tool for building a new web app could even come close to what Rails has to offer across the full stack.

because they are not javascript??? you realise that ruby and php still need to interact to JS in the end

so why not use JS directly or build on top of that???? that's what people do

Re: Why we still build with Ruby

#35

Post by realusername »

tayo42 wrote: post #12
vindin wrote: post #2

I don’t understand why Ruby and Rails get a reputation for being outdated or “legacy.” Over the last several years both have seen massive numbers of contributions, both in improvements and new features. I’d be surprised if any tool for building a new web app could even come close to what Rails has to offer across the full stack.

For anything else you might use ruby for you can use python, so you might as well just use python. If rails is the best at making web apps, and other ecosystems in other languages maybe get you 90% of the way, might as well use something else and not deal with ruby sucking at other jobs.

I'd say that other frameworks get you 70% of the way of Rails maximum and if that's what your building, it doesn't help knowning that the language is better in other areas you won't use.

Re: Why we still build with Ruby

#36

Post by Alifatisk »

cosmic_cheese wrote: post #15
tayo42 wrote: post #12

Earlier quoted context omitted.

For anything else you might use ruby for you can use python, so you might as well just use python. If rails is the best at making web apps, and other ecosystems in other languages maybe get you 90% of the way, might as well use something else and not deal with ruby sucking at other jobs.

Surely language preference factors in somewhere. Python is opinionated and not everybody’s cup of tea.

I prefer Ruby because of it's flexible meta-programming capabilities, like I would easily draft my own DSL if I have an idea of how I want the syntax to look like. This is such a powerful and underrated feature of Ruby in my opinion

Re: Why we still build with Ruby

#37

Post by Alifatisk »

vindin wrote: post #2

I don’t understand why Ruby and Rails get a reputation for being outdated or “legacy.” Over the last several years both have seen massive numbers of contributions, both in improvements and new features. I’d be surprised if any tool for building a new web app could even come close to what Rails has to offer across the full stack.

It's because it's not receiving a constant hype that other fullstack frameworks have, so people thing it's outdated. But in reality, Rails is boring, it's a beast and it just works

Re: Why we still build with Ruby

#38

Post by voidfunc »

doublerabbit wrote: post #8
rafark wrote: post #4

Earlier quoted context omitted.

It’s the same thing with php. I would say it’s probably because they are languages from the 90s, but then you have python and JavaScript which are from the same era too and people never question their relevance or “modernity”. All of these languages (even java) have been in constant development since then and all of them have modern features. Why are some considered modern and some outdated when they are all basicall…

PHP typically required a web-server, system administration which is old fashioned. No one wants to do that which is fine as it keeps me employed. When Ruby made western presence it was clunky. No one knew what it was and it got stuck with that personality. It had an ecosystem too but never hooked in to the western world. Java is tainted by Oracle and seen as "business". And it's also weird how Postgres has made an up…

Postgres didn't really become the darling of SQL databases until rather recently.. i'd say the last 5-10 years. It was a clunky DB back in the day compared to MySQL.

Re: Why we still build with Ruby

#40

Post by jmuguy »

vindin wrote: post #2

I don’t understand why Ruby and Rails get a reputation for being outdated or “legacy.” Over the last several years both have seen massive numbers of contributions, both in improvements and new features. I’d be surprised if any tool for building a new web app could even come close to what Rails has to offer across the full stack.

Since it doesn't have as much interest from FAANG people treat it like its dead meat. Rails powers a ton of smaller apps (and some very large ones) but everyone thinks their idea is the going to be the second coming and therefore it needs all the insane optimizations that power Google etc.
Post reply on HN