Suckless - "Do one thing and do it well"


@Askarus I know where you're coming from, and a couple of times I've thought the same.

I could be overstepping the mark, but I believe that many of those being more militant about it, are also likely on the autistic side of the spectrum.

Try not to take it personally, and do what you feel is right for yourself. Since I've moved to an Arch-based distro, and also moved to almost exclusively CLI-based apps, I've never been happier.

My daily driver now is a ten-year-old laptop (ThinkPad) I got cheap from eBay, and find it much more rewarding than the much newer & more powerful laptop I also have.

It's certainly not for everyone though; my wife will attest to that.
 
I could be overstepping the mark, but I believe that many of those being more militant about it, are also likely on the autistic side of the spectrum.

Maybe. Good point.
Don't worry, I don't take it personally :)

Try not to take it personally, and do what you feel is right for yourself. Since I've moved to an Arch-based distro, .

Besides the Pandora pure Arch was the first and only Distro I've used so far ;)
Installed Manjaro on my old Laptop now.

and also moved to almost exclusively CLI-based apps, I've never been happier

Interesting. That's definitely an advantage. You should have no problem switching to the Pyra then ;)
I go a different way.
Most old school CLI user claim GUI user to be slow and inefficient. My opinion is that GUI apps can also be used efficiently. Only the majority does not learn how to use it properly.
My approach is to learn the shortcuts for my GUI applications and use them.
The last days I have configured my preferred Editor. It's Geany.
It is much more powerful than it seems and you can configure it so 95%-98% I needed so far was away only 1-3 button combinations.
It has built in Terminal, built in GDB support, a tree browser that can easily be controlled per keyboard, macros, code snippet completion, can record keypress, bookmarks, split window and much more.

The only problem is that it's so tempting to use the mouse and not learn to do it the efficient way. That's the biggest issue of GUI applications I think ;)

#############################
BTW: To Topic:
@JDTAY
Thanks for the hint regarding the humble books.
If you want a language that is really nice, try Rust. I have not learned it now but it's high on my to do list.
Do some research. For me it sounds like a great language with much potential :)
 
In the current bit of code I'm hacking about with I started prototyping it in python but avoided using classes or generators or anything that couldn't be ported over later to C because I thought python would be too slow to be usable. But it turns out that even on my older computers, python is fast enough, so I've really made a rod for my own back, not having everything nicely encapsulated and unit tested away. But I'm treating it as a learning experience to get more familiar with debuggers instead at the moment, but it certainly feels like development is a lot slower. It's a lot quicker to hack up in the first place, but even a toy project like this benefits from having predictable tested components to build from, and cut down the amount of debugging you need to do.
 
So my C Pocket Reference arrived today. It covers ANSI C99, which is good because suckless says to use C99. suckless says not to use extensions though, and this book covers extensions. How do I tell which things are extensions? I don't want to accidentally suck.
 
as with all philosophies, sometimes moderation is best to be practical...

i.e., if you're going to need a hash table, use C++ rather than C and rolling your own...
 
A terminal that can only do one thing and that well, would be one that would be able to open and close.
giphy.gif

Everything on top makes it hypocritical at best.

Technically I think I'm also "cheating" by using tmux (with tmux-urlview) on top of st to add scrolling and link navigation...
Doesn't that completely defeat the purpose?
 
Guys, I have a problem I haven't been able to Google my way out of. How do I make the code completion in Code::Blocks work for just C instead of C++?

Man, something like this should be super simple. If it turns out to have a complicated solution, I'm gonna be cheesed.
[doublepost=1518823468,1518820421][/doublepost]I think the problem might be that I'm using the newest version of Tiny C Compiler, which is newer than the version of Code::Blocks I'm using. Code::Blocks gives me a warning saying it doesn't know how to set optimization flags for my compiler.
 
Back
Top