> We What does Backbone solve exactly?
Introducing Ampersand.js
61–70 of 83 posts
Re: Introducing Ampersand.js
#62I think properties should allow direct constructor assignment. I think it looks better than strings.
props: { name: String, age: Number }
Re: Introducing Ampersand.js
#63I think properties should allow direct constructor assignment. I think it looks better than strings. props: { name: String, age: Number }
That works for native types but gets trickier for custom datatypes, and ones where you want to specify custom getters and setters for example, and then specifying some as strings and some as constructors gets messy.
We do need to do some more documentation/cleanup around custom datatypes though for sure.
Re: Introducing Ampersand.js
#64I hate posts that don't show code. Show me the code, don't hide behind a huge post with buzzwords like "mobile first" and "modular". Show me what it actually does.
> I hate posts that don't show code. The quickstart (called "Learn") is 2 clicks away, well written, and full of code samples: http://ampersandjs.com/learn I hate it when people are lazy. ;-) But seriously, I agree that the code is what matters, not some blog post. However, I don't know if you could really unpack a framework in a single blog post anyways...
I agree with @inglor, the post could do a bit more to reel you in. From skimming over the content I could only understand that it is not backbone, modulesmodulesmodules. I found the page has issues conveying their surely valid and useful point, but they are using all the lazy folks, which are also potentially the lazy people that want to build apps using a framework.
Re: Introducing Ampersand.js
#65Earlier quoted context omitted.
Sorry, we just wanted to give the background to the project and why in the post, rather than focussing too heavily on code. There's plenty of API docs for the core components in http://ampersandjs.com And the clientside code for the example application generated by the cli is here: https://github.com/AmpersandJS/ampersand/tree/master/templat...
> Sorry, we just wanted to give the background to the project and why in the post, rather than focussing too heavily on code. Your landing page should contain what your users want to see, not what you want to put there. You might be excited about the motivation behind your project but nobody cares, really. I clicked on the link and I spent ten minutes reading a wall of text hoping to find good reasons why I should sw…
>Your landing page should contain what your users want to see, not what you want to put there.
Were does the entitlement come from?
Re: Introducing Ampersand.js
#66There's quite a bit about this library that I'm excited about, the small module philosophy, for one. But I started digging in and am finding typos and errors all over the place in the docs. Either this is still a work-in-progress (which would be surprising since it's major version 4) or the maintainers just aren't spending much time keeping up the documentation.
To the core team here and anyone making a library: please make sure your documentation is flawless and your example code exemplary. Thanks!
Re: Introducing Ampersand.js
#67There's quite a bit about this library that I'm excited about, the small module philosophy, for one. But I started digging in and am finding typos and errors all over the place in the docs. Either this is still a work-in-progress (which would be surprising since it's major version 4) or the maintainers just aren't spending much time keeping up the documentation. To the core team here and anyone making a library: plea…
With regards to "major version 4" we are doing our best to follow semver, where backwards incompatible changes require a bump in the major version.
So yes and no, this is a work in progress (what isn't) and we will constantly be pushing to make the docs better. We've been working hard over the last couple of weeks to get this into some form of a publicly releasable state, but yes it's not perfect :)
If you want to help us out, feel free to submit PRs or issues on github. The main site is at http://github.com/ampersandjs/ampersandjs.com while the API references are generated from their individual readmes, all available in that github org.
Re: Introducing Ampersand.js
#68There's quite a bit about this library that I'm excited about, the small module philosophy, for one. But I started digging in and am finding typos and errors all over the place in the docs. Either this is still a work-in-progress (which would be surprising since it's major version 4) or the maintainers just aren't spending much time keeping up the documentation. To the core team here and anyone making a library: plea…
With regards to "major version 4" we are doing our best to follow semver, where backwards incompatible changes require a bump in the major version. So yes and no, this is a work in progress (what isn't) and we will constantly be pushing to make the docs better. We've been working hard over the last couple of weeks to get this into some form of a publicly releasable state, but yes it's not perfect :) If you want to he…
I do often submit PRs for occasional typos in docs, but I don't really feel like copy-editing a whole README, which is what's required here. I'm not trying to be difficult, just honest.
I appreciate the use of semver, but I don't think the intent is to go through three major versions in as many days...
Re: Introducing Ampersand.js
#69Earlier quoted context omitted.
With regards to "major version 4" we are doing our best to follow semver, where backwards incompatible changes require a bump in the major version. So yes and no, this is a work in progress (what isn't) and we will constantly be pushing to make the docs better. We've been working hard over the last couple of weeks to get this into some form of a publicly releasable state, but yes it's not perfect :) If you want to he…
I do often submit PRs for occasional typos in docs, but I don't really feel like copy-editing a whole README, which is what's required here. I'm not trying to be difficult, just honest. I appreciate the use of semver, but I don't think the intent is to go through three major versions in as many days...
Sure, I wasn't expecting you to copy edit if you don't want to, just pointing you to the source.
> I appreciate the use of semver, but...
Oh, we aren't breaking things _that_ quickly! ampersand-state for example has been a repo since February.
Re: Introducing Ampersand.js
#70Earlier quoted context omitted.
Sorry, we just wanted to give the background to the project and why in the post, rather than focussing too heavily on code. There's plenty of API docs for the core components in http://ampersandjs.com And the clientside code for the example application generated by the cli is here: https://github.com/AmpersandJS/ampersand/tree/master/templat...
> Sorry, we just wanted to give the background to the project and why in the post, rather than focussing too heavily on code. Your landing page should contain what your users want to see, not what you want to put there. You might be excited about the motivation behind your project but nobody cares, really. I clicked on the link and I spent ten minutes reading a wall of text hoping to find good reasons why I should sw…
[deleted]