5 ms·
Good work, but I prefer the syntax of cookies-js [1] Side note, Bower is a dying package manager. You'd get better results if you promoted the npm link over bo
by izolate 10y ago
Good work, but I prefer the syntax of cookies-js [1]
Side note, Bower is a dying package manager. You'd get better results if you promoted the npm link over bower.
[1] https://www.npmjs.com/package/cookies-js https://www.npmjs.com/package/cookies-js
- franciscop 10y agoFair enough, I didn't like it and that's the main reason why I continued and published this package. Is it just a preference or do you have any reasoning for liking it?
- izolate 10y agoIs preference not a valid reason? :) Other reason: the syntax is more explicit, and already familiar to anybody who has used Maps [1] I find your syntax a little confusing. It's not immediately obvious how I would set multiple cookies with different options, for instance. [1] https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_Objects/Map https://developer.mozilla.org/en/docs/Web/JavaScript/Referen...
- franciscop 10y agoIt is totally a valid reason, that's what I wanted to say with fair enough (: I see, you could just call the same function few times with different options (preferred) as cookies(cookie1, opt1); cookies(cookie2, opt2); or concatenate them: cookies(cookie1, opt1)(cookie2, opt2); but this is arguably really strange syntax. I will add more examples to the readme.md to make it more clear :+1:
- Fifer82 10y agoUnlike izolate, I prefer your API. Great Library!
- franciscop 10y agoThank you
- kakarot 10y agoIs this something like putting it out of its mercy, removing your open support for bower because you hear it's dying?
- Kiro 10y agoTo be honest I tend to avoid packages that have bower support. It just gives me the feeling of legacy. It's unfounded, I know, but that's me.
- konradb 10y agoTo an old man out of the loop, what gives you a supported, future-looking feeling?
- izolate 10y agoPrecisely that. To in-the-loop JS developers, Bower is old news. To see Bower/Less/jQuery in 2016 conjures up images of out of touch backend developers living in 2011. There are better alternatives available (NPM/PostCSS/vanilla.js to the above)
- konradb 10y agojQuery to me has the same connotations but I was surprised by Bower. As an out-of-the-loop sometime JS developer what's respectable these days, npm/gulp/sass, vanilla.js/react/angular2?
- franciscop 10y agoBut bower came after NPM... Anyway, I didn't really intend this library to be in-the-loop. I just did it because I couldn't find one I liked in 2016. Which is just nuts on itself. so I went all old-school and tried to keep cross-browser support high and make it simple. It took an hour to be done and a couple of them to test and document it (plus another couple of them for small details such as CDN, bugs/patchs/small features).
- 10y ago
- berdario 10y agoBower is definitely not dying, and in fact Npm is totally unsuited for some communities http://harry.garrood.me/blog/purescript-why-bower/ http://harry.garrood.me/blog/purescript-why-bower/
- zatkin 10y agoTL;DR: dependencies are a difficult problem. When you use two distinct dependencies that subsequently have the same dependency but separate major releases, you may encounter breakage. The author simply prefers Bower because of how it handles this problem differently than npm.
- joshwcomeau 10y agohttps://www.google.com/trends/explore?q=bower,npm https://www.google.com/trends/explore?q=bower,npm "Dying" is a bit strong, but there's no question that NPM is becoming the go-to choice for javascript development across the stack.