Was Vibe Coding Before It Was Cool

So OpenClaw created a registry that's basically a buffet of malicious npm packages, and now they're getting roasted for not having a plan to deal with it. Classic "move fast and break things" energy, except they broke the entire supply chain. The maintainer's responses are *chef's kiss* levels of passive-aggressive helplessness. "Yeah got any ideas?" "I don't have a magical AI" "And who reviews the flags?" Dude basically built a vulnerability-as-a-service platform and is now asking the internet for product management advice. The "I understand you have a lot on your plate" reply is the most polite way anyone has ever said "bro you're cooked." That table showing skills with 3+ variants and 400+ downloads? That's 200+ malicious packages just vibing in the registry, waiting to pwn some junior dev who npm installs without reading. The real kicker is everyone realizing there's no review process, no flagging system, and apparently no exit strategy. Just pure chaos with a nice UI. Someone suggest they just shut it down and got hit with "or people us their brain when finding skills" – because yeah, expecting developers to manually vet every dependency has worked SO well historically. 🙃

Content STOP DOING OS • CPUS WERE NOT MEANT TO BE SHARED! • YEARS OF SCHEDULERS yet NO REAL-WORLD USE FOUND for running more than one task at a time! • Wanted to terminate a process? We had a tool for that. It was called manual restart. • "Please give me 30 bytes of virtual memory. Please allocate it on the heap. ' - Statements dreamed up by evil wizards. LOOK at what kernel developers have been demanding your respect for all this time, with all the memory and CPUS we built for them. (This is REAL KERNEL CODE, done by REAL KERNEL DEVS): prev_state = READ_ONCE(prev->__state); if (sched mode == SM IDLE) { * This is how we return from a fork. * SCX must consult the BPF scheduler to if (Irq->nr_running 88 !scx_enabled()) { i SYM_CODE_START(ret_from_fork) next = prev; bl schedule_tail goto picked; cbz x19, 1f MOV x0, x20 } else if (! preempt 8& prev_state) { try_to_block_task(rq, prev, prev_state); switch_count = &prev->nvcsw; blr X19 1: get_current_task tsk MoV X0, sp } bl asm_exit_to_user_mode ret_to_user next = pick_next_task(rq, prev, &rf); rq_set_donor(rq, next); SYM_CODE_END(ret_from_fork) NOKPROBE(ret_from_fork) STOCALE UEFANEX drag pushO: __diag_ignore(GCC, 8, "-Wattribute-alias", dancinkage cong sysomndnes Marta, aC vecc, VA AKUS_/ attribute (altas( stringity( se systanane)))); ONGsystanane, ERRNO); _do_systinare(__MAP(X,__SC_DECL,_VA_ARGS_ _se_sysmenare(__MAP(X,__SC_LONG,__VA_ARGS__)): se sysauname MAP(X, SC LONG,VA ARGS_)) do sussunare MAP(X. SC CAST, VA ARGS. _MAP(X, __SC_TEST,__VA_ARGS_ -PROTECT(x, ret,__MAP(X, __SC_ARGS, _VA_ARGS__)): 10000 94 static inline long SYSCALL DESTEX - do systanare (_MaP(X, _ SC_DECL, _ VA ARGS_ ????? ?????? ??????????? Hello I would like to a process please. They have played us for absolute fools.

When the compiler says "Error on line 34" but line 34 is just a closing bracket. That moment when you realize your entire codebase is a house of cards held together by hopes and prayers. The real error is probably 200 lines above where you forgot a semicolon, but the compiler decided to wait until now to have its emotional breakdown.

Content if you ever feel useless, just remeber the things exist : if you ever feel useless, just remeber thse things exist :

Content THEN I'M HOMOSEXUAL. ProgrammerHumor NOW I'm JavaScript developer STONETOSS.COM withe Sad Memer

The prison hierarchy just got disrupted by a frontend developer. While one inmate brags about murder, our CSS criminal quietly admits to writing <div class="right">Fat unibrow guy</div> – a crime so horrific it sends the murderer cowering in the corner. When you use meaningless class names and non-semantic HTML, you're not just hurting yourself... you're terrorizing every developer who inherits your code. The real prison was the codebase all along.