00:37 <johnjaye> i would think the only reason ruby would work as a shell is the omitting parenthesis thing

00:37 <johnjaye> every other language forces you to have parentheses because i guess the more the better right

01:01 <weaksauc_> johnjaye nah any language could make a shell. their shell only executes ruby only when you pass in `: some_ruby_command`

01:52 <libsys> I use parentheses on my ruby code because it makes things easier to understand in a ton of cases, and for consistence with that

01:55 <libsys> isene: heyy, that seems pretty cool

01:56 <libsys> what do you guys think of ruby in comparison with python? in my mind they serve a pretty similar purpose, but ruby seems way nicer

01:57 <libsys> pity that python is way more popular

02:03 <weaksauc_> libsys i think the main rule is always use parens when calling a method with parameters and omit if not

02:03 <weaksauc_> with a few exceptions

02:03 <weaksauc_> but maybe a handful

02:31 <libsys> weaksauc_: I do the same

05:56 <Mahfuj> Hi everyone!

05:56 <Mahfuj> Seareed Inc. is seeking a skilled and passionate developer to join our dynamic e-commerce platform. If you are an experienced professional who thrives in a deadline driven, and fast-paced environment, and who has a strong background in web development, this is an excellent opportunity to contribute to the growth and success of our platform. At Seareed, we value creativity, innovation, and a passion for delivering exceptional user experiences. If you are

05:56 <Mahfuj> excited about joining a dynamic team and making a significant impact on the future of our e-commerce platform. Our technical requirements includes doing many payment integrations, but the main framework is Stripe. Pay range 40 USD -100 USD per hour depending on skills, and experience. Please email me resume, portfolio, your relevant experience and why you are interested in this position at reazmahfuj124@gmail.com. We look forward to hearing from you!

12:21 <aestheti1> isene looks like you are getting some traction on HN, nice

13:43 <isene> aestheti1: HN?

13:43 <bhaak> isene: https://news.ycombinator.com/item?id=36184039

13:44 <mooff> nice!

13:46 <isene> Oh, cool

13:47 <isene> Guys; any ideas for features?

14:18 <mooff> isene: perhaps "help" or ":help" could print the intro text again :-)

14:38 <isene> Yes!

17:56 <rapha> good god

18:29 <blackmetal> Anybody often rebase and rearrange their commit history only to be bombarded with merge conflicts 99% of the time about Gemfile.lock or db/schema.rb?

18:29 <blackmetal> What's the best way to solve this? Should I somehow ignore these files and their inevitable conflicts, do my rebasing and rearranging, and then make some script that goes from the first to the last commit doing ie. `git checkout HEAD -- Gemfile.lock && bundle && yarn && rails db:drop db:create db:migrate && git add db/ Gemfile* yarn.lock && git rebase --continue` (maybe in addition to a script that

18:29 <blackmetal> rearranges migration filename dates chronologically)?

20:17 <isene> mooff: Implemented

20:42 <weaksauce> isene do you spend all your time in rsh?

20:45 <isene> Not when I'm sleeping

20:46 <isene> ... it's 50/50 rsh/zsh now

20:48 <isene> Spending half the time in zsh (extensive antibody setup) to get inspiration for rsh

20:48 <isene> Like the latest feature to do automatic git status for git repos