I am in Magic Recipe Hell.

Is anyone familiar with Magic Recipe Hell? This is the place developers suffer when the start learning a new framework where every slightly different variation of functionality you want to implement requires a new magic incantation and cannot be built with any combination of the previous magic incantations you previously learned.

Reply to this note

Please Login to reply.

Discussion

Ruby on Rails

It happens all over the place, this time dioxus. But it happened to me with django too.

There is one way to create a context that automatically passes to your child components. There is a different way to create persistent data that uses LocalStorage. But you cannot just combine these.

And Copilot has no idea how to stick with version 0.6, even when yelled at it puts code in there that cannot compile because that isn't how they do it anymore.

And the 'basic' way is to pass props, but you cannot pass props through a Router with a Nav (at least no example combines these things and the compiler hates it).

Convention over configuration! Lol

JK I still love Rails

crying in yelds

Try an LLM. Even if you throw out 95% of what it writes, no feelings were hurt

Persistance!

Bash your forehead against the keyboard in the imaginary battle against the computer. You will win as the computer can't regenerate tissue during sleep.

Yes. It was the Zend Framework and Magento for me. I got so sick of having to learn new incantations that I created my own php mvc book of spells that instead of of doing "convention over configuration" I did convention by configuration. I.E. the framework would do magic however I want.

Still need to go back and finish modernizing that one.

Try using Rust next time