61–70 of 200 posts
Can all the JS framework people lock themselves in a building for a year and figure our the right way to do this -- and only then share it with the world? Getting ridiculous.
we need a standardized declarative dom patching mechanism with data-binding that has optimal perf so we dont need to keep reimplementing virtual-dom.
Can all the JS framework people lock themselves in a building for a year and figure our the right way to do this -- and only then share it with the world? Getting ridiculous.
You could point to frameworks which have had majority usage at any given point and say those were the "right" ways at the time. But ideas evolve, which isn't so ridiculous.
Can all the JS framework people lock themselves in a building for a year and figure our the right way to do this -- and only then share it with the world? Getting ridiculous.
Edit: Sorry, I misunderstood your comment. I interpreted your comment as saying all of these new frameworks are making things ridiculous. This implies that Moon is contributing to that, and I'd rather have feedback.
Can all the JS framework people lock themselves in a building for a year and figure our the right way to do this -- and only then share it with the world? Getting ridiculous.
This is a common thought: https://xkcd.com/927/ You could point to frameworks which have had majority usage at any given point and say those were the "right" ways at the time. But ideas evolve, which isn't so ridiculous.
If you want a blazing fast JavaScript framework that's actually supported by a big company, look to Marko: http://markojs.com/ The syntax is a bit strange, but once you get used to it, it's a pretty simple framework to grok.
all frameworks are blazing fast, but some are more blazing fast than others.
https://rawgit.com/krausest/js-framework-benchmark/master/we...
Earlier quoted context omitted.
BareDOM is a proof of concept, the code is not very clean, but I'm sure you can get the ideas. Since Moon has a specific way of using the DOM, you might be able to cut down on the number of array positions per node (currently 8).
Is there any documentation on why to use a typed array
The API looks very similar to Vue. Are there any places where you specifically chose to be different, and can you explain some of your reasons?
I chose to be different in small things, such as being explicit about getting and setting properties on an instance. There are a couple oddities I didn't like with Vue as well, such as the syntax for a couple directives.
Check out the Medium article[1], it has the main reasons on why I made Moon.
Can all the JS framework people lock themselves in a building for a year and figure our the right way to do this -- and only then share it with the world? Getting ridiculous.
I'd love to know why you think Moon is ridiculous, so I can try to improve it. I honestly think what you're doing here is really ridiculous, try and give some feedback instead. Edit: Sorry, I misunderstood your comment. I interpreted your comment as saying all of these new frameworks are making things ridiculous. This implies that Moon is contributing to that, and I'd rather have feedback.
If you want a blazing fast JavaScript framework that's actually supported by a big company, look to Marko: http://markojs.com/ The syntax is a bit strange, but once you get used to it, it's a pretty simple framework to grok.
careful now... all frameworks are blazing fast, but some are more blazing fast than others. https://rawgit.com/krausest/js-framework-benchmark/master/we...
Earlier quoted context omitted.
And your time commenting would be better spent doing pushups. But that's not really how motivation and interest work.
But I also do push-ups. See, it is rarely an either-or proposition. One could push vue.js to the limit and then decide to do a rewrite. But to take the rewrite option as the first available exit whilst explicitly referring to the original is fragmentation where I wonder if it is actually needed.
These sorts of comments amount to judging how others spend their time. It's just as silly to me as me suggesting that you spend your time credentializing in React so you can improve it for free.
I'd say there's plenty of value to offer the world by creating alternative projects that stand on their own, experimenting with different approaches.