systoll

useEffect is treating undefined as meaning undefined.

It makes perfect sense from inside of useEffect.

If there are no dependencies ([]), the dependencies can never change, so React can always reuse the old effect.

If the dependencies aren’t defined, there’s no way to tell if the old effect is OK, so React must always rebuild it.

**

But `useEffect(()=>{})` doesn’t explicitly show that React will get `dependencies = undefined`, and in this case that’s unusually important.

You could have ESlint force you to change that to `useEffect(()=>{}, undefined)`, I suppose…

It’s more like leaving out 9/11 when discussing the effects/impacts of the PATRIOT Act.

The consumer price index has been relatively flat since the Fed started raising interest rates.

https://tradingeconomics.com/united-states/consumer-price-in...

The generally quoted inflation rate compares now to this time last year – so until next June, it includes the increases that happened before the Fed decided there was a problem.

This is useful in a lot of contexts, but if you want to know whether prices will be higher next month, it doesn’t make a whole lot of sense to use a lagging indicator.

The precedent is purely that the AI itself won’t be awarded the copyright.

The claimant here explicitly denied being involved in authoring the piece, and the copyright office took that at face value.

Anyone who actually wanted copyright would claim to be the author.

I tend to oscillate between it and Safari.

It’s Chrome with vertical tabs, and that’s better than Chrome.

Worth noting that the numbers you get at the end exactly match original claims from in The Bell Curve by Herrnstein & Murray.

They’re not from any American Psychological Association study.

"Small kids and elderly people: please don’t eat [these]."

Probably in front of mochi or some other choking hazard.

No they aren’t.

They thought they had peaked. IE - they thought the peak was in the past. IE - they thought emissions were higher in the past than they are right now.

The hammer is pretty good at screws.

And CSS grid is only working on pentalobe screws, until subgrid is usable.

https://caniuse.com/?search=subgrid

As qrian said – they’re abbreviations.

They’re repeated to cover the different ways typing them might get encoded.

Hangul writing combines all the characters in a syllable into one block. The keywords are the first character in each block.

EG: Safari is 사파리. You’d usually type ㅅㅏㅍㅏㄹㅣ and have the input method combine things according to the 'rules'.

ㅅㅍㄹ breaks the rules, so the IME might end up encoding ㅅㅍㄹ as three blocks, or as one.

No font in the world is going to know how to make ᄉᄑᄅ actually fit in one block, but it’s valid, distinct unicode, and it’ll get treated as one thing for selections and cursor movement.

(Modern Korean has clear rules about what valid syllables there are, but old Korean doesn’t always follow them, so unicode doesn’t enforce it)

> It's 2022 and I am using a Samsung A8 phone from 2018 which is pretty good

And if it can’t scan QR codes from the camera app, that’s purely because your carrier is withholding software updates from you. It’s built-in from Android 8.0 and Samsung supports the 2018 A8 up to Android 9.

I get the sentiment, but the ire is better directed at those preventing older/cheaper phones from doing what they’re capable of.

It’s more what they’re not doing.

The main issue is that they linearise the sRGB colour space before adding together the components… and then never 'delinearise' it afterwards. Human brightness perception is non-linear and WCAG totally ignores it.

This is a collection of 'even' black-white gradients in different colour spaces.

https://docs.krita.org/en/_images/trc_gray_gradients.svg

LAB is pretty much the standard for a perceptually even colour space.

The sRGB gamma curve was chosen based on CRT mechanics… but it’s pretty close.

The WCAG calculations only make sense in a world where 'Linear TRC' is perceptually even.

The cable is included - https://www.apple.com/iphone-se/specs/

Whoops – https://papers.ssrn.com/sol3/papers.cfm?abstract_id=931454 is a better source for the second one.

https://papers.ssrn.com/sol3/papers.cfm?abstract_id=996629 , is the 2.3%

https://www.researchgate.net/publication/228207991_Innocents... is the 5%.

3.8mB is an auto-update framework – https://sparkle-project.org

3.5mB is for a Quicklook plugin, so that Torrent files can be previewed in the Finder.

4.5mB is UI 'stuff'. The Cocoa 'nibs' that define the application UI tend to be bigger than comparable GTK XML files.

> Sigmoid Functions & Binary Classification

Sometimes you want to do binary classification.

This isn’t all there is.

> Layers - Why are artificial neural networks setup as "layers"?

They aren’t all set up like that. It’s a simplification of the effects of the limitations of the speed limits of synapses firing and vs the distances between them.

Spiking neural networks model the propagation more precisely, and have some promise. Their biggest issue is that it’s hard to get training data into an appropriate format for them… and that once you do... they don’t really seem to do better.

If the webpage declares that it wants JPEGs or PNGs, but not HEICs, Safari will transparently convert the file before the webpage sees it.

<input type="file" accept="image/jpeg" />

you can do this now with the contacts widget.

The iPhone is using a quad-bayer filter. Most of the time, it is behaving as a 12MP camera with error correcting photodiodes.

Compared to a normal 12MP camera, the 48MP one will collect slightly less light due to there being more gaps, but the bet is that the increased noise from that is less than the noise reduction from the pixel-binning.

Every photodiode has three others around it with the same colour. If they’re all similar, the sensor will average them, and if one of them is way off, it’ll throw that one away and average the rest.

This is better than doing noise reduction on either a 12MP, or a standard 48MP sensor because the space between comparable diodes is reduced, making it less likely to falsely treat small things like stars as noise.

As a bonus, if the user zooms in on a really sunny day, the 48MP might actually be worth using directly.

$5/year is an extremely high estimate.

A phone with a 5000mAh battery (more than any iPhone) takes about 20 watt hours of power to charge.

Charging it from empty to full each day would use about 7.3 kWh per year.

Electricity costs about 15c per kWh.

> In a flat monitor centered in front of your head, the distance between your eyes and different pixels on the screen varies depending on how close they are to the edge, thus distorting the sizes of the rendered sprites. Curving the edges reduces this effect (depending of course on the exact curvature and distance to the monitor).

That’s the same distortion that we encounter for all real-world objects all the time, and process automatically. We can’t turn that off, so I’m not sure it makes sense to try and compensate for it.

For 3D games, we’re trying to trick ourselves that we’re looking into a window. Curving the screen gives us a bigger window without a bigger monitor.

But 2D games are usually representing a flat surface intentionally.

EG: Mario runs to the right. Rendering it to a curved screen without correction suggests that he’s instead running clockwise around the viewer. For big enough stages, it brings into question why he doesn’t loop back on himself.

Correcting for that would mean shrinking things on the sides of the screen – effectively rendering to a flat surface behind the curved monitor.

It’s a weird case IMO — CreditKarma played a role but it seems like all the actual harm was elsewhere.

1. The Criteria are given by the banks via 'Lightbox'. If they were misrepresenting those criteria, it seems like the harm was to the banks, but this isn't mentioned. And if they couldn’t express their criteria via lightbox and used it anyway… again it seems like that’s mostly on the banks.

2. I suspect these estimates were better than nothing, which is basically what bank websites usually give you before you apply.

3. CreditKarma isn’t making the applications. The lenders are the ones forcing a 'hard pull' before telling you if the loan is available to you.

4. The credit score companies are the ones that decided that the 'hard pulls' would reduce people’s credit score for a significant period. Why is this only a problem if they used CreditKarma?

5. The new lender is the one rejecting loan applications based on credit score changes caused by the client shopping around. Why is this only a problem if they used CreditKarma?

**

It seems like there’s a need for a 'credit lock' that absolutely tanks your credit score while you are being checked, to avoid people applying for multiple lines of credit simultaneously.

Having lasting impacts beyond that seems anti-consumer, since it means you’re penalised for shopping around.

CreditKarma was an imperfect band-aid over that, but penalising them for that seems like treating the symptoms and not the cause.

One decent argument not made: this would avoid “spam” reaching people’s inboxes from people trying to sign up with emails they don’t own.

As the owner of a very common [initial][last name]@gmail.com address, I’d take the trade off, but this might be even more niche than neomutt users.

Android is in basically the same situation.

Obviously both Android & iOS let you open things in the default browser.

iOS has SFSafariViewController, which more-or-less corresponds to Chrome Custom Tabs on Android. These basically make a browser UI that is in the of the app for the purposes of multitasking/app-switching, but which is controlled by the browser. Devs can't inject code into these.

And both have WebViews, which let the dev do more-or-less whatever they want inside their own app.

We have interoperable, open systems; things like IRC and XMPP exist.

People chose discord over them.

The terms of service are just Discord being transparent about what they’re doing.

The thing actually stopping you from using Discord with a third-party client is that Discord’s server software responds differently to the way the third-party clients talk to it.

You’re in charge of what runs on your computer, and they're in charge of what runs on theirs.

It’s mostly an ergonomic difference.

Google Sheets has custom functions in Javascript; excel has them in VBScript. Both are part of the 'product', but they’re not integrated into the spreadsheet user interface at all. Using them is more like writing an extension to the Excel/Google Docs app, than it is like editing a document.

To define a custom function you need to leave the spreadsheet UI and define it in a totally different programming language. It’s a major barrier to entry that most users don’t cross, and the context-switching is a hassle even if you’re comfortable with both.

Lambdas let you write a function that takes arguments in the same way you would write a formula that references other cells.

The writer of this article determined Kraft singles to be the second best American cheese… second to a generic version of Kraft singles.

https://www.seriouseats.com/the-burger-lab-what-is-the-best-...

So… it well may be a Kraft Single.

Safari has tail-call optimisation.

We don’t have it elsewhere mostly because Google:

1. Agreed to implement it [it’s in ES6]

2. Implemented and shipped it behind a flag

3. Unshipped it.

4. Proposed something else [ https://github.com/tc39/proposal-ptc-syntax ]

Prior to that, Firefox had proposed a carve out for cross-realm calls, but then they didn’t bother implementing anything.

While apple is against Syntactic tail calls, they’re mainly just opposed to versions of it that would remove/unrequire the tail-call optimisation they already do: https://github.com/tc39/ecma262/issues/535

For the version of it that is backwards compatible, they wouldn’t need to do anything other than ignore the syntax. Their main concern is that it "could add confusion with very little benefit."

Beauty score of 10.5 out of ten?

I’ll thank our AI overlords for the compliment, but I don’t think I’m off the charts attractive.