I picked up a basket (with a bunch of other varieties) from miamifruit.org a while back. They can't ship a lot of things to California, but if you live elsewhere in the lower 48 you should check them out.

    Redirect: https://www.youtube.com/shorts/*
    to: https://www.youtube.com/watch?v=$1

An interesting historical note is that across much of the west, each of those mile square sections was divided up into 16 pieces at 40-acres, which IIRC was the smallest unit of land you could purchase from the federal government.

You'll still find a lot of old homestead remnants across the west -- I used to climb through a few of them on a ranch I spent time at as a kid.

See:

- https://en.wikipedia.org/wiki/Section_(United_States_land_su...

- https://en.wikipedia.org/wiki/Public_Land_Survey_System

- https://en.wikipedia.org/wiki/Land_Ordinance_of_1785

    paste <(printf "a\nb\nc\n") <(printf "1\n2\n3\n") | while 

Kinda silly for this example, but very useful in things like `kubectl` pipelines -- you can do something like this:

    kubectl get pods --all-namespaces | awk '{print $1 " " $2}' | grep "doesntexist" | while read x y; do kubectl delete pod $y --namespace $x --wait=false; done

    grep -l -r pattern /path/to/files | while read x; do echo $x; done

This uses bash read to split the input line into words, then each word can be accessed in the loop with variable `$x`. Pipe friendly and doesn't use a subshell so no unexpected scoping issues. It also doesn't require futzing around with arrays or the like.

One place I do use bash for loops is when iterating over args, e.g. if you create a bash function:

    function my_func() {
        for arg; do
            echo $arg
        done
    }

Also, bash expansions (https://www.gnu.org/software/bash/manual/html_node/Shell-Par...) can save you a ton of time for various common operations on variables.

https://www.google.com/search?q=alex+trebek

My read on it is that it was never intended to be a consumer project as soon as they launched it (which explains the lack of polish), but the high level of interest when it was announced convinced them to launch it as one just in case they had stumbled on the next big thing. When that failed to materialize, they dropped it back to a research and enterprise project as was initially intended.

Been a few years, but IIRC a labmate of mine got a few units of .5mm highish ball count to work using that process and a toaster oven, but it is a bitch to test.

Would maybe do for a hobby project assuming you have access the equipment (e.g. a hackerspace or something) and are willing to drop a buttload of time into trying to get it to work, but if you are working for someone it is probably more cost effective to save the manhours and get it done by someone with the right equipment.

I wonder if they may have cut onboard graphics to increase yield by lowering the bar for a QA pass in the lower product ranges. If they are having process difficulties at 10nm, that would allow them to push some of what would normally be rejected to market.

If you want to use it, though, you have to leave the US or have a veterinarian as a friend. An acquaintance of mine gets DMSO gel used on horses to treat inflammation from a vet and uses it to reduce swelling in his back (has had multiple major spinal surgeries).

The common conspiracy theory is that DMSO is too cheap and treats too broad a category of ailments, so drug companies are lobbying against it with the FDA any time it comes up, as it would jeopardize the revenue streams from steroidal anti-inflammatory drugs, painkillers, etc.

https://en.wikipedia.org/wiki/Dimethyl_sulfoxide#Medicine http://www.dmso.org/articles/information/muir.htm

Python is a good alternative as well.

It does not support different sized drives in a raidz (equivalent to an mdadm array), as far as I know, but you can mix raidz and singular drives in a pool, though that is a bit silly. It also does not support adding disks to a raidz, which is equivalent to growing a raid5 or raid6 array, which is admittedly a pain in the ass.