🧐 Issue #13 - 03 - 09 October 2022
The one where we share our love of Ruby and Rails
If you want a short excerpt of this newsletter containing only some of the images with code, I created one here. But I invite you to read the entire newsletter as it has excellent content 😊.
This edition was created with support from @adrianthedev from Avo for Ruby on Rails (a friendly full-featured Rails admin panel) and from @jcsrb, who sent me recommendations to include in the newsletter.
Here are some answers:
“The community. To be more specific the freshness and joy of Ruby 3 and Rails 7 that I think is fueling an excitement of the community and a desire to attract new people in the community” (@lucianghinda)
“Hotwire. Wish Rails would offer a PWA solution out of the box.” (@th1agofm)
“Alternative ruby frameworks to Rails. Which ironically strengthens the rails and Ruby a lot.” (@kowfm)
“The error reporter interface became more mature and adoptions are increasing” (@_st0012)
“Rails 7 changing the game and getting us back to our roots. It has me so dang excited. Not just what hotwire delivered but a renewed excitement in the framework and the fundamentals that made us love it in the beginning.
I love writing rails so much” (@schwad_rb)
“Hotwire! One codebase, instead of Rails API + gigantic pile of JS. I can maintain a Rails+Hotwire app myself, much harder to maintain both Rails API and React frontend by myself” (@aidanhmiles)
“Feels like anyone can become a one man coding machine with Hotwire. I wasn’t even doing frontend until Hotwire. Didn’t have the interest before then because I found it a nightmare. Now, it’s the most fun I have had in years!!” (@mhenrixon)
“That my lack of interest in learning a lot about React in recent years...might be paying off.” (@robbyrussell)
“For me it’s the basics. That it’s a solid platform with a good, supportive community that makes it easy to build cool things!” (@rose_w)
“Particularly for prototyping a new app for feature, it's still the best way to do it by a significant amount. That's still, to me, the big problem Rails solves very well that nobody else is really trying to solve.” (@codefolio)
“the additional focus from the community on helping juniors, learning and teaching ❤️, things like new podcasts, courses, newsletters etc.” (@afomera)
“Just how easy it is now to build high-fidelity user experiences in Rails with Hotwire, custom Turbo Stream actions and the myriad of possibilities they enable, CableReady::Updatable, etc.” (@danieldopence)
There are a lot more anwers. You should read all the replies.
To check if you have this issue:
In case you are wondering how does ENV behave when using with fetch or access through :
And it seems the reason Rubocop suggest this change is to make the default value implicit.
Read the tweet, as there are more examples there.
Joshn Cheek shared a piece of code that will show the source code and line number from where that objects was defined (the code can be found in this gist or a version that will also show the class name along with source code here):
Here are some answers from the replies, but I invite you to read them all as people share a lot of knowledge about what works and does not work for them and why:
To organize ALL files by type is to take what was a good idea at a certain level and apply it way beyond what makes sense.
What good could it possibly do to have all your factories in one folder, for example? What meaning or utility could that have?
Don't organize your Rails code by design pattern. Organize it by meaning.
If you have read so far and you like the content, maybe you take into consideration sharing this and subscribing:
Related (but not Ruby specific)
He also added:
Code is only hard because we don't talk to each other nearly enough, and assume that there's a technical solution to every problem.
Here is one of tweets in this thread:
🧐 Julie asked as question about how to teach kids how to code:
There a lot of good answers in the replies that I invite you to read.
Articles and Videos
Something to read
🗞 Chuck Smith shared a new edition of Women on Rails Newsletter #36: The year of the crab, build trust while remote, create good Pull Requests. Read the English version, French version, Italian version, Spanish version
🗞 Greg Molnar shared a new edition of This Week in Rails written by Petrik de Heus. Read Updated Permissions-Policy directives and LSP support?
Something to watch 🎥 or listen 🎧
🎥 Jared White shared a new video about HTML modules and going through the history of 25 years of web development. See The Rise (and Fall) and Rise Again of HTML Frameworks
🎧 Audio & Podcasts
🎧 Joël Quenneville shared a new episode of The Bikeshed where he talks with Stephanie Minn about the value of specialized vocabulary and the power of names. Listen to The Value of Specialized Vocabulary
🎧 Jason Swett shared the final episode of Code with Jason where he talks with Nick Schwaderer. Listen to The Final Episode (for Now): Nick Schwaderer - The Code with Jason Podcast
🧰 Gems, Libraries, and Updates
🧰 There is also an open discussion in Ruby bug tracker abour import module. Read it here. It might (or might not) come in the next Ruby version.
🧰 Jean Boussier shared a (pre)version of pitchfork - a new Ruby HTTP server optimized for latency and memory usage. Check it out at GitHub - Shopify/pitchfork. Here is a short comparison between this server and Puma:
Music for coding and fonts
Coding and Hacking Vibes (spotify) - electronic/instrumental
Music for Coding (spotify) - relaxing lo-fi hip hop and chillhop
Concentratio(Spotify) - a more alert music
Hip Hop LoFi Piano Beats for Progamming (Apple Music) - Lo-Fi with Piano
If you enjoyed this and want to receive the newsletter weekly in your inbox, consider subscribing: