GitLab just doesn’t compare in my view:

To begin with, you have three different major versions to work with:

• Self-Hosted open source
• SAAS open source
• Enterprise SAAS

Each of which have different features available and limitations, but all sharing the same documentation- A recipe for confusion if ever I saw one. Some of what’s documented only applies to you the enterprise SAAS as used by GitLab themselves and not available to customers.

Whilst theoretically, it should be possible to have a gitlab pipeline equivalent to GitHub actions, invariably these seem to metastasize In production to use includes making them tens or hundreds of thousands of lines long. Yes, I’m speaking from production experience across multiple organisations. Things that you would think were obvious and straightforward, especially coming from GitHub actions, seen difficult or impossible, example:

I wanted to set up a GitHub action for a little Golang app: on push to any branch run tests and make a release build available, retaining artefacts for a week. On merging to main, make a release build available with artefacts retained indefinitely. Took me a couple of hours when I’d never done this before but all more or less as one would expect. I tried to do the equivalent in gitlab free SAAS and I gave up after a day and a half- testing and building was okay but it seems that you’re expected to use a third party artefact store. Yes, you could make the case that this is outside of remit, although given that the major competitor or alternative supports this, that seems a strange position. In any case though, you would expect it to be clearly documented, it isn’t or at least wasn’t 6 months ago.

It’s very mass market, not particularly well informed general news source and this is a specialist community where this is relevant to its specialist field

Zim desktop wiki? I’ve used it for years. Cross platform, open source, lots of features. Bear in mind that there are a lot of plugins, including one specifically for journaling

Coming from what looks to me like a different perspective to many of the commenters here (Disclosure I am a professional platform engineer):

If you are already scripting your setups then yes you should absolutely learn/use Ansible. The key reasons are that it is robust, explicit, and repeatable- doesn’t matter whether that’s the same host multiple times or multiple hosts. I have lost count of the number of pet Bash scripts I have encountered in various shops, many of them created by quite talented people. They all had problems. Some typical ones:

The thing about Ansible is that it can be modular (if you want) and you can use other people’s code but fundamentally it runs one step at a time. You will know for each step:

• Are dependencies met?
• Did that step succeed or fail (in realtime!)?
• (If it failed) what was the error?
• (Assuming you have written sane Ansible) you can re-run your playbook at any time to get the ‘same’ result. No worries about being left in an indeterminate state
• (To an extent) It is self-documenting
• Host architecture doesn’t really matter
• Target architecture/OS is specified and clear

Reading the article it seems to me that this girl was pushed ‘to excel’ beyond endurance…

Great location for a music video

This + ‘fish’

Is there some cache on your old phone from some previous ‘activate on this device’ required?

This is generally a good article but this section

Erin Rackham proposes being perceived as another type of sense.

She can propose but the link is to a TikTok and meantime ‘gaze detection’ has been disproven repeatedly. Here’s a link to an accessible article by an accredited neuroscientist writing in an academic journal discussing exactly this

I’m curious if the collision detection activated

Look into ssh

… Or not, as in my case.

The SDF Lemmy instance (not sure about Mastodon) has issues with federation ongoing for the last 2 weeks at least and the admins have been MIA. I’ve had to switch to an alt account

You’re forgetting that they had a good market position with Windows Mobile. They saw off Palm and were competing with Symbian and RIM. Then they rebooted with Windows phone and again with Windows phone 7 and again with Windows phone 8 and again with Windows phone 10. Each generation incompatible with the last. Sometimes even known in advance, e.g The 8-10 transition leaving Osborned devices on sale for nearly a year Meantime Android was available ‘free’ to manufacturers, compatibility was maintained between operating system versions and across manufacturers. Customisation was a big thing for OEMs - look at HTC and Samsung on Android. Every Windows phone had to look IDENTICAL on screen by order of Microsoft.

Microsoft did it to themselves with mobile. Ballmer era MS thought they could ‘bulldoze the market’ like the early PC era again but that didn’t work when they had to actually compete.

You’re aware that luxury cars may have both, e.g. Aston Martin DB11

If you read the original Reddit post, or watch the MKBHD video specifically referencing it, you will see that Brownlee recreated an experiment demonstrating that the phone was inserting a pre-made image of the moon when and where it ‘recognised’ the moon in the scene. This is beyond what you could call ‘post processing’, it’s in the realm of ‘photoshopping’. No Brownlee was not especially outspoken but I don’t think there was anything ambiguous or deceptive with his presentation.

In April 1940, early in the Second World War, Nazi Germany invaded and occupied Denmark.[97] To prevent the Germans from discovering Max von Laue’s and James Franck’s gold Nobel medals, Bohr had de Hevesy dissolve them in aqua regia. In this form, they were stored on a shelf at the Institute until after the war, when the gold was precipitated and the medals re-struck by the Nobel Foundation.

Excuse the ignorance but what stops Meta setting up their own instance?

I had a Plex subscription and switched to Jellyfin. Same reasons as everyone else- it was all about Plex’s content and recommendations running on my equipment when the whole point for me was to have something with only my own content.