Workaround: Potato peeler extends peeler, so just cast your carrots as potatoes before you peel them, and then cast them back to carrot afterwards
To cast them, it uses libvegs however. It is not available in any standard package libraries, so just quickly build it from source
Yeah but the current build of libvegs has some conflicts with libfruit, so if you need to use both you have to build libvegs in a different directory and then simlink it in /lib.
Tomato keep being casted as fruit, even that for any practical purpose it should be as vegetable
That's it, let's re-write the entire backend in C++ to make use of multiple inheritance to tackle this one use-case!
What do you mean "this is overkill"? Do you have any idea how many tomatoes go into a fucking salad!?
Someone should do it in rust now
Maybe cooking isn't for me.
Yeah but that's all my replacement's problem to deal with
I hate that I understand this. Well done.
Internal screaming.
If you forget the second step, well, that's what sweet potatoes are.
I'm a sysadmin by trade. My hobbies are:
Brother :(
only hobbyists and artisans still use the standalone carrot.py that depends on peeler.
in enterprise environments everyone uses the pymixedveggies package (created using pip freeze of course) which helpfully vendors the latest peeled carrot along with many other things. just unpack it into a clean container and go on your way.
I know you're joking but you basically just suggested buying a pack of frozen mixed veggies so you can pick out and use only the carrots for your stew, and the idea of someone actually doing that sends my brain into a tailspin
Do NOT give the carrot industry that idea
Big Carrot is coming for your stew
I got into cooking during lockdown, and have managed to get surprisingly good at it, to the point where if you asked me to make a meal of your choosing I could probably make it without looking up a recipe. It's actually unbelievably simple to make even complex stuff, basically using all the same rules you apply at work:
"RTFM" My irritation is that most recipes make a huge amount of assumptions - at least as many as code that assumes a certain version of library. You can get recipes that say things as vague as "prepare the chicken" and aren't at all clear what they mean, unless you've seen someone do it first, but it's published in a book like you should just know. I hate that. I also frequently see quantities like "1 can" which just drives me insane as though that's a standard unit.
There's also plenty of cooking specific jargon, so densely packed that beginners might spend the majority of the recipe looking up what the terms mean. "Chop" parsley - how finely? "Mix the ingredients" how long? What the fuck is Golden Brown actually?
Golden brown is however seared you like it, as long as it's cooked, and there's no pink. Cooking is not a science, unlike programming. Personally, I like a good crusty sear.
4.3 ??? Hell, I haven't updated my peeler since 2.1 - no wonder my stove won't even boot.
If you missed the 2.3 security update, you peeler is now mining crypto
I really enjoy programming, but generally I dislike cooking. I just want to eat, not spend time preparing to eat.
My experience with cooking has been that because I don't do it enough, I'm constantly dealing with food expiration dates and having to plan carefully around them.
In comparison, I've got some servers that have been running maintenance free for 5+ years. (Probably not the most secure thing, but meh, I don't have customers other than myself)
I think programmers often have hobbies that are more physical though. For me, I like working on my car because turning bolts and working with my hands lets my brain turn off for a while. I could see cooking and following a recipe being in the same category for others.
You should really try cobol, lisp, ada, or erlang. Dead languages are the best
So funny story. My stove is currently inoperable because the door lock on the oven is fucked up somehow. Why an oven needs a door lock and why the door lock being fucked should prevent the whole thing from working I cannot tell you. I've literally never used it. Thanks whoever programmed that...
The door lock I can understand for safety reasons. Bricking the whole thing because one part broke is lazy programming.
Every stove I've had with a self cleaning option also has an automatic door lock. The oven gets extra hot during self cleaning mode.
So.... just don't let me use self cleaning... Why does the whole thing need to be bricked because the lock doesn't work for a single function I'm not using? It doesn't lock when you use it for baking.
One like my washing maschine has, with touch display and all the firmware bugs where you sometimes have to reboot the maschine to unlock?
No no it’s the pot that’s behind . After you already peeled and chopped .
Unless this is an agile thing
An agile pot?
Will it run from me while I try to put ingredients in it?
Why would you peel a carrot?
Depending on the carrot, the skin can be significantly more bitter. And sometimes peeling can be quicker than trying to scrub dirt out of particular lumpy carrots.
YMMV
Just fork peeler from 4.2, rename it to "Skininator 4000" and set up a BuyMeACoffee button.
Why would you peel carrots? The peel has the healthy bits and it doesn't bother any dish.
Edit: or you could half-peel it, in stripes. Mom did this with cucumbers and zucchini.
Carrots often have dirt caked on the outside that's hard to get off with just water, so peeling is a good way to help with that.
The peel has the healthy bits
Sort of, but not really. The nutrients of a carrot may be slightly more concentrated in the skin, but all layers of a carrot contain those nutrients. You're not depriving yourself of an appreciable amount of nutrients by peeling a carrot.
...you understand carrots don't have skin, right? You're just removing the dirty part.
The code for the peeler is stale, it stopped working three carrot seasons ago, but no one wants to rewrite the PeelerBladeRdge class.
Hey man, leave the carrot alone.
Post funny things about programming here! (Or just rant about your favourite programming language.)
