11–20 of 42 posts
Maybe start moving away from Ruby on Rails. Good web stacks in Golang and Rust do exist and at that scale they're likely the only sensible choices. How far must the sunk cost fallacy go before something is done?
Maybe start moving away from Ruby on Rails. Good web stacks in Golang and Rust do exist and at that scale they're likely the only sensible choices. How far must the sunk cost fallacy go before something is done?
Which Golang or rust web stacks are as good as rails?
Meaning that at one point extra programmer difficulty is worth it if your everyday web stack can't keep up.
Maybe start moving away from Ruby on Rails. Good web stacks in Golang and Rust do exist and at that scale they're likely the only sensible choices. How far must the sunk cost fallacy go before something is done?
Rails is a huge problem, but the most mature libraries/frameworks in Go/Rust are all micro-frameworks, which isn't much of a replacement. Maybe some .NET frameworks would be a better choice.
Though I'd personally do it in Elixir but again, speed. GitHub is huge and should rise up to the challenge.
Earlier quoted context omitted.
Which Golang or rust web stacks are as good as rails?
I'm not saying they are as good -- I'm saying that they are good. Meaning that at one point extra programmer difficulty is worth it if your everyday web stack can't keep up.
Earlier quoted context omitted.
I'm not saying they are as good -- I'm saying that they are good. Meaning that at one point extra programmer difficulty is worth it if your everyday web stack can't keep up.
Oh I see. It’s difficult to justify replacing rails, that has been successfully used for many years, by something not as good (worse?).
My point is that if the stack regularly falls over then the programmer convenience has to be sacrificed in favor of stable and mega-fast alternative that requires more programmer energy.
I love working with dynamic languages. I can prototype almost anything that I want to do, in hours. But I also recognized the need for a hardcore stack for a previous contract and went the long and painful route with Rust.
Result: the project is running for 7 months now, has only been restarted 4 times for updating it (re-deployment), never crashed once, handles 5000+ network connections and streams data from them 24/7.
Peak CPU usage on a 4-core VPS: 27%.
Peak memory usage: 180MB. Normal average memory usage: 80MB.
Right tool for the job.
I'm not sure about the technical details behind their outages since they're a little vague on that, but it's funny how every Rails developer champions Github as a Ruby on Rails shop as why Rails should continue living on when their availability is some of the worst in the tech scene. Lazy evaluation is great until it's not.
Isn't it GitHub Actions that has been having the availability problems for a while now? It started having problems after Microsoft acquired GitHub and there has been speculation that it is because it was ported to .NET and Azure. Is codespaces created with Rails?
Earlier quoted context omitted.
Oh I see. It’s difficult to justify replacing rails, that has been successfully used for many years, by something not as good (worse?).
Rails is convenient and intuitive, I don't think anyone reasonable is arguing that. My point is that if the stack regularly falls over then the programmer convenience has to be sacrificed in favor of stable and mega-fast alternative that requires more programmer energy. I love working with dynamic languages. I can prototype almost anything that I want to do, in hours. But I also recognized the need for a hardcore sta…
I'm not sure about the technical details behind their outages since they're a little vague on that, but it's funny how every Rails developer champions Github as a Ruby on Rails shop as why Rails should continue living on when their availability is some of the worst in the tech scene. Lazy evaluation is great until it's not.
Isn't it GitHub Actions that has been having the availability problems for a while now? It started having problems after Microsoft acquired GitHub and there has been speculation that it is because it was ported to .NET and Azure. Is codespaces created with Rails?
I'm not sure about the technical details behind their outages since they're a little vague on that, but it's funny how every Rails developer champions Github as a Ruby on Rails shop as why Rails should continue living on when their availability is some of the worst in the tech scene. Lazy evaluation is great until it's not.
Isn't it GitHub Actions that has been having the availability problems for a while now? It started having problems after Microsoft acquired GitHub and there has been speculation that it is because it was ported to .NET and Azure. Is codespaces created with Rails?
Earlier quoted context omitted.
Rails is convenient and intuitive, I don't think anyone reasonable is arguing that. My point is that if the stack regularly falls over then the programmer convenience has to be sacrificed in favor of stable and mega-fast alternative that requires more programmer energy. I love working with dynamic languages. I can prototype almost anything that I want to do, in hours. But I also recognized the need for a hardcore sta…
Why do you assume the outages are language related and not due to the complex product having bugs? How does Rust prevent bad schema changes or missing data in the DB?
Obviously I can't know for sure but it's not an uninformed assumption.