mtsr

I think the effects of noise on sea mammals is a fairly recent area of research. I know of a researcher who has been working on this as part of research into offshore wind environmental impact. But they were already researching porpoises and this was just a new thing to keep track of.

Are they still covered by the patents that made them unattractive initially? Patent expiry could very well be the reason for their increased popularity.

And maybe not being the start of another MS embrace-extend-extinguish ploy.

Too much CO2 is known to lower IQ scores significantly, for the duration of exposure.

> Cyclic references can be dealt with runtime safety checks too - like Rc and Weak.

Indeed. Starting out with code sprinkled with Rc, Weak, RefCell, etc is perfectly fine and performance will probably not be worse than in any other safe languages. And if you do this, Rust is pretty close to those languages in ease of use for what are otherwise complex topics in Rust.

A good reference for different approaches is Learn Rust With Entirely Too Many Linked Lists https://rust-unofficial.github.io/too-many-lists/

Or maybe the commercial misuse of the word free should be challenged?

Generally “included (in the price)”, complimentary (costless but usually limited) or another word better fits the situation. But everyday language around this has gotten very imprecise.

And the penalty for non-compliance, another 0.5% fine?

So long as repercussions aren’t more serious (see EU fines) or more personal (hold C-suite personally responsible for contempt of court or similar), nothing will change.

Indeed, this is my preferred solution too. Unfortunately this doesn’t protect one from snooping by network intermediaries, although that’s much less of an issue in the EU due to privacy regulations. At least in principle, but it’s hard to be sure.

There’s also doubling the environmental impact of already pretty nasty dishwasher detergent.

You can’t turn off undefined behavior in C++ either. Lifetimes exist whether the language acknowledges them or not.

Except if you go to a GC language, but then you’re prototyping other types of stuff than you’d probably pick Rust for.

I run pihole, my own DNS resolver and some other stuff and I get the cloud flare checking your browser page on every single site using cloud flare.

Fortunately I haven’t seen the longer blocking you mention.

Competitive salaries with the US isn’t really a thing in countries with socialized healthcare, welfare, etc. With these institutions in place life looks qualitatively different at any salary.

Problems start when these institutions get systematically dismantled and salaries don’t change to make up for them.

Hex keycaps are definitely less common, but can still be found (https://www.littlekeyboards.com/products/hex-keycaps). Or you could get 3d prints of the exact profile you want.

Edit: Interestingly, above were also the result of an experimental musical instrument. See https://kbd.news/0xC-0x33-1525.html

But since you can't get much use out of music theory without going through some user interface (a particular instrument or notation), you also need to learn how it's laid out (how one maps onto the other, really). But maybe something like this keyboard could be an interesting teaching tool?

It'd be interesting to see a fantasy layout: say you were to let go of the computer keyboard layout, how would you set it up? Thumb keys, foot keys, toggles, etc, go wild.

Edit: There are decent guides to designing and hand-wiring keyboards using computer keycaps. I haven't looked far, but something like this https://medium.com/cracked-the-code/a-complete-guide-to-buil... .

The linked layout editor (http://www.keyboard-layout-editor.com) allows pretty wild layouts. Try loading the ErgoDox layout. While you might want to go farther still, it does nicely showcase rotated thumb clusters.

The plate & case builder tool can then generate some basic CAD files for a sandwich keyboard build to fit your keys. This can then be laser cut or something.

Because most designs use a Teensy with USB connection, you might even be able to make the keyboard output MIDI, so it could easily plug into a DAW, or whatever.

This. Patents (excepting those describing otherwise unreproducible inventions) have no real downsides.

I’m sorry if I phrased my comment in a way that offends you. I did not intend it as such and wanted instead to offer such a more fluid view of autism. Not only the definition, like you say, but also how different facets affect each person with ASD to a different extent which also changes with circumstances and throughout life in general.

And if you can accept these different facets being more fluid, I’d propose that rather than curing autism (something I don’t believe in and would never champion), one might be able to moderate specific facets of ASD that people on the spectrum themselves find a hindrance by changing the microbiome. Say some kinds of stimuli-caused overwhelm. Similar to somebody changing their diet to limit hangriness or blood sugar drops.

Note that at no point am I suggesting somebody with ASD needs treatment, just that they might see some improvements in their well-being if they wanted.

Finally, I derailed my comment by mixing it with a well-intended comment about mindset. I mean no judgement w.r.t. a fixed mindset, just that I found it a hindrance myself and have been happier since I started working on changing it.

For example being able to write down some things I may have held as axiomatic in the past (e.g. ideals or standards of behavior) and being able to consider how they may not be so fixed and deciding to change them or ignore them entirely is very liberating.

Among other things it lets me view my identity as separate from my feelings and behaviors.

P.S. I don’t appreciate the ad hominem at the end of your comment. Even if I unintentionally offended you don’t think I deserve that.

Fair point. But once you start comparing regions that differ in one way (say food between Western European countries), they most likely differ in so many other ways that the analysis becomes very very hard.

Have you got any citations for this? I’d be interested to learn about any more definitive results in this area.

I think it’s worth looking at what different facets are part of being autistic. It might be possible to differentiate between personality characteristics that are important to you (that you associate with your sense of self) and those that you can see as somewhat less essentially part of who you are.

For example, you might have a particular way of thinking that is different from other people which is both important to you and often associated with ASD. That doesn’t feel like something likely to change qualitatively from say a diet change.

On the other hand, there might be aspects like being overwhelmed by particular kinds of stimuli, that feel less personal and may feel more likely to be impacted be something like a diet change.

Finally, consider that you might be holding too tightly to some aspects of who you are “right now”, to be able to see and accept how some of these things might change. I know I do sp sometimes (regardless of whether I might be on the spectrum, or not). At the very least a relatively fixed (as opposed to growth) mindset is also often associated with ASD.

Kind of like ascribing someone’s talents to a handicap (blind musicians, creative people with ADHD, supremely skilled people with autism). If somebody is good at something, they probably put in the hours.

Indeed. Raw pointers are mostly when either crossing FFI barriers (say, calling or being called by C) or when what you want to do can’t be expressed within Rust’s ownership rules without taking on overhead (Rc, cloning, indirections, etc) that’s unacceptable to your specific use case.

I think some of the snideness is probably due to different senses of what amount of unsafe is actually needed. There’s so much premature optimization in many cases that wouldn’t even come up if the language were Java, Go or whatever. It’s totally fine to initially accept some known overhead from cloning or Rc if you don’t know yet it it’s going to significantly impact performance.

I wonder how tractable it would be for the compiler to suggest when your API needs Rc or boxing without being just as wrong in other cases.

I think now that too many lists is part of the book, maybe the compiler can link to that in some cases, hah.

It’s just the compiler assuming you know what you’re doing. You’re building this data structure on the stack, so it’ll point out where you’re not sufficiently explaining to it how the lifetimes of your code are safe. And even if you build it on the heap (using Box) you’ll still need to get the ownership right (using e.g. Rc).

There’s only so many variations that work for something like trees (especially with doubly linked nodes) in any language, without either inherently unsafe lifetimes (because the particular language can’t express them as part of the API) or some kind of indirection (such as ECS style indices). Or garbage collection or ref counting, but one probably uses Rust to be able to control that kind of overhead instead of having to use whatever the language creators picked.

If you want to learn about this, instead of using a ‘blessed’ implementation, read “too many linked lists” https://rust-unofficial.github.io/too-many-lists/.

As for the front-loading comment: yes, Rust requires you to get some things right from the start, particularly ownership and lifetimes. If you want to work in Rust like in a scripting language, you can just use Box, Rc and clone() everywhere. But getting it right without those might require a significantly different API. Which isn’t that much different with your rough C implementation. To get any kind of safe API there will require just as many changes (if not more).

It didn’t even need to trickle up, it was exclusively handed out to the top on the assumption of “trickle down economy” being a real thing.

I’ve read one needs to be careful with that because the resulting oxalate isn’t healthy (increases kidney stone risk, for example).

There’s not much you can do since adding chalk (which used to be common for both spinach and rhubarb) just creates the oxalate in the pan instead of your body and you can’t remove it. But cooking with lots of water (very short in the case of spinach) and throwing out the water does help to reduce the amount of oxalic acid.

Indeed. Many laws and regulations around government agencies (not US specific, as I’m in the EU) specify what the agency is allowed to do, rather than what it isn’t. This is much easier to enforce, although it does require more regular review of regulations (that specify the details) to keep with the time.

That depends. Climate change might very well (seasonally) increase cloud cover, vastly decreasing the power produced.