👨🏼‍💻 Pro OSS services 🔜 pro-rb.org
đź’ś Core team at @hanamirb/@dry_rb/@rom_rb
đź§ #ADHD #NeuroDiversity
@chris I see, I’d appreciate some info about it. We have a bunch of gems written in a way that crucial parts (and bottlenecks) can be easily rewritten as exts, because those are pure functions (as in, singleton methods, that receive args, and have no side-effects).
In example transproc is used for data transformations, and it’s based on singleton methods. dry-validation uses predicates from dry-logic and they are singleton methods.
@jsrn most of the projects I’ve worked on suffered from poor performance, and I’m not necessarily talking about response times, but things like background jobs processing larger amounts of data that’d take way too long than it should.
Re MRI, it’s hard to tell, really. There are big plans for MRI 3.0 too, but to be honest I’m more excited about TruffleRuby than MRI these days.
Here are 3 things why I believe the future of Ruby can be bright:
1) Lots of modern libraries are growing very fast these days
2) Modern Ruby implementations are in the works, and they show very promising improvements in performance. Especially TruffleRuby[1] and Ruby+OMR[2]
3) Rails seems to have less influence on the ecosystem these days (controversial? maybe)
1) http://chrisseaton.com/rubytruffle/
2) https://developer.ibm.com/open/2016/11/18/introducing-ruby-jit/
Listening to the new Mastodon album. Tooting about it on Mastodon. My head just exploded.
http://www.reactiongifs.com/r/2013/10/tim-and-eric-mind-blown.gif