kazinator

Suppose we require it that the output flush must take place before the behavior becomes undefined by a bad division. That doesn't buy much because the visible effect is only that some bytes are passed from the stdout stream to the host environment. The undefined behavior is allowed to bring down that entire environment though; so our requirements don't add up to the certainty that the output has been transmitted out of that host system to some output device (display, serial or network, ...), or committed to durable storage. (The latter could be wiped out by the UB, even if so).

Basically, standardization groups should be dissolved long before they devolve into stuff like this, where they are just creating churn for the sake of their own continuation.

My point is not to shill for a Google thing, but more that the ability to hookup the plumbing around an LLM to give answers tied to a document is something that has already long been done; it doesn't depend on "Jev".

But in terms of usability, if you can fog a mirror and move the needles on an EEG, you can probably upload documents to LMNotebook and punch in a question.

22 of these are "red" states: Alabama, Alaska, Arkansas, Florida, Idaho, Indiana, Iowa, Kansas, Kentucky, Louisiana, Mississippi, Montana, Nebraska, North + South Carolina, North + South Dakota, Ohio, Tennessee, Texas, Utah, West Virginia and Wyoming.

6 more are blue-leaning "purple": Arizona, Colorado, Georgia, Nevada, New Mexico and Wisconsin.

Only four are "blue": California (ban coming into effect 2027 as per article), Hawaii, Illinois, Maryland.

I don't understand why the ban cannot come into effect immediately. Like, wouldn't want to spoil someone's child marriage plans in the next year or so because it would be rude?

The potential for undefined behavior means ... the potential for a situation to emerge where no further requirements apply.

If you regard undefined behavior as having ordering requirements, it's game over for optimization (not to mention the current understanding of undefined behavior). Any time you have bona fide observable effects near calculation, you are hamstrung, because the potential for UB is in every nook and cranny, around every corner.

I think it's perfectly fine for the division by zero to occur before the output is produced and flushed, in that example. The UB of a bad division can time travel because a division is assumed not to have UB and can be reordered before a visible effect to which it is not related (the effect doesn't require the result of the division, nor does the division require an output tied to the production of the visible effect).

What these people are looking for is a safe calculation mode in which a bad division does something that is well-defined, like raise an exception that can be caught. That is then deemed visible, and must not be reordered w.r.t. other visible effects. And while it does hamper optimization, it is a translation mode that can be enabled or disabled around a block of code. If the programmer is certain there is no bad division, or else don't care about that being ordered w.r.t. a visible effect, then they declare a low safety level. (Which, this still being C, could be the default level).

As long as C standardization thinking remains obtuse or hostile w.r.t. this type of programmer-controlled safety level concept, they will be forever confounded by dilemmas caused by wanting intuitive outcomes that logically require undefined behavior to be partially defined.

To web-search (two syllables)

To google (two syllables, only slightly glibber, due to no "b-s" plosive-fricative combo).

Maybe "web search" can be shortened to "bsearch" or "besearch", like "web log" got shortened to "blog".

"besearch" has grammatical precedence: bestow, bequeath, behead, bewitch, belabor, befriend, ...

I just web-search. Let me web-search that for you. According to a web search, it's fine.

To web-search works perfectly well. "I web-searched it". This is what I use.

Where organically sometimes means "in service of monopolists".

You can do that with Google's NotebookLM. Upload docs, ask questions where the answers are strictly referenced to the docs. I used it for "where does it say that" and other types of questions about ISO technical standards, traffic codes and other documents.

but "previous observable behavior" just means whatever actually happened, not that it was required to be previous.

x being a register connected to the processor's division machinery doesn't speak to the fact that division isn't a language-defined visible effect, and so the implementation is not required to schedule it in a certain way in relation to the store to x.

> The question here is: can the compiler hoist the final division operation above assignment to x?

A division calculation not a visible effect. Therefore the question doesn't even m ake sense: it's asking: can we see something that is not a visible effect (division) before or after a visible effect (modification of a volatile object).

Actually, I should mention that I didn't know about their corporate change from a co-op with members. My first contact with the change was my account being erased and being told to create a new one because they are "changing over to a new system". No mention of having become a different, scummy company. Basically they started out by lying to long-time customers of the old MEC that it was just their database that was changing and for some inexplicable reason, not being able to migrate the old membership accounts. Just despicable.

That is conscious; the page references oracle bone script / seals as being close to their concept, and kamon as being even closer.

I don't think you can drop the word "mon" into a conversation and be readily understood without additional explanation; what you want is "monshō" (紋章) to talk about heralds in general.

I had an automatic Micra (2016). It was a gas guzzler in the city, striking at 10l/100km at times. When shopping for a car to replace it, I did check out the 5 speed manual version. That stupidly asks you to rev 3000 RPM in 5th gear at 100 km/h. There is a 6th gear missing there, or a taller fifth: oops, fail! And they thought that someone who wants a manual car won't be needing air conditioning or power windows, etc. the idiotic, outdated thinking that the manual transmission is just an ingredient in making the cheapest possible version of the car, and not somehing that is a special feature to the enthusiast. Double fail ...

The number one goal for AI labs is obviously their self-preservation, by any means.

NeoVim is a forked continuation of Vim.

Blaming Vim is like politicians blaming the previous administration.

Nobody should have to read release notes to avoid data loss; there should never be a change such that someone who hasn't read the release notes (or missed a detail in reading them) to avoid such a problem.

That doesn't work here because the data was not wiped by a generic cache flush from a third party script or whatever, but a targeted hit from the application itself on files known to be persistent undo.

You just can't point the finger at file system standards, or shoulda-read-release notes or whatever.

There is no such thing as "by mistake, we historically stored persistent files in a directory with 'cache' in its name, contrary to a popular standard, so that makes it okay to trash them now".

I had a membership since 1994. They basically erased it.

Between that, and selling out to a foreign-private-equity-held holding, and the incident during which an innocent shopper who came to return an item was attacked by a security guard, and the idiotic Vancouver location with no connection between underground parking and the store room, I decided never to set foot there again.

Fuck MEC, the Mountain Equipment Coo^H^Hompany! Not the MEC you knew.

It didn't. The battery killed itself. Modern rechargeable batteries don't like being left discharged in storage.

In what way is it not a process restart if I stop the process, install/upgrade NeoVim and start a new process?

Why don't the idjits just offer two levels of "Eco"?

Maybe people like the regular Eco mode for reasons other than economy; like they use it as a kind of one-pedal driving, since it offers regenerative braking when you back off the accelerator.

There needs to be a mode for those drivers, and a mode for those who are serious about maximizing battery run times.

Fighting and backlashing over mere software configurations of one thing is so senseless.

"Sporty" isn't what is interesting for me. Any kind of driving is nicer in a manual; including obeying all speed limits, giving right of way, stopping for pedestrians, etc.

I try to make it so that you can't feel that I'm changing gears, and that's next to impossible under "sporty" driving, where you can't hide the difference between hard acceleration and no acceleration during the rev hangs.

6 speeds gearboxes that have about the range of 5 speeds are great for smooth gear changes because the gear ratios are closer, and so if you accelerate gently and shift at low RPMs, the rev hangs are very quick. You can also gently pause and resume accelerations and shift during the pauses. The last shift at cruising speed is free of acceleration also.

I also use cruise control whenever possible. That's all the self-driving I need, thank you very much. Previous manual cars I've driven didn't have it! Manual + cruise = super!

They are boring to drive. Using an electric car has the all the fun of running a load of dishes through the dishwasher.

I have to drive quite a bit because kids. If I like the driving, it's less of a chore.

With a manual car, I never grumble when I have to drive, even if it takes me away from something fun.

I was without a car for half a year 2026-02 to 2026-08 and drove a number of electrics from the local car share (where I've had a membership since around 2011). Hyudai Kona, Kia Niro, Chevy Bolt, ...

I had a good camping experience with the Niro. Since Kia doesn't believe in spare tires being default, I was able to stuff sleeping bags, beds and a bunch of other stuff all underneath the hatchback floor, in all that secret space, leaving a ton of room above for everything else.

I like the acceleration and quiet/clean operation of electrics, but in the end I got a 6 speed manual.

Electrics are super dangerous; they accelerate like souped-up competitive track cars. They really need to tone that down: use much smaller motors with less torque, and hack the software to cap the acceleration.

I'm a much calmer driver in a manual. I'm driving for fuel economy, so I'm always in a gear where I have no power. (And in a 6 speed that has about the range of a 5 speed, there is always a good gear to be in at city speeds, where you are at between 1500-1800 RPM). So, I cannot just step on the accelerator on a whim because that will usually do nothing. There is an activation energy for speeding up, due to the chore of shifting down, which discourages doing it casually. In an electric it's like, oh, I suddenly see this opportunity, and blam: you're on the accelerator and the distance between here and there is erased faster than you can hit backspace.

Kia Niro is where the Koreans have invested their stuipd; a stateful panel in which volume and temperature knobs are multiplexed, and and so are tactile-free touch places on the panel between them. And it won't stay in the same mode; it changes it behind your back. You think the knob is volume because you last tweaked it a minute ago, but nope, you are messing with the temperature now.

Nope! Parallel programming is all yahoo, wee, look at that go!

Then comes the parallel debugging.

Pretty soon it's 15 years later, different person, yahoo-wee bro having long moved on.

"'grep -r' discovers .letter.fZ9cx~ file from 2012 that I never sent, all by itself. Honest!"