29 karma · joined February 7, 2015
Why is it a problem exactly ? If something great appears on the web it will be shared, saved and discussed and not forgotten. If something is useless or bad, it will be lost when the server stops, and that's good right ?
Same happened with paper books the last 2000 years, great one were replicated, shared etc. others went lost.
Not every website has open useful data for the long term.
Like JSLint or "use strict"; didn't remove JavaScript possibilities, it encouraged us to not write insane JavaScript.
They should consider making a document that lists all possibilities to organize code in modules and explain why some are betters than others, then in the same document explain the benefit for new syntax.
Do we really want to add more ways ? Complexity is an enemy of security, it will add more confusion. Maybe we should first disable/remove ways to load and execute JavaScript.
We should also think, if what really need is a client solution or a better tool/system to transform scripts, in a script server side.
Why, what should be clearly answered before thinking in terms of how.
Sometimes having the bigger picture in your head helps.
>If your traffic is huge, you need your own account in CloudFront or somewhere else. My service is for small projects.
Can you define exactly what small is ?
Proper template engine API and more system improvement coming next.
- What are the advantages over Knockout? I didn't use Knockout since a long time, it was a source of inspiration, so I can't fully answer this question. DOM99 doesn't tell you to use the Model-View-View Model pattern, but lets you organize your application as you want. This can also be a disadvantage if you are doing it wrong for example.
- Why does it weigh so much if its only ability is two-way data binding? Because you looked at source files that are not minified.
- Why the heck do I need to use Browserify for something that will NEVER EVER run on a server side?! You don't need browserify at all. I wrote the readme a bit too fast and forgot to mention other methods. You can also load it like any normal js file.
Hope I helped, I will update the readme in a few minutes to show how to use it without browserify. If you have other questions just ask.
- More examples that you can look at
- Templates with data population mechanism
- Better Readme file (how to use babel etc.)
- Other system improvements
I search criticism to make it better.
I know a couple of open source project that have their own library ready for reuse, but http://libraries.io/ doesn't find them because they are not for reuse for npm, and the like. And if I know a couple, there are probably thousands. These libraries are not not re-use first, but project first, re-use second.