______-_-______

If you're comfortable self-hosting, I think PeerTube is the go-to option. Federation is optional.

That's actually not a terrible idea! German is known for having words for concepts other languages lack, and I guess that applies to Danish by extension. Maybe I should ditch the thesaurus and teach myself German.

Sure, and MPEG isn't AV1. Apple was welcome to hop onboard Vulkan. My point is:

Apple's involvement with OpenGL for decades didn't mean they wouldn't abandon it and roll their own.

Apple's involvement with MPEG for decades doesn't mean they won't abandon it and roll their own.

Apple participated in many of the OpenGL working groups for decades, but they still rolled out Metal.

I 100% agree.

That said, "percent" is a common and precise word, and I haven't come up with anything quite as good for variables in range [0,1]. I generally use "ratio," but I don't love the word. Is there anything better?

I was tinkering with building a wayland hello world a few weeks ago (on manjaro+gnome), and I could reliably hang the desktop by starting to create a window but not finishing the handshake. Many reboots later, even after finishing the handshake, running my app would break mouse input across the system until reboot. I never did figure that one out.

The experience left me feeling that any misbehaving app/driver can break the desktop. And since you can't restart the window manager without losing your session, you'll lose a bunch of time every time something goes wrong.

btw I should say I was seriously impressed by the UI in general and how smooth everything felt, but stability is ultimately more important for me.

Correct me if I'm wrong, but Wayland, the protocol, doesn't support restarting and reconnecting to running apps. That means any little bug and you lose your entire session. X11 does support this, even Windows supports it (win+ctrl+shift+b). I wish wayland had a way to make things robust in the face of bugs, because bugs are inevitable.

XFCE doesn't support wayland.

This seems like a job for archive.org. But I don't think even they could deal with the scale of something like Vimeo with only a week's notice. Sad days.

If you haven't flashed OpenWRT or something similar… most probably yes.

"I wish most of Canada wasn't so cold"

And the monkey's paw curls.

Worked for me just now. You can also see it archived: https://archive.is/IPfVP

Yeah, the performance really makes the tool live up to its name. Where is the rewrite-in-rust strike force when you need them?

I bet everyone who's used git for a while has their own `git shove` alias different from everyone else's.

Mine basically does `git pull && git merge && git push`

$(git rev-parse --abbrev-ref HEAD)

This is my favorite one. Being on stage and hearing music come out of your mic is a hell of a trip.

That question has been closed and locked since Obama's first term

Alerts haven't locked up the browser since the Bush administration.

You might be looking for this thread https://news.ycombinator.com/item?id=30699673

The human body likes a consistent schedule. When the schedule is disturbed, you get problems like these:

https://healthblog.uofmhealth.org/heart-health/why-daylight-...

https://www.healthline.com/health-news/daylight-saving-can-m...

This is being downvoted but I think it's an interesting question.

If your life was on the line and you had to choose—would you do business with Google, or GoDaddy?

That line of thinking only works up to a certain point. I could say assembly language is simpler, now you don't have to think about functions or basic blocks, you can save your thinking for the problem you're trying to solve! But sometimes pushing complexity into the language instead of onto the users is the better way to go. Higher-level abstractions make things easier. I would rather spend my thought cycles on the business problem, than on reimplementing sum types, or casting interface{} everywhere, or propagating errors by hand.

Here's the original Rob Pike quote:

> The key point here is our programmers are Googlers, they’re not researchers. They’re typically, fairly young, fresh out of school, probably learned Java, maybe learned C or C++, probably learned Python. They’re not capable of understanding a brilliant language but we want to use them to build good software. So, the language that we give them has to be easy for them to understand and easy to adopt.

The source seems to be MSDN, but the link has bit-rotted. https://channel9.msdn.com/Events/Lang-NEXT/Lang-NEXT-2014/Fr...

This attitude I think is the reason most experienced deveploers I've worked with are put off by the language. You don't have to be a "researcher" to understand sum types or generics. There's a large part of the industry that thinks we should limit ourselves to concepts that can be understood by a beginner, and I think it's holding the industry back. I can't think of another industry where people think this way.

In other words, 90% of everything is crap, both then and now. And thanks to Lindy's Law, you're usually better off buying something old than something new. But that's not how most people think :(

https://en.wikipedia.org/wiki/Lindy_effect

For some reason I thought it was a throwaway account name. Thanks for pointing out the obvious!

I'm planning to buy a house in the next year or two. I would 100% hire this guy as the inspector if I knew who he was. Those photos are more effective than any marketing.

I'm curious. What were the ratios of:

- people who ignored the text

- people who were annoyed

- people who changed who they were voting for after receiving a text

?

We're a verb now, we've never had a profitable quarter, and we're still trying to come up with a business model.

UEFI needs ~complete access to the machine so it can initialize hardware devices and pass control to the OS (which also has ~complete control of the hardware). How do you think sandboxing it would work, practically?

> “Sorry, you need to use this software; there is no other way.”

That's your cue to set up mitmproxy (or the 2003 equivalent?) and figure out how to talk to the service directly.