#Ruby on Rails

[alycesutherland]

First Steps:

So I want to learn how to get access to the spotify api and my data first in my terminal. So I want to:

Get my top albums in terminal

Get my top artists in terminal

Get my top songs in terminal

If I figure it out really quick:

Add that json data into an xbar project on my Macbook

If that is easy then I'll add more stuff for when you click on xbar

[bunabyte]

So I was testing out the profile banners on my website, and...

What in the actual fuck is this?

[the-knights-of-rohan]

20/100 days of productivity.

It's actually less busy than I thought it would be today. Classes have been pretty chill, and a couple of my teachers got sick, so there's not much to do. But I finished my college apps, so now it's just interview prep for Saturday. I am...very nervous, especially because the school is quite literally the best for my major.

(Ice in that water looking CRISP.)

Today’s productivity:

Did AP Physics practice FRQs to prepare for unit test on drag and motion, luckily the test got postponed to next Monday.

Did AP Statistics review questions on experimental design, not too bad.

Did US Government notes, long and boring.

Worked on website for my club, we're using Jekyll to create all of the pages. Now I can add Ruby to the list of languages I am "moderately proficient" in!

Spent an hour flashcarding for Japanese 4 new chapter vocab

Self Care:

Daylight savings meant that I got to sleep in an extra hour. That was fun.

Spent a good hour playing Monster Hunter Rise, and getting blown out by the Variant Malzeno.

Future Goals:

Study for 3 tests in the coming weeks; AP Statistics (Experimental Design), AP Computer Science (String manipulation), and AP Physics (Friction and Drag)

Figure out how I'm going to read The Jungle without spending money (read: One Piece-ing)

Keep preparing for college interview (僕はスペインにいる。スは静かだ。)

Song of the day:

Name: Pyro

Album: UNLOCKED

Artists: Denzel Curry & Kenny Beats

[bitcodevsdigitalmarketing]

Unlock the Power of Ruby on Rails with Bitcodevs: Expert Development for High-Quality Web Applications

[leecrey]

This is my very first post

[cuteimu]

Popular Back-end Web Development Technology

We can talk about some back-end technologies, that can be:

JS (Initial release- 1995): popular for Netflix, Candy crush, Facebook app building.

php : popular for WordPress, Wikipedia, Yahoo! App building.

There is some popular as well as the best technology, that is-

Spring: For java enterprise this is the most popular application development framework.

Ruby on rails: Most popular server-side web application framework.

Asp.Net: Another popular development platform with tools, libraries, and programming language.

[layover-linux-official]

There's this Ruby on Rails shop that I might have a shot at, which probably has a better work environment than my current place, and may have better pay. But it means I need to brush up my RoR skills. And that means I've been spending the last couple days thinking about what kind of personal project I might be able to use for that skill building.

Well by jove, I think I've finally figured it out! I used to do a lot of game design, especially tabletop, as a hobby. One of my problems is that I was always coming up with little individual ideas for mechanics, but to make a whole game, I really want to have some kind of "storage drawer" of mechanics to easily pick from so I can easily find mechanic combos that fit nicely together. The best way to do this would be in Obsidian and driving my existing website, but I could do it as a separate domain and tech stack for the Rails practice.

It also might be a nice opportunity for me to try a branch where I follow some of the language design conventions I've been cooking on for the programming language I've been working on. Many of those conventions are hard to test drive in existing languages because they depend a bit on language support to actually be ergonomic, but Ruby is such a flexible monkey-patchy language that I could actually maybe exercise those principles in an existing language, which would let me validate my opinions more strongly before going all in on language implementation.

Basically, this lets me headshot a surprising number of birds with one stone, and if I can summon the motivation, I think it'd be multiply good for me.

[zandyland]

Speeding up requests with Rust

I'm working on an application in Ruby on Rails that saves user data and processes it into documents. This is very common in B2B software. Consumer software can keep data in the format most convenient for the developers, where it can be rendered onto pages. B2B software often replaces an existing process and needs to produce a document that looks and feels like the old process, but is faster for the worker to produce.

Ruby on Rails is built for the typical consumer website. It's probably the fastest way to get a CRUD app from zero to live. Rails also likes a monolith. You keep all your logic in your controllers, which react to user actions.

However, Ruby is not particularly fast. That's normally okay for most cases, as Rails is well-written and can render a page fairly quickly.

So you need a strong case to add a separate service. Here's my B2B case:

Users want to download a document that will be printed and posted to the wall

The document is typically well-structured, so some print-specific CSS won't suddenly make the HTML page fit to print.

These documents are posted in paper and sent in email.

Suddenly PDFs are looking pretty good. They are displayed consistently on all devices and don't need a special license to view with consistency (unlike DOCX, which often displays oddly in LibreOffice or a native viewer).

Now, PDFs bring their own problems:

We need a library to produce them. (Does Ruby have such a library?)

They take a discrete amount of time to process and save.

They need to be produced quickly after "Publish" is pressed, but...

They can't hold up user actions (such as page loads) while being processed.

It is fairly simple to set up asynchronous actions that queue up and process over time, so that's an exercise left for the reader.

But here are a couple drawbacks:

We're using up precious processing time making PDFs that could be used fulfilling user CRUD requests.

Ruby's dynamic typing and wimpy type system are great for quickly spinning up applications, but not great for ensuring integrity and avoiding crashes

Making PDFs takes only data in and produces a product - it doesn't have to keep track of state like a web app. Wouldn't a functional approach be cleaner and easier to reason about?

With all this in mind, it seems obvious that PDF production can move to a separate service, and since we're doing this over HTTPS anyway, even a service that's not written in ruby!

With rust's Tokio, it's easy to create short-lived jobs that take only input, send back output, and keep no state. A lack of global state is actually the easiest way to write a tokio app!

There's obviously a lot more to the actual execution, but I'm happy to report that the advantages of a compiled application and strong typing leads to very fast request fulfillment! Every document takes less than 1ms to complete on a very wimpy Raspberry Pi 5. Even if I failed to make document processing async, users would experience more lag from network issues than document processing after pressing the Publish button.

The "mu" means millionth, by the way.

Of course, this took planning and solid logic. No programming language can save you from a bad algorithm or costly calculations. But the rust service is easy to test, easy to reason about, and has strong guarantees thanks to rust's philosophy and tools.

Thanks to a simple retry queue, upgrading this service is also fast with almost no downtime. Stopping the old version and starting the new version takes the service down for about ten seconds. Tokio is lightweight so the service is back up almost instantly. This is fast enough that the retry queue doesn't flinch. Three retries and a dead-letter queue, plus an admin tool for DLQ alerts and manual reruns means I don't have to think about deployment as a downtime issue.

Ruby is strong for the application, rust is strong for the document queue. All tools for their appropriate purpose.

[bitcot]

Top Programming Languages for Full Stack Development | Bitcot

Choosing the most appropriate coding language is the most critical component of developing a solid full-stack application. JavaScript (Node.js for the backend, React for the frontend), Python (Django, Flask), Ruby on Rails are the most in-demand options. Each language offers its benefit, depending on the nature of your project. Bitcot helps companies decide the most apt technology stack for effective and scalable development.

Decide which one is best suited for your project. Learn more here: https://www.bitcot.com/full-stack-programming-languages/

[alycesutherland]

Finally got OAuth working!!!!

The war is over. Figured out the hard way that OAuth makes the routes for you <3

Now I can start coming up with models to store the data from users. If anyone has any ideas on how I should make those relationships with other data tables for songs and artists let me know. I’m going to reblog this post with some of my own ideas.

I also have a login page and dashboard with hard coded data to get a sense of what I want the backend to supply. Good progress! Will also reblog with pictures of that.

[ehwesson]

ruby on rails to me is like looking into a glimpse of what programming could have widely been if we didnt all fall into the capitalism tar pit

[maxcobmara]

Week 2 2025

Lets see.

Do a triathlon in a month week. Still haven't cycled, So the Olympic requirements for a triathlon are Swim 1.5km Cycle 40km Run 10km , so thats my target right now. I thought I had targeted an IronMan which is Swim 3.9km Cycle 180.2km Run 42.2km. I was wondering why an IronMan seems so easy. lol Anyway achievement this week.... (drum roll)

0.66km swim and 12.5 walk/run. So I over achieved on the run part. Time to focus and hit some targets.

Learn something new and valuable everyday. So I diligently focused and completed Ep1 in Deanins 20 in 20 series. Most of the stuff I have in production, but you never know what new things you can learn, and are now halfway through episode 2. at 40 mins to 2 hours a pop it is hard going, especially when stuff seems 'basic' your brain just kind of wanders. So have implemented pomodoro and managing it in 25minute sessions.

https://youtu.be/WwClobViifU?si=dM0LunTceC5PMELd

Work a little on code everyday. Upgraded my Asus Zenbook Windows and WSL from 20.4 to 22.04, and just realized its still running rbenv.

Just pulling all the code I expect to be working on and making sure the apps run. The target is to have all the apps runnable on all the available devices, so I can grab any one, the best one, to go.

I'm probably procrastinating, but I'll get over this. Windows 11 24H2 is a dog though, and will randomly freeze every so often./

Do some investment reading, and stockwatching Been super active, learning new things, but I am using at as an excuse to procrastinate doing the things I'm supposed to.

Revisit projects in my head. Getting all the projects running in WSL. Will probably upgrade one to project to Rails 8 this week.

Housekeeping Have cleaned up one bag of "to be sorted miscellaneous" , and a lot more to go, but trying to build a habit. Ive stared to live again in Any.do and living by GTD habits. Channels Adding channels this week because it doesn't really fit anywhere else. Focus on channels that can generate $$ now.

So done my medical checkup for PSV license, more about that later and class is tomorrow, so that's the me part almost done, would have been done last month but I got sick, and couldn't do a medical checkup or attend the once a month availability course. Have studied up for the insurance course, but I need to bring my original high school certificate (SPM for those that know) and I left mine on the bus many years ago, on the day I collected it from High School. Yes theres a way to get a new one, will share soon.

[yiebackenddev]

[bluetickconsultants]

Ruby on Rails has always been a favourite framework for building modern web applications. With the release of Rails 8, developers are now armed with enhanced features that significantly improve performance, scalability, and developer productivity. One of the standout additions to this release is the upgrades to Active Job, which bring a host of new capabilities to improve background job processing. In this blog post, we'll explore the exciting new features and optimizations that Rails 8 introduces, and how developers can leverage these enhancements to build more efficient, responsive applications.