"tl;dr: if you want to do web development but dislike Rails, your best bet is probably to switch to a different programming language than Ruby."
But... wasn't this the underlying point of Solnic's opinion piece?
Due to Rails "well deserved" domination in the web framework space, POROs never had a chance of contributing to friendly and just competition across the Ruby community. We simply ended up with shitty alternatives because no one was given the proper chance to be BETTER Rubyists.
They just kept eating the gluten and feeling the allergy pains, so to speak.
I concur. Coming from São Paulo, Brazil, I thought Akita's post was well written and derived out of positive, lightly spoken, opinion. Breath of fresh air against the backdrop of hostile tech machoism.
Couldn't agree more, and came here to say this also. I understand that they are driving forward with new features for developers, but security cannot be taken seriously enough when they are hosting organisation's private code. I cannot take them seriously until they add this feature.
I just don't get the reticence to implement it - I added 2FA to a customer facing app we produce in less than a week - and most of that time was coming up with a nice/pretty setup workflow to enable it on your account.
