carwyn

Double Reed instruments have also been shown to have a positive effect for those suffering from sleep apnoea. It seems due to the higher air pressure needed to play: https://en.wikipedia.org/wiki/Double_reed

Presumably quadruple reed instruments (that require even more air pressure to play) would be even better: https://en.wikipedia.org/wiki/Quadruple_reed

How does this compare to https://gitlab.gnome.org/GNOME/vte/ ?

And the author's prompt response.

Second generation moved away from gVisor:

https://cloud.google.com/blog/products/serverless/cloud-run-...

You can use the real compose (Go) with Podman now. The Python clone is not your only option.

Sometimes it crashes just running regular apt-get upgrade if it has too many packages to update, or takes too long. Switching away from the app can also mean it crashes.

Nice idea, nowhere near ready for anything but playing.

The sub-issues are good, with more relationship types coming (dependencies, not just parent-child). The better search is welcome. However there are some questions for me in relation to the overall semantics of labels, issue types and project fields.

Labels are repo only and multi valued. Issue types are organisation wide and single valued, project fields are the richest, but no multi-valued option, and they end up in a disjointed place in the API (you can't get at them easily when what you have is the issue, you have to go in via the project).

An example of this disjointed feeling it that there are no "issue type"s for a PR. This means that if you want to share metadata between PR and Issues, you have to use labels anyway.

I do wonder if types could have been better implemented as namespaces for labels. This combined with being able to have organisation or repo context label namespaces would have allowed for far more flexibility.

The other thing that vanished from the public roadmap amongst all this was support for better workflows. Currently there's no easy way to create allowed state transitions between metadata state (e.g in a project stop issues being able to skip the QA status).

The attention this area is getting is welcome, and there are many good things in there, but it does feel a bit disjointed. A more unified metadata model would be welcome.

They are in some countries. The sugar tax in the UK quickly led to many places only selling non sugar variants or charging a premium for the sugared versions.

They still have big issues with keeping on top of firmware updates. They still haven't managed to ship a stable EFI update for the 12th Gen for example. This is even after main stream tech press getting on their case.

Agreed, I'm seeing people of all ages not having to interact with the desktop metaphor at all any more. Typically people that manage to do all their "computing" on Android, iOS or sometimes ChromeOS (where they are email and SaaS based).

The metaphor is more of containers/projects and save slots/objects. Far more like video games than the traditional model.

Most of the Gerry Anderson shows are available to stream on ITVX in the UK. The Re-imaginings of Thunderbirds and Captain Scarlett in 3D are there too.

Fireball XL-5, Supercar, Joe 90, Space Precinct (sub needed), UFO, Terrahawks, Space:1999, The Secret Service, Stingray, Gerry Anderson's New Captain Scarlet (3D), Captain Scarlet, Thunderbirds the Anniversary Episodes, Thunderbirds Are Go (3D), Thunderbirds.

See "Adopters" section of the GitHub README:

https://github.com/lima-vm/lima?tab=readme-ov-file#adopters

It goes further than that. If you file a bug on Red Hat's bugzilla with or without a support contract, you will quite often get a response if you put the effort into producing a detailed report. No guarantee, sometimes just others with the same issue, but still pretty good. You will also find Red Hat employees on the mailing lists for the OSS projects they contribute or depend on who actively participate in conversations there.

If you have a support contract though and open a case, the level and quality of support is usually very high.

The best part of early WoW for me was working through the PvE quests with a few friends and especially taking on the 5 person dungeon instances while leveling up to 60. The combination of needing to form a group of mixed tanking, healing, DPS and crowd control to take on the dungeons was amazing.

Are there any games out there since that capture this as well? Most I've seen since don't seem to capture the need to work with others nearly as well, usually as all classes can do too much.

Very similar to GitHub Flow is trunk based development:

https://trunkbaseddevelopment.com/

Slightly more here: https://secure.phabricator.com/w/changelog/2021.22/

Shame, the code review was good and one of the few that supported task dependencies :(

It means the developers are dogfooding their WASM support as Godot runs on top of its own engine.

Also excellent for ease of adoption with beginners due to zero install overhead.

How does this compare to https://www.snowpack.dev/ ?

Skynet is coming ...

There's an article over at TheRegister related to the FootFallCam saga:

https://www.theregister.com/2021/02/12/footfallcam_twitter_k...

The initial blog post with more of the technical detail is here:

https://cybergibbons.com/security-2/serious-issues-in-nurser...

This pattern or close variants or subsets are fairly common:

https://github.com/golang-standards/project-layout

There's a possibility that this isn't the big deal people think it could be. It all depends on the day to day stability of Stream. Red Hat distros already have a testing repository channel for example. If stream updates are QAed through something like this the resulting platform may well be stable enough for many use cases. It would be no different to enabling the 7x/8x repo in the current releases.

In many respects I'd rather have a slow trickle of updates than the current flood of each point release. We've had lots of experience of dealing with all those changes landing at the same time breaking things.

Like many my first reaction was shock, but at the same time not surprised. Have even emailed the address provided with feedback as I work for a University which like many use a mix of RHEL and CentOS.

As per the FAQ though I suspect there is more to this than meets the eye. Two things strike me: 1. The suggestion that low or no cost options for RHEL are coming for certain categories of user. 2. As much as Stream will be a rolling and "beta" channel, Fedora/CentOS/RHEL already have testing repos within their release process so Stream may not be as unstable as this might first suggest.

With local staged repository mirrors Steam may end up being less volatile than the existing point releases which were notorious for breaking things at times.

Almost, I'd say it's more like:

Rawhide <=> Sid

Fedora <=> Semi-stable-ish but short-lived and moves fast.

CentOS Stream <=> Bullseye but possibly less stable than Fedora in parts.

RHEL <=> Buster

Regular updates on the bug/task tracking systems together with notification and Q&A on a more stream based async system like Slack work well for us. Lack of activity is usually a sign of an issue, usually someone being stuck, a bit down or on a roll. All need a check-in, even the on-a-roll person as sometimes they get carried away without letting people know about changes. We tend to have weekly in-person synchronisations meetings.

This does really vary hugely from team to team and even project to project though. I fear "agile" methods have forgotten the meaning of the word they are based on at times. Regular re-factoring also applies to development and operational models I find.