svrtknst

Without prediction, we wouldn't have goalies.

A puck can pretty easily travel something like 30-40 m/s, and shots are regularly taken 4-5 meters from the net.

Goalies have, what, 1/10th of a second to track and evaluate the shot and make a qualified save. If that was pure evaluation and reaction we would be far too slow.

I also think most people who've played goalie in any sport know that you get a _sense_ for where the shot is going. High, low, left, right etc so it's not just guesswork and statistics either.

Don't put secrets into things you dont have control over lol.

ChatGPT is cool and all but I often feel people are too naive when using these tools, with little consideration as to how their inputs are used, if the output is copyright protected, etc.

I've tried something similar, but splitting the args into Head and Tail and extending the Parameters<F> of the input function and some other trickery Been a little while since I looked at it tho

I've been bashing my head trying to create some sort of typed pipe for a while, with a syntax matching Elixirs, to avoid having to create curried functions all the time. The farthest I've gotten is that I achieve typing, so long as the function isn't generic. So this works:

  const plus = (a: number, b: number) => a + b;

  pipe(5)
    .thru(plus, 3) // Pipe(8)
           //   ^---- this is inferred as `number`

But this doesn't

  function plus<T extends string|number>(a: T, b: T) {/* ... */}

  pipe("five")
    .thru(plus, "three") // Pipe("fivethree")
             //   ^--- this isnt inferred or narrowed,becoms `unknown` iirc

Is it normal for these suits to be so... salty? in their formulations. I've never read one before, but a lot of the wordings are pretty hilarious.

> Carlsen, having solidifed his position as the "King of Chess", believes that when it comes to chess, he can do whatever he wants and get away with it.

> On September 4, 2022, Niemann soundly defeated Carlsen during an in-person game > Notably, this was not the first time that Niemann beat Carlsen at chess

> Notorios for his inability to cope with defeat, Carlsen snapped. Enraged that the young Niemann, fully 12 years his junior, dared to disrespect the "King of Chess", and fearful that the young prodigy would further blemish his multi-million dollar brand by beating him again

Unnecessarily hostile and bad-faith interpretation. We can be more respectful towards each other than that.

IMO the code runing in cars (and other types of vehicles) should be made available to inspection agencies, pref. written in languages that can make certain guarantees, or at the very least be required to be written in clear, legible manners with certain standards.

bone apple tea

Not just zero physical evidence - zero evidence _at all_. Afaik it doesn't appear until Plato uses it, and he claims that its thousands of years old or something like that. That should reasonably have traces in other accounts through the years.

I did hear a fairly credible theory that it is just an allegory invented by Plato, but influenced by various other myths and political centers (such as king Minos rule on Crete).

Not saying you're right or wrong - personally I like the palette but not the theme - but these comments give off a pretty arrogant attitude that I think is uncalled for.

which implies that there is no risk of period tracking apps being subpoenaed or selling user data?

Something I believe is overlooked that is relevant here is the effect of large volumes of feedback, even positive. Sara Chipps wrote about it in her blog post on Stack Overflow[1].

I don't believe we as people are desgined to handle feedback and opinions from a large number of people, and it's very easy for even neutral or benign questions ("is this planned for a release?", "any news on this?") to become grating.

Kinda similar to when kids go "Mom, mom, mom, mom" - nothing harmful is being said, but the cumulative effect is exhausting.

IMO it's a good idea to question, has someone else asked this? has someone else already stated this opinion? before posting on forums.

1. https://stackoverflow.blog/2019/07/18/building-community-inc...

I use IKEA wireless stuff (which in turn use Zigbee) and, outside of a relatively slim range of products, they work great. Good quality stuff, easy to set up, and continue to work even if my internet cuts out.

I'd argue that environmental impact is a health issue.

ok boomer

This is an increasingly common sentiment among hockey players too, that softer shoulder pads could be a way to decrease head trauma

This is a Hot Take (tm) that I havent fully considered so grains of salt etc, but boolean flags are in essence bad product type. Given a function

  create(entity, bool_a)

we have a function that creates an entity and take a bool flag, and it has 2 possible variants (entity + true, entity + false). If we add another bool flag

  create(entity, bool_a, bool_b)

then it increases to 4 states. Add another and you're dealing with 8 states, and so on and so forth. We likely don't care about all 8 states - rather 4 or 5, but complexity increases.

In this case, with the type key, we're essentially dealing with a sum type that has two variants

  (admin, attributes) | (customer, attributes)

which is fairly clear. if we add another variant to it, we only increase by one

  (admin, attributes) | (customer, attributes) | (distributor, attributes)

It's also not just a strip of cloth - it's a decent strip of cloth, fasteners, nuts, bolts, washers, something to fasten the seatbelt etc.

Which isn't a lot and I think this is an unfortunate oversight, but I can see it being a bit difficult to do properly.

Of course, doing it improperly with a rope would probably have been better than not at all.

I don't know if or how it could be leveraged, but marking something as irrelevant is also providing information to the ad system. Even if that data is "Less of this, please".

"Crash" can mean a lot of things, and in Erlang, a crash occurs whenever your functions are unable to perform their task (for instance, there were no functions that match your input data), or when process calls time out. More obvious crashes exist as well - a remote connection hangs up, a computer catches on fire, etc.

You could also use a variety of supervisor strategies or methods to detect what caused the crash.

One benefit of the "let it crash" mentality - provided the language and runtime has the right set of tools - is that you can focus on programming the happy path.

Simplified example, but if part of your app is a parser, you can write functions that parse known tokens. If the input contains bad data, your parser will crash. Its supervisor will detect this and be able to restart the parser,and can pass an error back to the user.

Now, should you add on code that handles known errors more gracefully and provides more info? Absolutely, but you don't have to, and imo that enables a very pleasant programming experience

There are some nice bits in here.

tap() and then() are fairly minor, but very nice quality-of-life additions.

The work on numerical, livebook, Mix.install etc are healthy steps to take.

Nice work.

> I would rather have had something closer to Koa

I'd just use Plug then. Not every tool suits every job

I'd say your unlikely to pick up the entirety of OTP in a few days, but agree that it should'nt be too daunting to train in it.

I'd say it's rather the other way around. Your infrastructure now solves what Erlang did 25 years ago.

Not to argue your point, though.

Erlang started in the late 80s and saw production use roughly 95

What you're getting in return is improved UX and performance, albeit it is a more abstract and collective gain than discounts.

You also get (unless you are a contributor, I guess) a very capable and transparent music editing software for free.

Imo the last part is a bit too dismissive. It's not too hard to imagine how telemetry from software can be used for ad targeting, or for more nefarious purposes, since the telemetry would have access to track info, including metadata.

If we're imagining worst-case scenarios, my first thought is "use track info to discover unlicensed music usage". Or for ads.

Both yes and no imo. I strongly believe that they have good intentions and that the reception has been a bit in bad faith.

I think it's a reasonable assumption to make, but as a user I'd want insight and granular choices, rather than just "allow telemetry? y/N"

But its funded by the tax, ergo it literally is their tax money at work here.