jsveiga
So many. Unfortunately most of you will miss the lyrics, which are real poetry. Here are a few:
A rosa (1917 song by Pixinguinha, rendition by Marisa Monte in 1991)
Bahia com H (1981, João Gilberto, sang by himself, Caetano, and Gil)
Luiza (1987, Tom Jobim)
Slashdot was becoming too toxic, I moved to reddit.
Reddit wants me to use their obnoxious app, I moved to Lemmy.
Reddit is a business. If they can survive doing what they see fit, good for them.
I moved on. Life goes on.
J, like in GIF…
You answered “trying” as something that “is ALWAYS worth it” - which was OP’s question.
If you now say you need to “weigh the pros and cons” - which I agree - then trying it’s not ALWAYS worth it, no?
Then as someone else commented, each person has their own risk tolerance, so once each person weigh the pros and cons, trying will be worth it for some and not for others.
So answering “trying” to “what’s something that’s always worth it” is rather paradoxical, as what you probably meant then was “trying it, but only when it’s worth it”.
It was not the most important thing for me, but I agree: 15-20 years ago, veg options (and sugarless too btw) sucked. You really had to be committed to the cause to endure them.
We’re not vegetarians, but my daughter has allergy to eggs and milk. We buy cakes, pies, brownies, cookies, etc from a vegan bakery that honestly are delicious - better than most non-vegan equivalents. We all end up eating them, although only she actually “needs” them.
If vegan activists worked more towards kindly creating and showing the world vegan options that are as good as/better than their animal counterparts, it would help their cause MUCH more than pestering people, destroying property and making everyone hate them.
But if you ask yourself “what’s the worst that could happen?” you must realize that sometimes trying is NOT worth it.
Like this guy, for example:
Yes, back in 2009, after a kernel update to 2.6.26 there was an intermittent and hard to reproduce problem with Intel’s e1000e ethernet linux kernel module. It only happened when some specific switches/hubs were connected to the interface; the interface would initialize in an unusable state (about 50% of the computer boots).
The e1000e module was used by a lot of Intel onboard ethernet interfaces, including the one used by Dell Vostro computers.
I found other people reporting it in the kernel’s bugzilla, and added my case.
The Intel developer couldn’t reproduce it (he didn’t have one of the switches that triggered the problem), so he asked me to use bisect to help narrowing down to the commit that started the problem.
Because it was an intermittent issue, I wrote a script to reboot the PC multiple times on each bisect try, to eliminate false positives.
(I didn’t remember all these details, but googled my name and bisect, and found the bugzilla thread; it’s an interesting bisect use case: https://bugzilla.kernel.org/show_bug.cgi?id=11998#c8 - no I don’t mind this associates my lemmy user name with my real name).
The bisect did locate the culprit commit, and after many other tests, it ended up being an issue with the MDI/MDIX (crossover or straight connection detection). The correction was pushed into the kernel.
Bisect definitely helped to find an important and otherwise difficult to find problem there.