Angular touted its declarative syntax, but really what does that give you? It saves a few strokes over something like Hey, how are you! And then in your javascript: controller.onStateChanged("name").set(function () { $(".myapp-name", container).html(state.name); }); The latter is more explicit and also declarative. It also gives you a lot more flexibility and is much more efficient than dirty-checking. React kind of…
Hey, {{name}} how are you! When one has 500+ states to manage, it's not just a matter of saving a few strokes anymore. now if you're really smart you'll write a compiler that desugar and inline everything so you get the best of both world: A declarative syntax and production speed.
“Implement text editor DOM updates manually instead of via React”
221–225 of 225 posts
Re: “Implement text editor DOM updates manually instead of via React”
#222Earlier quoted context omitted.
So use a component adapter, like polymer... That said, I wouldn't mind something closer to XAML or Flash/Flex that was an open specification, with a cleaner language implementation (though, I like JS)... The trouble is actually getting a cross-platform rendering engine working everywhere that HTML/HTTP already works... So, you go build it, get it working at LEAST on Windows, OSX, Linux, Android and iOS... then we'll…
> So use a component adapter, like polymer I am yet to be on a project where the customer uses them on their stack. >So, you go build it, get it working at LEAST on Windows, OSX, Linux, Android and iOS Qt, JavaFX, Xamarin Forms, any SDL based GUI
I don't want to spend money on the side projects I'm just playing with, but it would be nice to have them cross-platform (including mobile). Do any of those options still apply? IIRC Xamarin is expensive and there's no free way to run Java on iOS? All the SDL-based GUIs I've seen have looked awful.
Qt would be lovely - what does using it from Android Java look like? I remember messing with the Qt Java bindings a while ago and finding them a bit ropey.
Re: “Implement text editor DOM updates manually instead of via React”
#223Earlier quoted context omitted.
Mobile and micro-services will change what? Even then microservices are an architectural pattern, it's not inherently tied to a platform, whether it runs native or in the browser.
Many native application on the mobile space are using micro services with a native UI, as a means to provide an integrated user experience with the respective platform features and keeping the business logic portable.
Re: “Implement text editor DOM updates manually instead of via React”
#224Earlier quoted context omitted.
It is obvious, because when you use a component, it's usage is as a single root node. should not render multiple root nodes.
return label ; That's illegal and will fail to compile and it's not obvious why that should happen.
Re: “Implement text editor DOM updates manually instead of via React”
#225Earlier quoted context omitted.
Can you add something more about what is the minihtml module? Google says nothing.
Grep the ST3 dev channel changelog [1] for "minihtml". [1] http://www.sublimetext.com/3dev