joachimma

That's the opposite of the criticism that was levelled at him, during earlier launches, when he was preferring his own cameras even though they only caught fog.

I played X-Wing on my mother's work Thinkpad 486, I used the pointing stick that was located in the middle of the keyboard, It kind of worked like a mouse with infinite range. Never having to lift and reposition the mouse was great. I eventually wore out the red rubber on the pointing stick, but I kept playing until losing the skin on my finger made it to painful. I figured out that I could wear a rubber dishwashing glove, it became very sweaty by I kept playing, later I realised that I could cut the glove since I only needed to cover my finger.

At the final missions the game became very hard, but you could cheese it by doing a failed hyperspace jump, that would race past a lot of the enemy waves.

Does anyone know if Apple would actually agree to sign and allow the distribution of such a driver? The vendorid and productid clearly belong to another entity, which could hypothetically want to create their own driver?

I assume you're joking, Either way. One morning when I took the bus to work the bus driver had repeated problems getting the bus to start due to the breathalyser. I heard him complain to the passenger behind him, about it malfunctioning. The passenger volunteered to test this theory, by also blowing into the device. The driver handed him the hose, the passenger gave it a go, the bus started, and the driver shrugged his shoulders, and off we went, only slightly delayed.

I'm not sure if this is preventable.

Eye of the Beholder is about 1MB, for comparison Terminator 2 on cartridge from back in the day was 512kB.

But the cartridges themselves contains gigabytes as you say.

It seems perfectly plausible to me that the economic incentives are such that there is no need to "design" any of this, no smoke-filled back room needed.

I wonder why round-trip is such a small concern for people implementing serializers/deserializers of various kinds. I usually throw in an "Unknown" node type, which stores things unaltered until I can understand things again. The parsers I usually write are very small, so I haven't seen what issues comes up at scale, maybe there are dragons lurking .

For a while I thought you meant Hermes the luxury brand tossed your stuff in the bushes. Apparently there is a delivery company under the same name.

For me the issue to be solved is how to easily get the team to run the tool. Some focus should be on integrating build tools.

When I or a team member do gradle build, npm build or cargo build or similar on a fresh checkout the tool should ask to be installed.

No, in logic that is a vacuous truth. All my hats is true for zero hats. But that would not be a lie. And since the liar always lies, that can not be case.

Does anyone know why gitea is developed on GitHub?

I used to have lucid dreams regularly until I was 17, until I told a friend and never had a "real" one since. I am not sure if it is connected. I mostly used it to avoid nightmares as a child, unfortunately after a while, I got psychological nightmares instead. Waking up multiple times within a dream (There is no Limbo from Inception for me) with something really stressful having happened (dead body under the bed and police knocking on the door, it's just a dream there are no police, but the body is there, type stuff). I still have partially aware lucid-dreams occationally.

> These include statements before super(…), which would give developers greater freedom in expressing constructor behavior – meaning string templates. This would make it easy to express strings that include values computed at run time – meaning scoped values. This would enable sharing of immutable data within and across threads; and implicitly declared classes and instance main methods.

I don't like the restriction on code before super. But I don't have a clue what they are referring to here. The code example doesn't use a template either.

  PositiveBigInteger(long value) {
    if (value <= 0)
      new IllegalArgumentException("non-positive value");
    super(value);
  }