vitno

I work on virtual machines at Google. I usually suggest "Hardware and Software Support for Virtualization" [1] to new team members without a virtualization background.

[1] https://www.amazon.com/Hardware-Software-Virtualization-Synt...

It's absolutely absurd. I'd almost be more OK with it if it was a monetization scheme _for Signal_, this seems blatantly corrupt as I understand it.

I'm baffled how people assume this is monetization.

Signal has been a nonprofit for years and has no money issues: https://signalfoundation.org. The organization has no formal ties to the alt-coin, although Moxie does. It doesn't monetize the Signal foundation.

I'm very unhappy with this, but it's not a monetization scheme.

This explicitly doesn't monetize Signal so this line of argument isn't particularly relevant.

I am incredibly disappointed in the Signal team. I don't want cryptocurrencies (or even any payments!) in my primary text app. Crypto/blockchain is fine, but if I want to use it I'll download a different app.

I'm finding this announcement creates some uncertainty in my head about Signal's long-term future.

Free Software is not open source and the article points that out as well.

I'm not convinced they want to destroy Free Software either however.

calling this "scientific denialism" seems like a huge stretch to me. It's not a science, it's housing policy.

that's not true these days, rustls is a great TLS lib that has been through at least one serious external security audit.

https://cure53.de/pentest-report_rustls.pdf

Except that Rust is also a much much more expressive language. Even ignoring things like solid module support and libraries you'll find your Rust programs to be much fewer LoC (assuming bug/LoC is the right metric) for equivalent functionality.

I agree that rewrites have the serious potential to introduce new bugs and the cost is rarely worth it if the codebase is actually that stable and low througput, but the reality is that most aren't. A one time high cost in exchange for introducing 70% less bugs over a period of N years starts to look like a good trade off.

Yes, complexity is the root of all evil. I can get onboard with the whole statement except the "no matter what language you use". If you have the ability to use any language that enforces memory safety, we should use it.

I agree Rust is not a panacea and that rewrites create their own set of problems, the only issue with this analysis is assuming 1/10 bugs are memory corruption related.

Both Chrome & Microsoft found about 70% of bugs to be memory safety related. I've heard similar numbers out of FB as well. The math looks a little different with that data.

https://www.chromium.org/Home/chromium-security/memory-safet...

https://www.zdnet.com/article/microsoft-70-percent-of-all-se...

The "originally meant as a joke" belief is derived from an Eric Raymond quote in the Jargon File, not the tool makers.

This still requires a fairly pricey license from Arm to use the ISA

Please don't make comments like this

Fantastic. Thank you so much for chiming in!

to be clear, I don't speak Arabic - I'm merely intrigued by etymology.

I think they are referring to "إنسان" or "Insaan" which has the root of nisyah which means "to forget".

My understanding is that this isn't the common word for person, which would be "شخص" or shakhs. However that also doesn't originate from the word for earth. What word are you referring too?

I'd love for an arabic speaker to chime in!

Dunning-Kruger effect seems like a weird accusation to throw here. The whole basis of it is "a false sense of superiority", but the author is clearly willing to engage on this issue.

I think a better way of terming this would be that you have concern the the author might not have enough domain expertise, which is very different than being incompetent.

This gives me pause that Maud isn't right for a production system at this time, but is that so surprising for a 0.11 library?

Only if you are interested in working on legacy systems in large bureaucracies.

This may or may not pay well. My understanding is that most of the well paying side of this has actually invested in migrating off COBOL over the last decade.

It's a joke about https://en.wikipedia.org/wiki/Edsger_W._Dijkstra

I know people who were working on, what is now called, Libra at FB more than a year ago though. The paper was published a year ago. This just looks like a case of multiple people having the same idea.

Fuchsia is not realtime.

That's not "not attracting attention", that's called living in fear. I don't know the particulars of where you live, but it makes me sad you feel this is necessary.

This is a cool idea I've seen increasingly talked about, but in practice? I hope it never happens. Single Address space computing is a bad idea.

https://www.cs.princeton.edu/~appel/papers/memerr.pdf

On the other hand, I think this is great.

These dockless systems are simply a way to move the negative externalities of the system onto the taxpayer. They clutter sidewalks, result in poor rider behavior, and generate massive amounts of e-waste.

Sometimes, SF actually makes the right call.

This makes me really sad. This place was invaluable when hacking on old hardware, it was a true institution of Silicon Valley.

I was once hired for a C++ position _because_ I hated on C++ during the interview.

This is all true, but there is historical basis, explicit and implicit, from the writings at the time supporting the idea that at least one factor for the second amendment was the ability to defend against state oppression.

"It is a natural right which the people have reserved to themselves, confirmed by the Bill of Rights, to keep arms for their own defence; and as Mr. Blackstone observes, it is to be made use of when the sanctions of society and law are found insufficient to restrain the violence of oppression." - 1769 newspaper editorial.

they didn't say syntax, they said Python idiosyncrasies. Knowing move/copy rules in python counts as that. It's something that isn't intuitive unless you know python, ex: the matrix question. An experienced dev who isn't a python person would pick the intuitive choice, see the matrix is malformed, then Google how to clone objects in python.

we also have a tech blog that we are revitalizing!

http://tech.okcupid.com

OkCupid | New York, NY | FULL TIME | ONSITE | https://okcupid.com/careers

We're currently hiring for a bunch of Backend positions! We have a 6-person Backend Software Engineering Team, which manages all aspects of the Backend. We have a massive amount of impact per engineer. We also have a lot of autonomy here as well as input into product.

The core site infrastructure is written in C++, so experience with that is a huge plus.

Some buzzwords for you that we use: C++, Python, Javascript, React, Kubernetes, Rust, MySql

email me at ben@okcupid.com if you have any questions or apply online at our careers page.

OkCupid is over a decade old. XDR was pretty good back when people started writing our services.

My goal here isn't to migrate our RPC system... yet. My goal is to stand up Rust services in production. I need to be able to issue calls between services and thus, I need it to speak XDR. Migrating your RPC system in a production website is a non-trivial task.

I've done some investigation into switching to something like flatbuffers or cap'n proto. That's a project for another day though.