Well, maybe I’ll try again in the future but I don’t currently own a Samsung.

I guess the answer to at least one of those is no. Last time I tried a battery replacement, I broke the screen either during assembly or disassembly. I build my own desktop PCs, and have fixed laptop monitors and drives, but every time I attempt hardware repair on something phone-ish, I make it worse (even going back to when I owned an OpenMoko).

Maybe he’s got a finer point, but it actually just looks like an argument against categorization. It’s like saying I don’t trust math about “triangles” or “scalene triangles” or “rhombuses” when you find out about the special properties of the equilateral triangle or the square.

The fact that there are differences between elements of a category does not eliminate the utility of the commonalities shared by elements of a category. It does limit that utility, yes.

For example, just because you are getting plenty of protein, if you somehow completely avoid one of the amino acids that the human body uses but can’t synthesize, then eventually you will have some fairly specific health problems. That’s not strong evidence that it’s worth micromanaging your macronutrients by tracking your intake of all amino acids individually. (It might be; I haven’t seen it studies either way.)

Maybe I’m missing some context, but I also get the “anti-science” vibe from the image.

Not every error bar represents a Gaussian, if for no other reason that most error bars aren’t symmetric.

The error bars for small sample size relative to population size are Gaussian.

Error due to a non-representative sample can have a variety of shapes, but their distribution might also be unknown. We do frequently, almost implicitly, assume unknown distributions to be Gaussian, but we should recognize that’s not necessarily a true fact about the universe.

It’s a very non-representative, very small sample. The error bars in the statistical inference to the whole population includes both “very common” and “one-in-a-million”.

It’s like intraoffice e-mail.

That’s why Elmu wants to go to Mars.

Agreed. I tend toward more literal translations for instruction/explanation – it made things stick better for me when learning Spanish. But, yes, in context “harder” is a definitely a more useful translation.

“tres bien” is “very good”

“si vous plait” is like “please”

“plus fort” is like “more strength”

I’ve never studied or learned French, but you can pick up some of this stuff from “throwaway” French in other context and the etymology shared with other languages.

So, basically just the stock U.S. porn phrase translated to French.

Honestly, I don’t like either programmability approach (vimscript/lua OR emacs-lisp), but I’ll probably just stick with neovim, because when I’m on a system without my configuration, I’ve more productive there, and I don’t want to learn enough emacs-lisp “APIs” to reproduce my somewhat small vim configuration.

I have a prior source to refute that: https://www.arjen.eu/2011/09/how-to-prepare-a-kiwi/ /s

Nobel prize-winning anti-parasitic for humans, yes.

Several studies show no statistically significant effect on COVID-19 length or severity.

You can do single-blind. You do prep, anesthetize, then open the card that decides if the surgery continues, or if the patient is simply awakened at the expected time.

You can also do it for surgeries that use locals, but then the surgical staff has to do a lot of miming/acting instead of actual cutting.

Medlife Crisis did a couple of Placebo effect videos, and mentioned that he participated in a single-blind stent study.

I don’t know how you’d do double-blind.

• In https://lemm.ee/comment/20947041 they claimed “implicit type coercion” and showed many examples; they did NOT claim “string concatenation”.
• However, that was in reply to https://lemmy.world/comment/17473361 which was talking about “implicit conversion to string” which is a specific type of “implicit type coercion”; NONE of the examples given involved a conversion to string.
• But also, that was in reply to https://lemm.ee/comment/20939144 which only mentions “implicit type coercion” in general.

So, I think probably everyone in the thread is “correct”, but you are actually talking past one another.

I think the JS behavior is a bad design choice, but it is well documented and consistent across implementations.

I think it’s less about type system, and more about lack of a separate compilation step.

With a compilation step, you can have error messages that developers see, but users don’t. (Hopefully, these errors enable the developers to reduce the errors that users see, and just generally improve the UX, but that’s NOT guaranteed.)

Without a compilation step, you have to assign some semantics to whatever random source string your interpreter gets. And, while you can certainly make that an error, that would rarely be helpful for the user. JS instead made the choice to, as much as possible, avoid error semantics in favor of silent coercions, conversions, and conflations in order to make every attempt to not “error-out” on the user.

It would be a very painful decade indeed to now change the semantics for some JS source text.

Purescript is a great option. Typescript is okay. You could also introduce a JS-to-JS “compilation” step that DID reject (or at least warn the developer) for source text that “should” be given an error semantic, but I don’t know an “off-the-shelf” approach for that – other than JSLint.

(.) is a valid expression in Haskell. Normally it is the prefix form of the infix operator . that does function composition. (.) (2*) (1+) 3 = ((2*) . (1+)) 3 = 2 * (1 + 3) = 8.

But, the most common use of the word “boob” in my experience in Haskell is the “boobs operator”: (.)(.). It’s usage in Haskell is limited (tho valid), but it’s appearance in racy ASCII art predates even the first versions on Haskell.

Oddly enough, in Haskell (as defined by the report), length is monomorphic, so it just doesn’t work on tuples (type error).

Due to the way kinds (types of types) work in Haskell, Foldable instances can only operate over (i.e. length only counts) elements of the last/final type argument. So, for (,) it only counts the second part, which is always there exactly once. If you provided a Foldable for (,) it would also have length of 1.

This is my favorite language: GHC Haskell

GHC Haskell:

GHCi> length (2, "foo")
1

Here in Arkansas, I don’t know any “trash” that you can pick up for a deposit. I think when I was a small child in the 80s you could do glass bottles, but when plastic came in that ended. As a teen, and up to maybe a decade ago, you could get paid for aluminum scrap (by weight), but both of the metal recycling places in my county (Polk) do not pay for aluminum anymore (they will accept it, but not pay for it).

Only if that browser somehow becomes overwhelmingly popular in a market segment BEFORE it gets JS support.