Theodo Blog

Hello, congrats on the release of your framework! I myself also wrote a reactive library for my own projects long ago when jquery was still widely used. Anyways, these days I moved from React to Solid.js so I know a bit how Solid works. 1. Solid.js also has "stores" and "createMutable" which allow deep tracking of objects and are also built on Proxy objects. Signals are great for single values, but Solid stores and createMutable are for more complex data. 2. Solid.js doesn't redraw entire components. (It's not like React.) It is fine grained and only updates the minimal exact DOM nodes required. This is why it is so fast and topped benchmarks when it first came out. https://dev.to/ryansolid/introducing-the-solidjs-ui-library-4mck I found https://blog.theodo.com/2023/07/solidjs-beginner-virtual-dom-signals which might be a good intro explanation to it. > Yeah, until you want to add some loops and conditionals in there. That's what regular programming languages are really good at. But it's a trade-off for sure. Solid's <For> and <Show when={}> and <Switch> tags are actually quite nice and very easy to parse visually. Regarding the "gaslighting" comments, I kind of feel the same way as the grandparent. No offense meant and I support everyone coding new open source frameworks, but it does kind of feel like that. I suggest doing a deep dive into Solid and even checking Ryan's blog https://dev.to/ryansolid or YouTube channel. There are a ton of concepts and good ideas to…

> Being fully documented means anything can work in any way. A protocol being fully documented does not mean you can get a device you cannot control (like an Homekit lightbulb) to connect to your server instead of the manufacturer's. If requests are signed and/or encrypted, knowing the protocol won't help if you don't have the keys. See also Tivoization. > For example, search the web for ‘homebridge alexa’ I had found it. I don't think you realize that there's no Homekit there at all. The point of Homebridge is to translate from a Homekit-speaking control app/assistant to a non-Homekit-enabled device: https://blog.theodo.com/wp-content/uploads/2017/08/workflow.png But when you use homebridge-alexa, you're replacing that first link with another protocol (specifically, MQTT+JSON, which is what it uses to connect to https://www.homebridge.ca/). So you've actually removed all Homekit parts from your smart home system!