software_writer

Such a pretty website / blog. You don't see many of these nowadays.

> Opinions are apparently valuable.

I'd think so, given the same opinions when applied to a programming framework have generated hundreds of billions of enterprise value in the past.

I've been using ThinkPad E14 (AMD Ryzen 7, 16GB RAM, 512 SSD) - very happy with it. No problems with performance, battery, etc. at all. The new Dell XPS 13/14/16 is also good. Just get one with Windows and wipe it clean when installing Linux.

In fact, I was going to buy a $4K M4 MacBook before I saw Omarchy and decided to give it a try with a new $730 ThinkPad. Exceeded all my expectations. Omarchy literally saved me thousands of dollars.

Same here. Using my ThinkPad became much more fun after I installed Omarchy on it.

Switching to Omarchy was one of the best decisions I made last year that improved my everyday computing experience so much, and introduced me to so many amazing tools like neovim, tmux, tiling window managers, Arch Linux, and countless TUIs.. Haven't touched my old MacBook this year at all.

If you're in the market for a new laptop / operating system, I highly recommend you give it a try.

After more than a decade with Apple (and Windows before that), I’ve been using Linux with Omarchy exclusively for the past few months and have been very happy with it. Can’t imagine going back to Mac or Windows at this point.

I had never really used Linux as a daily driver (aside from sysadmin stuff on remote servers), but Omarchy setup took less than 10 minutes and getting comfortable took just a few hours. Since switching, I’ve seen clear productivity boost, and the competency gained in Linux, Vim, etc. and overall performance made it totally worth it.

I’m running it on a cheap ThinkPad for all my daily development work and it likely saved me over $4000 since I was planning to buy a new MacBook Pro before trying this. Haven’t touched my old MacBook in quite some time.

Just wanted to share my experience with Omarchy, definitely worth trying if you're on the fence.

A classic book. I learn something new each time I read it.

Also, Dave Thomas, one of the authors, is looking for a job.

> So, I'm looking for a job!

> Internal or external consultant, devrel, training, team fixing, design, architecture. WFH or travel the world.

> So, if you know any company that has a Dave-shaped hole, please email me. Some more about me on my site. Links below.

> Many thanks.

> email: [email protected]

https://x.com/pragdave/status/1978142569272877078

100%

This post shows how your application servers (Rails, Django, Laravel, etc.) can offload file delivery to reverse proxy servers like Nginx using the X-Accel-Redirect (or X-Sendfile) header. We'll also read a new reverse proxy's (Thruster) source code in Go to learn how this pattern is implemented at the proxy level.

You can append the dasherized version of the headline (or specifically, the id of the header) to go to that specific section:

https://rubyonrails.org/2024/9/27/rails-8-beta1-no-paas-requ...

For a concise overview of all the new frameworks and announcements, I recommend reading the official Rails blog post from DHH:

https://rubyonrails.org/2024/9/27/rails-8-beta1-no-paas-requ...

ConvertKit supports 10,000 subscribers on a free plan.

https://convertkit.com/pricing

Author of the original post here. I have no affiliation with either the Flatiron bootcamp, nor the SuperByte company. But I know Pedro and he (and his story) is real.

If you take a quick look at the rest of my blog, you'll quickly know that this was neither an ad for any bootcamp or company, nor an attempt to 'manipulate tech news readers'.

Ruby's defined? keyword is an elegant way to check if a variable is defined or not and also to cache expensive operations. However, it's confusing, and a few gotchas await the new Rubyist.

In this post, we'll learn how it works and how to use it correctly to cache expensive operations returning `nil` or `false`.

In this article, we'll build a simple but complete application in plain Ruby without Rails, to get a deeper understanding and appreciation of everything Rails does for us.

Rails 7.1 ships with a handy `perform_all_later` method that lets you enqueue multiple jobs to be executed at once, reducing the round-trip to the job backend like Redis or the database.

Although it's currently supported only by Sidekiq and GoodJob (as far as I know), it provides a nice abstraction to enqueue multiple jobs at once. This post explores this method including the behind-the-scenes implementation.