cyclohexane

joined 3 years ago
MODERATOR OF
[–] [email protected] 3 points 6 months ago

Well I am speaking about users who may be picky about mastodon's features. If someone is picky, I don't imagine they'd care much about just finding a platform with their preferred features, similar to how they didn't like mastodon and found bluesky instead.

[–] [email protected] 1 points 6 months ago (2 children)

The fediverse has many micro blogging implementations outside of mastodon if you don't like their featureset (and they federate with each other, unlike bluesky). The only features I couldn't find are those that contributed to making Twitter the dystopian toxic space that it is.

[–] [email protected] 3 points 6 months ago* (last edited 6 months ago) (3 children)

Is anyone here opposed to bringing more people? I'm upset that people are going to an unfederated platform like BlueSky. I wish more people to join, no matter who they are.

I haven't been on mastodon much, but lemmy is quite diverse.

[–] [email protected] 2 points 6 months ago

Very much the same. I was terrified of regex, now I love it

[–] [email protected] 13 points 6 months ago (11 children)

I preferred the Internet that isn't driven by non-genuine posts by profit driven influencers. I am glad that those people don't like mastodon so they don't ruin another platform.

[–] [email protected] 7 points 6 months ago (1 children)

It's not the best platform for the profit driven, and I much prefer it that way.

[–] [email protected] 2 points 6 months ago

Oh no, now nostr is ruined

[–] [email protected] 6 points 6 months ago

And you'd still have federation issues, so doesn't solve OP's problem.

[–] [email protected] 11 points 6 months ago

Actually being able to self host and federate, and without any dependence on the main instance.

And ability to federate with other open and federated services, like how mastodon can federate with so many others like lemmy and pixelfed.

[–] [email protected] 2 points 6 months ago

This is actually exactly what I asked for, thank you!!

[–] [email protected] 4 points 6 months ago

The appeal for json and yaml is readability, and partially ease of parsing. I say s-expressions win over both in both aspects.

Can you please expand on your references to no-sql and your reference to "lightweight markup"? I don't quite understand what you meant there.

[–] [email protected] 9 points 6 months ago (11 children)

What's so good about it?

 

There is this common narrative I see all the time, implying that we as individuals are empowered to choose and manifest our own destiny, and this comes up often in privacy discussions.

Don't like Facebook's privacy nightmares? Just don't use Facebook!

Don't like personalized ads? I remember a popular post on reddit saying "if your ad interrupts my YouTube video, I will hate your product".

Don't like Google chrome hegemony? Just use Firefox!

And while I agree that we should strive to do that, the battle doesn't end here. Facebook has shadow accounts for people who never signed up. Google chrome keeps it's hegemony despite people on the Internet advocating Firefox day and night. And ads continue to be extremely profitable despite you "hating the product" because it interrupted your YouTube video.

Even worse: even if you "hate the product", you now already know it. You now know they product exists, and possibly whatever they wanted you to know about it. The reality is that these companies own your eyes. They control what shows up on your screen. And even if you hate it, they control what you end up learning.

the reality is that our individual resistance is very far from enough

I am not saying it is completely futile. It is a step in the right direction. But the only effective solution is organized action. We, alone, cannot achieve much. Unless we organize our resistance against privacy violations, we will continue to live through this privacy nightmare.

 

Hi all,

I've managed to get the GOG of horizon zero dawn starting up. But my DualShock 4 controller is not recognized by the game. Now the controller works as a mouse (with the pad), so I know it's at least connected.

What can I do to fix this? I am running it through bottles flatpak. I am using gentoo Linux if that matters.

 

From my understanding, at least one other necessary component is dxvk, and that wine is not enough.

If I dont use lutris or some other manager, how can I game on linux? do I have to configure dxvk? do I need soemthing else too? vulkan?

Is there a guide that explains it?

 

Hi all,

I use a wayland Gentoo system, but I want to run Lutris for gaming. I would like to do this with at least some degree of filesystem isolation, as Lutris seems to install dependencies on its own and it pollutes the system in ways I cannot track.

What is the best way to do this? is it possible to do in a chroot? or mount namespaces? will it give me a lot of trouble?

It seems that merely installing things in a chroot and running it is not enough.

 

I mean, sure, that's probably heavily influenced by the need for bundling for the frontend.

But it isn't done blindly. Bundlers reduce the overall size of the code, either due to minification or tree-shaking (removing unused modules). It also removes the filesystem overhead of resolving and opening other modules.

Would bundling be useful in other interpreted languages?

I suppose you may count JVM's compilation to bytecode as being very similar.

 

So apparently there are two editors inspired by vim, but built from the ground up (as opposed to neovim, a vim fork that seeks to improve on top of vim).

I've heard of Helix several times prior, but it never quite attracted me. Seemed like vim, but different key bindings and much worse plugin system. It also has different visual and normal modes than vim, but it didn't quite click with me. I do like it's multi-cursor ability though.

Then it turns out that Helix was also inspired by not just vim, but also kakoune. Kakoune also has different keybindings, and different modes, but its different modes make sense to me. It fuses visual and normal mode into one. Your normal mode is for both navigation and selection.

Kakoune promotes the idea that you should visually see the text you're operating on before running the command. You know how in vim, "dd" deletes a line, "dw" deletes a word, and "d$" deletes to the end of the line? In vim, you don't see what you're deleting before its gone (which is fine and works for many). In kakoune, the selection happens first before the action. So you select the word or the line, and then you delete.

But what I found to be Kakoune's killer feature was its shell integration. Kakoune seemlessly integrates into the unix shell, allowing you to offload many tasks to it. For example, instead of it having a built-in sort command, you use the unix sort command to sort your lines.

I'm surprised kakoune isn't more popular. Yes, it is still in a much earlier phase than vim, and the ecosystem is far less mature, but I am surprised to see Helix gaining more traction.

 

Yes, I know so much of Alpine's lightweightness comes from not using glibc.

But still, the other options I see are far from being slimmed down. Debian, Ubuntu server, CentOS... They all could use some cuts.

What's the most slimmed down non-desktop distro that still has a glibc base? I honestly don't care if it has its own package manager (build tool handles this for me). Just wanna use it in containers for running server apps.

 

Yes, I know so much of Alpine's lightweightness comes from not using glibc.

But still, the other options I see are far from being slimmed down. Debian, Ubuntu server, CentOS... They all could use some cuts.

What's the most slimmed down non-desktop distro that still has a glibc base? I honestly don't care if it has its own package manager (build tool handles this for me). Just wanna use it in containers for running server apps.

 

Some backend libraries let you write SQL queries as they are and deliver them to the database. They still handle making the connection, pooling, etc.

ORMs introduce a different API for making SQL queries, with the aim to make it easier. But I find them always subpar to SQL, and often times they miss advanced features (and sometimes not even those advanced).

It also means every time I use a ORM, I have to learn this ORM's API.

SQL is already a high level language abstracting inner workings of the database. So I find the promise of ease of use not to beat SQL. And I don't like abstracting an already high level abstraction.

Alright, I admit, there are a few advantages:

  • if I don't know SQL and don't plan on learning it, it is easier to learn a ORM
  • if I want better out of the box syntax highlighting (as SQL queries may be interpreted as pure strings)
  • if I want to use structures similar to my programming language (classes, functions, etc).

But ultimately I find these benefits far outweighed by the benefits of pure sql.

 

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?

view more: ‹ prev next ›