Going to this wholesale electricity pricing site (I'm assuming this entity is a volume buyer and could get close to that):

https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fwww.pjm.com%2Fabout-pjm%2Flearning-center%2Fprice-ticker.aspx

If you did it in Philadelphia right now (PECO) you'd be paying $47 per MWh.

0.77 MWh * $47 per Mwh = $36.19 per ton.

So if we were willing to tax carbon at around 1/4th what Uruguay does it would be profitable in Philadelphia, assuming all this scales and the rest of their claims pan out.

I love this stuff too and I want people to have access to less expensive computers and be able to keep things working, but this just a practical way for a person who is strapped for resources to get a functional computer in 2022.

Everything they want to do is on the web, and more importantly, everything they *know how* and *need* to do is on the web. A computer that can't access the Department of Motor Vehicles website or log into gmail is not a practical device in 2022, it's a hobby device.

The best option for a person who lacks money, time and information (people forget you need all three) is an android "free phone" on a Cricket plan. I had one for a minute as a loaner two years ago and I was shocked by how capable a "bad" phone is at this point. That device can do just about everything you hafta-gotta do with a computer for the cost of signing up for one of the cheapest phone plans in the United States, which you also hafta-gotta do, if you're not rich enough to disappear.

If that person has just a little more money, time and information, adding an older- or base-model Chromebook and Comcast Internet Essentials ($9.95 per month) is probably worth it, but the phone is the gotta-have.

Nowhere in this user story is there space for an Amiga running NetBSD. That's a device for those of us who have time to play with it. It's very cool though.

So... it's compiled... like literally every other program every made?

What exactly makes compiled code special? EXEs are compiled code. The term "run-only" is stupid. You have to be able to read the thing to run it, and the computer can read bytes just fine, so... where's the problem?

"Tragedy of the commons".

Building a walled garden can be bad, but allowing free and unfettered access to an open field for everybody's use can too.

Right, I truly understand the urge to just take them down, but isn't the country also swarming with talented drone pilots? I get that a night pursuit would not be easy but someone with a good torch and a long range drone would succeed... or wait, they would need a license for a drone like that. Maybe nobody wants to be arrested just to find out the DEA was doing something asinine but legal.

Hey now, don't be raging on the white hat for doing white hat things. Not all of us have the meme darkness in our souls.

Had to Google to find out that they actually meant a trolley system at street level.

For everybody in the US: "tram" = trolleys on rails in the street. Just so you know.

Why are you touching all those paper towels? Grab one, throw in the cart, get on with your damn day.

Most people do not take that kind of time to comparison shop. If they can just deliver me the damn towels, then that's fine, I do not have brand loyalty toward most household products, nor do I need to molest my items in order to determine that it's a paper towel.

As in, have they figured out how to make their burger taste like a burger? Or the fish taste like a fish?

Because the burger is straight garbage. I don't understand the hype here, those things do not taste like real meat in the slightest. Texture isn't bad, but the flavor is just wrong.

In theory you're right, nobody sells for zero. In practice, there's a point where it's not worth anybody's hassle to sell or even track a price - there is always overhead. Thus zero.

JavaScript doesn't work that way. JavaScript runs in a very restricted security environment. It can do math, it can interact with the user, it can communicate with the website it came from. It can't spam the world without sending it all through the server it came from, which would defeat the purpose.

"To reach the other goals of the device, and provide an answer to the question ‘is the stellarator the right concept for fusion energy?’, years of plasma physics research is needed. That task has just started."

This is a long, long way from "star in a jar works."

Actually, as soon as we were notified of the issue, the plugin was closed and hidden on a temporary basis until we had time to evaluate the problem. Once we had done so, I personally created a new version of the plugin, without the malicious code, and pushed it to the repository in order to get the update out to the affected users. The existing committers were all removed, leaving the plugin entirely in the hands of the plugin team. The latest version is now safe and will not be otherwise until we determine the full details of what happened here.

Full disclosure is great, but some advance notice longer than a day or so helps a lot. We will always protect our users to the best of our ability, but sometimes, we get blind sided. It happens. Nobody posts about the dozens of other times we fix things before they get exploited. Not judging, just saying.

I worked with a Russian programmer of very few words, who willingly ran AIX as his desktop OS. When asked why, he said "I enjoy the strict confines of AIX."

I had absolutely no idea how to respond to that.

We've got a fair number of SSDs here. Failures have been really rare. The few that have:

#1 just went dead. Not recognized by the computer at all.
#2 Got stuck in a weird read-only mode. The OS was thinking it was writing to it, but the writes weren't really happening. You'd reboot and all your changes were undone. The OS was surprisingly okay with this, but would eventually start having problems where pieces of the filesystem metadata it cached didn't sync up with new reads. Reads were still okay, and we were able to make a full backup by mounting in read only mode.
#3 Just got progressively slower and slower on writes. but reads were fine.

Overall far lower SSD failure rates than spinning disk failure rates, but we don't have many elderly SSDs yet. We do have a ton of servers running ancient hard drives, so it'll be interesting to see over time.