assbuttbuttass

It's actually better in many cases for businesses to hire undocumented workers, since it makes the workers position much more tenuous. They are much less like to unionize, demand higher pay, etc. if the threat of deportation is hanging over their head

lmao

The main problem is that Goroutine stacks are small, starting at 2KiB. When you're calling a C function, the Go runtime can't know how much stack space the C function will use, so it has to defensively expand the stack in a lot of cases

Sounds like a great way to get dozens of dependencies before you even write a line of code

And then bisect fails because it finds one of the many commits that broke the test before the actual regression

Suppose we have a failing test. For many commits, gp carefully separated their change that would break our test, from the change that would fix the test. At some point, someone forgot to run the tests, and introduced a commit that broke the test without adding a second commit to fix it. Now it's treated as a "pre-existing failure," and many more commits are added on top.

How would you identify the commit that broke the test?

Of course, but this thread was in the context of someone "carefully curating" their git history

That sounds like it would break bisect

We've entered the "bond villain" era of VC startups

If someone manages to become a world class chess player, they are likely very good at chess

> I must admit I'm a little surprised how many people seem to disable secure boot.

To me, secure boot is the setting that I need to remember to turn off before installing the OS, but I would be willing to be convinced otherwise

Hmm I wasn't familiar with join, but it looks like you still need join + fmap for the construction? I believe fmap would also need a generic method

It's (sadly) still not possible to express monads with this change, since generic methods can't implement interfaces. You'd probably want something like:

    type Monad[T any] interface {
        Bind[U any](func(T) Monad[U])
    }

However this requires the Bind method to be generic, which still isn't allowed in an interface

> Why would there be paranoia when writing blocking code with async?

In languages like JavaScript, you have to be careful to avoid blocking the event loop, and use something like worker threads for CPU-intensive tasks. Otherwise you will end up with long tail latencies. In Go, the runtime automatically manages this and can suspend and resume long-running goroutines.

> naively accessing a global value can lead to race conditions

Fair point that the language doesn't automatically catch this, but that's what a mutex is for. In return you get actual parallelism that can use all your CPU cores