kentor

The logo is not as cute, sad :(

Just replaced Firebase with this in my personal notes app. Also removed redux along the way :) This is great!!

chess.com's 72-page report[0] alluded to this video, and I'm glad this is what they had to say: "We have concluded that the methodology and the underlying tools used in those analyses do not meet our standard."

[0] https://www.chess.com/blog/CHESScom/hans-niemann-report

He's a native speaker, just spent too much time around people with broken English recently.

I was pleasantly surprised to find that they finally dogfood Fresh for https://deno.land/

Source can be found here https://github.com/denoland/dotland

Video is cut off on mobile

I've recently used Deno to implement a couple of bots for a small discord channel, namely webhook handlers for Discord Slash Commands and Twitch's EventSub. It's honestly been amazing. Next to no configuration and deployments are dead simple. Just set up some env vars and push to github to deploy.

Is there a way to play at 2x speed?

Edit: Oh they're on the overcast app, which allows playing faster.

The 3b1b video was mind blowing. Link: https://www.youtube.com/watch?v=spUNpyF58BY

Why hate JSX? There are lots of benefits to it, like debuggability and variable scoping rules are exactly those of javascript. Templating languages, on the otherhand, are not debuggable and have awkward scoping rules. And, they always feel broken in one way or another.

JSX is not magical which is what I appreciate the most about it.

That is just javascript trivia that one rarely encounters in real code, and shouldn't be used to dismiss the entire language.

My view is you define methods with parameters, you call methods with arguments.

`ArgumentError` is consistent with an error during call time.

Mutable strings was a mistake.

"const a = {}" disallows reassignment to "a" but still allows you to mutate the object e.g. "a.b = 1". The const context does not allow you to mutate the object.

I wrote one for node: https://github.com/kentor/tiny-ssg

No "configuration". All code. You have to assemble the libraries from npm to make anything useful out of it though. Good luck.

Maybe if it weren't plural. You're way over thinking things.

Still no support for 4 column panes :\

Even a thin doctor who stays thin with a terrible diet?

VSCodeVim is atrocious in handling multiple cursors

amVim does it better, but is missing ; for repeating the last t or f command

if you have yarn run

    yarn why crossenv

Why would it?

Graceful degradation working though.

I have a few large React apps that have been using mostly Immutable.JS from the very beginning, so I rarely run into issues where I need to think whether what I'm dealing with is an Immutable.JS object or plain JS objects. I can see an issue if you are incrementally converting an app to Immutable.JS and dealing with a mix of plain JS objects though.

I have heard criticisms of lisp macros as making it a write-once language. If you're not working on a team then maybe it's fine, but other people aren't gonna want to figure out how your macros work.

Indeed! It also isn't for people who have "javascript fatigue." And they can use any of the 10 in the list by the OP.

I wrote my own because I don't like magic, reading a lot of documentation, and I hate templates. Using server side rendering with React is great! https://github.com/kentor/tiny-ssg

It would be weird for async functions to be synchronous wouldn't it?

Also the consumer is not required to use await with a called async function. They can use .then on it, or pass it around to other functions that consumes promises. Or, you could pass the async function to decorators that consume promise returning functions. Using experimental decorator syntax:

    @debouncePromise
    async function() {
       ...
    }

Also... the right side of await will effectively be wrapped in a simple Promise.resolve() if it is not a promise. Proof: http://babeljs.io/repl/#?babili=false&evaluate=true&lineWrap...

There is another talk on that: https://www.youtube.com/watch?v=6v4E6oksar

Nope. For dom elemenets I have been using `data-{name}` attributes, and pulling them out from the handler using `e.currentTarget.dataset.{name}`

I heard there will be copy-on-write for files. For web devs this would save a lot of space and time when copying files from yarn cache to node_modules.

You're not crazy. I think the people who want such colors (which I'm guessing is a very small minority) should use a custom css, instead of straining the eyes of the majority of users.