KindaABigDyl

joined 2 years ago
[–] [email protected] 3 points 5 days ago* (last edited 5 days ago)

Well, it's gotta be a tiling system. And a good one. At this point I can't function in a non-tiling environment. Specifically a manual tiler with an auto-tile a la i3 w/ i3-alternating-layout or a dynamic tiler that still let's you break stuff (doesn't really exist).

It's just a better way to use a computer, and I can't go back. It's so much nicer. I would stop using a computer before I go back to dragging windows around.

And that rules out most DEs. It rules out Mac OS and Windows, as well, but at least on Windows I can almost get by with Fancy WM. It's "okay."

And speaking of just getting by, that's Polonium with KDE. KDE is pretty good as an "environment," but it doesn't have a tiler that meets my needs, or at least I thought it didn't until recently. Then I discovered Polonium. It works pretty well. Used it for several months (and still do on one machine). It's very bare bones tho, and is hard to configure the handful of floating windows I do want like popups. So KDE is just scraping by.

GNOME on the other hand has the excellent Pop Shell 2. But well, GNOME is GNOME. It's buggy when you try to use it a different way than intended. God forbid I want Qt, Gtk2, Gtk3, Gtk4, and libadwaita apps to all look nice on my system! It's clunky, but the tiling is excellent at least.

Now you mention XFCE. So what about that? You could use i3 as the WM for Xfce. I used i3 for years and years and years as my WM and know how to build a DE around it. Why not use Xfce + i3?

Well, the thing is X11 is as good as dead, and while XFCE now supports Wayland, you can't use a tiling system with the Wayland version of XFCE.

So what does that leave me?

Nothing. At least for a full on DE, which is what you asked.

There is not a single (pre-made) Desktop Environment that suits my needs. Not a one. Either it doesn't support good tiling, is too rigid, or hasn't switched to Wayland.

My only options are:

  • Roll my own DE built around Hyprland/Sway, and since I'm on nvidia, those aren't fantastic options (albeit Hyprland works a lot better on Nvidia these days), and that's what I'm using.
  • Deal with the slight annoyance of the under-implemented Polonium in KDE

Right now I'm on Hyprland. May go back to KDE bc multi monitor is being weird on Hyprland rn.

My one hope is that COSMIC polishes itself up and gets to its first real release.

[–] [email protected] 2 points 1 week ago

You can put anything in your dialog box

[–] [email protected] 5 points 1 week ago (1 children)

I made a shortcut that's Ctrl + S to save and Ctrl + X to exit, so I don't have to remember it and have now forgotten to make room for more Rust knowledge

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

So... pure functional programming w/ out state?

[–] [email protected] 2 points 2 weeks ago (5 children)

That’s why kernel anti-cheat is effective

Is it actually effective tho?

[–] [email protected] 8 points 3 weeks ago

Sweet! Now that 4.20 is officially released it's in Nixpkgs. That means xfce4-panel is 4.20 in unstable

Might go back to Hyprland from KDE now that there's a half-decent bar for Wayland compositors!

[–] [email protected] 1 points 3 weeks ago

Sweet! Now that 4.20 is officially released it's in Nixpkgs. That means xfce4-panel is 4.20 in unstable

Might go back to Hyprland from KDE now that there's a half-decent bar for Wayland compositors!

[–] [email protected] 2 points 3 weeks ago* (last edited 3 weeks ago) (3 children)

Yes. The only way to send patches without something like Github is over email. I don't mind all the other stuff, but there's no other way to do PRs than over email, and I hate email. I didn't see that he gave alternatives. His preferred solution was an email

The formal PR button in a forge is a way to do that with one click, but a short email with all the same information is just as good.

Like, dawg, no it aint

[–] [email protected] 3 points 3 weeks ago (5 children)

I wouldn't mind doing a self-hosted git repo and only using cli if I didn't have to also use email to do so.

Seriously the worst part. Email is a technology that should be left in the past. It's just awful. There's no good way to do email.

[–] [email protected] 2 points 1 month ago

does represent /ð/ in this romanization, yes.

As for being thou or tu, I'd have to check my design document.

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

I did once make a conlang that was what an Old English-Old French creole would be like.

Here's the Sermon on the mount:

[–] [email protected] 8 points 1 month ago (1 children)

Isn't anarchy just against imposed hierarchy? Most anarchists I've met are okay with heirarchies that form naturally, and believe those hierarchies to be enough for society to function, hence why they call themselves anarchists, not minarchists.

1
submitted 7 months ago* (last edited 7 months ago) by [email protected] to c/[email protected]
 

I created a little side project over the past few days, a new build system for C and C++: https://github.com/blueOkiris/acbs/

I've seen a lot of discourse over C build tools. None of them really seem solid except for (some) Makefiles (some Makefiles are atrocious; you just can't rely on people these days). Bazel, cmake - they're just not straight forward like a clean Makefile is, basically black magic, but setting up a Makefile from scratch is a skill. Many copy the same one over each time. Wouldn't it be nice if that Makefile didn't even need to be copied over?

Building C should be straight forward. Grab the C files and headers I want, set some flags, include some libraries, build, link. Instead project build systems are way way way overcomplicated! Like have you ever tried building any of Google's C projects? Nearly impossible to figure out and integrate with projects.

So I've designed a simplistic build system for C (also C++) that is basically set up to work like a normal Makefile with gcc but where you don't have to set it up each time. The only thing you are required to provide is the name of the binary (although you can override defaults for your project, and yes, not just binaries are possible but libs as well). It also includes things like delta building without needing to configure.

Now there is one thing I haven't added yet - parallel building. It should be as simple as adding separate threads when building files (right now it's a for loop). I know that's something a lot of people will care about, but it's not there yet. It's also really intended to only work with Linux rn, but it could probably pretty easily be adjusted to work with Windows.

Lay your project out like the minimal example, adjust the project layout, and get building! The project itself is actually bootstrapped and built using whatever the latest release is, so it's its own example haha.

It's dead simple and obvious to the point I would claim that if your project can't work with this, your project is wrong and grossly over-complicated in its design, and you should rework the build system. C is simple, and so should the build system you use with it!

So yeah. Check it out when y'all get a chance

 
 
view more: next ›