vitno

sorry dang! Thanks for moderating

warning for folks looking at the webassembly/javascript roles: I talked with a recruiter about these last month but the job description is really poorly written. It reads like a toolchain/platform role but the recruiters are focused on typescript and frontend.

I live on a street in New York that's pretty popular with filming. I generally try to be respectful of their work, but I work from home and sometimes I need to go get a coffee.

I'll usually ask if when I come back in 5 minutes or so if they'll be filming so that I don't disrupt them. Even if I'm super respectful, they usually wind up trying to stop me from getting back to my apartment when I return. It took me a while to figure out that I can just ignore them and keep walking.

Still, it was cool to see Oscar the grouch on my street.

Hahaha, I really like the "painter" terminology. A+

Official governance vs the effective governance is the real crux of this issue. Immediately starting from the lead developers separated by companies already puts a deep corporate interest spin on the project. Choosing to do a lot of the initial work in secret and then disclosing is also a pretty big data point.

I think this is going to be an uphill battle for them and I hope they win it but I'll be skeptical unless if I start seeing radical (for google) transparency basically immediately.

Also worth pointing out that the language is not immediately worthless even if they fail or only partially succeed in this endeavor!!

The governance of the project is not immediately clear to me, and I have to assume that the Google team is working in good faith. That team cares a lot about C++ and its future. They are obviously aware of this stigma. I also think that Google is pretty bad at open source governance though :/

Disclosure: Former Google engineer who worked sorta adjacent to some of those people.

It's not immediately obvious from this page and GitHub org, but this is a Google led project. It's led by Chandler and the c++ toolchain team. I have no idea of it's endgoals or how open to non-Google ideas it will be.

This frequently isn't true, although I'll admit it's industry dependent. This is the rhetoric used to depress the wages. Sure, they have extra costs but when you do the math, frequently the wages are still just a drop in the bucket of the operational expenditures.

Pay better. It's totally possible that you are paying appropriately, but I've been disappointed with my most recent job search and am likely winding up doing backend work again simply because those roles pay almost double.

But they aren't. I just did an apartment search after living in Manhattan for years and 5k was the number my partner and I wanted to be under. It was basically impossible and I'm now leaving my neighborhood.

Oh, strong agreement. I was addressing the comment since it seemed framed independent from the stay-at-home context

Why would you assume the ideal environment for learning social skills is in a school with children interacting primarily with other poorly developed children?

Life experience and growth shouldn't be confined to a standard classroom.

As someone who was both home-schooled and went to public school, you are buying into the mythos around school too much. I had my own experiences when I was homeschooled that were far better than "enduring the horrors of PE".

This comment really misses the point of the post and kinda just feels like you have an ax to grind about sorting. This feels like when people say "don't worry about memory safety, just don't write bad code". "don't worry about generics, just don't sort"

Generic sorting is something all programmers are familiar with so it makes good examples.

This person isn't wrong. A lot of serious Rust users don't agree with what the GP is suggesting. `unsafe` has an explicit meaning: the user must uphold some invariant or check something about the environment, otherwise it is memory unsafe.

I have several times in code review prevented people from marking safe interfaces as "unsafe" because they are "special and concerning", overloading the usage of unsafe is itself dangerous.

The process of evolution doesn't care much about survival of the parent if they aren't passing down genes.

unique_ptr counts as a affine type, the linearity is enforced at compile time. (even if access safety is not)

I was in the space around Rust in the early days: ~10 years ago.

It was 100% research based. Everyone working on the language was familiar with this literature and many of the early contributors were PL Phd people.

here is an example: https://sfpl.org/about-us/confidentiality-and-usa-patriot-ac...

"The Library does not maintain a history of what a borrower has previously checked out once books and materials are returned on time."

This is at least common in US libraries. The San Francisco public library as well as the library system where I grew up both do not keep library records after you have returned the item. I know there is a lot of contention about their private partners keeping records (ex: Overdrive) but I haven't followed that conversation much.

Actually, libraries intentionally do not keep records of what books you've checked out for patron privacy reasons. It can be annoying, but it's a the right thing to do.

Any != All. There is a difference between synthetic benchmarks and real world test cases.

4 day work weeks as a concept real clicked for me when put into ratios. It's a 50% increase in personal time and only a 20% reduction in work hours.

Sure, but also many of the agricultural ingredients in the "fake meat" are subsidized too.

Perhaps not to the same degree, I'm not sure, but worth pointing it out when claiming only one is a subsidized industry.

It's not every song, the model is built from a list of N (100k?) most popular songs. If you pick something a bit obscure it won't work. The model is updated on occasion and pushed in bulk to pixel devices.

That works somewhat similarly to the "Ok Google". Dedicated chip and super small on-device ML model. Nothing goes back to the cloud.

Its not so much that it needs to be made "illegal", The problem is that terms of service itself is a legally enforcable idea. Facebook is the one using legal frameworks to overstep into our life.

Whataboutism, also known as whataboutery, is a variant of the tu quoque logical fallacy that attempts to discredit an opponent's position by charging them with hypocrisy without directly refuting or disproving their argument.

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

Whataboutism is a lazy rhetoric device, the term was literally coined by Kasparov about Soviet dictator apologists.

Generally "systems-y software" is my background. I joined Google for a semi-experimental operating system project and from there it was a small jump to virtualization when I decided I was interested in doing something else. I'm definitely on the platform side, but been doing some interesting stuff recently :)