tech2

Jira and the Unassigned/Automatic selection when trying to change a story assignment, I'm looking at YOU in particular!

I don't think it ignores robots.txt, I think it just doesn't have a very good parser and you need to give them their own user-agent block. I had a similar level of frustration.

https://www.feitsui.com/en/article/32

I think that one of the issues with edge-connectors (beyond thickness and distance as mentioned in another comment) is capacitance, which is one reason why CAMM is structured the way it is.

I'm a big fan of the idea of CAMM in general. It's this, or we end up with locked-in amounts of RAM as per things like the M[1-3] Macbooks. The connectors won't be cheap, so I suspect uptake for laptops might not be so common, but this is a big help for desktops going forward.

It's a meme from the movie Demolition Man - https://www.youtube.com/watch?v=gdnuOa7tDco

Right, and because radio stations do that I'd wondered whether marketing choose to "make it sound like radio" so people don't complain when they buy the disc

> My 1996 Mustang's CD player has a "Compress" button on it, to make listening to highly dynamic music more feasible in a noisy car environment.

I believe _this_ is where the issue mostly originated (well, radio, really). Radio is already massively compressed, and many people were either listening to things in the car, on some tiny little radio in the kitchen, or with awful cheap headphones with their walkman's built-in radio.

All of these weren't great environments to start with, and the dynamic range of radio was tiny given the overall bandwidth available to most FM stations.

So, companies compress, people get used to it, and thus the horror continues.

One would hope they might instead consider the use of CAMM - https://en.wikipedia.org/wiki/Compression_Attached_Memory_Mo... - but I guess we'll see :(

REXX itself was a language made by IBM used for all manner of purposes, AREXX was a slightly simplified take on that for the Amiga. A number of programs on the Amiga would have an AREXX "port" which provided a set of APIs which could be called from AREXX to control aspects of the application. This meant that AREXX was often used to control multiple applications or chain them together (a bit like a batch control language used to achieve an objective by having each of the programs perform part of some greater whole).

Except that nothing is passed by reference (or everything is, depending on how you look at it). It's just that some objects have methods which can modify state (like list, dict) and others don't (like int, str). Ned Batchelder did a good presentation on this many years ago which is still probably the best I've seen for explaining how it works to people coming from other languages - https://nedbatchelder.com/text/names1/names1.html - where the names passed to a function act just like regular assignment.

And thus AREXX rises from the ashes of the corpse of Amiga.

  export PIP_REQUIRE_VIRTUALENV=1

has been quite helpful in the past as pip then refuses to just install things directly.

Or, since we have a word already, we could use that... Fortnightly. Biweekly needs to mean, specifically, twice a week.

Sather was something I was first exposed to at university in the mid 90s, and I still have a lot of respect for its looping mechanism. Code inclusion in classes rather than inheritance was also pretty cool. Pre/post conditions, invariants. I miss a lot of it.

I recently revisited it for Advent of Code (where part of the challenge was getting the compiler itself to even build with even semi-modern tooling), and a lot of the above features still have value.

CoPilot sticks its fingers in its ears, scrunches its eyes closed, and shouts "Not Listening!" repeatedly...

I'd wondered the same, but even with that question hanging I think the outcome of being able to electrolyse sea water directly was interesting.

Great news! Now a request for similar research against Type I/Insulin-Dependent Diabetes Mellitus.

"not increasing" is a permissible interpretation of monotonic though. The clock should never go backward, but not increasing for a brief period is acceptable. It does mean you can't use it for 100% high-precision work, but at least you'll not be surprised by a negative result.

And that comment reminded me of a New Zealand Sky TV advert that I haven't seen in decades, but still lives on as a meme between a number of friends. Thanks for that :)

https://www.youtube.com/watch?v=NyRWnUpdTbg

On the floor!

Python 3.11 introduced asyncio.TaskGroup[0] to cover the same use-case as trio nurseries (scoped await on context manager exit). It's imperfect, sure, but it improves matters.

[1] https://docs.python.org/3/library/asyncio-task.html#asyncio....

Can any of it be recycled/reused, or is it destined to be incinerated or chemically stripped?

I agree, to a point. My initial comment was related to the "100% recyclable" bit. The aluminium certainly is, the can itself isn't just aluminium though. This wasn't to say that cans aren't better, merely to draw attention to the fact that it's never as simple as we might like (and bisphenol-A, one of the common ingredients in the epoxy lining, is pretty awful stuff).

Aluminium may be, but interior of the can is coated in plastic (some quite unpleasant), and painted/coated/labelled externally too.

The reason people hated Steam at the time of CS 1.6 is because those people who owned CS on WON would need to repurchase CS on Steam. Since all new players were on Steam it meant that the existing playerbase were excluded (there was no WON/Steam cross-play).

I appreciate this is a 3-day-old comment now, but consider MISTer - https://github.com/MiSTer-devel/Main_MiSTer/wiki - which allow access to all of these older systems rather than being locked down to one of them. You could then also move through time, from an original Apple I, through Commodore 64, Amiga, etc. Also permitting your child to learn about FPGA, hardware, etc. at any point.

REM<SHIFT-L> - it's weird the things that stick in your head after all this time. Likewise SYS 64738, 64760, 64767 and a few others. One to really mess with people was: POKE 53280, 0 # set screen to black POKE 53281, 0 # set font/foreground black SYS 64767 # fast restart which doesn't unset colours. At that point unless they know what's happened they cant RUN-STOP/RESTORE to get out of anything.

I do miss the 64 (and the Amiga which followed). The variety of machines back then was really refreshing compared to now.

That would be a monopsony, making NASA a monopsonist.

I've occasionally toyed with the thought that political duty should be managed in a similar manner as jury duty.

(One of) The problems with political representatives is that they _want_ to be politicians. Either as a means to an end, or as a mechanism to better serve themselves or others like them. On more rare occasions you find the occasional altruist.

Since there's a selection bias going on, how can the current crop act as representatives of their populace when they aren't _like_ those they claim to represent?

That's history coming back to bite it though. There was a period where the symbols True and False existed in Python but the bool class did not. True was _literally_ 1, and False was 0. Because of this, for backward compat, bool is a subclass of int.

TCP/IP might be a reasonable example. There's a reason "network byte order" and "big endian" are the same thing.

The Sony Xperia Z5 Compact was my previous phone that I'd had from 2015 until mid last year. It was close to perfect. Waterproof, headphone socket, SD slot. If a new version of that were released with less of a screen border than the original I'd buy it in a heartbeat.

Thickness could stay the same too, I'd like the additional runtime rather than everything needing to be wafer-thin.