Two figures that inspired me were missing, why the lucky stiff and Ryan Bates from railcasts fame. Otherwise great docu with DHH "f*uk you" slide which does give an insight into successful open source projects.
I'm always here to speak praises for Ryan Bates. His practical videos to build features was a huge insight for me as a junior developer at the time.
Ruby on Rails: The Documentary [video]
111–120 of 248 posts
Re: Ruby on Rails: The Documentary [video]
#112I had a lot of fun watching this documentary. The one person framework really comes out in the personal story of Toby from Shopify. "From Hello World to IPO". What I also loved is that he mentioned that if you open up any Rails application, it looks basically the same in structure whether it is the biggest Rails app there is or a new one. Sure that can be true for many apps, but in a world of, for example, APIs and f…
Do I have to deal with JavaScript in any way?
Re: Ruby on Rails: The Documentary [video]
#113Earlier quoted context omitted.
Is there any comparably complete framework that does not need any significant adjustments even when it's used by 1000s of developers building the same app?
Probably ASP.NET is as close as it gets.
Re: Ruby on Rails: The Documentary [video]
#114Earlier quoted context omitted.
True, nodejs really doesn't have _the_ framework. Python had flask, php is WordPress and RoR. Why is that? Especially since most of the new frameworks copy the ideas of existing frameworks. P.S. Perhaps because a JS framework based off the ideas of rails would be called jails! /s
I've wondered about this for years. Express was the default with Node for some years but it was mostly used for APIs to feed front ends. These days lots of people have switched to Fastify but again mostly for APIs. There's really nothing fullstack in the JS world that can be compared to Rails, Laravel, or Django. Current fullstack solutions (Next, Nuxt, SvelteKit, etc) in JS are trying to kludge front end components…
I think you make a good point here, JS is uniquely able to be executed both frontend and backend, hence things such as underscore templates.
Other languages don't have that ability. Therefore I would agree that there is no point in making a 1to1 copy of existing MVC ideas.
Being an ex-rubyist and now doing a lot of NodeJS, I really enjoy moving server code to the client at zero mental cost since it's mostly the same APIs
Re: Ruby on Rails: The Documentary [video]
#115Two figures that inspired me were missing, why the lucky stiff and Ryan Bates from railcasts fame. Otherwise great docu with DHH "f*uk you" slide which does give an insight into successful open source projects.
I agree with that, I would also have liked to have seen Tenderlove in it.
Re: Ruby on Rails: The Documentary [video]
#116Earlier quoted context omitted.
Ryan did so much for the rails community and all because of the joy for RoR. Unfortunately iirc Ryan suffered a burnout and had a lengthy break. I hope all that is better now.
All is better. I still plan to blog about the burnout.
Unfortunately having folks around me that had burnout helped me to avoid one myself.
Re: Ruby on Rails: The Documentary [video]
#117Re: Ruby on Rails: The Documentary [video]
#118Re: Ruby on Rails: The Documentary [video]
#119Earlier quoted context omitted.
> You're building CRUD apps. No. "we" are not.
> Domain. Team. Project Planning. Combine any of them and the projects demand different things, but with Rails you are out of luck hmm, sounds like this rails app that one might have not heard bout. You should check it out. Think it's called Basecamp
Re: Ruby on Rails: The Documentary [video]
#120I had a lot of fun watching this documentary. The one person framework really comes out in the personal story of Toby from Shopify. "From Hello World to IPO". What I also loved is that he mentioned that if you open up any Rails application, it looks basically the same in structure whether it is the biggest Rails app there is or a new one. Sure that can be true for many apps, but in a world of, for example, APIs and f…