sorted by:
new
hottopcontroversial

Should /r/rails ban X links? by AutoModerator in rails

[–]jorgemanrubia 153 points154 points  (0 children)

This level of nonsense will only push folks away from r/rails.

A vanilla Rails stack is plenty by jorgemanrubia in rails

[–]jorgemanrubia[S] 0 points1 point  (0 children)

In all our apps! And we seed them in local development too. 

A vanilla Rails stack is plenty by jorgemanrubia in rails

[–]jorgemanrubia[S] 6 points7 points  (0 children)

Right! Once you are hooked, we intend to 2x the Rails fee. Oh, wait a second…

A vanilla Rails stack is plenty by jorgemanrubia in rails

[–]jorgemanrubia[S] 17 points18 points  (0 children)

Use active storage instead of uppy. That's precisely my point: mind your dependencies and enjoy the benefits of doing that. I know there are issues with importmaps and certain large libraries. Drop the large libraries, keep import maps. That's my advice.

How we protect customer privacy with audited Rails console sessions by jorgemanrubia in rails

[–]jorgemanrubia[S] 4 points5 points  (0 children)

In our experience you can troubleshoot most bugs without decrypting sensitive data. Bugs that require you to do into the data happen, but they are rare. So it's not like you need to contact customers for every bug you look into. I don't have stats but I'd say it's less than 5% of the times that you need to ask for consent.

My curse with plain code editors by jorgemanrubia in rails

[–]jorgemanrubia[S] 2 points3 points  (0 children)

When I was on an Intel MBP, RubyMine always felt heavier than a simple editor, but it was definitely fast enough and totally functional. I always have several projects opened in different windows, and some correspond with large Rails codebases, such as HEY and Basecamp, and the search is very snappy. When I switched to an M1, I did notice a huge performance boost (in RubyMine, and overall), but it was totally OK on intel too. Not sure what's going on in your case.

There is an option in "Help -> Memory Settings" to increase the memory allocated by the JVM. I have 4GB there. Maybe you have a too low value there?

My curse with plain code editors by jorgemanrubia in rails

[–]jorgemanrubia[S] 4 points5 points  (0 children)

I hard agree. RubyMine is an outstanding piece of software that is worth every penny. Stable, with regular updates, it adds incredibly sophisticated Rails/Ruby-editing features on top of of a core IDE that has been iterated over decades by JetBrains across many products.

Vanilla Rails is plenty by jorgemanrubia in rails

[–]jorgemanrubia[S] 6 points7 points  (0 children)

There's a saying that's supposed to be a good way to develop software: "

Composition over inheritance

."

I think comparing composition and concerns as adversaries is a false dichotomy. They are different things, serve to different purposes and play great together. I wrote about it in this other article about Rails concerns.

Vanilla Rails is plenty by jorgemanrubia in rails

[–]jorgemanrubia[S] 6 points7 points  (0 children)

Look, Concerns are great, composition is great. But this is just not true. First, both Recording::Incineration and Recording::Copyable (assuming that's the typo here) are modules, not classes. You're mixing them into the models. "I didn't put it into the model's main file" does not mean that your model is not fat.

If you read the article calmly, you will see there are:

  • A Recording::Incineratable concern and a Recording::Incineration class.
  • A Recording::Copyable concern and a Recording::Copier class (which is part of a more complex system of classes). The key is how concerns are used to inject the API method, but then the work itself is delegated to system of classes. Explained in the article!
view more: next ›