So, they're using Windows in Star Wars?

Content T TotallySD 1 year ago "code either works or it doesn't". - Someone who never did CSS before 1 1.6K REPLY View 58 replies

Content my linkedin profile R, python, javascript, shiny, dplyr, purrr, ditto, ggplot, d3, canvas, spark, sawk, pyspark, sparkly, lodash, lazy, bootstrap, jupyter, vulpix, git, flask, numpy, pandas, feebas, scikit, pm, bayes, h2o.ai, sparkling-water, tensorflow, keras, onyx, ekans, hadoop, scala, unity, metapod, gc, cct, krebase, neo4j, hadoop. I typically ask recruiters to point out which of these are pokemon.

Content Stable library that worked for years with no changes GitHub user Is this project dead?

Content Is ManualPayment.js X components ManualPayment JS ManualPayment.js ... 42 43 const toggleModal, refetchorders props; 44 const (products, loading, refetchProducts useProducts) : 45 const publishProducts usePublishProducts() ; 46 const apolloClient useApolloClient (); const id: shopid useShop() ; 47 const setupTotal, setSetupTotal useState(0); 48 const bondTotal, setBondTotal) useState(0) ; 49 const deliveryTotal, setDeliveryTotal useState(0) ; 50 const lateBookingFee, setLateBookingFee useState(0) ; 51 const startDate, setStartDate useState (new Date()); 52 const (endDate, setEndDate useState(addDays (new Date(), 1)) ; 53 const days, setDays useState(differenceInCalendarDays (endate, startDate)); 54 const (selected, setSelected useState( (1) : 55 const customerEmail, setCustomerEmail useState(""): 56 const customerName, setCustomerName useState("'); 57 const fulfillment, setfulfillment useState ("Pickup"); 58 const defaultoptions, setDefaultoptions useState(1); 59 const options, setOptions useState( (J) ; 60 const selectedCartVariants, setSelectedCartVariants useState( 1); 61 const uniqueInstanceIdentifier uniqueId("AddressForm"): 62 const paymentInputRef, setPaymentInputRef useState() ; 63 const paymentMethod, setPaymentMethod - useState("stripeinvoice"); 64 const customPrices, setCustomPrices useState(()) ; 65 const creatingCustomVariant, setCreatingCustomVariant useState( false); 66 const createCustomVariant, updateCustomVariant, createNewCustomProductWithVariants use 67 const newProducts, setNewProducts useState( ()) ; 68 const displayNewProductform, setDisplayNewProductform useState(false); 69 const customDeliveryPrice, setCustomDeliveryPrice useState("'); 70 const stockAlert, setStockAlert useState( J) ; 71 72 const display0rderConfirmation, setDisplay0rderConfirmation) useState( false); 73 const display0rderSuccess, setDisplay0rderSuccess useState( false); 74 75 const address1, setAddress1 useState(""); 76 const city, setCity useState("'); 77 const (region, setRegion useState(""); 78 const postal, setPostall useState("'); 79 const metafields, setMetafields useState(!)); 80 const cart, addItemsToCart, onRemoveCartItems, checkoutMutations ) useCart); 81 const cartStore useStores (); 82 const (lendersCartItems, setLendersCartItems useState(U)) ; 83 const (deliveryFeeAddon, setDeliveryFeeAddan useState (e) ; onths ago 84 g5 const (lendingSettings, setLendingSettings) - usestate(); DeLL ProdrammerHumor.io

This meme perfectly captures the love-hate relationship programmers have with Rust's infamous borrow checker! The meme shows how the Rust borrow checker (the system that enforces memory safety) is perceived differently depending on your programming background: If you come from low-level languages (like C/C++), the borrow checker feels like a blessing - "Oh dear, oh dear. Gorgeous." It's preventing memory leaks and segfaults that would normally haunt you! If you come from high-level languages (like Python or JavaScript), the borrow checker seems like an unnecessary obstacle - "You f***ing donkey." Why do I need to fight with the compiler about ownership when I'm used to automatic garbage collection? It's that moment when you're trying to write a simple Rust program and the compiler keeps yelling at you about lifetimes and borrowing rules... while C++ programmers are nodding approvingly because they've dealt with much worse memory issues!

When your operating system manual casually transitions from "Having Children" to "Watching Your Children Die" in the process management section, you know you're dealing with some dark humor. The meme brilliantly plays on the parallel between human relationships and computer processes. In Unix/Linux systems, a parent process "forks" to create child processes, and sometimes has to "kill" them or watch them "die" when they misbehave. That section on "Killing Yourself" is just process termination, but out of context? Pure psychopath energy. No wonder developers stare blankly into the void sometimes—we're just following the documentation.