zeroimpl

Maybe it will? They didn’t say why they can’t sit through the videos, it might be because they are too slow to get to the point?

I don’t really see what value your comment is adding. The parents’ post was reasonable to me.

As an algorithm, this is simple (4 very basic lines of code).

As an approach to sorting, this is fairly complex - many simpler to understand solutions exist.

If you have no equity in a business, I'm not sure why the promise to sell/not to sell is even relevant. If it was some charity/non-profit or other group with a mission to make the world a better place, I could understand it. But why an employee of an email marketing business with no-equity would care is beyond me.

Any good explanation why HSV has the color distortion problem mentioned in the article? I thought hue was the main thing it got right. Is it due to a problem with sRGB itself?

Related study showing similar results: https://www.ahajournals.org/doi/10.1161/CIRCRESAHA.121.31890...

I don’t mind the & being required, I just don’t like the fact that there are 2 syntax options depending on whether & is at the start or not.

If the parsing problems are that difficult, I’d rather the @nest be always required.

The term "unbounded" seems a bit strange to me too. At worst you only need to lookahead until the next ; or { to figure out if it's a property or a nested selector.

I guess that's unbounded because the parser can't know how much data it will have to buffer, but in practice we're talking like a few dozen bytes most of the time.

Remotely disabling stolen internet-connected devices is good common practice. We used this once at my company for some items which inexplicably went missing from the manufacturing line. A few years later I got a support ticket escalation about a customer who got a device from “some weird turn of events” (something like that) and couldn’t figure out how to activate it, it kept saying to contact support.

I know the assumptions are wrong. But the point is the lack of explicit copyright notices on blogs or SO posts is probably enough to convince most courts that you did not willfully violate copyright. The parent I responded to implied you’d have to convince a court that you thought the copyright expired due to death.

In general I suffer from NIH complex so don’t really copy code from those places ;)

What I look at answers on Stack Overflow, the lack of copyright notices on the code makes me feel safe to copy it. Same goes for grabbing code from random person's blog.

If they had put explicit copyright notices in the code snippets, I'd assume otherwise.

I specifically clicked on this topic because of the word “opinionated”. As I already know how to use xargs, I was curious what kind of non-conventional or controversial opinion the author might have.

I think a good way to dumb this down is to use bacteria as an example. Most people know that improper use of antibiotics is leading to a surge of antibiotic-resistant superbugs. This is basically the same mechanism as far as I’m aware - evolution due to selection pressure.

If vaccinated people also keep wearing masks and social distancing, dangerous mutations should be much less likely.

The other problem with insect protein is it doesn’t qualify as vegetarian (nor the new hip name “plant based”), so it’s not clear who it is marketed to.

You start the shut down process from it...

It seems Apple only applies this if you sync photos to iCloud. Isn't the solution just to not use iCloud? I've personally never used iCloud sync for photos, am happy enough managing the files myself. Demanding that Apple allows you to use iCloud to host illegal pictures seems a bit entitled to me.

I am concerned about the slippery slope of if they start scanning files that were never going to go through their servers in the first place though.

Funny how they say SQL gets it right, but then shows an example which is the opposite of my experience.

From PostgreSQL

    # select '5' = 5;
    ?column?
    --------
    t
    (1 row)

I believe this is standard SQL. Putting something in quotes just means it is a literal, doesn't mean it is a string. Of course if you explicitly cast it to a string, then you get an error. As in:

    select '5'::text = 5;
    ERROR:  operator does not exist: text = integer
    LINE 1: select '5'::text = 5;
                             ^
    HINT:  No operator matches the given name and argument types. You might need to add explicit type casts.

I agree with the premise - SQL gets it right, but perhaps only in PostgreSQL?

Swapping for a non-dairy fat is trivial and won't really affect the flavour.

Cool never knew this - this will make me about 20% more productive at tailing!

I wonder if this misconception has more to do with the fact that programming languages define left/right bitshift operators and since left shift means making a number bigger, that implies the most significant bits are on the left (eg first in a LTR language).

> this may entitle all GitHub users to receive a copy of GitHub’s source code under the terms of the AGPL

Given that GitHub’s code runs on their own servers, doesn’t that protect them from needing to provide source code to anybody? I’ve always assumed running GPL code in the data center is fine.

I don't follow - If you are on a freshly cloned repo, none of the commits were made when the current branch was master, they were made on another user's git repo before your repo existed.

But commits change branches. None of the commits started on the "master" branch, they started on some developer's branch (which might also be called "master" in a different repo, but is still separate).

Doing it the way I suggest is directly in line with their final recommendation of passing the whole script as a single string.

Why not just this:

    ssh $server "$(cat script)"

So far that has worked fine for me. Curious when base64 is required?

Presumably there’s some similar food culture between Spain and Spanish-speaking countries?

Most tax software will automatically claim all such credits like this. Somebody would probably have to go out of their way to opt out of receiving the credit.

Something like:

    assertEquals(0, add(0,0))
    assertEquals(1, add(0,1))
    assertEquals(2, add(1,1))
    assertEquals(8, add(3,5))
    assertEquals(-3, add(2,-5))

PS: This kind of proves why a test is a lot less useful than the algorithm. Try figuring out how to implement "add" from the above test.

What are the odds that a website will run a computationally hard hash function on every single HTTP request just so it can log something less sensitive than an IP address?

Anybody know if there any performance/query plan differences between the following?

    WHERE details->'attributes'->>'color' = 'neon yellow'

And

    WHERE details['attributes']['color'] = '"neon yellow"'

Hash tables perform poorly when they need to be resized periodically as the table grows (as everything needs to get rehashed). Using a tree structure instead ensures consistent performance.