Large enterprises class systems are notoriously difficult to work Ai. It’s the context window limitation. Assuming 10 tokens per LoC. The best models today cannot wrangle 100k distributed LOC across multiple repos. It’s great for building new and maintaining smallish codebases. All this code being written is fantastic, but maintaining them efficiently over the code lifecycle is tricky.
This is a good thing. Adjustment of status for those within the USA is backlogged- by years for people from certain countries. Going to the home consulate for the final stamp will save years for many people.
F1 and h1 are non-immigrant visa.
American law only allows a person to reside in the country with one Visa type.
The green card is an immigrant visa - and the new visa is issued through an adjustment of status for those inside the USA (backlogged) or by consulates (nearly immediately).
So this is a good thing. It’s easy to get alarmed.
Because America only has a few processing centers in within the US where is that literally hundreds and hundreds of consulates that can now take on this activity they have always been doing this activity but the vast majority of the backlog is caused by the slow processing of the US processing centers.
Each country can only get 8500 gc’s per year. My numbers are probably incorrect, but some countries have literally hundreds and thousands of people in the pipeline while some other countries only have perhaps thousand. The ones with long waiting periods will clearly benefit.
Edit. Via OpenAI
2025, the cap was about 26,323 per country because the total visa pool was larger.
Important details:
1. The cap applies to:
* Employment-based green cards
* Family preference green cards
2. The cap does NOT apply to:
* Immediate relatives of U.S. citizens
* spouses
* parents
* unmarried children under 21
Those categories are uncapped.
3. The cap is based on:
* Country of birth (“chargeability”)
* Not citizenship.
4. In practice, countries like:
* India
* China
* Mexico
* Philippines
hit the cap constantly, causing very large backlogs.
Simple example:
If 500,000 Indians qualify for employment-based green cards, but only ~25k–30k can be allocated annually under the cap system, the remainder wait in line. That is why Indian EB-2 and EB-3 wait times can stretch into decades.
From what I've gathered, the consular route is nowhere near immediate, especially if they are from one of the countries typically backlogged (e.g. India). You're saying that someone who gets married while on F1 + OPT/STEM should leave with their partner, potentially for months if not years, while pursuing the consular route.
No. All it leans that you go to the consulate on your appt and get your immigrant visa stamped - you get an appointment date and that’s it’s. It was a 3 hour process for me. I flew into Frankfurt and flew out the same evening.
It depends a bit on exactly what your use case is (i.e., which features are even relevant to you) and specifically what the alternate vendor would be. I really do try hard not to oversell what we offer.
I'll say this: if you're looking for an open source solution built to make B2B auth easy, we're the only option of the three. For Keycloak, for example, it's been an unresolved feature gap for many years that it can't support SCIM provisioning [0]; an unrelated characteristic -- not necessarily a flaw -- of Keycloak's is that it's quite agnostic to your use case and consequently requires some effort to implement.
On the other hand, we don't yet offer a huge amount of customization. We've instead -- for now -- prioritized building a relatively opinionated and therefore straightforward product. Similarly, if you're looking for some long-tail features, a longstanding vendor like Auth0 will very likely be able to help you.
Probably a few other considerations might be relevant that I'm neglecting. Send me an email if you're interested in chatting more (contact in HN bio) -- more than happy to help explore some of your options, even if that means we're not right for you.
You wanna load test the local DOM rendering or what? Otherwise, whatever endpoint is serving the HTML, you configure your load tests to hit that, if anything. Although you'd just be doing the same testing your HTTP server probably already doing before doing releases, usually you wanna load test your underlying APIs or similar instead.
After years of large MBp I switched to 15 inch MB air. Then the 13 inch. It’s moment of inertia is closer to the palm holding - i.e., it feels very light.
Screen is a bit tight. So all I do I crank up the size (setResX), put on pair of 0.5 readers and voila instant large screen. I can go all the way to 2560x and still read and work.
That is a pre-indicated stipulation of the green card validity, not revocation based on the whim of an evaluating (non-immigration judicial) official -- ie CBP and DHS and ICE cannot (read: should not be able to) revoke green cards.
The "basic US presence" requirement of green cards has always been present in the validity clause alongside the 5-10year expiry date, and not committing immigration fraud and other basic requirements to maintain green card -- a comical number of European green card holders gloss over/forget this clause every year, that is made explicit to them upon receiving the card and proceed to forfeit their green cards by not entering the US for over a year -- that is not a revocation (implies a subjective decision made by an official), it is a lapse of validity (implies some pre-stated condition was fulfilled).
Yes. People are generally familiar with rights that can lapse if eligibility is not maintained - consider the right to vote in state elections, which you lose if you fail to maintain residency in that state. Nobody yanked your state voter registration or your eligibility for in-state tuition, you abandoned it.
