41–50 of 83 posts
When I read something like this: "One of the problems we’ve had at &yet especially when working on large Backbone applications is a sane way to document the type of properties a model is supposed to contain. Backbone models, by default, don’t enforce any structure. You don’t have to declare anywhere what properties you’re going to store. As a result, people inevitably start saving miscellaneous properties on models f…
What a terrible lead-in example for justifying Ampersand.js. If you want structure, why not use a strongly typed language that transpiles to JavaScript? I don't understand how all these micro libraries you created get you any assurance of what you were after.
Can you please explain further why I would use Ampersand.js? Coming from TypeScript, I just see no substantive argument. If I were a Backbone developer who had monolithic dependencies, I could see your argument. I also get AMD modules or CommonJS modules for free with TypeScript.
> 4. Strict semver all the things > 5. Tiny module all the things! > The smaller the feature set of the low-level modules, the easier it is to avoid breaking changes. > 6. Expose the simplest API possible.
This is great, but what I would rather see is strict code coverage guidelines on contributions. The whole point behind having micro libraries is that writing unit tests should be easier, because there are simpler dependencies and each simple dependency is easier to mock.
Similarly,
> 7. Optimize for minimal DOM manipulation and performance.
The best way to optimize for performance is to include various performance testing, and never let performance get slower when considering patch contributions.
In short, less marketing fluff, more community process.
>>>> Backbone models, by default, don’t enforce any structure. You don’t have to declare anywhere what properties you’re going to store. As a result, people inevitably start saving miscellaneous properties on models from within a view somewhere, and there’s no good way for a new dev starting in on the project to be able to read the models and see exactly what state is being tracked. What a terrible lead-in example fo…
>>>> Backbone models, by default, don’t enforce any structure. You don’t have to declare anywhere what properties you’re going to store. As a result, people inevitably start saving miscellaneous properties on models from within a view somewhere, and there’s no good way for a new dev starting in on the project to be able to read the models and see exactly what state is being tracked. What a terrible lead-in example fo…
TypeScript isn't a client-side framework.
I realize you are trying to say I am comparing apples to oranges, but the site explicitly mentions Human Javascript approach as inspiration, and Human Javascript is all about choosing your tools. I am pointing out that there is an incredibly powerful tool that works extremely well for large-scale software development.
There are probably good use cases for Ampersand.js. The argument in this article is a really mediocre at best use case.
Earlier quoted context omitted.
I hate to say it, but there is a nugget of truth to this; the post is a giant wall of text when there should really be a summary of what the project is first, with the 'why' second. It took some browsing of the GitHub repos for me to figure out what this is. But I like it, and will probably use it, so the code is not the issue, just the presentation. :)
Did you see ampersandjs.com? Perhaps we don't link to that clearly enough. Though yes, a better overview would be useful.
When I read something like this: "One of the problems we’ve had at &yet especially when working on large Backbone applications is a sane way to document the type of properties a model is supposed to contain. Backbone models, by default, don’t enforce any structure. You don’t have to declare anywhere what properties you’re going to store. As a result, people inevitably start saving miscellaneous properties on models f…
Earlier quoted context omitted.
Parent should not have been downvoted and it irritates me that it was 1. hasenhj is correct, Backbone has been superseded for "advanced" webapps for at least two years and should not be used for new webapp development 2. I had the same confusion and question about what exactly ampersand is and what "advanced app" problems it sovles emotional edit: I've used Backbone, Knockout and React in "advanced" (enterprise-scale…
Complete shenanigans. Backbone is still heavily used in production for tons of "advanced" web apps. You can't just make statements like this because you decided you like angular or something better.
Just some hopefully helpful advice.
http://hueniverse.com/2014/05/30/the-fallacy-of-tiny-modules...