Ephera

Might be a song from Kevin MacLeod? His songs get used a lot on the YouTubs.

https://incompetech.com/music/royalty-free/music.html

When I just searched "Kevin MacLeod jazz", the first result was "Acid Trumpet", which seems like it could fit your description.

I enjoy anise-fennel-caraway tea. It doesn't taste as watery as many of the fruit-based teas and not as bitter as black tea and such. I find, it's also decent at clearing out my throat.

Peppermint tea is second place for me, for very much the same reasons. 🙃

Not sure, if I stopped listening to mainstream music around that time, but uh, both of my examples are from 2011, apparently:

• Kind of a classic response to this question, is "Pumped Up Kicks" from Foster The People. It's got that upbeat melody, and the lyrics are this:

All the other kids with the pumped up kicks
You’d better run, better run, outrun my gun
All the other kids with the pumped up kicks
You’d better run, better run, faster than my bullet.

• And my other example is "The A Team", apparently originally from Ed Sheeran, and apparently also with an upbeat melody. I think, I only ever listened to a cover version. But yeah, it's about drug use and sex work, and how those kind of necessitate each other...

Personally, I've found Poetry somewhat painful for developing medium-sized or larger applications (which I guess Python really isn't made for to begin with, but yeah).

Big problem is that its dependency resolution is probably a magnitude slower than it should be. Anytime we changed something about the dependencies, you'd wait for more than a minute on its verdict. Which is particularly painful, when you have to resolve version conflicts.

Other big pain point is that it doesn't support workspaces or multi-project builds or whatever you want to call them, so where you can have multiple related applications or libraries in the same repo and directly depending on each other, without needing to publish a version of the libraries each time you make a change.

When we started our last big Python project, none of the Python tooling supported workspaces out of the box. Now, there's Rye, which does so. But yeah, I don't have experience yet, with how well it works.

Python never had much of a central design team. People mostly just scratched their own itch, so you get lots of different tools that do only a small part each, and aren't necessarily compatible.

We've got a WebAssembly web-UI at $DAYJOB. Implementation language is Rust, we use the Leptos framework (although other mature frameworks are available for Rust).

Pros:

• Same language and similar tooling as in the backend. Most libraries work the same way (obviously excluding libraries that read from the filesystem, for example). This is especially good, if you've got lots of "full stack" devs.
• Same model classes as in the backend. If you change a field, the compiler will force you to fix it on both sides. It is compile-time guaranteed that backend and frontend are compatible.
• Rust is a nicer language than JS/TS. I find especially Rust's error handling via Result and Option types + pattern-matching works really well for UI stuff. You just hand the Result value over to your rendering stack and that displays either the value or the error. No unset/null variables, no separate error variable, no ternaries.
• Having a strict compiler makes it less bad when you're lax on testing, and frontend code is a pain to test.

Cons:

• If you've got pure frontend folks, or people who are deep into React or Angular or whatever, those are not going to be as productive.
• The JS ecosystem is massive, you just won't find as many component libraries for Rust, which can definitely also reduce productivity.

With me being in a team with few frontend folks, I would definitely opt for it again.

Yeah, Google likes to guess the language preference based on the IP address, which thankfully never goes wrong.

Apparently, OP's wife prefers the taste of the pre-made stuff, because it reminds her of her mother's cooking. But yeah, kind of a weird info to omit...

Yep, how to make predictions about the Future™:

1. Find something that offers a mild advantage, but we don't do, because of the massive disadvantages that come with it.
2. Claim that those disadvantages have been eliminated, because it's the Future™.

Hmm, maybe this was considered for putting onto the Voyager Golden Record or something like it...?

At the risk of calling someone's work boring: Might help people fall asleep?

Me on Lemmy today: