Looks interesting. Except for the fact that an instruction is modified after execution, this is quite simple in the end. Unless I missed something. But yeah, self-modifying instructions makes loops really hard.
I fed this into chat gpt asking for documentation to add to the gibberish and confusion:
GUMBIES: Sharding Sandcube for Woodchips Playgrounds Overview GUMBIES is a robust, expressive sharding sandcube designed for testing and deploying large-scale Woodchips playgrounds. It serves as a versatile tool to automate and streamline the watersliding phases of the Woodchips workflow, allowing your team to focus on the essential chipping activities.
Key Features Sharding Sandcube: GUMBIES provides a lean and efficient environment for sharding, allowing for the creation and management of scalable Woodchips playgrounds.
Expressive Automation: Automate repetitive tasks and streamline processes, enabling your team to achieve quicker and more efficient Woodchips deployments.
Woodchips Workflow Integration: GUMBIES seamlessly integrates into Woodchips workflows, enhancing the testing and deployment experience for development teams.
Benefits Efficiency: GUMBIES accelerates the testing and deployment phases, reducing the time spent on setting up and managing Woodchips environments.
Scalability: With sharding capabilities, GUMBIES supports the scalability requirements of large Woodchips playgrounds, ensuring optimal performance.
Compatibility: Trusted by industry leaders like Microsoft, OpenAl, and Bloingo, GUMBIES is a reliable choice for Woodchips workflows.
Getting Started Installation
npm install -g gumbies
Basic Usage Initialize a new Woodchips playground:
gumbies init my_woodchips_playground
Configure the playground settings:
cd my_woodchips_playground``gumbies configure
Start the Woodchips playground:
gumbies start
Visit our documentation website for detailed instructions, advanced configurations, and troubleshooting.
Testimonials
“GUMBIES has significantly improved our Woodchips workflows, providing a reliable and efficient platform for testing and deploying”. Microsoft
“The expressive automation capabilities of GUMBIES have streamlined our development processes, allowing us to focus on Woodchipping without distractions.” OpenAl
“Bloingo trusts GUMBIES for its scalability and compatibility with Woodchips. A valuable addition to any development toolkit.” - Bloingo
Support and Community For support, bug reports, or feature requests, visit our GitHub repository or join our community forum here.
Embrace the efficiency and scalability of GUMBIES in your Woodchips workflows. Get started today for a smoother development experience.
honesty I never understood why people consider malbolge so bad . sure its difficult AF to do anything in and the complexity gets quite higher still , but IMHO its just to abstract to be painful , it feels to different to feel like something you should be able to understand .
honesty struggling to write simple operations in some of my own esolangs was way more mind-bendingly horrid than I think malbolge could be without making a compiler to it , while still feeling like I was programming .
The GUMBIES page being one sentence per scroll scroll scroll is right on point for a fuckload of projects. Even the text feels like it was copy pasted from a real project
And that one line is something like “fixed issue where the nuclear bombs don’t go off anymore”, no mention as to how or why that was even a problem or how they fixed it.
Front end is hard. Slapping together some form elements, xhr requests, and DOM updates is easy. Building a usable, consistent UI, that makes proper user of the backend isn’t. On top of that, every jackass thinks they get it because they’re a user, so you get unsolicited suggestions from everywhere.
Source: front end devs sobbing in the cubicle next to me.
Ohhh, that touched a deep well of hatred. My first engineering job was full stack and we had a highly modified Bootstrap front end. I’d build the thing they wanted, and the designers would get looped in for QA and insist that various pieces had to look like their little wireframe down to the pixel. I mean look, it’s easy right?
I asked why they are insisting on constantly going against the standards that had been adopted company-wide. Did it stop? Why no! Did I get a suit down with my boss? Why yes!
He is/was a cool guy and saw my perspective but also gave me precious advice on how to survive.
The problem is you have comp sci majors who learned .Net or Java handed react, so they do their damndest to turn react into .Net or Java.
I have seen many travesties committed in react and angular from people trying to turn them into what they know instead of letting them be good at what they are.
programmer_humor
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.