phaker

<inconsequential webpage bug report> First few images link to the full size version of the _next one_ </inconsequential webpage bug report>

1. It's a hobby in your own right. The nasty is not that bad, back in the day the annoying thing was how fiddly it was but the community thought of better ways like etching with a sponge. You can get better boards made online but that applies to all hobbies.

2. In most of US/EU you get them for $5 in up to _two weeks_, or in two days for $5+$2X or more which adds up quicklyand can be more than the rest of the project. Even next day shipping loses out badly to making it yourself in ~30 minutes, turns into two days delay unless you're lucky to have an idea in the morning and time to work on it in the next afternoon, a lot of the time i see people bodging things i'd make another board for because it's just easier.

Surprisingly many forgeries were exposed due to Calibri, Wikipedia has a short list:

https://en.wikipedia.org/wiki/Calibri#In_crime_and_politics

I feel like I remember the topic having its own list article but can't find any trace of it.

It's also made by the top contributor to erg (github user mtshiba), and erg is trying to be a compiled typed python.

If you're already making that then building a type checker wrapper on top of it makes perfect sense.

SVG filters default to linear color (but svg gradients etc default to srgb) so the 'SVG fe' are all linear. Color space used changes where the midpoint is so nothing else here uses linear color (unless they've decided to fudge that to match user expectations).

It and it's getting late here so i can't try it myself, at least not today, but i'd try moving in a fixed, sparse, pseudorandom pattern but vary operation size.

I think this should give a more staircase-y plot, with jumps when the size of each individual copy passes whole multiple of cache line width.

I think this way you don't need to fight prefetching, and there will be one read-modify-write per operation except right at the edges which is another signal.

Quercetin is present in grapes. Wikipedia says it's "the main flavonol" in both red and white wine ( https://en.wikipedia.org/wiki/Phenolic_content_in_wine ).

It is or at least was pretty common to hear about flavonols, flavonoids and specifically quercetin in various foods and their purpoted health benefits. Seems we've moved on to other compounds that are not yet known to be ineffective.

When it's young it works as is, it is more annoying but i like the results. For thin crusts i work a bit on it so likely few more grams end up on the inside, and it's mostly crust. You do need to stretch it in more steps and can't leave it resting for too long as it'll stick to the counter. Also I worked my way up from 66%.

We all want to make something and pick methods in pursuit of that. I always liked light, airy, bubbly, crispy things which drove me to high hydration and savory, beery, bready things which drove me to long fermentation. For pizza this means i liked bubbly high crusts and savory thin as a pancake pizza bassa, so that's what i tried to make.

When it's getting old i deliberately fold in extra flour. Notice it doesn't take that much to push it down because the quantities are quite small -- i've settled on 144g flour, ignoring everything else at ×1.75 it's 252g of dough, it'll take 18g of extra flour to push it all the way down to classic 66%, that's a heaping tablespoon. And i rarely really reach 75%, i aim for just under 75% and generally end up making 72~74% after including what it absorbs as i work it.

I keep them in the fridge, yes, should have mentioned that.

Oh, and another thing i should have mentioned is that if the dough is older i make sure to fold it few times more and work a bit more fresh flour into it. And i use high hydration (as high as i can make it, about 72~75%), when i pull it out from the fridge it's _wet_ so even when it's as old as it should be (2~7 days) the crust will be mostly fresh flour.

The trick is that there is no trick and you just let it overferment but pick style that will work well with it. You need savory toppings to go with the taste, e.g. salami and maybe sharper tasting cheese. Making very thin pie will be difficult with dough so weak so don't do that, it won't rise very high so don't make it too thick either.

And 14 days is the furthest i recommend taking it. As i wrote above two to seven days is best, of course it tastes differently after seven than after two days but both are good and perfectly within the canon of 'pizza' and you can prepare it anyhow you want.

Beyond that you're pushing it, but since the topic is what shortcuts you can take i'll still recommend more than you need and using it longer than you'd think to over trying to make it the same day. 30~40 minutes from a decision to a pizza, it does taste right too.

You can go the exact other way, plain pizza dough is best after anywhere from 2 to 7 days in my experience. You can push it to 10 or 14 days too, which will taste different but still very good and the dough will be quite weak by then for thin crust pizza.

You still have to think of it ahead of time but this removes need for coordination and lets you do it in batches.

Also I just make one kind of starter bread dough in batches and then make everything out of it, some things as-is (bread for first ~4 days, bread dough pizzas for 14 days), some by mixing it with fresh dough (bread afterwards, everything else). But i'm specifically after the heavily fermented dark dough taste.

I expected this to be about hyphenation, which (as i just realized and checked) breaks search because it won't find hyphenated words. I'm "happy" to see it's an entirely different and another problem.

Afaict other than water water, vitamins, preservatives, organic acids and glycerine the only common ingredient between the two is magnolia officinalis. Wikipedia mentions two psychoactive compounds in it with a matching mechanism:

https://en.wikipedia.org/wiki/Magnolia_officinalis

This depends on the distribution, for a uniform distribution all 16 hex digits are equally likely in every position.

Also for benford's law to show up you want your data to span several orders of magnitude (so e.g. you have numbers in tens, hundreds and thousands) and for a datapoint to be about as likely to give an n-digit number as a n+1-digit number, not everywhere and not exactly but it needs to dominate over there being ten times times as many of them with each step.

Haven't heard this one.

Do you have a name or source or something? Can't really google that.

With this attitude you'll see conspiracies everywhere, and that's a self reinforcing spiral.

If this is how much evidence you need to dismiss something without checking, then you'll dismiss everything and you'll never find out if/when the hunch was wrong.

There was a very noticeable uptick in spam (and also false positives like news Russia wouldn't like suddenly being marked as nsfw) starting after Elon laid off everyone he could. So i guess the human half of moderation disappeared.

The 'apply' button is active so these are unapplied changes.

TAI is the 'UTC without leap seconds'.

UT1 is an evolution of solar time, and wobbles when Earth does because it's using the Earth and Sun (and other bodies) as a clock.

UTC is TAI with leap seconds added when UT1 drifts too far away.

Disable https everywhere

Rephrased it even sounds better:

It's easier to educate the motivated than motivate the educated.

You were powering it through the protection diodes.

Some 10-15 years ago someone built dirt simple radio tags this way. Just a microcontroller, with a capacitor and an antenna trace connected to some io pin. I loved that hack.

First, it _would_ make sense to use a narrow c-like subset of c++, but lots of people wanted to bring 'good practices' from c++ to the kernel.

And many of these were _bad_, C++ was a different language back then and the culture of how you write C++ was different. There were times when it was fashionable to write OO spaghetti almost as bad as the stereotypes about java, or templates that worked except for some unforeseen footgun (then you could template libraries that worked correctly but figuring out how was a trip). And before all of that there was a decade when C++ compilers were just _full_ of bugs, and before that there was no standard and every compiler was different. The negative stereotypes about C++ come from all that.

I think he had every reason to fear that e.g. he would have to fight someone who implemented control flow using an inheritance hierarchy because it's a pattern. And he could find himself in the minority.

(Also I'd say there are still counterproductive fads, and it's still common to write C++ that's beautiful on the outside and completely inscrutable inside, or generally pay a huge price in code size and complexity for marginal gains elsewhere, or to depend on optimizations that don't trigger. Same in many other higher-level languages but somehow not in C.)

Second, more important, i don't remember any talk of adapting C++ to bare metal programming, while there is an ongoing cooperation with rust folks already.

It's something teenagers say, or used to say, so i wouldn't judge the author just yet.

It _may_ become something only far right nuts say, same as with frogs and other 4chan stuff -- young people invent something, culture drifts, dumber or isolated people are least likely to drift with it and most likely to have violent views, eventually mostly violent people say something and the rest stops saying it because they don't want to be taken for one of the violent group -- but i don't think it has happened already.

In related news you just found out why many adults treat anything and everything teenagers do is something rude and offensive that needs to be suppressed. Teenagers are loud and annoying so their stuff is something loud and annoying people do. It's something you need to control.

Or i might be wrong, this can change quickly, but then the author can be wrong too.

The plot says it's 212.18mm (= 21.2cm / 8.35 inches). You mixed up a decimal or something, sorry.

Do you think it is the responsibility of academia to teach "industry relevant stuff"?

I don't think that was what ibains was going for, though i don't fault you for seeing this in that comment. (Especially that i don't think this course suffers from that problem and generally i think things are rapidly improving on this front.)

That problem to me and i think to him too is that quite a lot of things that such courses tend to teach as well thought out, well working solutions and approaches just don't work very well and frequently i find comments on what's a 'good taste' solution and what isn't that are completely my understanding of the problem space which is why.

E.g. in parsing (as that's the topic he mentioned): First, lots of people just spend way too much time on it. And they focus on parts that are of zero use to beginners (like explaining all several grammar families) and then use obtuse parser generators that save no work and sometimes use them in bizarre way (like picking a lalr parser generator then hand editing the output to support a not-quite-lalr language). Meanwhile a recursive descent parser is easy to write, fast and gives pretty good error messages with _very_ little work. You do need to know enough about grammars to be able to write one down and know if it describes an ambiguous language etc so this should be taught, but you don't need to understand the language zoo well.

And multiplication is a fancy convolution (with carries).

Fast convolution algorithms use FFT and run in O(n log n) time, which is why fast multiplication algorithms are based on FFT and why everyone was looking for O(n log n) one, which was found like a year ago.

(Though from what i can tell in "Faster Convolutions" section the article claims you can easily build O(n log n) multiplication using FFT which doesn't work as it ignores carries)

MAP agreements are illegal in EU. They were specifically banned, and for good reason. Which is why calling Shimano's stance a "refusal" to deal with some problem gets you a negative response.

Still, feel you on the retail apocalypse, and how every other new internet darling can somehow skirt taxes or... and the problem is unfixable until right after it doesn't matter anymore. It took something like twenty years for Amazon to start paying US sales taxes most of the time, in many cities Uber's business model was price dumping etc.

From what i can find, the difference is that ergot is parasitic and rare but the fungus growing on darnel is symbiotic and common.

Polish wikipedia says up to 86% of seeds carry it but without source. This paper [1] says 70% of 'wild populations' of related L. perenne, implies infection in darnel (L. temulentum) is also prevalent, but notes most populations have low frequency of infected individuals and then tries to explain that.

[1] https://mivegec.ird.fr/images/stories/PDF_files/0250.pdf

it _is_ an e-paper / e-ink / electrophoretic display. E-ink went back to color filters because their filter-free color displays take tens of seconds to refresh and nobody was buying them.

And the problem is kapton is just one of many polyimides, (pmda-oda) there are other others like P84 (btda-tdi/mdi).

But nobody knows the generic name (the acronym isn't even in the wikipedia article) so fly by night vendors use 'kapton' wherever they can get away with it.

(and as with teflon, iirc they sell other polymers under the name of kapton too)