ec changed the topic of #elliottcable to: a 𝕯𝖊𝖓 𝖔𝖋 𝕯𝖊𝖙𝖊𝖗𝖒𝖎𝖓𝖊𝖉 𝕯𝖆𝖒𝖘𝖊𝖑𝖘 slash s͔̞u͕͙p͙͓e̜̺r̼̦i̼̜o̖̬r̙̙ c̝͉ụ̧͘ḷ̡͙ţ͓̀ || #ELLIOTTCABLE is not about ELLIOTTCABLE
Rurik has quit [Quit: Rurik]
Rurik has joined #elliottcable
Rurik has quit [Quit: Rurik]
Rurik has joined #elliottcable
_whitelogger has joined #elliottcable
Rurik has quit [Quit: Rurik]
Rurik has joined #elliottcable
<inimino>
ec: I'm in SF
Rurik has quit [Quit: Rurik]
Rurik has joined #elliottcable
Rurik has quit [Quit: Rurik]
Rurik has joined #elliottcable
Rurik has quit [Quit: Rurik]
<ec>
inimino: hm?
<ec>
:P
<ljharb>
ec: aren’t you in like Chicago or something
Rurik has joined #elliottcable
Rurik has quit [Client Quit]
<jfhbrook>
so uh, do any of you work with ruby? I feel like a few of you have ruby experience
<jfhbrook>
thinking about working for a rails shop, hoping the full-stackedness is pervasive enough to be interesting, but I've never worked with ruby beyond doing the rails getting started tutorial
<ec>
I love Ruby, as a language
<ec>
hate rails … but i’m sure I, too, am gonna end up at a Rails shop
<ec>
I’m also apprehensive about working in ruby *with a group*. It’s a very flexible language, and lends itself well to duck-typing, meta programming, etc; and *doesn’t* lend itself well to … structure, collaboration, fixedness? lol.
<ec>
I assume in an org a lot of those things instead have to be enforced socially or by tools; and afaict none of the tools are all that powerful … (basically just Rubocop, right? no typing tools that I know of, nor stronger static analysis)
<ljharb>
ruby gives much more hanging rope than most languages
<jfhbrook>
I mean I've written javascript before ;)
<jfhbrook>
some dudes made a type annotation library for ruby
<jfhbrook>
cool that you can do that without new syntax (apparently, anyway)
<ec>
ehhhhh, it’s different. JS’s “rope” is bugs, which you’re pretty much encouraged to avoid *both* by the language, the idioms, and the community
<jfhbrook>
and yeah I mean rails itself is whatever, I'd rather be using sqlalchemy but it looks fine for what it is
<ec>
Ruby’s “rope” is language-sanctioned features, designed to be used
<jfhbrook>
I'm gonna write so many DSLs
<ec>
and sanctioned by at least parts of the community — reasonably, for the things *they’re* working on, you know?
<ec>
what’s sqlalchemy
<jfhbrook>
the good (for an orm) python orm and query builder
<jfhbrook>
I did the rails tutorial and it was fine but I have a *lot* of questions
<jfhbrook>
like, why do I have to run bundle exec rails instead of just rails? why does my 2.5 environment install gems in the 2.6.0 gem directory?
<jfhbrook>
why aren't there any require statements inside the controllers or models?
<jfhbrook>
just lots of weird shit like that
<jfhbrook>
some of them are just fundamentally bizarre environment issues that I probably caused myself by fucking with system ruby in arch 🙃 but the lack of requires in the controllers file, that's not just me, something strange is going on there
<ljharb>
jfhbrook: stripe made types for ruby iirc
<jfhbrook>
ljharb: those are the ones yeah
<jfhbrook>
man this would just be super funny if I ended up working on a rails app