gwillz

Also, the expiry date should never be a date picker. I'm not trying to _choose_ a date, I'm just dumping the exact numbers from my card. I want to type, tab, type, tab, type, enter, and be done.

Well this might be an interesting discussion to read for you. Take what you will from it.

https://gist.github.com/isaacs/357981

I really enjoy the server-client diagram [1].

I've always thought myself very able to explain technical things quite well to non-technical people, but always struggled to explain the public/private key exchange in a simple way. This is really neat.

1: https://webauthn.guide/#authentication

In contrast, we had snow in our alpine regions into December. The weather is completely nutty recently.

In addition to that, some fires are burning so hot and so regularly that the trees and seeds completely die. They haven't got the breathing time to recover.

I'm really sad to see the GR8 gone from the world.

A while ago I was building some cool products designed around it. It was just so neat and did all the tedious, not-fun things of board design.

I can't tell if it's coincidence but I've had all of our GCE pull-queues failing with "transient failures" for pretty much the entire time GKE has been reporting this issue.

Have they only _just_realised_ this is affecting GCE after all this time or has it only _just_started_ to affect GCE?

I've always felt that manufacturers got the USB-C dongle very wrong.

Instead of converting USB-C to DP/USB-A/HDMI, the dongle should be converting DP/USB-A/HDMI to USB-C.

It's about upgrading the older perpherials instead of downgrading the new devices.

For example, the dongle is instead fixed to my DVI port on my monitor. Now my monitor has a USB-C socket, instead of my laptop or phone having a DVI socket.

It reduces bulk and now I truly only have to use USB-C cables everywhere. If someone knows where to find dongles like this I'd be very excited.

I've always felt like

Yeah I guess that's fair. It's a fairly shallow attempt to evoke a response.

At the same time, I still enjoy it because it did create a lot of responses.

I find discussions these days end up being an echo chamber of the same opinion. Something different and something to argue against is more interest than everyone just confirming each other.

I love this devil's advocation. I certainly don't agree with it but it makes a great conversation.

Stir that pot.

The coordinates are derived from the timestamp and satellite location - that's how GPS systems work.

All the satellites have the exact same time. But deviations in the timestamps when received (because the speed of signal is constant) help the receiver calculate it's own position.

What if I'm working for a global company based in Malaysia?

Would I be happy to be paid the regular rate of a Malaysian developer while I live in Silicon Valley? Or would I demand a higher pay? Does that mean everyone in the Malaysian office gets paid more? Does the company go under?

GitLab is in a weird position because they have workers in both. We don't chastise a local Malaysian company for paying the local rates, but we do for GitLab?

It's an unfair reality, but not an unlivable one. A cheaper lifestyle isn't necessarily a degraded one.

That still doesn't make it fair. I personally believe these global companies could step up and try to change that. But that's if it weren't about profits - which is is.

I think that's great example of why this is a difficult conversation. Global commodities are typically fixed and can be prohibitive to some localities.

Who budges? Do the global companies lower their prices or do local economies step up and pay more? Or even are they able to pay more?

I probably shouldn't have said "can't" be paid the same. Instead something more like "don't need to".

Up front, I believe everyone should be paid the same. I want that. But I do accept local living standards. I must - and therefore I am paid less. It's just a reality of our world today.

I think this conversation is about how global our economies are. Which I think are more local than people believe. Also keep in mind that cheaper living isn't always worse living, just cheaper.

I think it's a requirement of remote work. You can't pay someone in Malaysia the rate of someone in Silicon Valley.

Don't get me wrong, I think everyone should get fair wages. But that's just not how it works in different societies. "Fair wages" means different things in different places.

Well no, "fixed" is a position relative to the the viewport.

"Sticky" is like a conditional/hybrid between "fixed" and "relative".

I mean, I call this kind of footer "sticky" but it's not a great name and I can't think of anything better.

I was going to suggest the same but with LinuxFB. I don't believe it's hardware accelerated though.

https://doc.qt.io/qt-5/embedded-linux.html#linuxfb

Qt is fairly popular in the embedded space. I'd bet the support and robustness is quite good.

That's right. I was quoting DanielK.

It's a subtle thing for sure. Just because he prefaces it with "not to be an ass" doesn't justify being an ass.

Overall, it's still phrased in a demanding way.

This is bait.

But easily, Skype.

Not so much that it doesn't work at all. More like, it appears to work and then fails horribly down the road.

I've been bitten by it too much. It's typically the auto-complete feature of mobile keyboards that fails. Something that you don't always see in emulators.

It's great until you discover things like position-fixed doesn't work when there's an ancestor with a transform.

https://bugs.chromium.org/p/chromium/issues/detail?id=20574

It's really fun because even a will-change: transform will trigger it.

Legit Internode had native ipv6 enabled by default since 2008.

Whirlpool still exists also.

https://whirlpool.net.au/wiki/hw_feature_242

I guess it could make SSR easier for canvas based components. But how to translate that canvas state from server to client would be pretty interesting however.

Auto capitalization can also be fixed with a cheeky little `autocaptialize="off"` attribute.

https://developer.mozilla.org/en-US/docs/Web/HTML/Global_att...

I'm just spitballing here.

Could it be that either deduplication or idempotency are a sub category of the other? Or perhaps describe different aspects of the operation?

Like, you could argue that deduplication is a form of idempotency. Or that deduplication is an effect of idempotency.

I've always thought that an idempotent operation could actually continue an operation where it left off, rather than repeating the whole operation. Deduplication is a side effect of that process.

Is reentrant the right word? Like, you can repeat or continue this operation. This may mean no-op calls, or may mean it repeats everything but still achieves deduplication.

Maybe I'm desensitised from political agendas in films now, but from Captain Marvel I really didn't get a overwhelming feminist agenda that I felt impeded it from being a genuinely entertaining movie.

I'm disappointed about Brie's comment about Wrinkle in Time, however. It really wasn't a great film. The single feminist angle of 'girl saves boy' doesn't make it a great film. All I got was an "evil is a alternate entity you can defeat and bad actions aren't your own fault" lesson. This I thought was quite dangerous for children.

It's unfair to discard people's opinion just because they're white and 40. Just as much it's unfair to review bomb a movie because the actor said something in an interview.

I fully get this article for defending this movie and I'm also upset by the disproportionate ratings we're seeing from critics and audiences (see Orville vs Star Trek: Discovery). But something else stinks about this article.

I fully expected the 'use moment.js' part at the end. Javascript dates are certainly unpleasant, but moment can be kind of a blunt instrument at times.

There's growing support behind Luxon, a sub-project of moment that may eve become a full replacement. I've found it quite refreshing.

There's also date-fns which is designed with tree shaking in mind and people seem to enjoy it.

Or if you're a Java native, JS-Joda emulates the same API as the java.time libraries in Java 8.

Also +1 for GMT != UTC.

I'm fairly bothered by that non-linear scale in those graphs. Particularly because it's consistently non-linear for gender comparative graphs and linear for most others. To me it seems almost deceptive.

I don't mean to be accusatory, but I am curious about a reasoning for it.