The amount of new languages and "the absolute best framework" makes me think that big enterprises should never leave Java. Fancy project written on a newest tech is legacy before it is published. Scary from the business point of view. Disclaimer: I love Ruby.
Show HN: Compile Ruby to C
51–60 of 110 posts
Re: Show HN: Compile Ruby to C
#52Imagine going all in on a Ruby project with this specialized library that literally changes the way you write Ruby and still thinking that's a good idea. Keep Ruby as it is - slow and expressive. If you need to speed up, get faster hardware.
> Keep Ruby as it is - slow and expressive.
Why not try to make Ruby faster without changing how expressive it is? I don't think this project does that by the way - it breaks Ruby semantics - but let's aspire to make Ruby faster.
> If you need to speed up, get faster hardware.
If your code is still too slow for your required per-request latency on a top-of-the-range Xeon and your individual requests have no useful parallelism and are not memory or IO bound... where do you go from there? Where are you getting faster hardware from?
Sometimes there is no faster hardware.
Re: Show HN: Compile Ruby to C
#53The obvious performance and bloat overhead with RoR aside, I have yet to see a framework and ecosystem that lets you have a programmable web application up and running with typical features in comparable time. For shipping new products or testing out ideas, I have not come across a more optimal framework in terms of going from idea to market. Most often I've tried Phoenix, Django and Laravel as alternatives, but all…
This is what brought me to RoR land... and this is what made me leave. I agree rapid prototyping is an excellent point for RoR but when you need to actually evolve the project for years, it gets really tedious and hard. So for a dev shop RoR is quite fine -- you make the project, do very little iteration on it, and ship. That works well and I've experienced it. For longer-lived projects however, Phoenix is miles ahea…
In your experience, is there good resource for discovering the "de-facto" hex packages for a particular requirement - I end up Googling things like "Phoenix paperclip equivalent" and then evaluating all the various ones.
Alternatively are there some good "kitchen sink" open source projects that implement many of the typical web application features like auth, uploads, etc. ?
Companies like thoughtbot have been a gold mine of information and battle-tested practices - is there anyone similar in the Phoenix space that's worth following?
Re: Show HN: Compile Ruby to C
#54Imagine going all in on a Ruby project with this specialized library that literally changes the way you write Ruby and still thinking that's a good idea. Keep Ruby as it is - slow and expressive. If you need to speed up, get faster hardware.
> ...If you need to speed up, get faster hardware.
So if I need to speed up my Rails application on a AWS, GCP or Azure instance, you're telling me in order to increase performance, I need to upgrade to hardware that is able to take at least 4 to 6+ GB of RAM, to modern hardware on each of the servers I have to make it go faster?
Not only that it will still be slow, very expensive and an unnecessary waste of money (Given the absolutely huge cloud costs), it shows that it doesn't scale efficiently to save on costs at all. Oh dear.
This is like saying, "Can you please get a new laptop with 16GB RAM to let my hungry electron apps eat the RAM it wants?, 4GB RAM is not enough and literally causes starvation."
EDIT: To downvoters: Oh so the high overhead and heavy resources of a Rails app and upgrading your instances to new hardware and more RAM requirements is justified with the extremely high cloud infrastructure costs then? Explain your reasons if this is the case.
By the way, I don't want to see your gigantic operating costs if you're running Docker & Kubernetes on a multi-instance Rails stack.
Re: Show HN: Compile Ruby to C
#55Imagine going all in on a Ruby project with this specialized library that literally changes the way you write Ruby and still thinking that's a good idea. Keep Ruby as it is - slow and expressive. If you need to speed up, get faster hardware.
> Imagine going all in
> "a basic proof of concept"
Re: Show HN: Compile Ruby to C
#56The obvious performance and bloat overhead with RoR aside, I have yet to see a framework and ecosystem that lets you have a programmable web application up and running with typical features in comparable time. For shipping new products or testing out ideas, I have not come across a more optimal framework in terms of going from idea to market. Most often I've tried Phoenix, Django and Laravel as alternatives, but all…
Spring Boot Kotlin is worth giving a go. It has rapid prototyping abilities, but underlying Java promise of easy refactoring, great tooling. I recently refactored entire frontend and parts of backend code without ever having to restart server.
Re: Show HN: Compile Ruby to C
#57Imagine going all in on a Ruby project with this specialized library that literally changes the way you write Ruby and still thinking that's a good idea. Keep Ruby as it is - slow and expressive. If you need to speed up, get faster hardware.
> Keep Ruby as it is - slow and expressive. Why not try to make Ruby faster without changing how expressive it is? I don't think this project does that by the way - it breaks Ruby semantics - but let's aspire to make Ruby faster. > If you need to speed up, get faster hardware. If your code is still too slow for your required per-request latency on a top-of-the-range Xeon and your individual requests have no useful pa…
Ruby is getting a JIT in 3. So it's happening. I'm always supportive of small projects and this is no exception. Still, it is going to get crowded out by the generalized offerings of Ruby 3.
There may be some benefit to ultra specialized for this project to live in still but the audience is going to be quite niche.
Re: Show HN: Compile Ruby to C
#58The obvious performance and bloat overhead with RoR aside, I have yet to see a framework and ecosystem that lets you have a programmable web application up and running with typical features in comparable time. For shipping new products or testing out ideas, I have not come across a more optimal framework in terms of going from idea to market. Most often I've tried Phoenix, Django and Laravel as alternatives, but all…
Spring Boot Kotlin is worth giving a go. It has rapid prototyping abilities, but underlying Java promise of easy refactoring, great tooling. I recently refactored entire frontend and parts of backend code without ever having to restart server.
How is the ecosystem? For example - if I want to add auth, social login, profile picture and admin dashboard CRUD, are there mature packages that can be leveraged for these features?
Re: Show HN: Compile Ruby to C
#59Earlier quoted context omitted.
This is what brought me to RoR land... and this is what made me leave. I agree rapid prototyping is an excellent point for RoR but when you need to actually evolve the project for years, it gets really tedious and hard. So for a dev shop RoR is quite fine -- you make the project, do very little iteration on it, and ship. That works well and I've experienced it. For longer-lived projects however, Phoenix is miles ahea…
In your experience, is there good resource for discovering the "de-facto" hex packages for a particular requirement - I end up Googling things like "Phoenix paperclip equivalent" and then evaluating all the various ones. Alternatively are there some good "kitchen sink" open source projects that implement many of the typical web application features like auth, uploads, etc. ? Companies like thoughtbot have been a gold…
Sadly there aren't many better ways. For the moment the best course of action is to search on ElixirForum. Even if I love the language and still look for ways to work with it (in my new job where it isn't used) I recognize that the ecosystem is not that big.
For auth, the core Elixir team has made one prototype but I am not sure if they'll pursue it further. Outside of that, use Pow. For file attachments: Waffle. Authorization: CanCan, although the area has several very solid options, I heard.
Discoverability can indeed be a problem. Covid-19 hit everything pretty heavily and Elixir's community is no exception. Just a month ago people started finally hiring for it again (on the forum).
Re: Show HN: Compile Ruby to C
#60Earlier quoted context omitted.
This is what brought me to RoR land... and this is what made me leave. I agree rapid prototyping is an excellent point for RoR but when you need to actually evolve the project for years, it gets really tedious and hard. So for a dev shop RoR is quite fine -- you make the project, do very little iteration on it, and ship. That works well and I've experienced it. For longer-lived projects however, Phoenix is miles ahea…
What makes you say it is hard to maintain longer lived projects? (I used to be a RoR developer for a few years, so I'm curious about other people's experiences.)
It's mostly the "magical" parts like before/after hooks. When you are tracing a bug and are trying to do step-by-step debugging, it has been hell. Quickly jumping to definitions? Even RubyMine can't do it.
Furthermore, as the project grows, you need to introduce something more/bigger than MVC and people put these files everywhere. Sure it's a management problem but it doesn't help that people don't do the right thing by default.
In general, there's a breaking poing that you will very soon hit when you try to just pile things on top.