nolanl

14 ms·

91.
by nolanl 11y ago
If anyone's confused by the 4 "puzzles," I whipped up a JSBin to demonstrate: http://jsbin.com/tuqukakawo/1/edit?js,console,output
92.
by nolanl 11y ago
Bluebird is awesome. :) I especially love promisifyAll() and promisify(). The only reason I didn't include something like that in the post is that I didn't want to overwhelm newbies. I think it's already confusing enough what
93.
by nolanl 11y ago
Very true. And as I mention in the article, ES7 async/await should help fix that: http://pouchdb.com/2015/03/05/taming-the-async-beast-with-es...
94.
We have a problem with promises(pouchdb.com)
164 points by nolanl 11y ago|102 comments
95.
by nolanl 11y ago
Sorry, my bad. It's Chrome, Safari, and IE that don't have toBlob(). I'll fix the post.
96.
The state of binary data in the browser(github.com)
24 points by nolanl 11y ago|2 comments
97.
by nolanl 12y ago
That would be my #1 desired feature to add to this app - syntax highlighting for the Jison grammar. Since CoffeeScript and Handlebars are written in Jison, you'd think someone would have done this already, but I couldn't wrap my h
98.
Show HN: Jison Debugger – A visual editor for JavaScript parsers and lexers(nolanlawson.github.io)
24 points by nolanl 12y ago|5 comments
99.
by nolanl 12y ago
I agree that a purely blocking style would be best, and maybe we can hope for that in ES8. :) But async functions are still much nicer than promises. And in practice, I don't think it will be that hard to explain to newbie programmers.
100.
by nolanl 12y ago
My main point was that promises represent an entirely new coding style, which pantomimes the familiar try/catch/return, but isn't quite the same. So you have to learn two systems. For instance, the following three blocks are
101.
Taming the asynchronous beast with ES7(pouchdb.com)
30 points by nolanl 12y ago|18 comments
102.
by nolanl 12y ago
Unfortunately, support is still not great: http://caniuse.com/#feat=indexeddb Those yellows are really more yellow than green, in my experience. :/
103.
by nolanl 12y ago
LocalForage has great cross-browser support (automatically switches between IndexedDB/WebSQL/LocalStorage), not to mention workarounds for browser bugs and the ability to store more data than what LocalStorage allows (~5-10MB). It
104.
by nolanl 12y ago
Totally agree. I could write an even-longer essay on "How to be a good open-source maintainer." Too many projects have poor documentation/tests, or they don't make it clear how to contribute. Something as simple as a CON
105.
by nolanl 12y ago
Under the hood, it seems [1] to be based on the excellent LocalForage project from Mozilla [2]. It would be nice to acknowledge that on the website somewhere. [1]: https://github.com/Irrelon/ForerunnerDB/blob/
106.
How to be a good open-source citizen(gist.github.com)
3 points by nolanl 12y ago|2 comments
107.
by nolanl 12y ago
There actually is a PouchDB Node server already: https://github.com/pouchdb/pouchdb-server/ . Installing it is as easy as `npm install -g pouchdb-server` Also, Drupal recently announced that they're going to o
108.
Efficiently managing UI state with PouchDB(pouchdb.com)
1 points by nolanl 12y ago|0 comments
109.
by nolanl 12y ago
The WKWebView is buggy/breaking enough that the Cordova team has still not integrated it: https://shazronatadobe.wordpress.com/2014/09/18/cordova-ios-...
110.
by nolanl 12y ago
Interesting project! It seems to share a lot of the goals and design choices of PouchDB/CouchDB: distributed, offline-first, eventually consistent, deterministic conflict resolution, etc. One big difference I can see is that it's
111.
by nolanl 12y ago
PouchDB dev here. The map/reduce API is definitely a bit cumbersome, which is why we're replacing it: http://nolanlawson.github.io/pouchdb-find/ :)
112.
by nolanl 12y ago
Also Cloudant recently came out with their own libraries for iOS and Android ( https://cloudant.com/blog/introducing-cloudant-sync ), and in principle they should all be compatible with PouchDB/CouchDB. So I like to
113.
by nolanl 12y ago
Dale's humble, but he really is doing the Lord's work, because he set up all the Selenium/Saucelabs tests against the different browsers, fixed intermittent bugs and timeouts, etc. He's been doing all the unglamorous wor
114.
by nolanl 12y ago
Author here. :) To the credit of the standards bodies, I think speccing a database presents a totally different set of challenges than with the typical browser APIs. The fact that it took them three tries to get something everybody liked (L
115.
by nolanl 12y ago
PouchDB, ydn-db, IndexedDBShim, and Lawnchair will do this as well. Web SQL may be "deprecated," but it's unlikely to be dropped by Apple or Google, since so many mobile web apps depend on it. Even the mobile version of Gmail
116.
Offline-first is people-first(nolanlawson.com)
11 points by nolanl 12y ago|1 comments
117.
by nolanl 12y ago
Great list, but one thing you're missing is to also specify the prefix-less CSS attributes for -webkit stuff. It only takes an extra line of code, and it future-proofs your app for Firefox OS and IE Mobile.
118.
by nolanl 12y ago
Heh, I learned a thing about a thing! :) Curious to know how so many quirks slipped through, though. Maybe I should do a PR on the tests for bugs that the browser vendors might not know about, e.g. https://gist.github.com&#x2F
119.
by nolanl 12y ago
That's a good point, and one I could have added to the post. There are bugs in Web SQL, but they're largely the same on both Chrome and Safari. IndexedDB is trickier, because the bugs are all different between Firefox, IE, and C
120.
by nolanl 13y ago
PouchDB is a fairly up-and-coming JavaScript library, and the maintainer makes a good effort to mark issues as "goodfirstpatch" or "goodstudentproject": https://github.com/daleharvey/pouchdb/iss

More ›