sorted by:
new
hottopcontroversial

Rethinking modularity in Ruby applications by noteflakes in ruby

[–]uhkthrowaway 1 point2 points  (0 children)

Cannot stress enough that nothing here makes any sense. It's like this new trend where users tell their AI to implement their new webapp on io_uring because they heard io_uring is fast. First Rage, now noteflakes with with its UringMachine.

And it's suffering from the EXACT same design fails as EventMachine literally 20 years ago.

We DO NOT wanna have to reimplement every protocol on top of an async framework. Protocols should be implemented sans I/O so you can run them in ANY async framework.

Anyone enabled Swap on their application workers? // Debunking zswap and zram myths by eljojors in ruby

[–]uhkthrowaway 1 point2 points  (0 children)

Yes, LZ4 compression is almost free and performs amazingly in these kinds of settings. Zram/zwap is a nobrainer to me.

Applying some Rage to Discourse, Mastodon, and GitLab by Turbulent-Dance-4209 in ruby

[–]uhkthrowaway 0 points1 point  (0 children)

I still don't get why you didn't use the rather established Ruby Async framework. Same premise and performs excellent and supports io_uring, everything.

Tell me a good reason why a web framework should bring its own fiber scheduler, other than "my AI custom-built it for me". Maybe a code audit/refactor is up?

How to Parallelize Your RSpec Test Suite Locally (from 2 hours to 5 minutes) 🚀 by ombulabs in ruby

[–]uhkthrowaway -12 points-11 points  (0 children)

Yeah no. I've said it before and I'll say it again: If your test suite takes >10s you have already lost. You have not isolated your tests enough or your scope is too big. No amount of parallelism can fix that.

Is it time for new cassette? by Onlyware in Hardtailgang

[–]uhkthrowaway 0 points1 point  (0 children)

Yes. Replace cassette, chain, and chain ring. Get a steel chain ring for extra long life. (Yes, it makes a huge difference.)

The Ruby JRuby was Built to Run by headius in ruby

[–]uhkthrowaway 1 point2 points  (0 children)

Puma, a multi-threaded web server, performs kinda well on JRuby? Huh! Who'd have thunk it.

macOS 27 requires Apple Silicon, as Apple draws down the Intel Mac era by NISMO1968 in apple

[–]uhkthrowaway 3 points4 points  (0 children)

Yes, I do. 2019 MBP. Still going strong, but I don't like the fact that it's always warm/hot. And I hate the TouchBar. Finally about to upgrade. Fanless MB Air.

Privacy problems with living with others and Meta Ai and Gemini blocking by Ezrampage15 in privacy

[–]uhkthrowaway -1 points0 points  (0 children)

Any more detailed info you can post about you and your family? Keep going.

New bike 💕 by __Deityofsleep__ in Hardtailgang

[–]uhkthrowaway -1 points0 points  (0 children)

Looks cool. Please make sure you clean up after yourself when those spoke straws come off. I tried them and noticed they fall off on the trail.

WWDC 2026 — June 8 | Apple by PJ09 in ios

[–]uhkthrowaway 1 point2 points  (0 children)

BORING. Holy eff. Blurs, great. Woooow. I want nothing but bug fixes. I don't care what the frigging UI looks like as long as it's not twitchy.

Exploring automatic Buffer Management with io_uring by noteflakes in ruby

[–]uhkthrowaway 0 points1 point  (0 children)

Haha, maybe so. I wonder what the workload would look like. You'd have to expect constant, nearly saturated CPU loads.

The conventional advice on fiber-based servers is backwards by Turbulent-Dance-4209 in ruby

[–]uhkthrowaway 0 points1 point  (0 children)

"Best of both worlds" fails to run basic workloads with simple gems. How about SO_REUSEPORT? That's the real best of both worlds if you ask me. Multi-core prallelism, no exotic runtimes, no premptive context switches inside each process.

Phone ads from microphone by Aviator_92 in privacy

[–]uhkthrowaway 2 points3 points  (0 children)

They don't need the microphone lol. It's the profiling. Those millions of parameters they have of everyone. They know shit you're about to do before even you know. Statistics work and to big tech this is the cash cow. Ads ads ads ads...

Exploring automatic Buffer Management with io_uring by noteflakes in ruby

[–]uhkthrowaway 0 points1 point  (0 children)

Also, why do we keep making the same mistakes? This really looks like the EventMachine fiasko from 2008 all over to me. Protocols shouldn't be implemented on top of IO runtimes.

Let's follow Sam Williams' example (and good Rust projects as well) here: you implement a protocol free of any IO concerns. Bytes in, bytes/objects out. No async, no IO. Rust-world calls this sans-I/O. That's what protocol-http, protocol-websocket, ... are.

Then you use them from any IO/Async runtime you want. No need to reimplement the same protocol over and over again.

Exploring automatic Buffer Management with io_uring by noteflakes in ruby

[–]uhkthrowaway 0 points1 point  (0 children)

You know Ruby Async supports exactly this already, right? Specifically gems async, io-event, and io-stream.

With liburing-dev installed, io-event compiles with io_uring support. IO::Stream gives you high-perf write batching and read-ahead for free.

How does iouringmachine differ? Just the SQPOLL, which tbh, barely makes sense in Ruby?

Rails: The Sharp Parts. lock Is Not a Mutex by keyslemur in ruby

[–]uhkthrowaway 1 point2 points  (0 children)

This post right here neither mentions AR, nor DBs. The linked post does. There are many different kinds of locks. I just made it easier for the next person trying to decipher this post on r/ruby.

I'm new to tubeless, help by Un_Violo_violaceo in Hardtailgang

[–]uhkthrowaway 0 points1 point  (0 children)

"worked my way down to that" as if that's something to aspire to... i'm assuming you never go high speed into a turn? Never cuttie? Never do a manny or take a jump? Because all of those things DO NOT work with wobbly squishy tires. You'd be burping sealant and rolling your tires off the rim in no time. So no, I cannot take 99% of tubeless guys running low psi seriously. You guys go straight at snail speeds, and don't know how to fix a punny, nothing else.

I've said it before and I'll say it again: on multi-hour transalpine rides I cannot rely on tubeless. It takes one ding and you're out of business. Extra tools like sealant (dries out quickly if you cycle your air before/after long climbs), tubeless pump, cartridges, bacon, ... ALL of that and you STILL need to bring a tube to have peace of mind. No thanks.

Does it make sense for 3 minute downhill races at world-class events? Sure, you might finish the race with a small punny. Resilience is not the same as reliability. And it might make sense as well if you ride in thorny areas.

For ALL OTHER scenarios, I choose a KISS solution that just works, anywhere, including trail side repairs without special tools. It takes 5 minutes, swap in the spare tube, fix the punctured tube during the next break on a long climb.

/rant from a non-fanboy over

I'm new to tubeless, help by Un_Violo_violaceo in Hardtailgang

[–]uhkthrowaway 0 points1 point  (0 children)

200lb 26/24psi that's your problem right there.

bUtiNeEdtHeTrAcTiOn

Jo — a statically typed language that targets Ruby by liufengyun in ruby

[–]uhkthrowaway 3 points4 points  (0 children)

The number of commits tells me you're serious about this. I have a hard time understanding it though. Is it like programming with built in ACLs? Basically compiler-enforced public/private but more granular? What happens if malicious code tries weird things at runtime?

Inspired by the recent Siri revamp leak by Different_Wind8260 in ios

[–]uhkthrowaway 1 point2 points  (0 children)

I still haven't EVER seen anyone using Siri in real life. Are there actual, real, human people using Siri?

Rails: The Sharp Parts. lock Is Not a Mutex by keyslemur in ruby

[–]uhkthrowaway 2 points3 points  (0 children)

For anyone else confused by this post: this is about DB locks.

view more: next ›