matly

At least in some member states, that's a well used pattern when the soccer world cup is on (as in: people are focused on something else). Which at least has been going on in the last weeks.

Let's expand our own skillset by investing time instead of money (paying someone else). Sounds like a reasonable proposition to me.

Carpeweekem looks like a really cool idea! I suppose you exclusively use it for goal tracking and not for ongoing/open To Dos, right? At least if you don't carry over stuff from last week?

You could take a look at Obsidian [1], or similar knowledge management tools. There is certainly a lot of movement in the plugin ecosystem right now, for example the obsidian-canvas-llm-extender [2], which (likely) does what you're asking for.

1: https://obsidian.md/ 2: https://github.com/phasip/obsidian-canvas-llm-extender

These moving parts require active understanding and maintenance, as they will change on each and every upgrade, which also requires manual upgrade steps and potential debugging on breaking changes. OCI images let you worry less about dependencies, but what they don't eliminate is debugging and/or upgrading k8s configuration manifests (which we are looking at here).

> We can also take a look at the linux kernel that powers the docker instances and faint in terror.

Sure, and computers are rocks powered by lightning - very, very frighting. That doesn't invalidate criticism about the usability and design of this very product my friend.

As someone that develops native Kubernetes platforms: Providing the raw resources / manifests is almost the worst way of providing a user install. That works great as long as you never have a breaking change in your manifests or any kind of more complex upgrade.

Which brings me back to the initial question: Is this complexity and the external dependencies really needed? For a decently decomposed, highly scalable microservice architecture, maybe. For an Open Source (likely) single tenant management platform? Unlikely.

It highlights the problem of clashing requirements of different target user groups.

Kubernetes cannot ingest compose files as-is, no.

From a users point of view: If I'm interested in a project, I usually try to run it locally for a test drive. If you make me jump through many complex hoops just to get the equivalent of a "Hello World" running, that sucks big time.

From a customers point of view: Ideally you want both, local and cluster deployment options. Personally I prefer a compose file and a Helm chart.

In this specific case I'd argue that if you're interested in running an OSS project management product, you're likely a small/medium business that doesn't want to shell out for Atlassian - so it's also likely you don't have k8s cluster infrastructure, or people that would know how to operate one.

That's actually supporting the posters' argument.

Take a look at all the configs and moving parts checked in this very repo that are needed to run a self-hosted instance. Yes, it is somewhat nicely abstracted away, but that doesn't change the fact that in the kube directory alone [1] there are 10 subfolders with even more config files.

1: https://github.com/hcengineering/huly-selfhost/tree/main/kub...

Agreed!

I really enjoy seeing stuff like Horizon. There are so many bad examples for taxpayers money (e.g. Gaia-X), but Horizon ain't that.

Very fun article to read! There's one catch: Go styleguides strongly recommend short variable names. They do have a whole chapter about single/double letter vars [1] which boils down to: They have their place, as receiver variables and in any place where the short name would be too repetitive.

1: https://google.github.io/styleguide/go/decisions.html

Kind of nice visuals, although I still prefer functionality and speed over visual sparkles. For entertainment and a no-fluff service, I still recommend https://wtfismyip.com/, which offers the data in any output format you could ever need

There is an EU Court ruling that found that EULA/TOS are not applicable or enforceable in Europe, so that's kind of a non-issue. Also, this doesn't really change the outcome if a publisher would be forced to guarantee usability of their product after they shut down servers, does it?

https://curia.europa.eu/juris/liste.jsf?num=C-128/11

You'd be surprised about the amount of people wanting this kind of smartphone. The success of Framework, who are doing something similar in the Laptop world, could be a robust indicator for the demand. Especially the replaceable battery is something we really should get back to IMHO.

Interesting. How is the integration of the reMarkable into other ecosystems? Can notes be converted to text and used elsewhere easily? (e.g. Nextcloud or Markdown docs)?