Would you be fine with the ethical implications of funding the industry to fight WWII? Would you consider funding Ukrainian military unethical? Or Taiwanese?
This is, sadly, not theoretical, and I'm afraid we'll soon see more of such choices, not fewer.
If your debts are also denominated in USD, their value will be fixed relative to your cash assets. This assumes a fixed rate, of course, but a 30 year fixed is common in the US and makes up a substantial portion of most folks’ debt.
If only. At work I've got a new computer, replacing a lower-end 5-yo model. The new one has four times the cores, twice the RAM, a non-circus-grade ssd, a high-powered cpu as opposed to the "u" series chip the old one has.
I haven't noticed any kind of difference when using Teams. That piece of crap is just as slow and borken as it always was.
> If only. At work I've got a new computer, replacing a lower-end 5-yo model. The new one has four times the cores, twice the RAM, a non-circus-grade ssd, a high-powered cpu as opposed to the "u" series chip the old one has.
> I haven't noticed any kind of difference when using Teams.
If the device is a laptop, also the thermal design (or for laptops that are in use: whether there is dust in the ventilation channels (in other words: clean the fans)) is very important for the computer to actually achieve the performance that the hardware can principally deliver.
Both devices are laptops. The old one had regular cleanups with a compressed air can. The new one is… new. I never cleaned it, but I figure it doesn’t require any cleaning one month in (I don’t live in the desert nor in a mine).
The new one is a thick thinkpad with a fat heat sink and dual fans. Its cooling solution looks much more serious than the old one, which only had a tiny heat sink and a single fan. It was also thinner.
Yeah people love to shit on electron and such but they're full of crap. It doesn't matter one bit for anything more powerful than a raspberry pi. Probably not even there. "Oh boo hoo chrome uses 2 gigs of ram" so what you have 16+ it doesn't matter. I swear people have some weird idea that the ideal world is one where 98% of their ram just sits unused, like the whole point of ram is to use it but whenever an application does use it people whine about it. And it's not even like "this makes my pc slow" it's literally just "hurr durr ram usage is x" okay but is there an actual problem? Crickets.
I have no issues with browsers specifically having to use a bunch of resources. They are complicated as fuck software, basically it's own operating system. Same for video games or programs that do heavy data processing.
The issue is with applications that have no business being entitled to large amount of resources. A chat app is a program that runs in the background most of the time and is used to sporadic communication. Same for music players etc. We had these sorts of things since the 90's, where high end consumer PCs hat 16mb RAM.
The issue isn't usage, it's waste. Every byte of RAM that's used unnecessarily because of bloated software frameworks used by lazy devs (devs who make the same arguments you're making) is a byte that can't be used by the software that actually needs it, like video editing, data processing, 3D work, CAD, etc. It's incredibly short sighted to think that any consumer application runs in a vacuum with all system resources available to it. This mindset of "but consumers have so much RAM these days" just leads to worse and worse software design instead of programmers actually learning how to do things well. That's not a good direction and it saddens me that making software that minimizes its system footprint has become a niche instead of the mainstream.
tl;dr, no one is looking for their RAM to stay idle. They're looking for their RAM to be available.
I dunno man, I have 32gb and I'm totally fine playing games with 50 browser tabs open along with discord and Spotify and a bunch of other crap.
In not trying to excuse crappy developers making crappy slow ad wasteful apps, I just don't think electron itself is the problem. Nor do I think it's a particularly big deal if an app uses some memory.
You're right, Electron is not inherently bad and apps need RAM. There's no getting around that.
The issue with Electron is that it encourages building desktop apps as self-contained websites. Sure, that makes it easier to distribute apps across systems and OSes, but it also means you've got front end web devs building system applications. Naturally, they'll use what they're used to: usually React, which exacerbates the problem. Plus it means that each app is running a new instance of a web browser, which adds overhead.
In real life, yeah, it's rare that I actually encounter a system slowdown because yet another app is running on Electron. I just think that it's bad practice to assume that all users can spare the memory.
I'll admit that my concern is more of a moral one than a practical one. I build software for a living and I think that optimizing resource usage is one way to show respect to my users (be they consumers, ops people running the infra, or whatever). Not to mention that lean, snappy apps make for a better user experience.
The problem with having 32gb of RAM is that there is no mechanism to power off part of it when it is unneeded (plus RAM constitutes a significant fraction of a device's total power consumption) so if the device is running off a battery and is designed to keep device weight to a minimum (e.g., battery as small as practical), then battery life is not as good as it would be if the device had only 16gb.
This is why the top model of the previous generation of the iPhone (the iPhone 16 Pro Max) has only 8 GB of RAM, bumped to 12 GB for the current top model (the iPhone 17 Pro Max at the higher tiers of additional storage). If Apple had decided to put more RAM than that into any iPhone, even the models where the price is irrelevant to most buyers, they would not have been serving their customers well.
So, now you have to pay a penalty in either battery life or device weight for the duration of your ownership of any device designed for maximum mobility if you ever want to having a good experience when running Electron apps on the device.
Lazy developers can make bad apps that waste RAM no matter what framework. But even conscientious developers cannot make an app with Electron that compares favorably to a native app. Electron is inherently a problem, even if it isn't the only one.
Don't know about chrome, but Firefox has an about:memory special page that will let you know which tabs are using the most ram. Of all the sites I use, youtube is the only culprit. When I am done watching a video, I use the about:memory to kill the associated process (doesn't destroy the tab (in case I want to come back to it)). I assume it is all the javascript cruft.
The people I trust to give good security recommendations (e.g., the leader of the Secureblue project) tell me I should completely avoid Electron (at least on Linux) because of how insecure it is. E.g., the typical Electron app pulls in many NPM packages, for which Electron does zero sandboxing.
I think it's a correlation vs causation type thing. Many Electron apps are extremely, painfully, slow. Teams is pretty much the poster child for this, but even spotify sometimes finds a way to lag, when it's just a freaking list of text.
Are they slow because they're Electron? No idea. But you can't deny that most Electron apps are sluggish for no clear reason. At least if they were pegging a CPU, you'd figure your box is slow. But that's not even what happens. Maybe they would've been sluggish even using native frameworks. Teams seems to do 1M network round-trips on each action, so even if it was perfectly optimized assembly for my specific CPU it would probably make no difference.
Nearly all apps are sluggish for a very clear reason - the average dev is ass. It's possible to make fast apps using electron, just like it's possible to make fast apps using anything else. People complain about react too, react is fast as fuck. I can make react apps snappy as hell. It's just crappy devs.
Yea, these applications are typically not slow just because the use Electron (although it's often a contributor). But the underlying reason why they are slow is the same reason why they are using Electron: developer skill.
> Conventional rebase creates a fictional history where your commits happened on top of the latest main
This is not fiction though. If someone added a param to the functions you’re modifying on your branch, rebasing forces you to resolve that conflict and makes the dependency on that explicit and obvious.
It’s always amazing going to these stores and seeing the support they provide for frequent “how do I computer?” questions. To me, this is like going to the water department because you need a new faucet on the kitchen sink. We make no such distinctions about who fixes what for purveyors of Internet services though.
Jokes aside, this octogenarian was living his golden years enviably. He was summiting peaks last fall, doing 500 lb barbell curls, and still sparring in his birthday video just 10 days ago. We’ve all gotta go sometime, but the way Chuck Norris went out was the way I’d want to go—able to do it all right up until the end. He was a lot of folks’ childhood hero, but that title is freshly renewed in my eyes. I have new inspiration in my fitness endeavors going forward.
He forgot to actually curl it. Like someone else said, the weights are almost certainly not actually 500lbs. Even elite bodybuilders and strongmen in their prime don't come close to curling 500lbs, let alone an old man.
Looking at the video, if it was legitimate, it would be 585lbs (6 45lb plates on each side plus a 45lb bar), which is even less believable.
> It is a class action lawsuit… the parties agreed to settle instead of waiting for the trial…
It would be nice if members of the class could vote to force a case to trial. For the typical token settlement amount, I’m sure many would rather have the precedent-setting case instead.
If/when you get a postcard/spam email that you're included in a potential class action lawsuit settlement, you can opt out of the class (in which case you preserve your legal rights to sue separately) or file comments with the Court.
You can, but then you lose the power of a collective and have to manage a lawsuit yourself. If you are being represented as part of a group, then you should have means to direct that representation.
Surely some firms choose to hold referendums already, but I could see that being a good law! As Better Call Saul explored in its early seasons, the interests of the large law firm can easily diverge significantly from the interests of the plaintiffs.
The old copy/paste from StackOverflow was essentially vibe coding, it just took a bit more effort. I saw plenty of people Google their way to code that technically worked, without having any idea how or why.
If someone has been doing that for 10 years and learning nothing, that would be a huge red flag. One that will likely become more common has LLM usage increases.
> Do you really need to go to the ER because you stubbed your toe?
Where else are some people supposed to go? Maybe that toe is starting to change colors… is it broken? Do I need to have it set? Is that possible for toes?
People have valid medical questions and don’t want to wait weeks to see their primary care. They might not live near an urgent care. The urgent care may have terrible hours, or they made the mistake of mentioning chest pain for their heartburn incident and now they are forced to the ER.
It’s a chicken and egg problem. Faster medical answers will lead to reduced ER wait times. Reducing ER wait times lead to faster medical answers.
Code reviews are a volunteer’s dilemma. Nobody is showered with accolades by putting “reviewed a bunch of PRs” on their performance review by comparison with “shipped a bunch of features.” The two go hand-in-hand, but rewards follow marks of authorship despite how much reviewers influence what actually landed in production.
Consequently, people tend to become invested in reviewing work only once it’s blocking their work. Usually, that’s work that they need to do in the future that depends on your changes. However, that can also be work they’re doing concurrently that now has a bunch of merge conflicts because your change landed first. The latter reviewers, unfortunately, won’t have an opinion until it’s too late.
Fortunately, code is fairly malleable. These “reviewers” can submit their own changes. If your process has a bias towards merging sooner, you may merge suboptimal changes. However, it will converge on a better solution more quickly than if your changes live in a vacuum for months on a feature branch passing through the gauntlet of a Byzantine review and CI process.
Or the reviewer feels responsible for the output of the code from the person they are reviewing or the code they are modifying. For instance a lead on the team gets credit for the output of the team
Also, wanting to catch bugs on review before they make your on call painful can be a large motivation.
I've always encouraged everyone more junior to review everything regardless of who signs off, and even if you don't understand what's going on/why something was done in a particular way, to not be shy to leave comments asking for clarification. Reviewing others' work is a fantastic way to learn. At a lower level, do it selfishly.
If you're aiming for a higher level, you also need to review work. If you're leading a team or above (or want to be), I assume you'll be doing a lot of reviewing of code, design docs, etc. If you're judged on the effectiveness of the team, reviews are maybe not an explicit part of some ladder doc, but they're going to be part of boosting that effectiveness.
Only viable if you’re okay with the ethical implications of funding war.
reply