cyclohexane

Podman is a lot like Docker: a tool for running OCI containers. While it maintains backwards compatibility with Dockerfile and docker-compose syntax, it offers a lot of other benefits:

• daemonless: it can run containers without a daemon process running in the background.
• Rootless: can run containers without root privileges
• pods: can group containers into secluded pods, which share resources and network namespace

Podman has other features I haven't explored yet, like compatibility with Kubernetes yaml file, and being able to run containers as systemd units.

Have you used podman before? What are your thoughts on it?

There was a time where this debate was bigger. It seems the world has shifted towards architectures and tooling that does not allow dynamic linking or makes it harder. This compromise makes it easier for the maintainers of the tools / languages, but does take away choice from the user / developer. But maybe that's not important? What are your thoughts?

In a lot of projects, this is usually done via README. It tells you what running dependencies to install and how to run certain commands.

This can get harder to maintain as things change, the project grows, and complexity increases.

I see two parts to automate here: actually setting up the environment, and running the application or orchestrating multiple apps.

How do you address this?

why?

Because bash feels clunky to write and work with for anything non-trivial, especially compared to other scripting languages.

Why not another scripting language (no compile necessary)?

Because bash and sh are installed nearly everywhere. Any other scripting language means the user is required to have that installed, and that is far less likely to be the case.

If I could write my scripts in a nice syntax, but be sure my users will be able to use it effortlessly by distributing to them compiled versions, then that would make both of our lives easier!

Thoughts? Are there any languges that do this?

Hello all,

I am looking for suggestions for libraries to use on my project. It is a personal project, so I'm happy to experiment with lesser known or new libraries.

The application will be a mix of content-focus and client side interactivity (think to-do list with server side persistence).

My current approach is as follows:

• Server side rendering on NodeJS with a template engine, complemented with client side scripting for interactivity (mostly vanilla JS)
• Use liquidJS as template engine (any alternatives?)
• Use fastify as the HTTP / Backend server with @fastify/view plugin for serving liquidJS (and other template engines)
• use vanilla JS scripts for interactivity and DOM manipulation
• use vanilla-SWR for data fetching, mutation and persistence on server side. Link: droyson/vanilla-swr

Any other suggestions?

React (and Vue, et al) was built with client side rendering in mind. It just does not seem to fit the server side rendering pattern.

What are the use cases? From my perspective, if your app is a rich web app with a lot of interactivity, you probably want CSR and don't benefit much from SSR.

If you have a content-centric site, or a site with some interactivity but not much, you want a static site generator, or SSR. But in that case, a template engine with some smaller client side libraries (jQuery or AlpineJS or idk what all is out there).

Using React SSR for all of these seems like the wrong tool. What am I missing?

It seems that around July 15th, the repo for Barinsta, the FOSS instagram frontend that was abandoned about 1-2 years ago has been taken down.

The repo was hosted on codeberg, after the original author took the github repo down. The second maintainer moved the repo to codeberg, but it seems little was done to maintain it. The second maintainer seems to have deleted previous blog posts about barinsta as well.

I have the repo backed up locally (hence why I noticed), but it does not work in its current state.

Its probably not worth using instagram anyways

I've been using geometric weather, but wondering if people have other options for weather apps.

Widgets aren't necessary

I've been using geometric weather, but wondering if people have other options for weather apps.

Widgets aren't necessary

Binance.US ceased USD deposits, and became a crypto-only exchange

Are there any ways to buy crypto in the US, with the ability to withdraw easily, without paying fees? Or at least something with cheap fees?

I've looked into BISQ, but I am afraid of law enforcement retaliation. I'm not doing anything illegal, but I read stories of people getting arrested for not verifying the identity of who they sold to. Don't want that to be me.

Hello friends,

I am looking for a self-hosted task / to-do list app that supports:

• syncing across devices, preferably self-hosted
• sort items myself rather than by deadline or built-in priority features, and preserve that order when syncing
• allow defining arbitrary custom attributes

Some really nice to haves but not absolutely necessary features:

• treat custom attributes as first-class. i.e. allow showing those attributes on the task-list view, without having to view all details to see it. Or be able to filter or by the attribute or sort by it.
• allow custom logic for sorting
• just scriptable features in general would be nice

I have been thinking of making my own, but wanted to see if this exists first.

One of the things I like the fediverse is the oppposition to unhealthy social media use. I think infinite scrolling is one of the worst things about mainstream social media. Even when youre consciously against it, it is very hard not to forget and get consumed by the infinite scrolling.

My proposal is that front-ends should default (or at least provide the option) to a paginated interface. You get to the bottom and have to click a "Next" button. It acts as sort of a wake up call to your scroll-numbed mind. It is also a much more ergonomic interface anyways, and more lightweight on resources.

I strongly believe that, if presented the option, most people would prefer pagination over infinite scroll. It seems corporations forced infinite scroll on us for maximum time wasted.