<jhass[m]>
I've seen more than one useless fight over which one to use. More importantly I've seen more than once even experienced Rubyists stumble upon a new one and being like, "oh, what's that doing?"
motherr has quit [*.net *.split]
gr33n7007h has joined #ruby
pwnd_sfw7 has joined #ruby
motherr has joined #ruby
pwnd_sfw has quit [Read error: Connection reset by peer]
pwnd_sfw7 is now known as pwnd_sfw
<ccooke>
jhass[m]: I've generally felt that it's a bit of the dark side of "there's more than one way to do it"
<ccooke>
jhass[m]: More than one way means you can have different valid approaches to the problem, and that's good. But having multiple functionally identical solutions that only differ in the names of methods? That's... a burden for maintenance and actually a bit of a barrier to entry (because the feeling of confusion over "What does this thing do" is going to last longer)
<nakilon>
how does it compare to sinatra and hanami?
<gearnode>
Roda is a hard fork of gem called "cuba". The main difference with sinatra is the router. In Sinatra the router is flat when it is tree in Roda.
<gearnode>
Roda is basic router compatible with Rack is not relevant to compare it to Hanami. Hanami is more an Rails alternative.
<nakilon>
did anyone make anything big on roda?
<nakilon>
some guys are writing something big in roda+rom+dry+graphql for 5 years and "have some technical debt" -- I wonder how would it feel
<nakilon>
do people add some another gem for JSON API for roda?
Garb0 has quit [Ping timeout: 268 seconds]
<adam12>
nakilon: I haven’t.
<adam12>
nakilon: Actually, let me clarify.
unmanbearpig has quit [Changing host]
unmanbearpig has joined #ruby
<adam12>
nakilon: I have 4 large Roda apps, 2 medium sized Roda apps, and another handful of small Roda apps. The oldest ones go back to like 2016-2017. They all use dryrb and Sequel. None of them use ROM (tho I’m considering it for new projects).
<adam12>
nakilon: I’ve never added gems for JSON API or GraphQL, because I’m not a huge SPA / heavy front-end fan. Every app I build gets Unpoly on the frontend.
Garb0 has joined #ruby
<rapha>
:-(
Garb00 has joined #ruby
<rapha>
who names files *.png.10x20-200.png
<rapha>
is there a way to have a $ (end of line) in Dir[]?
<rapha>
or do i have to use a regex?
<rapha>
(want /.*\.png$/)
Garb0 has quit [Ping timeout: 265 seconds]
<rapha>
hmm seems #reject_if will be the easiest
<rapha>
argl my brain will never be able to remember why it has to be #reject but #delete_if and vice versa
<nakilon>
you define myriads of classes for everything, even for methods _<>
<nakilon>
relying on implicit calls between these gems it seems to be impossible to then untangle them
<nakilon>
people say "these are better because otherwise rails push you into a corner", but I fail to see how this isn't the same kind of cornering, just with a longer Gemfile
<nakilon>
no wonder those guys in 5 y.o. old project don't have unit tests, only api tests -- probably all the logic is within coupling these gems instead of creating own modules (I'm just theorizing)
<nakilon>
rapha delete_if is destructive, just use select and reject
<nakilon>
and probably Dir.glob accepts regexes
Garb0 has joined #ruby
<adam12>
nakilon: There’s pros/cons for both approaches. For my Roda apps, there’s never the _big upgrade_ like there is in Rails. When Roda has a new version, I update Roda, and when Sequel has a new version, I update Sequel. I don’t have to upgrade activerecord, activesupport, actionpack, actionmailer, etc. all at once.
<adam12>
nakilon: The downside is it’s very much an assemble-your-own-framework.
<gearnode>
nakilon: For me it's a feature you don't have to deal with the Rails complexity!
<rapha>
nakilon: i know the difference between them. i wish that (a) either both have _if at the and or they don't (b) destructive things all get the bang at the end as is the convention
jetchisel has quit [Ping timeout: 264 seconds]
jetchisel has joined #ruby
lunarkitty has quit [Quit: Connection closed for inactivity]
<nakilon>
"you don't have to deal with the Rails complexity" -- instead you invent your own complexity? )
<nakilon>
especially considering that your one will have almost no tests and docs ..D
<nakilon>
rapha thank rails that the "!" sense has vanished
<xuochi>
The true advantage to something like Rails is that when some poor developer 5 years from now has to take over the project he/she has some idea of where to start.
<gearnode>
nakilon: My complexity so small compare to Rails + my complexity
<gearnode>
is*
<rapha>
nakilon: i'm really not sure if the ruby world wouldn't have been better off without rails. but we'll never know...
gr33n7007h has quit [Ping timeout: 244 seconds]
<xuochi>
While Rails may have hurt Ruby's reputation, it is always what made Ruby more popular. So, it was probably neutral overall.
<clemens3>
well, ruby might have never gotten popular without rails.. I for one dropped rails long time ago.. love ruby, rails had one nice idea and concept, but that was it.. wish ruby would be better for multi threading now.. thought
<clemens3>
and well, rails not so alive anymore..
<clemens3>
maybe next gen language will have lot's of ruby similarities too thanks to ruby..
<clemens3>
nim, crystal, some javascript based languages, kotlin, all clearly have gotten their big influence through ruby..
Guest0 has joined #ruby
Guest0 has quit [Quit: Connection closed]
ule_ is now known as ule
ule has quit [Changing host]
ule has joined #ruby
gr33n7007h has joined #ruby
<xuochi>
I think Ruby is plenty "alive" just no in prominent apps and such.
<xuochi>
I know of a few massive multination corporations who use ruby for sysadmin/syseng stuff, but it's all behind the scenes.
<xuochi>
That amount of code dwarfs many major projects tho
jetchisel has quit [Ping timeout: 252 seconds]
<jidar>
I think one of the major things to watch is adoption of newer ruby versions in products that use ruby, when you start to see stuff like how python 3 adoption took forever
<jidar>
it becomes more clear that the language itself might see plenty of use in places all over
<jidar>
but often those uses are hidden behind the use of a single gem or examples like rails
Bounga has quit [Ping timeout: 264 seconds]
<newton>
I don't think python 2 -> 3 is comparable to say, 2.7 -> 3
<newton>
and rails is still alive that's a weird take. there's a lot of the new new out there to play with, but rails is still an amazing framework to get an idea to market fast imo
<bhaak>
the mindset for upgrades is different in the rails or ruby community than it was (is?) in the python community
<bhaak>
1.8 to 1.9 was technically basically the same as python 2 to 3
<bhaak>
but with big gems taking the leap as soon as possible or even big projects like Rails, it was never that contentious and backwards compatibility wasn't as big as it was with python
<bhaak>
I mean, the EOF of python 2 was in 2020! imagine that for ruby 1.8