Calling someone “smooth-brained” always felt backwards.

Like, I understand that brains are supposed to be wrinkly and there’s an actual disorder where the brain doesn’t have those wrinkles, which leads to developmental delays: https://en.wikipedia.org/wiki/Lissencephaly

But it still sounds to me like you’re just calling them “smooth” as in “cool”.

I mean, for me, it’s also mostly a matter of us doing embedded(-adjacent) software dev. So far, my company would hardly ever choose one stack over another for performance/efficiency reasons. But yeah, maybe that is going to change in the future.

Large shared codebases never reflect a single design, but are always in some intermediate state between different software designs. How the codebase will hang together after an individual change is thus way more important than what ideal “north star” you’re driving towards.

Yeah, learned this the hard way. Came up with an architecture to strive for 1½ years ago. We shipped the last remaining refactorings two weeks ago. It has been a ride. Mostly a ride of perpetually being low-priority, because refactorings always are.

In retrospect, it would’ve likely been better to go for a half-assed architecture that requires less of a diff, while still enabling us to ship similar features. It’s not like the new architecture is a flawless fit either, after 1½ years of evolving requirements.

And ultimately, architecture needs to serve the team. What does not serve the team is 1½ years of architectural limbo.

I mean, don’t get me wrong, I also find startup time important, particularly with CLIs. But high memory usage slows down your application in other ways, too (not just other applications on the system). You will have more L1, L2 etc. cache misses. And the OS is more likely to page/swap out more of your memory onto the hard drive.

Of course, I don’t either sit in front of an application and can tell that it was a non-local NUMA memory access that caused a particular slowness, so I can understand not really being able to care for iterative improvements. But yeah, that is also why I quite like using an efficient stack outright. It just makes computers feel as fast as they should be, without me having to worry about it.

Nah, I did understand it like that.

I posted that comment, because people generally wildly underestimate how common depression is. Because of that and because they don’t know how to deal with depression, they will look for other “explanations”, like yeah, sure, my kid’s just lazy. And that even despite these other “explanations” being extremely toxic and worsening depression.

So, this basic fact, that depression is among the most common disorders, would be part of my rebuttal. In hopes that she can accept that and help you work through it, like an adult should, rather than this silly game of peek-a-boo, where she hopes for it to not exist, so long as she doesn’t believe in depression. That is not helping anyone.

I don’t know what part of that is supposed to be an insult.

And the article may have talked of such stark differences, but I didn’t. I’m just saying that the resource usage is noticeably lower.

Yeah, you need to do tree-shaking with JavaScript to get rid of unused library code: https://developer.mozilla.org/en-US/docs/Glossary/Tree_shaking

I would expect larger corporate projects to do so. It is something that one needs to know about and configure, but if one senior webdev works on a project, they’ll set it up pretty quickly.

Major depressive disorder affected approximately 163 million people in 2017 (2% of the global population). The percentage of people who are affected at one point in their life varies from 7% in Japan to 21% in France.

https://en.wikipedia.org/wiki/Major_depressive_disorder#Epidemiology

This isn’t Reddit. You don’t need to talk in absolutes.

Similar to WittyShizard, my experience is very different. Said Rust application uses 1200 dependencies and I think around 50 MB RAM. We had a Kotlin application beforehand, which used around 300 dependencies and 1 GB RAM, I believe. I would expect a JavaScript application of similar complexity to use a similar amount or more RAM.

And more efficient languages do have an effect on RAM usage, for example:

• Not using garbage collection means objects generally get cleared from RAM quicker.
• Iterating over substrings or list elements is likely to be implement more efficiently, for example Rust has string slices and explicit .iter() + .collect().
• People in the ecosystem will want to use the language for use-cases where efficiency is important and then help optimize libraries.
• You’ve even got stupid shit, for example in garbage-collected languages, it has traditionally been considered best practice, that if you’re doing async, you should use immutable data types and then always create a copy of them when you want to update them. That uses a ton of RAM for stupid reasons.

Yeah, gonna be interesting. Software companies working on consumer software often don’t need to care, because:

• They don’t need to buy the RAM that they’re filling up.
• They’re not the only culprit on your PC.
• Consumers don’t understand how RAM works nearly as well as they understand fuel.
• And even when consumers understand that an application is using too much, they may not be able to switch to an alternative either way, see for example the many chat applications written in Electron, none of which are interoperable.

I can see somewhat of a shift happening for software that companies develop for themselves, though. At $DAYJOB, we have an application written in Rust and you can practically see the dollar signs lighting up in the eyes of management when you tell them “just get the cheapest device to run it on” and “it’s hardly going to incur cloud hosting costs”.
Obviously this alone rarely leads to management deciding to rewrite an application/service in a more efficient language, but it certainly makes them more open to devs wanting to use these languages. Well, and who knows what happens, if the prices for Raspberry Pis and cloud hosting and such end up skyrocketing similarly.

The problem is that it sounds like a riddle. In a riddle, you’re traditionally supposed to work within the rules that you’ve been told. So, not thinking outside the box here is not an indication that the person isn’t capable of doing so.

Of course, if I encountered this problem in real life, I’d ask Carol from accounting to check the other room, while I flip the switches. But my instinctive answer was that it is not possible, because I assumed it to be a riddle and the provided rules did not allow a solution.

More Bs means it’s softer, so more graphite will get onto your paper when you draw a line, which makes it darker.

More Hs means it’s harder, so less graphite. The advantage is that it doesn’t get used up as quickly and you can draw finer lines, although the latter is kind of a given either way, since you’re using a mechanical pencil.

It might genuinely taste different to you, and not just be a matter of preferences. There’s gene variations that alter the taste: https://www.bbc.com/news/health-50387126

Personally, I also found that it’s something you have to get used to. I used to barely eat greens and wouldn’t feel terribly great, if I did.
Then, earlier this year, I spent a month eating lots of greens. I’m guessing my gut microbiome adjusted, because yeah, now I can eat a whole salad bowl for a meal and if I don’t have greens at home for a few days, I will start to feel unwell.

By “unit”, you probably mean a SystemD unit, right?

I almost expected someone to learn that just from me posting. 😅

Basically, OpenOffice used to be organized by Sun Microsystems. Then Sun got bought by Oracle back in 2010.
Oracle does not have a good reputation at all, so the OpenOffice devs from back then figured they’d need to take things into their own hands and set up The Document Foundation to organize further development. But the OpenOffice trademark was owned by Sun/Oracle, so they had to rename and get a new homepage and everything. The name they chose is LibreOffice: https://www.libreoffice.org/

After the OpenOffice project was effectively dead, Oracle handed it and its trademark over to the Apache Foundation, where it’s seeing occasional bug fixes. But to my knowledge, they don’t even have the capacity to fix all the security problems.
All the actual feature development happens over on the LibreOffice side.

So, in practice, if you want OpenOffice, what you really want is LibreOffice.

I enjoy how the sign on the left says to not carry weapons and to follow traffic laws in all languages, except in German, where it just says that you’re entering the American sector.

Yeah, not great. You always hope that projects under a larger foundation, like GNOME, have a higher bus factor¹, but unless that foundation has dispensible income to pay someone, you’re ultimately still reliant on volunteers and not many people volunteer for maintenance.

What the foundation can do, though, which is also really important, is to hand over the keys to a new maintainer, should you disappear over night.
Like, yeah, forking is great, but some people will never learn of the fork. It happens about once a year that I find someone online who’s still using OpenOffice and that project has been practically dead since 2011.
So, I do hope we can get more open-source projects under some sort of umbrella. No idea how to actually do that, though. I also have open-source projects where I would not even know where to start to get them under some organization…

I mean, Firefox Reader View is probably the closest you will get…

Yeah, I also use the Lemmy webpage on my phone. In particular, I want to be able to come back to posts later, when more of a discussion has unfolded, which is where browser tabs work really well.