Happy Birthday, Ruby

Post by dnautics » Thu, Jan 10, 2019, 10:13 PM UTC

bonquesha99 wrote: post #184

dnautics wrote: post #180

Earlier quoted context omitted.

it's not nearly the same. Piping in elixir is a macro; it lets you preserve the other arguments in your function call. The IO.inspect(value, label: "label string") semantic is incredibly powerful. During debugging I often do this: value |> IO.inspect(label: "A") |> do_something |> IO.inspect(label: "B") |> do_something_else |> IO.inspect(label: "C") ... This gives me full visibility over the data transformations that…

That's what it's doing, arguments are preserved: # don't really know what IO.inspect is doing # but guessing something like this? def IO.inspect(value, label:) puts "#{label}: #{value.inspect}" value end value.pipe do IO.inspect(label: "A") do_something IO.inspect(label: "B") do_something_else IO.inspect(label: "C") end

Post by janee » Thu, Jan 10, 2019, 10:17 PM UTC

colechristensen wrote: post #145

TheRealDunkirk wrote: post #67

Earlier quoted context omitted.

So, I'm old, and have done lots of stuff in lots of languages in frameworks. For about a dozen years, Rails was my go-to toolkit. I've written a couple dozen production applications with it. Unfortunately, Rails has really fallen out of favor lately. Even a Rails-specialty shop I worked for briefly has pivoted to using ASP.NET. I've played around in that stack, and found it lacking. (EF just doesn't compete as an ORM…

Opposite ask: What would your state of the art be for starting something new with Rails? / suggestions to become quickly productive

Post by irishsultan » Thu, Jan 10, 2019, 10:36 PM UTC

UncleMeat wrote: post #166

skywhopper wrote: post #48

Earlier quoted context omitted.

I don't understand your bit about "cuteness over familiarity". Can you give an example outside that's not Rails-related (given that Rails seems to be the main source of your concrete complaints)? Sigils in Ruby actually do have strong and clear meanings. And the difference between symbols and strings is a useful distinction. And contrary to your statement, Ruby's stdlib is far more complete and more internally consis…

It's not the best example, but Ruby is the only language I can think of where an expression (e) fails to parse but ((e)) parses. I find that it encourages a bad kind of code golf that leads to hard to maintain code.

Post by ehsanu1 » Thu, Jan 10, 2019, 10:54 PM UTC

Rooster61 wrote: post #143

taf2 wrote: post #101

Earlier quoted context omitted.

That is why we have pluck

> it's hard to see those consequences at the outset due to the fact that Rails code is so easy to pick up and understand Yes, there are tools in ActiveRecord that can help mitigate some of the performance issues, but as I noted above, it's extremely easy to overlook such tools until you are too far down stream to really do much about it. The symptoms of not using such features may not show up until much later when th…

Post by sho » Thu, Jan 10, 2019, 11:09 PM UTC

cutler wrote: post #161

sho wrote: post #14

Earlier quoted context omitted.

Me too actually. I flirted with programming around uni-time and after - PHP, java, friggin' ada - and just couldn't see myself enjoying it so I went into network management instead. 10 years later I was thoroughly sick of that, so started to look around and heard about this little language called Ruby - and it was love at first sight. Then this little software project called Rails started to gain momentum and there w…

I don't get this Elixir as the natural progression for Rubyists. OO/mutable Ruby and functional/immutable Elixir are worlds apart beyond the superficial syntax similarities.