Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Building GitHub with Ruby on Rails

github.blog

Post reply on HN
Print view View original

91–100 of 332 posts

Re: Building GitHub with Ruby on Rails

#91

Post by that_guy_iain »

rimliu wrote: post #83
that_guy_iain wrote: post #71

Earlier quoted context omitted.

Comparing frontend frameworks with backend frameworks seems really odd to me. It takes a lot less time to build a JS framework. They do a lot less. This isn't to say frontend is easier or whatever. But they really do a lot less. That is why they're so many really good frontend frameworks. It's also a lot easier to rewrite your frontend than it is your backend. While backend there is so much to build that you really n…

JS is not only for frontend anymore. Alas.

Yea and new backend frameworks pop up every day. Wait, they don't. They were clearly talking about frontend frameworks.

Re: Building GitHub with Ruby on Rails

#92

Post by teshigahara »

bspammer wrote: post #79
neals wrote: post #52

[flagged]

Was this comment generated via ChatGPT? Not trying to catch you out, just curious if I'm able to successfully spot it in the wild.

I also got very "ChatGPT" vibes from that comment but thought I was being too paranoid by the last paragraph

Re: Building GitHub with Ruby on Rails

#93

Post by that_guy_iain »

irjustin wrote: post #86
that_guy_iain wrote: post #69

Earlier quoted context omitted.

> As someone who has experience working with large codebases, I am thoroughly impressed by GitHub's approach to upgrading their Ruby on Rails monolith. It is clear that the GitHub team has invested a significant amount of time and resources to ensure that their application runs on the latest version of Rails and Ruby, and this has resulted in real tangible benefits such as better database connection handling, faster…

I down voted because it just seems like you wanted to being up the dear GitHub. It's been years... 7? with great features that go well beyond the letter. Yes gh was stagnant but this is pretty well in the past and your points have almost no current relevance.

> I down voted because it just seems like you wanted to being up the dear GitHub.

I only brought up dear GitHub because I am sure people wouldn't have had an idea what I was talking about.

> Yes gh was stagnant but this is pretty well in the past and your points have almost no current relevance.

When my point is they used a bunch of time that other companies wouldn't give to build a solid foundation it seems very much that the past, that being the foundation, is very relevant. My entire point, is that they're in a very unique position a position that others can't really fairly expect since very few companies are able to ignore features for such a long time. This isn't to bash github. This is to put into persective what they've done and if others can do it. It removes the whole "GitHub did it so..." thing that many will suggest down the line.

Re: Building GitHub with Ruby on Rails

#95

Post by jeremyjh »

amrocha wrote: post #47
snemvalts wrote: post #34

Github is one of the few webapps where I can feel daily that the framework used isn't enough. So many things get out of sync/not up to date, which are fixed by refreshing the page.

Very true, but that's a frontend problem, not a rails problem.

These problems are always more common in server-rendered apps though, because front-end state is always a patchwork. And the Rails developers and community have a strong preference for this architecture.

Re: Building GitHub with Ruby on Rails

#97

Post by pjmlp »

roguas wrote: post #96
pjmlp wrote: post #59

Earlier quoted context omitted.

Errr, tail calls.

Every reasonable. Maybe I am wrong, but tco usually means no more stacktraces?

No, only dumb implementations, Scheme and other languages that require TCO have no issues mapping the debugging metadata to proper calls.

Re: Building GitHub with Ruby on Rails

#99

Post by codetrotter »

willriches wrote: post #94
bspammer wrote: post #79

Earlier quoted context omitted.

Was this comment generated via ChatGPT? Not trying to catch you out, just curious if I'm able to successfully spot it in the wild.

I passed their comment to ChatGPT 3.5 and it seemed confident that ChatGPT wrote it.

I don’t think ChatGPT can tell if something was written by ChatGPT. At least not reliably.

Re: Building GitHub with Ruby on Rails

#100

Post by Karunamon »

willriches wrote: post #94
bspammer wrote: post #79

Earlier quoted context omitted.

Was this comment generated via ChatGPT? Not trying to catch you out, just curious if I'm able to successfully spot it in the wild.

I passed their comment to ChatGPT 3.5 and it seemed confident that ChatGPT wrote it.

For the record, this (asking the model if the output is theirs) is not a reliable way to determine AI authorship of comments. The false positive rate is quite high, and will return true simply for a comment being well written and lacking idiosyncrasies.
Post reply on HN