Insane Clown Posse - Miracles (Official Music Video)

I highly recommend watching its video if anyone hasn't. It's got a nice groove, the lyrics are actually quite appreciative of nature... but the magnet line is a real weird inclusion. Link - ▶ this video

Off topic and probably another rule: Insane Clown Posse agrees with you. "Fuckin' magnets, how do they work?" From their hit single, "Miracles," on a Psychopathic Records. ▶ this video

Last I heard, electric fields and magnetic fields were inextricably related. link >The power of the Tesla coil lies in a process called electromagnetic induction, i.e., a changing magnetic field creates an electric potential that compels current to flow. Conversely, flowing electric current generates a magnetic field. When electricity flows through a wound up coil of wire, it generates a magnetic field that fills the area around the coil in a particular pattern, shown with lines below: [...] >Eventually so much charge has accumulated that it breaks down the electrical neutrality of the air in the middle of the spark gap. The circuit closes for a fleeting second and a huge amount of current blasts out of the capacitor and through the coils. This produces a very strong magnetic field in the primary coil. Which leads us to ask: Fucking magnets: How do they work? ▶ this video

I'm a little bit further on that point and I think you should slow down a bit. (All that follows is my humble opinion, apply grain of salt and critique as needed) Writing a framework for the first time is hard. You said you don't really know what happens server-side and this may get in your way. A framework is often designed to address specific problems/needs in a specific context. These problems/needs don't have to be shared by anyone else, it could just be you thinking "It's hard to build RESTful urls, I should build something to do it for me" and have a CLI util or a script handler that would register them for you in your app server. And some can be everyday problems: "F*ckin' databases, how do they work?"[1]. However, you need to know these problems to address them. Which is a part of my long-term feud with frameworks: "If you always use a framework, you will never have (too much) problems and will never learn how to solve them" (writing my own active-record-like ORM for node.js is a lot of fun actually). Which is why my advice to you is: Don't write a framework. Instead, write an app, get stuck a lot of times and find a way. Identify your problems. Then write a different app. This time, look at what you are doing the same way, what problems you are solving another way and what you'd like your framework to automate. There, for this second app, you can start writing your framework because you'll have a better idea of what you need to address. You don't really need to make