I’d argue the most elite use @radareorg with ghidra’s decompiler :)
-
-
Replying to @Jaywalker @ilfak and
I wish, but the fact that https://github.com/radare/r2hate still exists paints a real bad picture for the entire project... (inb4 i’m bombarded with hate mail from the devs)
4 replies 0 retweets 8 likes -
How so? I don’t see the problem. If you don’t like how they run the project you can fork it.. that’s the beauty of open source
1 reply 0 retweets 0 likes -
Replying to @Jaywalker @andxoror and
No, the beauty of open source is collaboration and being able to work together on a shared goal. Forking (in the impactful sense, not the GitHub fork-and-merge sense) isn't a "beauty", it's a defense mechanism against toxic communities, like Radare's.
1 reply 1 retweet 24 likes -
Well, I guess it depends on your ideal end goal. My ideal end goal is everyone running their own individual forks of just about every software so that it fits their needs so uniquely specifically that only they can drive it. Like suckless tools! To that end, forking is beautiful!
2 replies 0 retweets 0 likes -
Replying to @Jaywalker @andxoror and
Unfortunately, nobody has time time to fork everything. I have a grand total of 21 custom patches I use for all software on my main workstation and that's already a bit silly. It's a lot easier when projects are friendly, and everyone can share their improvements.
1 reply 0 retweets 14 likes -
But “friendly” usually means bloat and bloat is a great place for bugs to live. Skinny and easily patchable is better. I don’t know off hand how many personal patches I have exactly, but it’s certainly similar if not more. I don’t consider it silly; it’s just *nix user endgame.
2 replies 0 retweets 0 likes -
Replying to @Jaywalker @andxoror and
As a happy KDE user, we're going to have to agree to disagree. Customizability isn't "bloat" to me when it lets me make the software work how I want, without preventing other people from making it work how they want.
1 reply 0 retweets 8 likes -
I don’t begrudge those who use bloated software, if it works for you that’s fine. But as I see it, its a matter of choice in where you spend your frustrated/setup/“why isn’t this working” cycles:
1 reply 0 retweets 0 likes -
Replying to @Jaywalker @marcan42 and
With “suckless” software you spemd that time all upfront with setup, patching, and configuration. Whereas with “bloated” software you spend that time in little bits for the rest of forever dealing with inconsistent, hidden, undesired or unexpected functionality.
1 reply 0 retweets 0 likes
I'm pretty sure I spend less time running into bugs and "weird issues" cumulatively than I would building all my software out of patch files. Once you know how to use software it doesn't get in your way if it's any good, and it doesn't have to be 2000 lines of code to be good.
-
-
Hey, I’m not saying the 2k lines standard should be treated as scripture; but it is a good baseline to keep the core project slim. Honestly, I’d vote have the idea that all tool controls should be done via unix socket like bspwm so one tool can manage all keybinds be a core value
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.