oh I guess I really hadn't thought about heating needs. The batteries generate heat when being charged or discharged so I was just assuming they never really would need external heating.

I live in Iowa, and I've heard some pretty brutal accounts of bad EV performance when it gets really cold here. All rechargeable batteries perform poorly in the cold though, I remember NiCD batteries being absolutely terrible in the cold.

Not only do we have the concept of a plan for negotiations for a peace agreement; the current level of disagreement between the agreeing parties suggests that we actually have at least three distinct concepts of a plan for negotiations for a peace agreement! Where a lesser leader might myopically interpret having a single agreed-upon set of terms as essential to a treaty; Great Leader understands that American Greatness requires more.

Yes, you're the second person to point out the typo, which would have been edited within seconds of me clicking "submit" if we had an edit button.

Not sure what you're speaking about. VIM classic differs from normal VIM in that they do not use LLMs to help develop the editor itself, nor do they accept contributions from those that do. Where as the original VIM editor maintainers now use AI and LLM for bug fixing, feature developing, etc.

Is that really a bad thing? There are certainly plenty of examples of old things that suck; either because genuine improvements became available after they had already solidified or because they were always broken and are now running purely on denial-fueled risk tolerance; but, in principle, it seems like it should be a bad thing that age is seen as a bad thing. Especially when software is more like math than like civil engineering in terms of the tendency of its materials toward corrosion, embrittlement, and fatigue. (and when so many 'modernization' projects turn into expensive failures or go way behind schedule and over budget to eventually death march toward feature parity, sometimes even achieving it in time to be declared legacy themselves.)

I'm not calling for a crusade against 'fast fashion' software; if people want to bang out an app on the fast and cheap to catch the moment when people care they can do that; fine, whatever; but it seems like software built on real long term service timescales should get a lot more credit than it does. Absent specific criticisms; it's not "eww, there are people who weren't even born then", it's "the software has been in service for a generation".

All the more if there are a lot of outfits doing the same thing: having some unique oddball legacy thing means having potentially crushing maintenance requirements unless everything was gloriously secure from day 1, which it probably wasn't; but if there is some big mass of enterprise Java 8 why should we call it all eol and scramble rather than just maintaining java 8? Especially when we can do so in software, without some of the vendor and hardware inflexibility you see with things like old school mainframe applications where there's an implied commitment to a single old school mainframe vendor in perpetuity.

It's not elegant; but realistically we are far enough both into the history of computer science and the history of computers-as-hardware-you-can-buy that there's a lot less obvious, low-hanging, progress to be had by going 'modern' relative to the amount of fashion and fad chasing. Especially if (as is the case for a great many people and organizations) the scale of your problem has grown at or below the rate at which hardware advances have made systems not particularly well designed for scalability faster.

And also an inflationary currency is a very bad thing.

For one, it screws over debtholders (aka, most people), as the value of the debt owed grows instead of declining. If you work for a company making lumber, and a given board sells for $10 now, but 20 years from now sells for $5, and you sell the same number of boards per unit labour with the same relative margin, then all else being equal, your salary must be half in 20 years what it is today. But that mortgage that you took out today for $200k is still $200k (adjusted for interest and payment of principal). Which you have to pay on with a salary that is half what it is in dollars. That person is totally screwed.

Secondly, it discourages spending. The more you delay purchases, the more you'll be able to buy in the future. So everyone is encouraged to not spend. Which screws over your economy. It also screws over your tax base when taxation is based on taxing spending. Meaning you have to raise your spending-related taxes, which further discourages spending.

Third, it worsens wealth inequality. If you're living paycheck to paycheck, you have no savings. If you're a billionaire, you have a lot of savings. The billionaires see their assets grow and grow, and it comes at the cost of the working class. Also, said billionaires are encouraged to keep their money as cash rather than investment, which further ruins your economy.

This is no way to run an economy.

Another thing you REALLY don't want in an economy is instability. Aka, Bitcoin's fundamental nature, because it has no fundamentals and no attempt at monetary policy. Economies are fundamentally unstable. If you do not regulate them, they swing wildly. The faster an economy moves - and economies keep moving faster as technology advances, it no longer takes half a year for goods to arrive on a sailing ship or weeks to communicate with the other side of your country - the more unstable it is. This is terrible for both individuals and businesses.

What you want in an economiy is:

* Stability
* Low and steady inflation - a couple percent, to encourage spending, slowly devalue debts, and encourage investment. Too much is bad. Too little is bad.

Yet, silver is valuable as both a monetary metal and industrial metal.

Unlike bitcoin. You summed it up nicely right there.

Right now, I want to buy tin-silver alloy, to use in casting. But the prices of both tin and silver are insanely expensive right now. So I'm not buying now. If the prices go down? I'll buy. If they go down a lot? I'll buy a lot, perhaps even to sell on my sales website. And this buying is to *use* it. Which takes it off the market. There are fundamentals behind silver.

There are no fundamentals behind bitcoin.

401ks have fundamentals behind them (comprised of companies that make products and services that people want to buy, generally as repeat-buys)

Governments have fundamentals (the ability to levy taxes, backed by the full force of the courts, the police, and ultimately, the military)

Bitcoin has no fundamentals. It's a collectible. Its value is based purely how much people want that collectible. The only reason, as was stated, that people were buying it was as a lottery ticket. But there is no reason to "own" it beyond that. It's not generating dividends or doing stock buybacks based on profits. It's just there for those who want to collect it. And its value depends on how much people want to collect it.

(Arguably its greatest power is that its holders stand to lose so much if regulation goes against them that they tend to be very politically active, with large donations to pro-crypto candidates)

Eh... I think the "used for all kind of dangerous things" started with GPT-3. I used GPT-2 a good bit back in the day, and it couldn't pass as a person, let alone reason out as a cyberattack.

Since it wasn't instruction fine-tuned, you couldn't trust that GPT-2 would ever do what you wanted. The best you could do is "cute it" with leading text and hoping that it doesn't go off on a tangent. That said, you could kinda use it for things with decent reliability. For example, you could write a long paragraph, then write: "Or, to sum up everything above in one sentence" - and then (hopefully) get a one-sentence summary.

It could sort of try to write recipes ("Here is a recipe for [X]. INGREDIENTS:"), but far from usable (I remember that one contained vermiculite ;) ). You could write plays by starting out a play format, though the plotting was fairly incoherent. You could set it up to write a joke and it'd end up writing long anti-jokes where the punch-line never actually comes (in one, I set it up with "A nun, a priest, and a rabbi walk into a bar...", and it ended up with the bartender saying something antisemitic, everyone getting uncomfortable, and leaving, and priest turning to camera and talking about how antisemitism is bad). Etc.

It was this tantalizing glimpse of what was to come - not YET useful, but hinting at what could come if the models improved sufficiently. I don't think many people expected how quickly it would improve.

When GPT-3 came out (but not yet 3.5, aka ChatGPT), the writing quality was clearly dramatically improved. People were writing articles about GPT-3 using GPT-3, and only copyediting to piece the (small) chunks together. For me the big "Nothing Will Be The Same Again" moment was the "TheGentleMetre" scandal on Reddit, where it was discovered that someone had connected GPT-3 to their Reddit account... but it took like a month for them to get caught, and even then only because they were posting 24/7 at a regular pacing. And it was the fact that they weren't just writing arbitrary nonsense, but that there was logic to what they were writing. For example, one person asked something like "Would you rather have a psychopath or a Nazi as a roomate?" and it made a reasoned argument about how with a psychopath, there's something mentally broken with them, whereas with the Nazi, it's an ideology and there's still the possibility of changing that ideology. Back in that era, the notion that an AI model could do this was pretty staggering.

I mean, it is a pretty impressive model. And not just from the benchmarks. Relentlessly proactive and resourceful. It's a shame it's cut off.

Obviously this would require coordinated action, and some people likely have other reasons to want to either poke at or kill legacy applications; but(since all those java versions are solidly post openjdk) I'd be very curious to know how the cost and risk associated with "modernize because java 18 is going eol!" would compare to just...not...having java 18 go eol. Unsexy maintenance project that you'd need to pay to have done, sure; but very plausibly better characterized and lower risk than trying to deal with a lot of the oddball internal accretions that would otherwise need updating; and, depending on how much people have running on java 18, certainly possible that they'll individually spend a fair bit more running the treadmill than it would cost to just keep kicking java 18 down the road until (almost) nobody cares.

When I was a young college student I watched a professor working on some code in his office one day and saw how fast he was able to manipulate the text, cutting pasting, duplicating, all without hardly moving his hands. Ad hoc macros with the "." command were so powerful. I was very impressed and learned vi and never regretted it. vi definitely doesn't require touch typing! In fact I think it was designed for non-touch typers.

Now I have used vim for 30 years and am handicapped without it. I don't care if it's vim class, regular vim, neovim, or some IDE binding mode. I'm no vim expert and I really only use a small set of commands and keystrokes, but I appreciate the efficiency. The editor doesn't cause me to succeed or fail as a software engineer, but it does make my life more pleasant.

Reduction != None. Cities approve them because that even with any incentives offered they'll be raking in the cash, because the value of a datacentre is so high (even if you're in an area that only counts building + cooling + power interconnects + etc, but not the servers within, toward the property tax base)

You cannot simultaneously complain about consumer electricity prices and datacentres being bad neighbors due to having power plants on-site. Take your pick.

Datacentres buying power ALSO equals tax revenue, en masse, because electricity is taxed. And all of the jobs associated with providing that electricity.

A datacentre means a huge amount of income to the locality where it's at, plain and simple.

You know what property taxes are, right?

I mean, not surprising really. The military is less white than the general US population, and lower income than the US average.

I can also understand how the current administration's actions may be... less than popular.