I do in fact use unrefined, brown cane sugar, although I have not tried panela specifically.
The one I use pretty much looks like this:
It’s an organic fair trade brand, but I’d have to look up where it is imported from.
As I said, I can’t imagine making it with any other kind of sugar any more. Sorghum seems like an interesting idea, might have to experiment with that.
The key to amazing banana bread is to make it with soft, brown sugar. The stuff that is clumpy, glistening with moisture, reminiscent of molasses. It adds so much to the flavor. And actual nuts, of course.
I did that on purpose, i. e. I wanted to confirm your thoughts about uv, drifted off into a general rant, remembered OP’s original question and later realized it would have been better framed as a top level comment. In my defense, I was in an altered state of mind at the time.
pyenv and uv let you install and switch between multiple Python versions.
As for uv, those come from the Python build standalone project, if I remember correctly, pyenv also installs from there, but don’t quote me on that.
I moved all our projects (and devs) from poetry to uv. Reasons were poetry’s non standard pyproject.toml syntax and speed, plus some weird quirks, e. g. if poetry asks for input and is not run with the verbose flag, devs often don’t notice and believe it is stuck (even though it’s in the default project README).
Personally, I update uv on my local machine as soon as a new release is available so I can track any breaking changes. Couple of months in, I can say there were some hiccups in the beginning, but currently, it’s smooth sailing, and the speed gain really affects productivity as well, mostly due to being able to not break away from a mental “flow” state while staring at updates, becoming suspicious something might be wrong. Don’t get me wrong, apart from the custom syntax (poetry partially predates the pyproject PEP), poetry worked great for us for years, but uv feels nicer.
Recently, “uv build” was introduced, which simplified things. I wish there was an command to update the lock file while also updating the dependency specs in the project file. I ran some command today and by accident discovered that custom dependency groups (apart from e. g. “dev”) have made it to uv, too.
“uv pip” does some things differently, in particular when resolving packages (it’s possible to switch to pip’s behavior now), but I do agree with the decisions, in particular the changes to prevent “dependency confusion” attacks.
As for the original question: Python really has a bit of a history of project management and build tools, I do feel however that the community and maintainers are finally getting somewhere.
cargo is a bit of an “unfair” comparison since its development happened much more aligned with Rust and its whole ecosystem and not as an afterthought by third party developers, but I agree: cargo is definitely a great benchmark how project and dependency management plus building should look like, along with rustup, it really makes the developer experience quite pleasant.
The need for virtual environments exists so that different projects can use different versions of dependencies and those dependencies can be installed in a project specific location vs a global, system location. Since Python is interpreted, these dependencies need to stick around for the lifetime of the program so they can be imported at runtime. poetry managed those in a separate folder in e. g. the user’s cache directory, whereas uv for example stores the virtual environment in the project folder, which I strongly prefer.
cargo will download the matching dependencies (along with doing some caching) and link the correct version to the project, so a conceptual virtual environment doesn’t need to exist for Rust. By default, rust links everything apart from the C runtime statically, so the dependencies are no longer neesed after the build - except you probably want to rebuild the project later, so there is some caching.
Finally, I’d also recommend to go and try setting up a project using astral’s uv. It handles sane pyproject.toml files, will create/initialize new projects from a template, manages virtual environments and has CLI to build e. g. wheels or source distribution (you will need to specify which build backend to use. I use hatchling), but thats just a decision you make and express as one line in the project file. Note: hatchling is the build backend, hatch is pypa’s project management, pretty much an alternative to poetry or uv.
uv will also install complete Python distributions (e. g. Python 3.12) if you need a different interpreter version for compatibility reasons
If you use workspaces in cargo, uv also does those.
uv init, uv add, uv lock --upgrade, uv sync, uv build and how uv handles tools you might want to install and run should really go a long way and probably provide an experience somewhat similar to cargo.
Didn’t I just say that in the comment you replied to?
Also, ultraprocessed food is a fixed term that refers to
[…] foods […] ready-to-eat or ready-to-heat industrial formulations made mainly with ingredients refined or extracted from foods and contain additives but little to no whole foods.
It’s used as such in studies and reports.
I agree. When I was talking about “processed food”, I was talking about food that has been processed too much, i. e. cooked to oblivion, loaded up with preservatives, artificial flavor, colors etc. to maximize profit by making it last longer, be more attractive / “tasteful” to the point of addiction (think chips) no matter the nutritional value.
Food is of course processed even in the home kitchen, and there are processing methods that are totally fine (let’s say freezing, canning) and that have a long cultural tradition without adverse effects.
However, I think it’s hard to dispute that industrially processed (fast) food, convenience food, snacks, super high calorie foods etc. are a real problem. I honestly also blame e. g. the expectation society has with respect to its workers who can’t necessarily afford (money, time) to regularly prep healthy food at home, given the schedule imposed on them.
What are your requirements? I liked CalenGoo, I can live with aCalendar and BusinessCalendar.
Yeah, thanks, that comic was a little too black and white in 50% of the panels - acknowledging women’s rights and their role in society and abolishing child labor doesn’t mean that we did not process the shit out of food and invented the unholiest abominations as substitute for actual nourishment, or that it’s suddenly healthy to live in a concrete block after spending 10 hours in cloned cubicle #7.
Yeah, no lubricants and the look / style factor - that was my conclusion as well.
As for maintenance, while a belt might last 3 times as long, that’s not really a factor, given the price difference between belts and chains.
Exactly, which is why I was trying to think of any actual reasons I might want a belt, except style.
Are there any other reasons I’d want this apart from the lack of oil and the decreased noise levels, the coolness factor and the tinkering itself?
Every single one is a valid reason in itself of course, but maybe there is more.
I’ll post some links, but it’s a pretty busy week for me already, so give me some time.
An interrupt is an input that can be triggered to interrupt normal execution. It is used for e. g. hardware devices to signal the processor something has happened that requires timely processing, so that real-time behavior can be achieved (for variable definitions of real-time). Interrupts can also be triggered by software, and this explanation is a gross oversimplification, but that information is what is most likely relevant and interesting for your case at this point.
The commands you posted will sort the interrupts and output the one with the highest count (via head -1), thereby determining the interrupt that gets triggered the most. It will then disable that interrupt via the user-space interface to the ACPI interrupts.
One of the goals of ACPI is to provide a kind of general hardware abstraction without knowing the particular details about each and every hardware device. This is facilitated by offering (among other things), general purpose events - GPEs. One of these GPEs is being triggered a lot, and the processing of that interrupt is what causes your CPU spikes.
The changes you made will not persist after a reboot.
Since this is handled by kworker, you could try and investigate further via the workqueue tools: https://github.com/torvalds/linux/tree/master/tools/workqueue
In general, Linux will detect if excessive GPEs are generated (look for the term “GPE storm” in your kernel log) and stop handling the interrupts by switching to polling. If that happens, or if the interrupts are manually disabled, the system might not react to certain events in a timely manner. What that means for each particular case depends on what the interrupts are being responsible for - hard to tell without additional details.
It’s not like Bluetooth started demanding location permissions, the conceptual model of the permission was revised: having access Bluetooth means an app could determine your location via a form of lateration.
In earlier versions of smartphone operating systems, this was not transparent to users lacking the technical background, so Bluetooth also requiring location access is actually an attempt at making users aware of that. I’m not an iOS developer, so I can’t comment on iPhones, but on Android versions prior to 11, having access to Bluetooth meant an app would be able to determine your location.
Today, you can require the permission ACCESS_FINE_LOCATION, which expresses that your app might use Bluetooth to obtain location information on Android. Also, if you’re just scanning for nearby devices to connect your app to, but don’t want users to be confused why your smart fridge app needs to know your precise location, you can declare a permission flag (neverForLocation) and Android will strip beacon information from the scan results, better asserting your intentions.
So, overall: no, there is nothing nefarious going on, it was always possible to determine your location via Bluetooth, and the update to the permission model was an honest improvement that actually benefits you as user.
Now, there are still plenty of shady apps around, and apps that are poorly written - don’t use those.
If you’re open about your own sexuality, this is just a funny story. They share a fun fact about a common experience, the idea being that a majority of the audience is familiar with masturbation and can therefore relate to the frustration of not achieving the experience they initially envisioned.
Coming up with the pun of acoustic pussy is just a witty remark they deemed clever enough to add it to the story.
Yes, that is absolutely correct.