How’s their delivery schedule? Here in Norway we might be cutting 2-3k jobs in our mail and dropping mail delivery to one day a week (currently it’s every other weekday (yes, that means 3 or 2 days a week alternating)).

That’s getting some … reactions, but honestly I suspect the average Norwegian, receiving one letter in the mail a week, is pretty fine with it.

Also, who wants inefficient cars with oil prices where they are?

Oil execs, aka Trump’s friends. US people have been complaining about how hard it is to find a car they actually want for ages. Their dealership model seems to be geared for extracting money from them, and worse mileage at higher prices would be just more of the same.

First question is clear case of https://en.wikipedia.org/wiki/Betteridge's_law_of_headlines

Yeah, I think a lot of us frequently hear from suburbanites about how urban living is all “in a pod”, but then … they really should check their mirrors. Throwing stones from glass- and metal boxes, and all that.

People absolutely stop by coffee shops to get something to go in an urban context too. But the queueing that happens inside one of them, maybe even spilling out of the premises, still requires very little area and is pretty benign in an urban context. Especially if you wind up having a little chat with someone.

Something similar to the tiling model also dominates on small screens, like phones.

And while I’ve used tiling WMs on Linux for well over a decade (probably nearing two), it does seem that plenty of people will prefer the familiar over trying something new, c.f. Win8’s reception (I’ve never used it myself)

I’ll admit I have no idea what makes one of the Rust implementations preferable over the other. Nor can I go looking at the code myself now that GitHub has hosed itself again

There’s also https://github.com/tealdeer-rs/tealdeer

You might want to have a glance at the OpenSSF compiler hardening guide, and maybe try out ASAN (-fsanitize=address).

E.g. I get

[nobody@bb14e99a9c8e cldr]$ ./build/cldr --update --language C.
caution: filename not matched:  ethical-tldr/pages.C./*/*.md

=================================================================
==454==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 4 byte(s) in 1 object(s) allocated from:
    #0 0x7fa48a32c0c1 in malloc (/usr/lib/libasan.so.8+0x12c0c1) (BuildId: b8a4241051a1621937fdc46e867ba7ecb56d96ea)
    #1 0x7fa489e8be0f  (/usr/lib/libc.so.6+0x8be0f) (BuildId: 503200d7fda94a5dc6058d7e0694e5d1dcb2e372)
    #2 0x7fa48a2f2761 in vasprintf (/usr/lib/libasan.so.8+0xf2761) (BuildId: b8a4241051a1621937fdc46e867ba7ecb56d96ea)
    #3 0x561d84213d8c in strfmt (/home/nobody/cldr/build/cldr+0x6d8c) (BuildId: 2a0f13efc2c9b12a67e7dd810a2cbdfd1866e53d)

SUMMARY: AddressSanitizer: 4 byte(s) leaked in 1 allocation(s).

Yes, complete decarbonisation of industry is a longer canvas to bleach, but there’s also a significant difference between the market decarbonising completely, and renewables and heat pumps (and induction, I guess) doing enough to drop off demand. Drilling for oil & gas in the sea hasn’t been the cheapest source, and Norwegians will talk about the oil crisis of 2014-2016, where the problem was that it got so cheap that production here was halted.

Drive down demand for fossil fuels, and Norwegian exploitation of the arctic fossil fuels will likely just be priced out.

So-called oil fields also extract a lot of gas, and that is used for electricity generation.

Traditionally we call it the oil and gas sector in Norway, but these days it might be more accurate to call it the gas and oil sector.

Somewhat reminded of @jonah@neat.computer’s general recommendation against GPG (for other reasons than what this talk is about)

That is Labour’s position, and if left unchecked, they will form majorities with the Conservatives and the right-wing populists to go through with that.

The article I linked is from today and about the smaller greener parties’ opposition to drilling in LoVeSe and how they plan to use budget negotiations to get the government to commit to no drilling there. Currently only Labour is in government, as they failed to get more parties into government, instead relying on year-to-year budget negotiations with, uh, the Far Left, the Socialists, the Greens and the Agrarians (who are fairly populist and anti-climate-policies, no matter how much climate change wrecks their voters). The budget isn’t just moving NOK around, it also contains a whole lot of verbal agreements about what the government should do.

So while there’s no majority for a general bill banning arctic oil exploration, the other parties can still negotiate for the government to leave it be, at the cost of some other stuff they’d like to get into the budget, as Labour still doesn’t want to have to resort to a line-by-line treatment of the budget in parliament.

In Labour’s case it’s also a case of the main labour union umbrella organisation being very heavily influenced by the unions working in the oil sector. There are some other unions who are opposed to arctic drilling, and who would like to get the transition started before our customers start going away and we’re left with a very heavy case of Dutch disease. They’ve butted heads in the past, but I haven’t noticed any bickering recently, and the main union umbrella org itself just narrowly avoided having an oil guy becoming its leader (because he’d been sleeping with subordinates in the labour unions and Labour, not because of his policies).

Might also add that the way Norwegian oil taxes work, there’s very little taxes on anything oil-related until they start turning a profit, at which point the taxes kick in, feeding the oil fund. So there’s not all that much incentive for the oil sector to avoid possibly unprofitable ventures, as those turn into huge tax writeoffs.

Personally, seeing EV uptake accelerate this year, and the general exponential rollout of renewables, and developments in batteries, I suspect that by the time any arctic oil might find its way to the market, the market is going to be a lot less oil-and-gas-hungry, hopefully even to the point where pumping oil in the arctic isn’t actually a profitable venture.

No, it also matters for some admittedly unfortunate street layouts. E.g. here in Oslo we’ve had some one-way streets with parking on both sides, where we’ve had to remove parking on one side to allow buses and emergency services continued access in the age of SUVs.

Anything that has some sort of geometric constraint gets worse with big cars, and having an extra disincentive on huge cars is good.

edit: Car size creep will also eventually find its way into parking requirements, and parking norms, terrible as they are, require a certain amount of parking spots, not area dedicated to parking, which will make construction even more expensive.

Yeah, decent assumption, I’ll tone down my comment a bit.

Default/optional arguments: can be confusing when the default value is initialized.

Yeah, which especially becomes an issue in languages with poor mutability controls. Probably the most benign variant of argument defaults would be restricting them to being const, or at the very least immutable including internal mutability. Instead we have situations like in Python where it’s necessary for linters to warn people that setting [] or some other mutable data structure as a default is a bad idea (e.g. B006).

There’s also the issue that API designers may not want their parameter names to be part of the API

Yeah, this is also something of a mixed bag, where

• there are some cases where having the parameter name as part of the API is desirable,
  • e.g. if some parameter position both before and after a change is a T, but it’s used for different purposes,
  • though it is unclear whether that can’t always be better covered by using the type system better;
• while in most cases being locked out of doing some trivial renaming for whatever purpose (like s/blacklist/blocklist/) because it would break clients is just a PITA.

I wrote in another comment that I was partial to named arguments out of habit, but the more I think on it, I wonder if it’s not mostly a tool to work around missing type information and bad APIs, which, uh, may not be the most desirable thing to add to Rust.

Yeah, though in those cases you might get an extra question about why rect is a function and not a method, e.g.

Rect {
     w: 30,
     h: 20,
     .. RectArgs::default()
}.do_the_thing()

There’s also resistance in the Norwegian parliament for at least some of the blocks, most notably Lofoten, Vesterålen and Senja (LoVeSe). The way Norwegian politics works, Labour and the Conservatives are fine with making some decisions together, but don’t actually want to form a government together, and depend on smaller, greener parties for that, which have successfully blocked oil exploration in LoVeSe for a long time and intend to continue doing so.

It’s also kinda frustrating to deal with people who believe this decision can have any sort of short-term impact on prices at the pump. If Labour and the Conservatives get their way and there’s extraction of oil in the arctic in the future, actual oil deliveries will only start so far into the future that no matter what happens in Hormuz and russia, it’s the new normal. We’re talking over a decade.

When I do ls --help|less --raw-control-chars it doesn’t show the control characters, and it looks all neat and pretty. Isn’t this the opposite of how it’s supposed to work?!

You’ve gotten a longer reply to this, but just to make it clear: No, that’s how it’s supposed to work.

• By default less mangles control characters so they can’t do anything to your display (or bell)
• With -R, less will pass some control characters through raw and unmangled; enough to give you stuff like pretty colours
• With -r, less won’t mangle any control characters, which, if you’re doing something stupid like trying to read a binary file, can leave your terminal prompt fucked up and in need of a reset.

You may want to tag your triple-backtick with something like text or plain so you don’t get auto-inferred syntax highlighting. E.g:

 All commands now markup option names in --help and man pages,