zygo_histo_morpheus

joined 1 year ago
[–] [email protected] 21 points 2 days ago (2 children)

You could still automatically delete all new posts and comments or something like that I suppose

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

If anything I think that the current rust discourse is a fad. I'm not sure what it is about rust that makes people have so strong opinions about it but I can't wait for it to become a "normal" language so that people can chill about it a bit.

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

Yeah it seems like most Brazilian twitter users have gone to bluesky. I'm glad that so few went to threads actually.

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

I think there's a cultural difference too. Bluesky is much closer to (a subsection of) twitter culture pre-musk than anything else. Weather you think that's good or bad is a matter of taste but it is probably the easiest thing to get people who like pre-musk twitter to switch to.

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

I dunno, CMake has one of the worst syntaxes I've ever seen, and despite that it's one of the most popular languages used for C/C++ build scripting. This is because it has certain technical benefits compared to its competitors. I'm certain that having "bad" syntax is a disadvantage but it's less important than other factors. Also I don't think that Rusts syntax is universally disliked either.

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

If you're hobby programming then do whatever you want obviously but if you're part of some sort of larger project that's trying to decide between Rust and C++ then subjective aesthetic arguments probably aren't going to be considered as heavily as technical ones (and rightfully so), which in Rusts case could be that certain classes of bugs are impossible. That's not to say that it's not possible to make a technical case for C++ over rust but syntax preferences probably aren't going to play a large role in how widely used either languages are, which is good.

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

I don't think that everyone has to switch to rust or anything but "I dislike the syntax" and "I only want familiar things" are really bad arguments for not using a language. Try something outside of your comfort zone for a bit, it will help you grow as a programmer.

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

There are non-propietary versions of android, I use /e/OS for example. Try searching for de googled android if you wanna find out more.

[–] [email protected] 120 points 1 month ago* (last edited 1 month ago) (7 children)

I'm surprised that no one seems to have brought up curl, which is maintained by Daniel Stenberg who is Just Some Guy™

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

Maybe paywalled subreddits are more intended to become competitors to maybe patreon and only fans rather than present day subreddits? Like a lot of patreons have discord access as a perk, the paywalled subreddit could potentially fill that role instead. Don't think it seems like a good idea and don't think it'll become more than a gimic

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

Beeper is a free app that is built on the same matrix bridges, and it takes care of hosting for you. Downside is that this requires you to trust beeper

[–] [email protected] 1 points 2 months ago* (last edited 2 months ago)

When I'm just locally iterating on stuff I'll usually do a git commit -m "WIP: Description of what I'm trying to do" and then git commit --amend to it. A bit more ergonomic than stashing if I want to switch branches imo. I can also go back to old versions if I want to through the reflog.

git commit --fixup some-commit is also great for if I discover things in the review for example. You can then do git rebase master --autosquash to flatten them into the commit they belong to and that way you don't have to bother with commit messages like "fixed typo". Doing fixups for small fixes is good because it allows you to keep your mr broken up into several commits without also leaving in a bunch of uninteresting history.

Can recommend checking out the --fixup section in the git documentation if you haven't heard about --fixup before.

view more: next ›