For me it’s the bloody “video essay” format. Hyper narrated, spoken straight to the camera. Waste of traffic, waste of storage, waste of attention. People think the argument carries more weight, or is just more persuasive, when someone is speaking at you with some vaguely related visual in the background. But really a written piece could be pulled apart so much more quickly.

Unfortunately OpenAI’s Whisper doesn’t do written transcriptions fast enough on my workstation yet for me to use it full time.

BYD employ about 570,000 people and by some measures are the largest carmaker in the world. I’d never heard of them either until a couple years ago. They’ve definitely got the cash to put into PR like this. Past couple years Australia started importing their electric cars. https://en.wikipedia.org/wiki/BYD_Company

I use it for my very basic static site generator: https://www.olowe.co/2021/01/site-build.html

Ah come on, we all know as software people we can never stop the spreadsheets from being the real data interchange format ;)

I’m not so surprised anymore. I’m self-taught using open-source software projects for guidance. But not everyone learns like that. For example in the commercial software dev world, having patches easy to apply with minimum tooling isn’t usually a priority (for better or worse).

This is actually a little story I had half written down; your comment prompted me to finish it. Thanks! https://www.srcbeat.com/2023/11/git-email/

Yes that’s true. I guess what I wanted to point out is that GitLab has dependencies like Postgres, Redis, Ruby (with Rails), Vue.js… whereas Forgejo can use just SQLite and jQuery.

McCodeBurger

Something not mentioned yet: Forgejo, the software running Codeberg, has a smaller feature set and narrower scope than GitLab (“GitLab is the most comprehensive AI-powered DevSecOps Platform” from their website).

Forgejo is much easier to administrate for smaller groups. For example compare the dependencies mentioned in the Forgejo installation documentation and the Gitlab installation documentation.

MacPorts is so boring and underrated.

Sorry my comment was really snarky - I apologise. Long day! I’ll do better in the future :)

There has been criticism of this listicle format. Critics claim they are clickbait and machinated recycling of information/ideas. Listicles seem to exist to just get more ad impressions over entertaining and informing the reader.

The original article on the original site feels a bit like that. Loads of ads, with just one link to the actual nixos website, mid-sentence, towards the bottom of the article (where the majority of readers never get to).

Of all the articles to copy and paste without attribution, you chose this one…?

Devil’s advocate: what about the posts and comments I’ve made via Lemmy? They could be presented as files (like email). I could read, write and remove them. I could edit my comments with Microsoft Word or ed. I could run some machine learning processing on all my comments in a Docker container using just a bind mount like you mentioned. I could back them up to Backblaze B2 or a USB drive with the same tools.

But I can’t. They’re in a PostgreSQL database (which I can’t query), accessible via a HTTP API. I’ve actually written a Lemmy API client, then used that to make a read-only file system interface to Lemmy (https://pkg.go.dev/olowe.co/lemmy). Using that file system I’ve written an app to access Lemmy from a weird text editing environment I use (developed at least 30 years before Lemmy was even written!): https://lemmy.sdf.org/post/1035382

More ideas if you’re interested at https://upspin.io

They even have a term for this — local-first software — and point to apps like Obsidian as proof that it can work.

This touches on something that I’ve been struggling to put into words. I feel like some of the ideas that led to the separation of files and applications to manipulate them have been forgotten.

There’s also a common misunderstanding that files only exist in blocks on physical devices. But files are more of an interface to data than an actual “thing”. I want to present my files - wherever they may be - to all sorts of different applications which let me interact with them in different ways.

Only some self-hosted software grants us this portability.

I won’t speak for the OP, but yes it is a fair question about the automatic red-flag. There are characteristics of software described as cloud-native that are considered undesirable by some.

These could range from things as high level as an objection to how projects are funded, down to things like distaste for code complexity required to support opaque HTTP APIs over standardised protocols.

Ah yes good point. Fingers crossed.

Looks like that will happen later. From Mozilla’s original article:

Following a period of testing, these packages will become available on the beta, esr, and release branches of Firefox.

CNCF projects themselves are indeed FOSS, but “the cloud” as it is most commonly interacted with, by tech workers, are enormous collections of closed-source systems run by Amazon, Google or Microsoft (all under antitrust investigation either now or in the past).

I’m still super confused by this user’s posts lol. I get that (some? most?) of it is satire… but then why all social media engagement farming hashtag nonsense? Or is this all part of the satire…?

Good to see development effort going towards actual Firefox and not those random Mozilla products that I can’t keep track of

how can a writer be so ignorant.

They probably know exactly what they’re doing. Singling out Japan makes for a “better” headline to a mostly North American audience.

It’s also a bit of a clever headline. Compare the original headline and this one: “All major automakers continue to produce sports cars”. Both headlines could technically be true.

But the original headline lets you get away with stirring up some emotion e.g. “Japan alone is keeping the sportscar industry afloat, European, American manufacturers don’t care, sportscars are dying”. Life, death: strong words! It’s misleading and shitty journalism.