How many "homes for a year" does that equal?

Or maybe it reflects the intermittency of wind: one hour you're generating 30 kW, the next you're generating bupkis.

Oracle has entered the lead with audits for both their SQL database and their bytecode tooling.

I'll make your a bet: if these drives are less than $300 in two years, I'll buy you one. Otherwise you buy me one. That threshold is 50% above the price you predict. Deal?

Enterprise HDDs on the retail market (vs premium system integration costs) have been just about $20/TB for years. I discovered that they'll drop by 66% in the next two years.

Sure but Slashdot has previously covered the fact that curl's developers are writing off security bug reports, including about stream dependency cycles in the HTTP/3 protocol stack. It may be adding features but losing security!

(I don't actually think curl has bad security. Mostly I am just tired of reading about the same dude making yet another minor variation on his same complaint, without Slashdot acknowledging that the basic story is a repeat of something that it has covered at least three times before.)

I could if somebody told me the modulation and FEC schemes, but so far I haven't cared enough to see what the actual paper says about those. I suspect this isn't using DSSS or another scheme that has a substantially different chip rate than the coded bit rate.

The data rate in this experiment was 1.02 petabits per second, so the first number is correct -- but almost 20 times what was given for the previous record. The previous record was actually a tad over 400 terabits per second, or 50,000 GBps if one insists on using more digits than needed.

VB.Net has explicit syntax that follows C#'s try/catch/finally: https://learn.microsoft.com/en...

They added that as the recommended replacement for Visual Basic's legacy "On Error" -- so I don't think your suggestion holds up. Having vaguely similar effects doesn't mean the two "both work out to the same thing just with a different syntax" any more than being Turing complete means different languages are fundamentally equivalent.

Correction: like the name of the database says, there are 380k reports of adverse events after people got vaccinated. Study is required to determine whether those were reactions or coincidences (or indirect consequences).

After I got the first two COVID-19 shots, I got a survey that asked whether I had seen a doctor for any illness since then. I truthfully answered: I had a tick bite that ended up with a rash around it, and I went to a doctor to exclude Lyme disease as a cause. When I later doing it about VAERS, I searched and found an entry that signed like mine. I don't know for sure it was about me, but I do know that tick bite and infection had nothing to do with a vaccine.

The wording is very careful. It's talking about people who were not authorized to immigrate to the US, but used programs that made it very easy to get forbearance of removal and work authorization.

For example,this page describes one such group: Hondurans who moved to the US before 1999, and have not left the US since 6 January 1999. They immigrated illegally but can work and avoid being deported because they have "temporary protected status". This is one of the programs that the Trump administration is ending, causing the status changes discussed in TFA.

What's the C# equivalent to "On Error GoTo -1", to pick one of the annoying misfeatures of VB.Net?

Your own "about 48 months" metric shows that you are being more carbon-intensive than me -- and that your short-term leases will only put you farther behind over time.

https://carsbibles.com/how-muc... also says that manufacture and transport of an EV are roughly equivalent to driving 20k to 40k miles in an ICE vehicle -- even before we count the costs of driving those miles in the EV. Factoring that in, the lower end is consistent with your 48-month number.

"Carbon payback period" is only relevant when buying the same number of vehicles on each side of the ledger -- which, obviously, I have not felt compelled to do.

The popularity of leasing doesn't mean that it is the right thing to do -- it usually means people are spending more than they need to, and then shipping a barely used car to some third world country.

I have been driving the same gas car with a 400+-mile range since 2018. (A stranger crashed into my previous vehicle while it was parked, totalling it -- otherwise I might still be driving my 2012 vehicle.) I am pretty sure your two additional vehicles in that period more than balance out environmental impacts from the respective power sources -- especially since I've only put 60,000 miles on my current car.

I guess some people find that throwing lots of money down a pit every few years feels like progress.

If a function is simple enough that "buggy" can be defined in isolation, AI or a junior developer can probably write it without much supervision. Most bugs that escape the first-level developer are violations of contextual expectations: cases where the code would work as expected in a different application, with a different use case, or something like that. So the characteristics of "a buggy function" depend on the code, processes and users around it, and that is where junior developers often fall short.

Defensive programming or robustness and "good taste" reduce the frequency of those bugs, but knowing how to do those well usually comes from experience with mistakes in the general domain: for example, handling very long lines in line-oriented (text) input.

(Or, from my life last week, populating a "source identifier" field in a protocol. The code was targeted for use in two executables: one with a fixed source ID across all deployments, and one where four instances within the same process would each have their own source ID. For some reason, the software team decided to read the source ID from a config file -- and then never set up the config file, so it sent a zero ID. The protocol reserves zero values because somebody knew people will fuck up exactly in that kind of way. In a different environment, that module of code would have been fine, but it was buggy in the actual environment.)

What do you think "experience" means? How do you think people get it?

Junior developers will make mistakes, but if the environment is organized to support learning and the junior devs stick around for a bit, they will learn -- either from their own mistakes or from others' -- and get better. Sometimes you get someone with "one year of experience, ten times" instead of "ten years of experience", but a good shop should try to avoid or remove that, depending on the root cause.

I mean, it is trivially true that current junior devs will never have exactly the same experience as current experienced devs, and hopefully the experienced devs continue to get better and so the juniors might not fully catch up, but taken as a group, today's junior devs should eventually grow into experienced developers and be senior to tomorrow's junior devs.