aah my favorite template engine, I have seen it so long ago

From the list, openscad requires the least tutorial. Solvespace is really easy also, but you need to watch some exciting modelling videos before you get the idea around it. Blender is hard.

OpenScad also gives you a different modelling experience that lets you write reusable models, e.g. if you are a carpenter, 90% of your modelling is sizing and positioning fiberboards to shape a box. You can “automate” such tasks, easily. I wrote a script for myself that does that, and I’m now super fast at modelling furnitures. After some modelling you will be also capable of making such lib. (As a developer, I might be biased)

If you are interested in this library: https://github.com/fxdave/woodworkers-lib

Try solvespace or openscad or blender depending on your use-case.

afaik, fedora is the testing distro for RHEL. I also felt this way, when a new gnome version released much earlier than for Arch and it had an obvious bug that could be catched with little testing.

And many issues I found in Fedora’s bug tracker was auto closed by the new release. Which is quite frequent. Reviewing the bugs is not that frequent.

well, yes, but for e.g. I wrote a software piece that happened to be only a hotkey daemon. And I could write it with X. Now, hotkey daemons are no longer a separate thing unless the compositor exposes a grab API. Which never going to be in Wayland protocol, because they consider this client server architecture a problem.

There’s hope. Thanks for letting me know.

Now instead of having Wayland covering everything, applications try to cover every desktops. In the good old times, it worked everywhere.

Why does flameshot need to handle different wayland desktops separately? Because simply the protocol doesn’t do it’s job. It doesn’t cover everything. It’s indeed not ready.

I think it kills the community. Making a Wayland window manager is so much harder to do than an X one. This monolithic solution solves the problems of Gnome, and KDE developers but less people want to be involved in windowing systems. I’m just being sad for X11, because, although it had nonsense features, it made linux desktop applications compatible with every desktop and we had huge variety of wms, compositors, desktop environments. Personally I’m still on X because of bspwm, but eventually there will be wayland-only features which will slowly kill X.

I’m a contractor and I use linux if that counts :D

I recently installed Nix alongside with Arch. I feel the same. After years of using Arch I spent two days to get everything configured the same as in my Arch, and I haven’t finished it yet.

Don’t buy a Mac. That’s more limiting than a Windows. But yeah install linux.

yeah I’m a fucking idiot because I thought wrongly the redis’ language…

I use rust only if we need performance, for small services. The industry does the same. People use node for backend but e.g. redis is in rust. It’s a good tool if you use it for the right stuff.

EDIT: redis is not in rust, but e.g. aws writes many services in rust

Our views can be compatible. Endless os is quite limited right now, but if flathub would have xampp, for example, that would be easily the simplest way to run a webserver. However, every techy person prefers docker, me too. It’s just not something that my mother can deal with. In general, linux is lacking these mother compatible apps where we have more advanced solution. Of course, I wouldn’t recommend endless and others in the category if the goal is to run a webserver.

None of them good for non techy people. I wouldn’t recommend mint. Gnome is the most friendly DE with pleasing defaults. There are many immutable flatpak distros coming with gnome. e.g.: Endless os which is pre installed on some asus laptops instead of Ubuntu for reason.

Thanks for the question. GraphQL works with multiple languages, Cuple works only with Typescript. Despite this drawback this also gives you some advantages:

• The Request and Response types are auto-inferred from the endpoint you write
• Because the types are in Typescript you don’t need to generate a client, you just simply use it with @cuple/client and get instant feedback.
• You don’t have to learn another language. It’s just typescript.

Practically it means less boilerplate and it let’s you focus on the feature you write. Cuple is also not a query language, you get what the server sends you, it’s more likely a type-safe FFI binding. With Cuple you can build a REST API, or anything similar to that with HTTP method, header, path, query, body, and you can use it type-safely.

Also Modo

I deleted /lib64/ld-linux-x86-64.so.

I did it because valgrind had a problem with it. I thought I can fix it with reinstalling the package. I tried to lookup which package is it from, but the command I used was wrong and I didn’t get any result. So I thought, what if I created it, maybe I just forgot it.

the moment I deleted it everything stopped working. It was fixable only from a pendrive.

That’s fair. Typescript has to cook with the existing js ecosystem.

Have you tried it?