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.

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.

honey bees are bad for pollinators

Hm? What do you mean?

From this paper:

A. mellifera appears to be the most important, single species of pollinator across the natural systems studied, owing to its wide distribution, generalist foraging behaviour and competence as a pollinator.

This is a genuine question btw.

I shudder to think OP’s post was written by an actual person…

What’s a good way to financially support artists directly, without involving shady corporations, and without resorting to piracy?

Jokes on you, I look her up once a year to see what she ended up doing. I’m 100% her name is Danielle.

This, however, is about diagnostics, i. e. annotating delete with a reason (message) to express developer intent when deleting a function, not about memory management.

You share a room with the maid?

Side note: please don’t abuse the word “toxic” until it becomes absolutely meaningless. Let’s keep that to a more fitting context, having a

I was expressing an obviously personal opinion about the language itself, which is objectively a dull, barren wasteland that sucks out your soul while you walk it. That is precisely the reason why it’s so widespread and loved by business entities and managers - there is no excitement, no surprises, just an everlasting monotony of keys clicking produced by a horde of clones wearing button-down shirts while sitting in absolute identical cubicles, creating yet another instance of FactoryProducer. It’s very easy to plan and schedule for, while at the same time being unnecessarily verbose and mildly unproductive (compared to other languages).

Look, the JVM is fine, just pick another language. There is plenty of work doing Kotlin. But yes, if you’re doing this only for the money, go ahead. I’ve always been unable to separate my job fromy personal life and my other interests, I couldn’t imagine being cursed by Java again.

If you can sit somewhere for 8 to 10 hours each day, doing something that isn’t fun and separate yourself from it, not going insane, all the power to you. I also get that not everyone has the luxury of picking their favorite toy and making it their job, but I firmly believe there are options that are not Java.

Now, if you’re one of the rare types that actually enjoys Java, meet me in the closest Denny’s parking lot, I need your cranial measurements.

Please note: this post contains hyperbole and humor. I don’t hate any of you, I just hate Java

My personal recommendation:

• Pick up Python, it’s easy to learn and highly productive. If you also learn fastAPI, you can benefit from highly validated, declarative models to build REST APIs in the backend, well fast. It will yield quick results, you won’t become demotivated and you can pick up a paid project soon.

• Pick up Rust. It’s “in” right now and I get requests from marketing people that know nothing about programming, asking if their project could be implemented in Rust

• Go with memorizing the shell commands first, try to understand git later. Get productive, try to get where you were with e. g. svn or cvs. If you are comfortable, look at something in depth if you have a problem that you can’t solve with the knowledge you have.

• Fuck Java, seriously.

• You have commercial interests, so it is probably wise to look into becoming a fullstack dev to maximize the kind of projects you can do. Look into React, vue.js, svelte. React is probably still the most widely used framework, you’ll quickly do a project with vue.js and svelte is a super interesting look into things to come.

Sure. In my opinion, however, the overall context of the image does imply the jaguar enjoys similar effects to those clearly requiring the presence of DMT, as that is what is most people commonly associate with ayahuasca.

It’s a bit of a “look at all those animals getting high, this jaguar is even talking to machine elves in the 19th dimension” kinda thing, where - if I remember correctly - they actually consume the leaves for digestive purposes.

Again, the leaves do have an effect, e. g. they apparently act as an SSRI (that’s how common antidepressants work) and we can’t be absolutely sure about their effect on cats (catnip certainly has some effect on cats we don’t readily enjoy), so I can’t dismiss the notion of jaguars seeking them out for that reason as well.

Jaguars actually eat the leaves of b. capii, which acts as a MAOI in the Ayahuasca brew.

While there is some discussion that the harmala alkaloids in b. capii might also be slightly psychoactive in high doses, the actual main compound in Ayahuasca is DMT, which is certainly very psychoactive, but not bioavailable when consumed orally without a MAOI. Unless the jaguars have figured out how to combine the two and/or brew ayahuasca, I strongly doubt that’s their intention and that they’d get comparable effects.

I think the idea stems from the BBC show Weird Nature showing a jaguar eating yage leaves in episode 6, “Peculiar Potions”.

I’m not really sold on how well that content was researched.

That dude is joking of course, but touching someone in a subtle manner can be used to both express and indicate interest.

If all else fails, entangle him with silk and consume him.

Yeah, that’s the implication. Unfortunately, that is also misleading people into believing they might get a well-tested, nearly bug free game.

At 7h / day of just testing, 200k hours amount to approximately 110 years, given 260 working days per year.

Veilguard has been in development for around 9 years, so thats about 12 “years of testing per year”, so pretty much at least 12 people doing nothing else but testing (this assumes sane working conditions - hi EA!)

Given how long the game has been in development, what does that number even mean? How much of the stuff they wrote 9 years ago is still in place, given that players would expect the technological advancements available since 2015.

Also, it’s supposed to be released end of October, I believe? Or has it been postponed even further (again)? Anyway, why would they claim something like that before release? That will probably backfire.

You mean the company that had a feature in place that allowed law enforcement to request and access video footage from your devices without obtaining a warrant first?

As expected, their security measures were also found to be lacking.

Yeah, no thanks.