tokenizerrr

I really don't get why I would want to run an operating system where the vendor refuses to support my hardware.

Also, the font color on this blog is absolutely horrible.

This page is hosted by the verge themselves so has absolutely nothing to do with Google trying to control the web. It also does not load slower.

All of these packages are created by Jon Schlinkert (https://github.com/jonschlinkert). So if you want someone to blame...

It does not, and Google does not yet even attempt to use WebAuthn. They're still using the (now legacy) U2F authentication mechanism, which firefox does not fully support. It works in some sites if you enable it in about:config, but not all. Like google.com.

Doesn't work with Firefox yet AFAIK. That page mentions requiring Google Chrome.

Anyone know when the Google websites will start using this? Would love to finally be able to use my Yubikey with Firefox and Google.

Running it locally is fine, but a hassle if I need to access my mail on someone else's hardware (or my phone). I think this is one of the main reasons Gmail is so popular.

Would love to be able to self host this though and access it through the browser... That'd be awesome.

It seems bundling mails together isn't in Gmail yet? Too bad, it's the only reason I use Inbox.

> automated build process

> Mac

Why would anyone run a CI server on a Mac?

Putting a phone in a faraday cage kind of blocks the purpose of having a phone with you.

Daemon by Daniel Suarez is kind of like that, except it turns out the AI is arguably good and not exactly an AI. It's an excellent book, with an excellent sequel.

Federation is a completely different story from a third-party client.

They're very nifty, as you can use this to easily prevent all kinds of date range overlaps.

Yes please! It's one thing to know what you should do because you've been told to do so, but quite another to fully understand why you're doing something.

Well, I'm not really sure what to say other than that I don't have any of those issues. Sitting here right now with my HiDPI XPS13 screen and a regular HDMI monitor. Things look good and I have no scaling issues. Haven't messed with any of the settings, it's just an Ubuntu install with i3.

I don't know any specific macbook models as I'm not an apple user and there is like no visual distinction between them. All I know is that I have two coworkers who use macbooks, and theirs are incredibly loud & warm.

I'm using my XPS13 for like a year now.

> - Linux applications have a lot of trouble with the HiDPI screen

Honestly haven't noticed a single thing.

> - Coil whine

None of that.

> - Shitty battery life

What's shitty? It lasts 5 hours of me working with VMs. I don't think expecting more is reasonable. It's much less laggy than my collegue's MBP, which leads me to assume that Mac just throttles the CPU down to achieve longer battery life? I don't want that.

> - Shitty touchpad

Not at all. It works nicely. Much better than most touchpads I've used.

And as an added bonus, it doesn't get burning hot to the touch when doing actual work on it. Nor does it sound like it's about to take off. And it was like 1.5K EUR vs 3K EUR for a macbook pro.

This is what I use, and as far as I can tell it's better than a MacBook in just about every way.

There are plenty of other hardware manufacturers out there. One of the practices you might not wish to support is an OS being tied to a specific hardware vendor.

If you don't like the hardware you shouldn't be buying it.

E. Don't buy Apple.

You'll spend much less, and won't be supporting practices you don't approve of.

> website uses esoteric design conventions. A European thing? I don't know.

No, not a European thing. They are just special.

example.org works well

Reboot into single user mode, reset root password, and done.

Guess nothing I release will be used at Google. Oh well, none of it is particularly good or relevant anyway. Funny though, because they are doing exactly the opposite as what the license allows them to do.

Or the policy was misinterpreted. The piece of text that got quoted is present in every single EULA ever and does not at all indicate if this is actually intentional by GitHub.

Besides, you can request to disconnect your fork from an upstream project. I expect such a request will also resolve this problem.

Did you contact GitHub regarding this and ask them, before bashing them on social media? What was their response? They'll probably gladly remedy the situation.

When two people touch the same file and format it differently you get a merge conflict. Even if the actual code is identical.

The only way I can imagine how you never ran into this is that either your team is tiny, or that people don't touch other people's code. Both of which are not an option as you grow.

How do you get people to configure the pre commit hook consistently? As far as I know this can't be done automatically, right?

Why would you be annoyed by the avoidance of merge conflicts?

Depends on how often you release and who sets the schedule.