pixelscript

Do you have a minute to talk about our lord and savior Hydrus?

Nvidia and AMD broadly cover the same use cases. Nvidia cards are not intrinsically better to my knowledge, Nvidia simply offers ultra high-performance cards that AMD doesn't.

If you just need nonspecific games to run decently, a card from either brand will do it. If you need to run the most intensive games there are on unbelievable settings, that's when Nvidia should be edging out.

ML dabbling may complicate things. Many (most?) tools are written for CUDA, which is a proprietary Nvidia technology. I think AMD offers a counterpart but I do not have details. You will need to do more research on this.

I am going to continue to tell people "just get an AMD card", but only if they have indicated to me that they are shopping for new parts and haven't committed to any yet.

Giving that advice to someone who already has an Nvidia card is just as useless as those StackOverflow answers that suggest you dump your whole project architecture and stuff some big dumb library into your build to solve a simple problem.

Doing alright, I think.

Had a good weekend. Went to a rodeo and played a lot of Factorio SE.

Discovered yesterday that my clothes dryer vent is plugged. Probably has been for some time, maybe years? Put in a maintenance request to have it fixed. Hopefully in the next couple days I'll finally be able to dry clothes in a single cycle instead of two. Pretty stoked about that.

Work is a tad stressful. Boss kinda shot from the hip with a new overhaul of our logistical processes and suddenly needs our in-house software restructured with a plethora of new features it was never designed to handle. I fear I won't meet any of the deadlines at the pace I'm going. Boss seems to understand this at least and isn't the type to hold me over hellfire about it.

Looking forward to next weekend. Going to an annual Paddy's Day pub crawl and visiting my parents.

Generally my policy is that if it's news I need to hear, it will find its way to me one way or another. I need not go seeking it out. I will look up something I've heard if I want more info, but I don't read news for its own sake.

The great bulk of news that reaches me being second, third, fourth-hand and beyond means I'm not well-informed about anything. But at least I'm not wasting brain cells on whatever dumb shit did, or what shit said, or what breakthrough made that does not remotely lead to the conclusion the article implies, or some journalist's speculative opinion piece masquerading as news.

If I could just get a dry listing of everything that happened the previous day, only including events of actual consequence like "law passed" or "person died" or "business discontinues product/service", and leaving behind any event that can be effectively retold as " scrawled message on public toilet stall" (like many celebrity and political articles) or anticipation pieces that try to predict future events, I'd be satisfied.

Tab hoarding is just poor man's bookmarks.

Oh wait, you're on Gelbooru. Nevermind, I get it.

People tend to contribute to the projects they already have the skills for.

People also tend to pick up new skills when they have a driving incentive to do so, like supporting a project they have a vested interest in seeing improved.

You need to learn the language's structures

Most of the bread and butter ones have analogues in other languages you should readily understand. More language-unique structures are rare; the more niche they are, the lower the odds your ability to contribute in a meaningful way hinges on your understanding of them.

you need to learn how the compiler works

You really don't, though? Modern compilers, particularly the Rust compiler, are designed to abstract away as much of the details of compilation as possible. If the project really does need to tickle the compiler a certain way to get it to build, it will almost certainly have a buildscript and/or a readme.

you need to learn the libraries that the FOSS project is using

This is true regardless of the language in use. I'm not sure why you brought it up.

you need to learn the security pitfalls for the language

I would imagine most of these language-specific security footguns are either A) so specific that you will never hit the conditions where they apply, B) are so blazingly obvious that code review will illuminate what you did wrong and you can learn how to fix it, or C) so obscure that even the project owner doesn't understand them, so you'd be at minimum matching the rest of the codebase quality.

Mind, I am not insinuating that one can simply bang out a whole new submodule of a project in an unfamiliar language with minimal learning time. Large contributions to large projects can be hard to make even when you're a veteran of the language in use, as the complexity of the project in and of itself can be its own massive barrier. But not every contribution needs to be big. And for most contributions, I don't believe the language is the most significant barrier to entry. It's a barrier, sure. But not the biggest one.

I'd wager it's not having a significant impact on the volume of contributions to Lemmy in particular.

No one said it was shameful?

It's a huge win, but not the kind of win people reading the statistic with no context (like me) probably thought.

I'm sure a lot of us looked at "15 percent of desktop PCs in India run Linux" and, regardless of whether it was hasty and irresponsible for us to do so, extrapolated that to, "15 percent of Indian PC users are personally selecting Linux and normalizing its paradigms".

But in reality, it sounds more like "15 percent of Indian PC users use Linux to launch Google Chrome". Which is impressive, but not the specific kind of impressive we wanted.

It feels a bit like how I imagine, say, a song artist feels when they pour their heart and soul into a piece of music, it gets modest to no traction for a while, and then years later a 20 second loop becomes the backing track for a massive Tiktok meme, and almost zero of that attention trickles back to their other work.

these sliders are very thin, but not thin enough. neither of my laptops close correctly with one equipped. :(

Ah well. Masking tape suffices.

collaborate and listen?

Stateless functions still deal with state, they just don't hold onto it. Without state to mutate, a so-called stateless function doesn't do anything.

In declarative languages, your state is the sum of everything you've declared. You don't query results out of thin air. Computational results logically conclude from everything you set up.

HTML ""has state"", as in it has a DOM, but it doesn't do anything with it. You don't mutate the DOM after it's built, or query the DOM to compute results that weren't trivially evident from the state you declared.

You can do those things with JavaScript. But all that proves is JavaScript is a programming language, and HTML is just a data format it can interact with.