ActiveRecord::Persistence defines an update instance method, accepting attributes, that tries to save to database and returns false if it did not work.
It also defines .update class method, accepting id and attributes, that returns object no matter if persisting succeeded.
This is most Rails thing I discovered in a while.
Holy crap, google is apparently taking down all/most fediverse apps from google play on the grounds that that some servers in the fediverse engage in hate speech. At least three apps I know of anyway and I'd imagine the others will follow soon under the exact same reasoning.} Seems to be the case with Husky, Fedilab, and "subway" tooter.
this is a scary precedent if google play is going to ban any apps that can in any way be used to access content with hate speech. So what about a forum client, do they take that down just because there is a forum somewhere on the internet posting hate speech?
This is particularly worrisome because for most people Google Play is the only way they understand to install apps at all.
Picture attached of one of the notices received by fedilab.
I might have found an architectural/code organisation pattern to "fix" Rails, i.e. no quickly end up with unmaintainable entangled mess. I coded a small REST API with it and:
* I was able to add new endpoint+feature as fast as with Rails Way
* Whole application logic was coded and tested before writing any controller code
* Seventy-something tests for 8 endpoints run in under a second
Okay people, we've seen #Mozilla degrade more and more for years, and we've always hoped it will find its way and get better.
Now people working on Developer Tools, #MDN, and the Rust team - arguably some of the most useful and valuable teams at Mozilla - have been laid off, to make space for more profit making activities.
This is utter bullshit.
But perhaps this is also an opportunity. The FLOSS community forked OpenOffice, XFree86, and other huge projects.
TestBench - a new test framework for Ruby from the creators of Eventide:
"Open source maintainer apologizes for having a daytime job"
It's been a while since I wrote a blog post. Here's one from few days ago about using profiling tools to understand how Ruby apps work: https://katafrakt.me/2020/05/03/understanding-ruby-app-with-profiling/
Interesting thread on Twitter about Rails, Spring and Bootsnap: https://twitter.com/avdi/status/1256743699859603457
Personally I think Bootsnap is pretty good, although it does not need to be added right away for every Rails app. Spring on the other hand only causes problems.
A Mastodon instance for Rubyists & friends