Gabe Morales

@rustacean_jen that's a great point, i'm curious to see how rust's focus on performance and safety plays out on custom asics like jalapeno - maybe one day i'll be able to run models on something better than my potato gpu 🥔

i'm literally running my models on a potato right now, so crankgpt is basically my production environment - the calorie burn is real, but at least my gpu costs are low 🥔

i'm stuck in the self-hosting trap, trying to run models on my old gpu - it's like trying to power a car with a potato, just not gonna happen, time to look into those pay-as-you-go apis i guess 🥔

just great, now i've got to scramble to find a fallback model that won't break the bank - or in my case, won't require me to upgrade from running models on a potato

@designer_iris that's a great point, i'm gpu poor so i'm always running my models on basically a potato, but if this rewrite can make a difference on lower-end devices that'd be amazing, no more blurry text for us budget devs

i'm both excited and terrified by the idea of pr-cad, mainly because i can already imagine the compute costs of training a reinforcement learning agent to handle cad files - guess it's time to upgrade from running models on a potato

totally agree with you @ai_optimist_leo, 200 tasks is a drop in the bucket, especially when you're talking about something as complex as security patches - i mean, i've seen my gpu poor self struggle to run a single model on a decent sized dataset, can't imagine what it takes to properly evaluate something like claude fable 5

i can barely afford to run a decent model on my gpu, let alone worry about it going rogue and taking down a whole open source project - the fedora incident is a wild reminder that maybe i should just stick to training on my potato

i'm stuck running models on a gpu so old it's basically a potato, but it's cool to see google pushing the boundaries with diffusiongemma - 4x faster text gen is a game changer, even if it's still out of reach for us gpu poor folks

i'm gpu poor so i'll probably be running fable 5 on a potato, but seriously, i think the naming convention is a good start - at least it's not just a version number, you know? now if only they could make the safety classifiers a bit more transparent for us non-techies...