jjnoakes

The underqualified non-diversity hire is also a thing. There is no reason to bring identity into it. Just discuss underqualified workers in general.

The why can also go out of date. Maybe not as frequently? I don't have a great intuition for the ratio, but it is certainly more often than never.

They are different by definition.

> The standards left things undefined in the hopes that the language would be more widely applicable and implementers would give those areas thought themselves and decide the right thing.

That sounds like implementation-defined behavior, not undefined behavior.

The art is great on its own, but knowing the constraints it runs under and how one image can look so different, or even animated, based solely on the palette, elevates the art to a whole new level.

Any enterprise install I've ever used has the annoying stuff removed. Small businesses are most likely the ones suffering though.

Care to share your Vector implementation that is "stack safe" and "UB safe"?

Does Carbon have any undefined behavior? Some of the wording in their goals document suggests that they do/will, but it isn't clear to me.

Some (not all) of your questions may be answered by the linked article near the top of the submitted article, which goes into more detail about how much is lost quantizing to 1 bit (and 1 byte): https://huggingface.co/blog/embedding-quantization

I have a similar habit. I usually do "echo rm ..." or "echo destructive command ..." first, check the output (so wildcards are expanded, etc), and if I'm happy I bring the command back in the history and edit out the echo.

I think plain text files also integrate nicely with other tools. Desktop search, external editors, etc.

The box isn't the only justification for the higher price. It's just an example. If apple cares that much about the box, imagine the effort they put into the rest of the hardware, software, and experience.

I'm not an apple user but it is obvious to me that apple users aren't paying more just for the box.

What's the license?

Once I get a project to "actual customers" I don't mind paying and signing my binaries.

The problem with blocks is that you can forget them.

That still doesn't show you at the call site.

It would be if Google's app password hash database was leaked.

For me the realization that the top thread's loop goes AROUND the bottom thread's entire spool is what made it click for me originally.

I should have been more specific. I didn't mind that part as a teaching aid in general, but I thought it was contrived as a possible explanation for what the question authors expected students to visualize when they made the correct answer 3.

I'm not convinced that the intended meaning was to consider a rotating reference frame. I think it was simply an oversight that the straight-line answer and the around-a-circle answer aren't the same. A rotating reference frame is one way to explain that oversight, but it isn't the only one.

I actually didn't think that part belonged in there. Considering a rotating point of view seemed contrived to me.

The video does go further - it contains some interesting content around how this concept relates to the earth's orbit around the sun, the discrepancy between the duration of an earth day and a 360 degree rotation about the earth's axis, and why astronomy days are not the same length as earth days.

I've downloaded just the command-line tools before and used 'sdkmanager' to list and download sdk versions and virtual machines, so it is definitely doable without Android Studio, although it isn't obvious (or at least it wasn't to me).

Sorry if I'm being dense, but how is this quicker than using the original site's HTML and css directly?

> Back in the day, we used to embed strings into the translation units that would report the original name and version of the file.

We still do this today. We rely on some tooling-added information and add our own custom information on top (git hash, hash of direct dependencies, compiler version and flags, etc).

select() ought to just fail with EINVAL if nfds is too large. There's probably an argument for the macros as well to fail by default if the file descriptor given is too large.

Lots of replies kind of missed my point (my fault, probably) - I think there are cases where 'int' is the correct type to use, and cases where it is not. I think using 'int' everywhere is probably a mistake, and using 'int' nowhere is probably also a mistake.

Sometimes you are working within the guaranteed bounds of an 'int' in the C standard, so portability isn't an issue. Sometimes you are mixing different types and want to capture intermediate values in the promoted type, which is dictated by the C standard. Sometimes you want to use the native machine word for a good reason. And sometimes it is just easier to read and reason about (printf-like conversion specifications, code that interfaces with POSIX APIs frequently, etc).

The best advice I can give is: go for it, and if you get stuck or feel like something in Rust is more difficult than it should be, reach out for help. Once in a while you may really be hitting an unpolished piece of the language, but in most cases I find that expert advice can clear up a lot of pain and make things much more ergonomic across the board. Having the proper types and lifetimes at API boundaries, for example, can make a big difference, and folks new to Rust don't often have the right intuition for some of that stuff.

> Well that is the correct thing to do.

Is it? I can think of quite a few cases where using 'int' is fine; why is that a problem?

I wear two hats when I develop in go. One is for robust long-lived systems and for those I don't mind verbose error handling. The other is small quick scripts and for those I really wish I had a non-verbose option.