xutopia

In the local Rails community where I live we haven't used Heroku for a while now. Most of us have moved on to using Kamal with a VPS of our choice. The surprising benefit is that you can even host multiple rails app on a single VPS so it is ideal for playing around with multiple hosted apps.

As for raw performance I'm sure you'd get better deal with Elixir out of the box than Rails out of the box but if you wanted to keep all the benefits of Rails and scale websocket usage look into AnyCable.

I love how this article reads more like the individual ignores features and capabilities of other frameworks to then state that the framework he chose is better.

Rails has everything he mentions as an advantage of Phoenix. He's also implying that Rails does not use web sockets to communicate with frontend which is not only wrong it should be evidently wrong to anyone who built a Rails app in the last 3 years.

That's not to say that Phoenix and LiveView aren't phenomenal tools, they are! However what's keeping me in the Rails world is Hotwire Native. I truly feel like a one man army building mobile and web apps in a quick turnaround time.

The most likely danger with AI is concentrated power, not that sentient AI will develop a dislike for us and use us as "batteries" like in the Matrix.

While there will be spots where a human will be replaced by AI there won't be nearly as much as people think over the next decade.

What is the reasoning behind such a move? Is it just pure corruption (ie: Qatari plane and base) or is it something else?

You're not getting it. A modern Rails 8 application has so few lines of JS that you don't have to deal with all the problems you introduce with a heavy JS application.

I agree with the sentiment on this. I'm building applications that are easily converted to native mobile apps with minimal code and engineers left and right are telling me I should use 60 different libraries and frontend tools to reach the same goal.

Meanwhile Rails is becoming easier and easier to run complex apps with much smaller teams.

Apple folded way too easily to authoritarian demands and gives us no option to circumvent their walled garden. I've been a long time iPhone user (since the first one) and I'm not going to be purchasing another one.

Meta for a company meant to connect people is doing its darnest to reel us into a virtual world rather than the real one.

Imagine seeing everyone with glasses with suspicion because you don’t know if they’re filming you, reading notifications or actually conversing with you.

For me the main thing is that search is now more prominent for a lot of apps (this is even more true on iOS). It used to be that we had to go to the top on iOS to get search but now it's always at the bottom near the fingers.

React is a bad idea imo. I see small teams do way better with plain old HTML augmented with minimal Javascript. React itself is huge to download and slower to execute. I can't believe we're still stuck in React world.

That's because people don't trust AI that much... and most people don't differentiate between a really cool feature and AI so it's more confusing marketing than anything.

A lot of people who put their phone in their pockets do.

It's horrible how much Apple controls the market. I know of one startup who got shut out of the market because Apple considered there were already enough apps of that kind on their App Store. In many instances if you can't have a mobile app your startup is dead before it started.

I can't possibly recommend class based CSS soup anymore. Once you go with utility classes it's hard to go with anything else. It's super intuitive, you don't have to dig through loads of CSS files to figure out where the CSS is and you can simply remove or add classes as you need and see it right there in front of you.

Evidence to the contrary exists through. That our body is an antifragile system. If you apply the right stimulus it gets better at fending off for itself. We know from ample studies that darker skin gets less skin cancer. We know gradual exposure makes skin darker. Why is it so hard to fathom that maybe it’s a good mechanism for making our body more capable? Is it because a cute song tells us to always wear sunscreen?

This pisses me off to no end. I paid a lot... I expected my Nest gear to work for as long as I own my house. I paid extra to get someone to install it with my home system. Now I see that my Nest Protect is saying it needs to be changed... not some small module... the whole thing. Next will be my thermostats... I can't understand why I'd pay for them again.

The way the notebooks are built allow for passive cooling, fans are actually quieter and the CPUs run colder at same workloads as proven by cinebench per watt test. It's not just a simple thing.

Google is making harder and harder to depend on their software.

As a Nova Scotian I can tell you it was present before 2000s... at least 90s.

I love that theory. I very much spent time thinking that it would be cool if we were inside a black hold after reading A Brief History of Time.

I just ask ChatGPT based on the weight of the food I eat and it gives me pretty accurate results.

For me it's taking a walk.

Rails/Ruby is still top 10 on Github landscape in Pull Requests. Though it's lived through a relative decline people talk about it less because a lot of other frameworks and languages have improved in light of what the ecosystem had.

That said I feel like Elixir/Phoenix is doing a lot of things right today and if I were invested in one or the other I'd stick with that one. But I'm more of a bootstrapper than someone who looks for a job. Ruby is #8 in Pull Requests and Elixir #24 on Github. Source: https://madnight.github.io/githut/#/pull_requests/2024/1

If I were just looking to be marketable I'd consider Python, Java or Go... but I don't love working in those languages as much as I do Ruby (or Elixir for that matter).

That's crazy to not have responded to his repeated requests!

The majority of projects have their workers idle 98% of the time. When you do get to the point where you need the kind of optimizations you are talking about it is relatively easy to make the change. Solid Queue is easy, out of the box, works as is.

I think there are a lot of Rails developers available. The concern many devs have is that they fear they can't get a job anymore (they're mostly mistaking the downturn of the entire market for one limited to Rails).

If you mean codebase complexity and team size... then yes... types is more helpful with that. But in a small team with a small codebase you don't need types to do really well. I find types helped a lot when multiple teams were responsible for different domain spaces inside different components of a Rails app. I never saw the same advantage in codebases that are much smaller with fewer people.

I started my app using Rails and Hotwire/Stimulus and honestly finding myself way more productive than I did with more JS heavy options. Everything just works so nicely together in the Rails world.

I see what you mean but I have never found it to be an issue even in large codebases. Sorbet and RBS have been problematic. Lots of development slows down with these solutions. I wished it had something baked into the language as well but I'm happy without... just following conventions alone has worked really well for me.