jsveiga

IDK, but it took me a good 30s touching the posts in your screenshot trying to figure out wth was happening.

Maybe a safer option would be to simply be able to add specific users’ posts and/or commented posts to your landing page (which could even be implemented in the front end), never collecting or keeping any statistics of how many “followers” people have.

I think it’d be a risky route to take, as it creates the possibility of the general populace electing “lemmy influencers” and ruining it all.

There are two very distinct categories of content aggregation/social media: The ones where you primarily “follow” people/content creators (facebook, twitter, instagram, youtube, whatsapp) and the ones where you primarily “follow” subjects (reddit, lemmy, slashdot, etc).

The ones that focus on people are much more prone to create opinion bubbles, polarizing groups, and the obnoxious “influencers”.

Of course in some cases algorithms (as in youtube) may take in account the subject of your subscribed content creators, and feed you other creators covering similar subjects, but when the focus is on people, chances are they’ll feed you similar opinions, not only similar subjects.

It’s easy to see the difference if you compare subscribing to a “r/news” channel in reddit/lemmy with subscribing to a “foxnews” channel in youtube/facebook. One of those will get you a wider range of point of views (despite possible mod biases).

So I really hope subscribing or following people never becomes relevant in lemmy, let alone having algorithms tailoring what is shown to me. I want to know other people’s opinions; not an echo of my opinions.

Jerboa

It’s not normal to be constantly afraid of anything. That’s not healthy.

It’s normal and advisable not to completely trust the government, but being constantly afraid is paranoid.

Uh huh.

Because the tire is topographically a radially flattened torus, when you turn it half inside out, it becomes a 2D möbius strip. At this point it effectively has only one side. When you push such construct horizontally against a solid, because the z-axis perpendicular to the strip has no negative values (it only has one side), if that coincides with the orientation of the ∇Np of the solid, the z vector wraps around the solid. When the tire snaps to its rest state (inside in), it’s easy to see why it ends up around the pillar.

This 3D animation demonstrates the concept:

https://youtu.be/xvFZjo5PgG0

I see this, vlemmy.net!

I’m a 55 year old senior developer. I’ve been coding since I was 12 (yeah, RPG II in punch cards and COBOL stored in 8" floppies), and I have a TERIBLE memory.

Don’t bother memorizing and knowing every language feature and detail. Just get a general awareness of what it can do. Then when you need to accomplish something, it’s good enough that for the first times you do it you go “hey, I recall there’s a way of doing it” or at least (often happens to me) “hmm, this sounds useful enough that this language must have a built-in way of doing it”. Then you google or ask some AI, and you’ll get pointed to the general direction most of the times.

Then if you use it often enough, you’ll remember it. (and in my case, if I don’t use it for 3 months, I completely forget about it, and even get surprised when I see how I did it in my own old code).

In the old days, you could indeed know every feature and library (if any existed at all) of a language. Heck, I knew almost all hex op codes for the Z80 assembly by heart (still recall more of those than I recall my relatives names). Nowadays it is impossible to memorize everything.

In JS realm, if you look at the amount of components you have available in most frameworks, for example in UI5, or existing node modules for your node.js project, even trying to “memorize” them all is a waste of time. In cases like this, you just need to assume there’s a component or module that does what you need, then be good at finding, choosing, and understanding how to use one.

Not to mention the reduntant stuff they throw in “modern” languages, like javascript’s forEach. Some languages have 10 ways of doing the same thing, each one 0.1% more efficient for each particular case, but may catastrophically fail in some other specific case. Screw it. Learn the one that works well for every case and stick with it - you’re not coding ultra performance critical stuff in js anyway.

Programming today is usually more an integration of functioning pieces than building from scratch (assuming that if you’re talking about JavaScript, we’re not talking about creating microcode for bare silicon).

Worry about building an efficient and robust logic in your head. Then the programming language is just a tool, way less important than the logic you came up with.

J, like in GIF…