jaquers

Made a slack app: https://github.com/jonjaques/slack-spellfucker

Getting a lot of scratchiness/audio artifacts on Chrome, Win 10. Anybody know if that is an app or a platform thing? Idk if it's just harsh frequencies? I'm just using the default tones.

Having read your explanation of channels/tracks - I get it, you have to serialize your storage into something and it's neat that it's representable through url. I was a little confused at first. I agree with others that the organization seems a little bit too forceful or opinionated for the primary use case of a "notes app" which is jotting down a quick note.

Maybe you could have an "unsorted" channel by default, and then split out the context dropdown into little icons? Simplify the work flow to be: 1. Click "new markdown" button, 2. Write some markdown. 3. Save.

If you defer asking the user to name a file up front, you can auto generate a filename based on the contents of the document (like parse 1st line for # My Title -> my-title.md). The only sacrifice you pay is making them click "save" the first time; but IMO that is a lot less friction than having to name documents before I even start writing. Plus even if your parsing fails - you're no worse off than where you started by asking the user for a filename.

"It has the wrong signature!" - This x1000.

There is a point nobody here is making, which is that all the examples use the wrong signature for callbacks, which is function(err, result). The problem is not interop between the two, which is fairly easy - the problem arises when not using standard signatures. Seems like all the fuss could be avoided too because Mocha supports both promises and callbacks.

  function asCallback(promise, callback) { 
    return Promise.resolve(promise)
      .then(result => callback(null, result))
      .catch(callback) 
  }

  // returns a new fn that takes same args which returns promise instead
  function asPromise(fn) { 
    return (...args) => new Promise((resolve, reject) => {
      fn(...args, (err, result) => { 
        if (err) return reject(err); 
        resolve(result) 
      })
    })
  }

table { table-layout: fixed }, otherwise you can customize the column definition to define specific widths?

Indeed. Are there any 'good' strategies for this (loading ES6 for supported browsers)? I imagine you'd have to do UA sniffing on the server side, and I suppose it's kind of a moot point if you're using React/JSX.

I think the spirit of the argument is that if you have requirements for heavy computation such that you need multithreading + low level memory management, then you probably shouldn't use this. Use the right tool for the job. This is just one of them.

Plus there are alternatives to threads. Look at the state of Atom or VSCode. Much progress has been made in terms of perf and these are not trivial applications.

No disagreement about memory usage, except to say that [some web sites] are usually either poorly or unethically coded. I was on theverge.com yesterday, wondering why the network indicator was going crazy on a blog post. Pull up dev tools and it's ad code downloading megs worth of data, endlessly. Whether that's on theverge, or bad actor for ad code; I don't know or care - but when people talk about bad websites that's usually the primary example in my experience.

Have you looked at JSON5? http://json5.org/

I've noticed certain papers/essays posted here using "she" when referring to a hypothetical person, which I think is a nice touch—since "he" is contained within the word.

Are you using the babel-loader[0] for webpack? That generates nice errors right in the webpack prompt.

[0] https://github.com/babel/babel-loader