lynndylanhurley

They did this to us as well. And not only this, but they blocked our ability to push new releases until we opted into the new plan. And this literally happened on the day of a major release for our biggest client. It felt like we were being held at gunpoint.

We called them and begged them to give us an extension so we could perform the release, and their sales rep treated us like we were the irresponsible ones for not reading the emails they had sent us carefully enough.

We've since moved to Vercel and will never use Netlify again because of the way they managed this.

Rust is not well suited for the same things as javascript / typescript / jsx / etc.

Also javascript and typescript are not well suited for compilers and dev tooling.

It shouldn't be seen as a negative that Deno is using rust in places where it really shines, which is a totally different use case than what deno is typically used for.

I'm the creator / maintainer of a widely used authentication library, and I also don't know the answer to this.

There have been several issues reported around this, but no one seems to have a good proposal for a solution.

I've also discussed this with security auditors from Cobalt (because they flagged it as an issue), but they also did not propose any solutions (other than using httpOnly cookies instead of tokens, which doesn't really address the issue).

I had to use my old 2012 MBP the other day after using the 2016 MBP since it was released, and the 2012 keyboard was a stunning improvement over the 2016.

Which is strange because I never thought the 2012 keyboard was exceptional.

Do any of you prefer the new keyboard?

Here's a question - if the results were due to an obscure Safari bug, then why did Apple remove the battery life estimate with the latest OS X update?

I've been getting 2-3 hours max out of my new 15" 2016 MBP and I don't even use Safari. I'm just running webpack, vim and Chrome.

Try cmd + ` (backtick)

    You cannot invalidate JWT tokens
        

    This is simple not true. You ALWAYS will sign your tokens with a well known secret, you could eventually even add some salt from a database to it.

I think one of the benefits of some (most?) JWT implementations is that it doesn't hit the database on every request - the token is only validated against a global secret.

So you can't invalidate a single user's session without invalidating all users' sessions.

Not sure if joking...

The react test utils work in combination with jsdom. For example, TestUtils.renderIntoDocument will use jsdom as the document.

There is a facebook-sponsored test framework called "jest" that is more akin to mocha or jasmine, but of those three frameworks it is the worst in my opinion. It's absurdly slow, poorly supported, and it mocks all imported/required modules by default which causes me more problems than it solves.

Yeah me too!! Anybody know the status?

How does this compare with SuperCollider / Overtone or CSound?

This is exactly what I need. Does a polyfill even exist?

I completely agree with you on this. I've had to send my 1st gen retina macbook pro back to the service depot literally 5 times. The first hard drive was apparently defective, as were the first and second logic boards. And twice I had defective parts replaced with identical defective parts.

And whenever anything is sent to the service depot, they wipe the goddamn hard drive. No matter what. And you guys know the pain of re-downloading XCode, re-installing everything with homebrew, re-cloning all of your git repos, re-configuring all of your git-remotes, re-installing virtual machines for IE8, etc. It takes like 2-3 days. And it's not an issue that employers with deadlines are sympathetic about.

The stupid thing is that every time I get it back I think, "everything will be different this time". It's like a sick abusive relationship.

I just got it back like 4 days ago from the latest trip to the depot, and now there's a harsh buzzing sound that I've never heard before. So now I have to weigh the severity of this stupid issue against the headache of re-installing everything again and rolling the dice with another trip to the depot.

I guess what I'm saying is that you really should beware of 1st gen apple hardware.