you see the reason h1b is so popular with the c-suite in a lot of cases is that you get absolute loyalty to a company that holds all the power of your being allowed to stay in the us. you lose the h1b job and you have limited time to find a new valid employer to sponsor you or else you go back to your country. it's one of the reasons musk loves it for twitter.
I've had three different H1Bs. Yes, transfers are easy, but they're sure a hell more risky than staying at your current job and enduring whatever you have to.
You're not beholden to your employer, but you have borderline coercive reasons to stay.
Its all relative. A burned out American can drop out tomorrow with no short term plan. H1Bs cannot fo that unless they are ready to go back to their previous country.
> I'm curious what would stop you from opening it in restricted mode? Is it because it says browse and not edit under the button?
loss of syntax highlighting and to a lesser extent the neovim plugin. maybe having some kind of more granular permission system or a whitelist is the answer here.
opening a folder in vscode shouldn't be dangerous.
> opening a folder in vscode shouldn't be dangerous.
You're not "opening a folder" though, you're opening a codebase in an IDE, with all the integrations and automations that implies, including running code.
As a developer it's important to understand the context in which you're operating.
If you just want to "open a folder" and browse the contents, that's literally what Restricted mode is for. What you're asking to do is already there.
I've been using VS Code for many years and I try pretty hard to be a security aware dev.
I checkout all code projects into ~/projects. I don't recall ever seeing a trust/restricted dialogue box. But, I'm guessing, at some point in the distant past, I whitelisted that folder and everything under it.
I've only just now, reading through this thread, realized how problematic that is. :o/
Syntax highlighting should work if the highlighting is provided by a textmate grammar, it will not work if it's semantic highlighting provided by an extension and that extension requires workspace trust. If it's possible to highlight without executing code, that sounds like an extension issue for whatever language it is. I believe extensions are able to declare whether they should activate without workspace trust and also to query the workspace trust state at runtime.
yeah me as well. at least have the untrusted code allow certain plugins or certain features of plugins to run that you whitelist. not having vim keybindings or syntax highlighting is too barebones.
I think that if affinity chooses to make it work well on linux that would be a game changer for a lot of people. daVinci resolve works on linux for video so having a proper photo editor/illustrator tool that is not gimp would open up the option for most people to daily drive it. that's really the missing piece.
cachyos is a good os that is also performant. arch though so there are quirks around the rolling update model but you always have the newestish packages and if you update regularly there seems to be less headache.
I wonder how well this will work without other the states not being in on it and what other unintended consequences this may bring. sounds like a good start though.
One of the ways federal legislation gets passed is by state's passing their own laws, eventually industry gets fed up with having to comply with a dozen or more variations of the same law and starts harassing congress to take care of it.
California represents 12% of USA population, 14% of US GDP. Effectively that means CA can throw its weight around and companies are forced to at least pretend to comply. Whether they actually comply depends on enforcement.
Now if Delaware were to adopt such a law for every company “headquartered” there …
reply