How is that different from just making a call? It's much faster and you can both be looking at your respective screens with the same information

yes

> blacklist pcspkr

Have you ever heard about helicopters? There are hospitals that have them. Why do we need _personal_ airplanes for this to happen? Why you think doctors will have money or space for their own airplane when they have no helicopters yet?

In this scenario of yours where would this doctor have their "airplane" at home? In a airfield?

No, he would have a car of his own. That he can drive himself to the hospital. I'm not sure why you jumped to helicopters.

If he can drive and that’s not an emergency why wouldn’t take the train ? Less stress and more safe if he’s impaired.

For an emergency I would suggest a professional-driven ambulance with flashing light, or an helicopter if it’s remote if your wallet or country medicare afford it.

I think their point was a doctor being called in to work in an emergency not that the doctor is having an emergency.

Oh thanks that makes sense! Those "flying doctors" already exists in Australia and one of them saved my life 13 years ago : landed on a single lane road on the middle of the desert to pick me and my friend in a thought condition after a car crash. We arrived in the hospital 2 hours later, instead of 12 hours car drive. IIRC it was a small propeller plane looking simple and not so new or fancy. Didn’t remember the flight :( they quickly nailed me to dream after landing.

I can't take this language seriously. No enums, letter cases defining if something is "public" or "private", generics as an after-thought. To name just a few

To be fair, generics was an after-thought because Go was originally a "small" language used internally at Google, and they needed to ship the language in a working state. Generics was too complicated to handle for the first versions (according to Russ Cox). If you look at Java, generics didn't exist until a few major versions in.

Although I agree it probably should be done quite a bit earlier.

You'd get a Wine full of ads, the need for an account to use and the not so occasional BSoD /s

Plus probably worse off at running programs written for both old and new Windows versions than current Wine.

I guess something is better than nothing. But it's a shame to be launching something that seems obsolete from the start

It's not obsolete if it works and there's people paying for it. Most space rockets are decades old tech, calling it obsolete seems pointless.

Obsolete as in it can be competitive or not ...

This is Europe's slogan.

This is such a cool visualization. It's so interesting to see that Rust's embedded libraries are on a more separate, dense, group.

> high-bandwidth communication?

For me, absolutely no. I want high quality not high bandwidth. I don't want everyone interrupting me all the time with, relevant or not, questions. I want you to write me an email or message in the chat and I'll check it and answer in due time. I don't want to be interrupted to go to the cafeteria or "for a smoke" every 15min by a different person, or to have people standing besides me talking about their weekend or their kids. It's very invasive because I get distracted easily, even with good quality headphones, and it's hard to get back on focus.

With this said I don't mind going to the office where I can chat with people and socialize but I want to allocate time for that, not be forced into it. I feel that WFH allows me to balance the time I need to work and the time I need to socialize much better.

ebpf seems to be a very interesting idea and have been experimenting with it. Still I find it weird that we're doing documentaries on software "frameworks"

"Documentary" may be a bit of a strong word. It's more of an image film / ad for Cilium and/or the ebpf foundation.

I doubt they had the time to pull MacGyver stuff. This scenario was most likely already predicted and tested and it was a matter of changing configurations.