schleuss.online is one of the many independent Mastodon servers you can use to participate in the fediverse.
This instance has a focus on IT security, general computing, retro video games and game collector discussion. Please, no #NSFW and other 18+ discussion on this instance. See rules for more details

Server stats:

11
active users

#memory

1 post1 participant0 posts today

I recently took a dive into #C11 #atomics to come up with alternative queue implementations not requiring locking some #mutex.

TBH, I have a hard time understanding the #memory #ordering constraints defined by C11. I mean, I code #assembler on a #mos6502 (for the #c64), so caches, pipelines and all that modern crap is kind of alien rocket science anyways 😆.

But seriously, they try to abstract from what the hardware provides (different kinds of memory barrier instructions, IMHO somewhat easier to understand), so the compiler can pick the appropriate one depending on the target CPU. But wrapping your head around their definition really hurts the brain 🙈.

Yesterday, I found a source telling me that #amd64 (or #x86 in general?) always has strong ordering for reads, so no matter which oderding constraint you put in your atomic_load and friends, the compiler will generate the same code and it will work. Oh boy, how should I ever verify my code works on e.g. aarch64 without owning such hardware?

Continued thread

So it does look like the TypeScript language server has a limit of 4MB source size where it disables type checking (and actually shows an erroneous error stating that exports that exist in the file do not exist) for files that are imported but not open in the current workspace/session.

Still not sure if this is documented anywhere or not (haven’t been able to find it, if it is).

99.99999% of the time, unless you’re doing niche stuff like I am, you won’t run into this.

Workaround: should you have such a large file, e.g., with a large generated object, try and refactor to split it up into multiple files and rejoin it a separate file. The actual object size/memory usage isn’t the issue, it’s the file size.

github.com/typescript-language

I ran into an issue while creating and exporting a constant object that holds component versions of the ~1,500 icons in the Phorsphor icons library and I’ve created the simple reproduction below: D...
GitHubServer fails on import when exported object constant has too many entries/is too large · Issue #951 · typescript-language-server/typescript-language-serverBy aral
#TypeScript#max#lines
Had the wonderful pleasure of getting to see the outside of "Au Lapin Agile " while in paris. It looked very cozy so I was inspired to create this piece. Lots of artistic history associated with this petit cabaret. My mom told me that my great grandma used to spend her college years there and I like to imagine that she had the chance to meet Picasso or some other famous artists of the time. It is magical

#pixelart #pixelartist #illustration #aseprite #digitalillustration #bitart #8bit #ドット絵 #art #artist #spring #memory #pixelisland #paris

A quick demonstration of using the State: Overview page in Kitten’s¹ settings while developing to keep an eye on your event and event listener counts to avoid memory leaks.

Notice how the events and listeners counts change as I navigate between the People and Settings pages in my Place² node and that they are consistent. If they were rising as I navigated back and forth I’d know I had a memory leak somewhere.

If you use Kitten’s built-in features (e.g., the `addEventHandler()` method on your `kitten.Component` subclasses, Kitten will handle adding and removing listeners for you automatically during your component’s lifecycle. You can also do so manually in your component’s automatically-called `onConnect()` and `onDisconnect()` event handlers.

This view is useful during development to ensure you don’t have any memory leaks as pages are loaded and unloaded.

vimeo.com/1050714714

¹ kitten.small-web.org
² Place is in early development at the moment (codeberg.org/place/app)

Replied in thread


#Antidepressants "change your perception of the world, the kinetics of your movements or your emotional reactivity.
"Several studies have shown that very early changes (before any effect on mood) affect the recognition of facial emotions, the learning of new information or the updating of your beliefs."
[…]
"When you take an antidepressant, it is easier for you to recognize the smiles, the positive feelings on the faces of the people you're meeting on the street. It also is harder for you to recognize the negative feelings, the feelings of anger, the feelings of fear. And you have an easier recall of your positive, pleasant memories of the past.
[…]

Reference in French: radiofrance.fr/franceculture/p

Comment les antidépresseurs corrigent vos biais cognitifs : épisode 5/6 du podcast Les effets de la dépression | Radio France
France CultureComment les antidépresseurs corrigent vos biais cognitifs : épisode 5/6 du podcast Les effets de la dépression | Radio FranceAUDIO • Les effets de la dépression, épisode 5/6 : Comment les antidépresseurs corrigent vos biais cognitifs. Une série inédite proposée par France Culture. Écoutez Votre cerveau, et découvrez nos podcasts en ligne.

Land's End

When I was a teenager, I would swim across this inlet at slack tide. Once over, it was six hours before the next tide change when I could return.

The island on the other side is uninhabited, Walk in solitude for hours, in a wild place innocent of human ambition. Loggerhead turtles big as wheelbarrows. Carcass of a porpoise. A forest of live oaks salt-killed by ocean ingress, the bleached white bones standing in a graveyard of sand.

#photography
#landscape
#lowcountry
#memory

Replied in thread

除了记账,践行 daily-notes 笔记及每周/月/年总结,最大的触动就是像视频里说得那样,日子都去哪了?能直观地看到我的生活记忆是如此公式化和匮乏,反馈越来越多越来越强烈,可能这就是前段时间艰难决定的决心基础,从有 #觉察 开始,行动逐渐多起来,改变越来越大,看到这个TED演讲又才意识到这些,最近也有些周期性摆烂,接下来也要把一些随机性和新东西固化到生活习惯中

Pursuit of a memorable life | Dustin Garis | TEDxRenfrewCollingwood - YouTube
youtube.com/watch?v=nLe-8y7Tdd