estebank

The forcing function on my side was to avoid problems when changing jobs. I don't know what problems there might be claiming benefits that you are entitled to, but if you didn't have the change of status registered, that might delay things until you do. If you did change your status but didn't get a card, you can get a replacement one that won't have the text.

One of the things I was concerned for months until I got the new card is the federal government querying the social security database looking for immigrants or discrepancies with any of their other databases and not caring that the discrepancies are of their own making. Being a naturalized citizen with an accent, I keep traveling with my passport for internal trips.

> You could check social security (which I'm not sure definitively indicates status) and see the same for that.

It doesn't. When I naturalized, I had to schedule an in person appointment at the Social Security offices to change my status in their systems. There was a time gap between me being American, me having a passport, me being recorded as American as far as SS was concerned and me having a SS card that didn't have caveats written across it.

Without knowing the numbers, I'd wager that the majority of work Visas worldwide are "dual-intent", to use the USCIS parlance. Restrictions might be higher or lower in different countries, but there's generaly a path dor moving from a work visa to permanent residency.

> never have to deal with the reality of living and working under an oppressive bureaucratic state.

I see that you have never had to deal with the US government.

LaLiga has the same kind of attitude and culture as the RIAA. Interpret their words and actions accordingly.

This is not the one I remember but another one that does part of what I'm describing.

https://github.com/rust-lang/rust/pull/145354

Idempotent as in if the token stream in the input doesn't change, the cached result of the previous macro expansion is used during incremental, instead of being pessimistic and rerunning the macro.

Colpike as in compile typo.

Yes, I think here are workable designs.

There was an experimental PR that treats proc macros as idempotent with the corresponding colpike speed up. I don't know what happened with it, and stabilization required a lot of design work to not break backcompat. But this is something in the team's radar.

To add to the other replies, Firefox was explicitly never going to consume all of Servo. It was always meant to be a test bed project where sub-projects could be migrated to Firefox. I suspect that the long term intent might have been for Servo to get to a point where it could become Firefox, but that wasn't the stated plan.

To note that this isn't the executive or legislative but the judiciary doing the bidding.

The companies relying on cloudflare won't be in Spain. If you buy a GPS tracker by a Canadian company, developed in India, manufactured in China, they are unlikely to know, even it they cared, that a single country that accounts for a tiny percentage of their sales breaks fundamental internet infrastructure on the regular "because fútbol y dinero".

And when purchasing a product, there's no "bill of materials" telling you about the services it relies on, beyond "internet connection" at best.

How would that get around the SSL certificate?

> and I would really say this means something closer to 17% of the most popular Rust package versions are either unbuildable or have some weird quirks that make building them not work the way you expect

No, what it means is that the source in crates.io doesn't match 1:1 with any commit sha in their project's repo. This is usually because some gitignored file ended up as part of the distributed package, or poor release practice.

This doesn't mean that the project can't build, or that it is being exploited (but it is a signal to look closer).

Not only this, but the reason we can check what the discrepancy is is because crates.io distributes source code, not binaries, so they can always be inspected. In the end, whats in crates.io is the source of truth.

Paradoxically, given their otherwise positive standing, Lenovo has keept allowlists on their BIOS for specific devices on specific ports. For example, I have a T460 that has an m2 slot that only works with two specific WWAN modules.

> And I used to donate to the ACLU before they went crazy.

When was that? Because in 1977 they defended Nazi's free speech to demonstrate in a town that had jewish people as half its population so it tried to block them, and I don't recall them doing anything nearly that controversial since.

https://www.aclu.org/news/free-speech/the-skokie-case-how-i-...

Blocking people that annoy him on Twitter is the only humanizing thing about him. Deciding that someone has annoyed you enough on that platform that you don't care to ever hear from them ever again is the only thing that made that platform usable when you have any minimal audience.

"I've known you for all of 10 seconds and enjoyed not a single one of them" followed by blocking is good, actually. That doesn't make you any more correct or wrong, of course.

After one becomes wealthy, social media easily becomes the only place where anyone says no to them. When everyone who surrounds you tells you "you're absolutely right, let me get that for you", you atrophy the muscle that let's you course correct when you're making a mistake, and when someone disagrees with you it feels that much stronger.

Wealth is not the only way this can happen, you see it with notoriety and power who have gotten used to " being right" (Dawkins comes to mind), and now this experience is being "democratised" by LLMs.

Is there any package manager incapable of working offline?

Even side stepping that tokio no longer pulls multiple packages, it used to be split into multiple packages, in the same way that KDE in Rust would be hundreds of packages.

Rust projects tend to take their project and split it into many smaller packages, for ease of development, faster compiles through parallelization, ensuring proper splitting of concerns, and allowing code reuse by others. But the packages are equivalent to a single big package. The people that write it are the same. They get developed in tandem and published at the same time. You can take a look at the del tree for ripgrep, and the split of different parts of that app allows me to reuse the regex engine without dealing with APIs that only make sense in the context of a CLI app or pulling in code I won't ever use (which might be hiding an exploit too).

Counting 100 100 line long crates all by the same authors as inherently more dangerous than 1 10000 line long crate makes no sense to me.

Don't do this. Use a package manager that let's you specify a specific version to pin against. Vendoring side steps most automated tooling that can warn you about vulnerabilities. Vendoring is a signal that your tooling is insufficient, 99% of the time.

Social media being bad is partly because of shady business practices, and partly because a lot of people suck (in different ways, at different times, including us).

Having said that all of that, have you tried mastodon?

Hey! It also had a barely working physics engine.

Then again the dinosaurs were physics entities, so maybe you already mentioned it. :)

If the genersted PDFs are stored encrypted in an accessible server with proper access control, then that is a measurable improvement over email containing medical informstion that a random citizen would send, which would be bouncing around unencrypted around at least one third party SMTP server. Of course, if then that person uses an online Fax service, they are sharing that information with at least one other party...

And that's even without considering the security benefit of not receiving files that could be compromised, instead generating a file from an image stream. (Now I'm trying to picture what a daisy chain of exploits would be needed to craft a malicious Fax.)

The OP states they've migrated. That might mean that the field on their account database entry might be related to that move. The account is older, but when moving countries I've had to do weird dances to get my Google accounts to accept the new locale, and wouldn't be surprised if their computed account age coincides with me having done that change.

A law can be bad and its implementation can be worse.

I found that I would have enjoyed the movie a bit more if I hadn't read the book, but it was still a solid 8/10. I'm really glad that a movie like this did well in opening weekend.

> Zig vs Rust also shows up with how object destruction is handled.

I often hear critiques of Drop being less efficient for anything Arena-like, where batch destruction would be better, and holding that as the reason defer is a better approach. What is not mentioned there is that there's nothing stopping you from having both. In Rust you can perform batch destruction by having additional logic (it might require control of the container and its contents' types for easiest implementation), but the default behavior remains sane.

You can look at the discussions in any of the language RFCs to see that increased complexity is one of the recurring themes that get brought up. RFCs themselves have a "how do we teach this?" section, that IMO makes or break a proposal.

Keep in mind that as time goes on, features being introduced will be more and more niche. If you could do things in a reasonable way without the new feature, the feature wouldn't be needed. That doesn't mean that everyone needs to learn about the feature, only the people that need that niche have to even know about it (as long as it is 1) it interacts reasonably with the rest of the language, 2) its syntax is reasonable in that it is either obvious what's going on or easy to google and memorable so that you don't have to look it up again and 3) it is uncommon enough that looking at a random library you won't be seeing it pop up).