The fact that this exist shows open source is bad. We should have had an alternative to email by now

I wonder what Gavin Belson is up to. I'm thinking about the episode where Gavin opens up a plant in goldbriar north carolina (Not a real place)

I use a VPS. The strange thing is one site never drops a connection and another one does. I'm not sure if its the physical location or my config but one of the two instance works very well. Its a $5 VPS too

Does it send me notifications? Is it called NipAlert2? Is professor bighetti a collaborator?

Some days I wish I could go without a phone number and have all my communications through an open protocol

My team once needed to hire someone from the outside. I posted a C++ job saying we expect people to know C++11 and to be comfortable working with a C++20 codebase

Literally more than half the applicants couldn't figure out how to update/install clang/gcc to compile our test. It wasn't timed or anything it was essentially change the lambda so it's by reference instead of by value (or the other way around idr) and send us back the one or two line change

Some things that happened to me when I went for interview

- Refusing to tell me salary range, I stop speaking to them - Them not contacting me after my questions (salary range, vacation days, if I'm expected to do front end, etc) - Them stop contacting me when I say I am not interested in working with technology X Y and Z (usually java and mongodb, sometimes I'll ask if they use PHP then say I rather not touch it, I don't outright say I will never work with it) - They have a non technical person interview me who gets lost and think I'm bad at communicating when I can't see their face and have no idea what part I lost them - They have a technical person interview me who can't accept when I disagree with them

Maybe it's my imagination but it seems like more cores isn't helping performance as much? Does it seem every core after 6 cores is about 1/2 or 1/3rd the performance gain?

> Does this mean using C inside of rust is ok? I'm pretty sure the original team kept hitting memory problems and it was in fact not ok

This reads a little like flamebait.

Memory unsafety is bad. panic is _not_ a memory unsafe operation, it does not result in memory problems.

This post is not related to memory safety in any way.

The third sentence was the point. I don't want browsers being less reliable and terminating randomly due to unwraps

And how do you propose they do that? What you're saying is tautological. It's like saying, "I don't want browsers to use runtime invariants because they can be broken and thus causing my browser to terminate."

Like... yeah, cool. How do you do that exactly?

Also, please do consider reading the blog post I wrote. I wrote it to try to clarify a lot of confusing around this topic. It is nuanced, and it just can't be untangled in a few sentences in a HN comment.

I think you missed the point of the article. In fact, the article specifically covers catching panics, so it doesn't bring down the entire application. As well as covering when panic is okay. It doesn't say you should just unwrap everything and treat panic as error handling.

> the article specifically covers catching panics

I see 3 mentions of catch, all in the same paragraph. It says you can catch it, offers no reasons why you want to then provides an example of output when you don't

That doesn't sound like it "specifically covers catching panics"

People asked stuff like this 15years ago (do bunny ears on yourself or pretend to pick your nose). Usually to see if the other person is catfishing with a prerecorded video. It usually happens if the other person types instead of speaks (because it's "late" and people are sleeping)

The only thing interesting about the title is the possibility of real time deepfakes for calls. If it's not realtime then 15years ago called and they want their technique back