Breathe in – breathe out. Breathe in – breathe out. Ever tired of breathing? You will be.
I've seen all my favorite activities turn sour. Pleasure turned into pain. Relief out of reach. Breathe in – breathe out.
The world is like this. Breathe in – breathe out. It does not go anywhere, it just breathes. Breathe in – breathe out. Until it breaks. Breathe in – breathe out. Find your peace.
It does not mix, and does not obstruct my eyesight. I can read while 'seeing' the events in the book. It does not pass through the eyes, and it is as detailed and sharp as my sense of reality - obviously. It just does not come through the same channel and that's easy to notice.
As a side note, it can be really odd to read something like: 'She saw two doors in the room. She took the one on the left wall.' And my flow is broken and I have to stop and reimagine the room, because I saw the two doors on the wall ahead - what is the author going on about? Maybe they should not be so exact about a tiny detail.
I had to once code a ‘wheel of fortune’ UI, that simply revealed trivia in random order. You had the perception of control: you could set a speed for the initial spin and see it gradually stop – as if it was adhering to physical laws – on an item that you haven't seen yet. The same item never came up twice. You always got to see all items on the first try. It was so easy to trick the mind into thinking you had control.
Edit: Sure, having automatic HTML escape for values is good. I work with JSX every day, and I can't really imagine having it all in one huge chunk and no code reuse. Also, what about conditional hide/show and lists?
The very first example in the README shows how to render a list using `map`, duplicated here[0]. I don't know about conditional rendering; the README doesn't have any examples of that, and there doesn't appear to be any actual documentation.
Edit: You could probably create a separate function with an `html!` return and call that from the first? If the return types line up, which they should, I don't see why you couldn't do that.
VS Code will type check open files only. So this only works for tiny projects. And all that typing (overly verbose) seems a lot of pain compared to setting up TypeScript properly.
I have had success combining old jQuery based components with a Mithril based UI (Mithril is similar to Vue, but simpler). But this only worked because I defined clear boundaries between areas managed by Mithril and areas managed by jQuery. Nesting such areas was possible. It was possible to make them both notify the other when they were about to remove a nested area.
Deleting an element created by the other framework however is never a good idea. They can manage their own event handlers and metadata only themselves. Instead, you need to ask the other framework to detach itself. You can use jQuery's special events to detect elements about to be removed from the DOM [0]. Mithril lets you define an onremove lifecycle callback on any component. From there, it is cakewalk.
