throwaway3neu94

H1B's already need to exceed the prevailing wage, as determined by DoL.

You can argue about where they actually end up, but it's not the bottom 20%. Esp once you figure in immigration related overheads (that's staff, not just fees and travel).

Higher salaries for H1B's would require the right to change jobs easily, unlike now where there's a tremendous risk. And then there's L1's, who have no negotiation power at all.

I'm sorry if I didn't explain what I meant well enough.

I was talking about statelessness on the server side. If you remove cookies from HTTP, you now need a database on the server side.

You also get extra communication (between the client/DB, or the web service/DB), whereas previously the data would've already been available in both (the client has the jar, and the web service gets it in each the request). Turning a local memory read into a network request can be a difficult architectural change.

Also, DynamoDB reads are priced per unit ;-)

Statelessness is often a good thing in designs in many ways, performance, reliability, maintainability, operating cost etc.

As a concrete example for a common use case, websites show your user or first name in the top right corner. It's common to put this in a cookie set on login/logout. This avoids querying the user directory service (from the frontend or a different backend service) on every pageload. Security wise it doesn't matter if the user tampers with it, it's a display only thing. (More often than not it's signed anyway, and the cookie contains other things as well.)

Cookies meant to be presented back to a server can be signed and (optionally) encrypted. This is also a very widely used pattern ("cookie secret" is a good search term for concrete implementations in frameworks).

Everyone would've emulated cookies using HTML local storage, because it would be a pretty quick fix (just wrap all cookie API's). So you'd gain nothing except push people from a standard to an ad hoc solution.

Switching to server side storage would've been a too costly architectural change. What if the server side was stateless before?

And even if, web applications would still have needed to support the old model for interop reasons. It's not feasible for everyone to maintain code for both approaches when they are so different.

It'd also break many use cases, such as using a (signed) cookie as cache for some really frequently used data. Or more importantly authentication, where an auth service returns a token (in some cases a token that can be checked by a different service without contacting the auth service again).

So yeah, that was a non starter.

But when you push it in one direction too long, then let it go neutral, it'll have a bias into the other direction and move there by itself for a few seconds.

If we're adapting anyway, one change could be gradually leaving kids home alone for longer times.

"Kids always need supervision" is a US thing. Leaving kids alone for some time works just fine in other countries. Of course there would have to be law/regulation/policy changes (to keep CPS away) but so what.

On their website, there is a "Fact Sheet" PDF with a 1-page business description linked at the bottom. It says:

"Target consumer: wealthy individuals with home media rooms"

Duh.

It also says the two founders were CEO of ticketmaster, and home distribution president at Warner Bros. I suppose these two would know how to price this, and who to talk to for licensing.

Or maybe GIMP can do everything they need so nobody needs to get paid. But if nobody gets paid anyway, might as well copy photoshop instead. Legal issues aside, it doesn't seem that irrational.

I think in practice, the moral argument just doesn't work too well for intellectual property, and creators need to deal with it. Which, unsurprisingly, they do, in different ways (be it through making payment convenient like Netflix, prosecuting individuals like MPAA, or focusing on enterprise deals like Adobe, ... or still pushing the moral angle because a statistical effect is better than none).

How can I check that for my adapter?

"Thoughts and prayers"

It sets Err. Which is essentially how SH, C and Go work too.

(With the obvious exceptions of longjmp and panic/defer, global vs local var, and Go forcing to assign the error.)

On Error Resume Next isn't great, but calling it much worse than On Error Goto, or much worse than other languages, is a stretch.

My point is only that people complain about it in VB disproportionally often compared to other languages. (Does that mitigate the issue to some extent, if every VB dev is super aware of it?)

Not saying you can't coast through without math if you're somewhat picky, but it would be a significant restriction. And for me the realization that most CS problems can be approached in a very rigorous, mathy way was one of the main takeaways of all the time studying.

Agree OS is less mathy, but even for operating systems you need statistics the moment you want to talk intelligently about performance (look how many people average percentiles, do coordinated omission, or insist on averaging results instead of looking at distributions). Btw random webdevs handling A/B testing tools would benefit as well. We're talking MSc? Ok, a basic OS class won't occupy you for long, it's 5% (actual number of one uni) of credits for an MSc only. Let's say you stay in the field... queueing theory is somewhat mathy? Advanced data structures needs experience with proofs, which is taught in maths.

Maybe other fields are safer?

Computer graphics and it's subfields need lots of linear algebra.

Crypto? Symmetric crypto needs probability theory, asymmetric crypto needs number theory, side channel attacks need linear algebra.

Robotics, signals and systems, sensor fusion, electrical networks all need lots of linear algebra.

(I've taken all of above courses at some point, but not all exams.)

Because real CS degrees require a lot of it, and math exams are the main reason people wash out in the first 2 years. (There's some controversy around whether that should be but it is what it is.) And it's not a watered down version for CS students. In the universities I know, the first ~4 math courses are taken together by maths and CS students. I've heard "CS is applied math" a lot, and I agree with it. (If you want to become a programmer, you don't need to go to university.)

Actually some (popular) CA's can generate the cert on their side and let users download it. Not allowing this insecure practice is one more point in which LE is ahead of the curve.

That's misguided (I'm assuming you're the server admin).

Whether you use any specific CA, like LE, or not, has no security impact.

It's about what your users trust and you don't control that.

Bay area large (not huge) corp dev here.

We do. We have like a dozen shared, beefy shell servers (varies, but think ~32 core not too old Xeon, ~256GB RAM, 1G or 10G stable network that's local to the office, TB's of storage and essentially unlimited on NFS) for devs (and more of the same dedicated for CI/CD).

We need this because the codebases are huge and take hours to build on a laptop (and copying across a home uplink would take forever too).

Homedirs are NFS mounted.

It's more cost efficient than spinning up an AWS/Azure instance for myself, and more limited resource efficient than spinning up a VM in OpenStack (both of which I do when appropriate). And it's very convenient team work wise.

There are (many, some avoidable but hard to fix by now) downsides for sure, but I cannot imagine doing this work solely on a laptop.