JavaScript is actually a pretty interesting, powerful language, but one with quite a few problems. (I recommend the book JavaScript: The Good Parts by Douglas Crockford if you want to learn more about that.) TypeScript solves some, but by no means all, of those problems. From what I've heard, it's increasingly popular.

ED: "But it doesn't work for gravity with linear curvature"

Relativity = gravity is represented by the curvature of spacetime. Curvature is linear, R. The formula treats curvature linearly. As things get closer and curvature spikes, the math just scales at a 1:1 rate

Quadratic gravity = Squares the curvature. Doesn't really change things much when everything is far apart, but heavily changes things when everything is close together.

Pros: prevents infinities and other problems when trying to reconcile quantum theory with relativity ("makes the theory renormalizable"). E.g. you don't want to calculate "if I add up the probabilities of all of these possible routes to some specific event, what are the odds that it happens?" -> "Infinity percent odds". That's... a problem. Renormalization is a trick for electromagnetism that prevents this by letting the infinities cancel out. But it doesn't work with linear curvature - gravitons carry energy, which creates gravity, which carries more energy... it explodes, and renormalization attempts just create new infinities. But it does work with quadratic curvature - it weakens high-energy interactions and allows for convergence.

Cons: Creates "ghosts" (particles with negative energies or negative probabilities, which create their own problems). There's various proposed solutions, but none that's really a "eureka!" moment. Generally along the lines of "they exist but are purely virtual and don't interact", "they exist but they're so massive that they decay before they can interact with the universe", "they don't exist, we're just using the math out of bounds and need a different representation of the same", "If we don't stop at R^2 but also add in R^3, R^4, ... on to infinity, then they go away". Etc.

The theory isn't new, BTW. The idea is from 1918 (just a few years after Einstein's theory of General Relativity was published), and the work that led to the "Pros" above is from 1977.

In short, Java was invented for a reason, and while it has become a victim of legacy cruft as well, the underlying concept of truly portable apps, with a minimum of fuss to jump from platform to platform, still ought to be the preferable path. The problem is that that true platform neutrality/ambiguity pretty much kills Microsoft in all but a few niches, like gaming, but only because hardware vendors put less effort into drivers for other operating systems.

Yes, Office is still king, although I think that crown is beginning to slip, and it may end up being Excel, with its large list of features, that may last the longest. But it isn't 1990, or even 2000 anymore. Developers have multiple ways of developing portable applications, and while MS may (for the nth time) update or swap out its toolchains, the real question is will developers really care?

A bit more about the latter. Beyond organophosphates, the main other alternative is pyrethroids. These are highly toxic to aquatic life, and they're contact poisons to pollinators just landing on the surface (some anti-insect clothing is soaked in pyrethrin for its effect). Also, neonicotinoids are often applied as seed coatings (which are taken up and spread through the plant), which primarily just affect the plant itself. Alternatives are commonly foliar sprays. This means drift to non-target impacts as well, such as in your shelterbelts, private gardens, neighbors' homes, etc. You also have to use far higher total pesticide quantities with foliar sprays instead of systematics, which not only drift, but also wash off, etc. Neonicotinoids can impact floral visitors, with adverse sublethal impacts but e.g. large pyrethroid sprayings can cause massive immediate fatal knockdown events of whole populations of pollinators.

Regrettable substitution is a real thing. We need to factor it in better. And that applies to nanoplastics as well.

So, when we say microplastics, we really mainly mean nanoplastics - the stuff made from, say, drinking hot liquids from low-melting-point plastic containers. And yeah, they very much look like a problem. The strongest evidence is for cardiovascular disease. The 2024 NEJM study for example found that for patients with above-threshold levels of nanoplastics in cartoid artery plaque were 4,5x more likely to suffer from a heart attack. Neurologically, they cross the brain-blood barrier (and quite quickly). A 2023 study found that they cause alpha-synuclein to misfold and clump together, a halmark of Parkinsons and various kinds of dementia. broadly, they're associated with oxidative stress, neuroinflammation, protein aggregation, and neurotransmitter alterations. Oxidative stress is due to cells struggling to break down nanoplastics in them. They're also associated with immunotoxicity, inflammatory bowel disease, and reproductive dysfunction, including elevating inflammatory markers, impairing sperm quality, and modulating the tumor microenvironment. With respect to reproduction, they're also associated with epigenetic dysregulation, which can lead to heritable changes.

And here's one of the things that get me - and let me briefly switch to a different topic before looping back. All over, there's a rush to ban polycarbonate due to concerns over a degradation product (bisphenol-A), because it's (very weakly) estrogenic. But typical effective estrogenic activity from typical levels of bisphenol-A are orders of magnitude lower than that of phytoestrogens in food and supplements; bisphenol-A is just too rare to exert much impact. Phytoestrogens have way better PR than bisphenol-A, and people spend money buying products specifically to consume more of them. Some arguments against bisphenol-A focus on what type of estrogenic activity it can promote (more proliferative activity), but that falls apart given that different phytoestrogens span the whole gamut of types of activation. Earlier research arguing for an association with estrogen-linked cancer seems to have fallen apart in more recent studies. It does seem associated with PCOS, but it's hard to describe it as a causal association, because PCOS is associated with all sorts of things, including diet (which could change the exposure rate vs. non-PCOS populations) and significant hormonal changes (which could change the clearance rate of bisphenol-A vs. non-PCOS populations). In short, bisphenol-A from polycarbonate is not without concern, but the concern level seems like it should be much lower than with nanoplastics.

Why bring this up? Because polycarbonate is a low-nanoplastic-emitting material. It is a quite resilient, heat tolerant plastic, and thus - being much further from its glass transition temperature - is not particularly prone to shedding nanoplastics. By contrast, its replacements - polyethylene, polypropylene, polyethylene terephthate, etc - are highly associated with nanoplastic release, particularly with hot liquids. So by banning polycarbonate, we increase our exposure to nanoplastics, which are much better associated with actual harms. And unlike bisphenol-A, which is rapidly eliminated from the body, nanoplastics persist. You can't get rid of them. If some big harm is discovered with bisphenol-A that suddenly makes the risk picture seem much bigger than with nanoplastics, we can then just stop using it, and any further harm is gone. But we can't do that with nanoplastics.

People seriously need to think more about substitution risks when banning products. The EU in particular is bad about not considering it. Like, banning neonicotinoids and causing their replacement by organophosphates, etc isn't exactly some giant win. Whether it's a benefit to pollinators at all is very much up in the air, while it's almost certain that the substitution is more harmful for mammals such as ourselves (neonicotinoids have very low mammalian toxicity, unlike e.g. organophosphates, which are closely related to nerve agents).

This is so true, so true.

And it's not even US specific. In the wake of the Ukraine war, German parliament voted to give itself 100 billion of additional taxpayer money (i.e. debt) to spend on defense. Recently a report came out of all the money spent so far, 90% did not go towards the intended purpose.

Why any of the jokers in charge of our governments are still not in jail baffles me more and more every year. Oh yes, it's because they make the rules, sorry, my bad.

That's what campaign donations get you, if they are large enough.

This is why congress occasionally bullies the big tech companies. We all think they might want to have some regulation or to punish them. Oh sweetie... they're saying "nice company you have there... would be a shame if something happened to it..."

The best time to leave github was when the evil empire bought it. The second best time is now.

Seriously. Anyone who thought MS wouldn't fuck it up in the same way they fuck up everything they touch can't be helped. It's Microsoft for crying out loud.

A year? I've regularly written that much in a month, and sometimes in a week. And, counter-intuitively, its during those sprints when I'm pumping out thousands of lines per day that I write the code that turns out to be the highest quality, requiring the fewest number of bugfixes later. I think it's because that very high productivity level can only happen when you're really in the zone, with the whole system held in your head. And when you have that full context, you make fewer mistakes, because mistakes mostly derive from not understanding the other pieces your code is interacting with.

Of course, that kind of focus is exhausting, and you can't do it long term.

By focusing on the structure, not the details. The LLM and the compiler and the formatter will get the low-level details right. Your job is to make sure the structure is correct and maintainable, and that the test suites cover all the bases, and then to scan the code for anomalies that make your antennas twitch, then dig into those and start asking questions -- not of product managers and developers, usually, but of the LLM!

But, yeah, it is challenging -- and also strangely addictive. I haven't worked more than 8 hours per day for years, but I find myself working 10+ hours per day on a regular basis, and then pulling out the laptop in bed at 11 PM to check on the last thing I told the AI to do, mostly because it's exhilarating to be able to get so much done, at such high quality, so quickly.

This is an interesting observation, but not entirely false. There are edits on Wikipedia that basically amount to "wiki link every word in the article". IMHO this could well be in violation of potential laws against algorithms. I'm not sure if Wikipedia should get a pass because it is "free" or whatever.

Why would they build a machine which just does what humans do in the field instead of building a stationary machine in a factory which builds 20' long sections which fit on a Semi trailer( 2 sections end to end and 2 sections side by side ) and then just have a standard crane on wheels run the sections out onto pre-installed posts? They are talking about "utility scale" installations so the ground has been leveled and prepped so it's not like the custom layouts needed for root-top distributed solar installations.

It seems short sighted when companies build robots which just mimic what humans do with our limited 2 short arms and 5 digit hands.

LoB

That's a valid point, though right now while they're facing competition from startups the dealerships do provide them with a moat that they want to preserve. If/when the startup threat is gone, the automakers will go back to hating the dealerships.

I think people forget how everyone laughed at Tesla because everyone knew that starting a new car company in the United States was impossible. Now we also have Lucid and Rivian. Maybe someday Aptera will manage to get off the ground. This is a novel situation for American carmakers.

They had to say it that way, because the more accurate statement is that the dealership law unfairly advantages existing automakers. It's not about the dealerships being good or bad, it's about the fact that setting up a dealership network takes a lot of time and money and requiring it is a good way to keep new competition out.

The correct term is "regulatory capture". Private businesses use the power of the state to protect, subsidize or otherwise benefit them and harm competitors and potential competitors. It's extremely common and the more pervasive the regulation is, the more common it is. Red tape and government procedures benefit entrenched players who have built the institutional structures and knowledge to deal with them.

This isn't to say that all regulation is bad... but a lot of it is. There was never any consumer benefit to banning direct sales. All regulations should be thoroughly scrutinized for their effects on the market, direct and indirect.