With the exception of maybe Princeton or Columbia, top research isn’t coming out of Ivy League schools.
Doesn't Harvard have one of the most advanced medical programs in the entire world? Perhaps the best even. Especially in fields related to cancer research.
"Pay money, receive happiness" is just so typically corporatist. Ridiculous, absurd amounts of money. Sometimes, more than an entire family makes in a whole year.
Even better when it's used as a blackmail for children's happiness. Trying to make it seem like spending 5 figures USD is some quintessential part of life, otherwise your children will not have a complete childhood.
21st century economics at its ~~worst~~best here, everyone!
Oh I guarantee you, the Disney Corporation has a very sophisticated shadow marketing operation
The full write-up can be found here and should be fairly readable for users of this forum.
Some quotes that I thought were interesting:
With a heap corruption as a primitive, two FILE structures malloc()ated in the heap, and 21 fixed bits in the glibc's addresses, we believe that this signal handler race condition is exploitable on amd64 (probably not in ~6-8 hours, but hopefully in less than a week). Only time will tell.
So 64-bit systems seem to be a bit more resistant to this it seems? But I can't be completely sure given how much I've read about this yet.
This vulnerability is exploitable remotely on glibc-based Linux systems, where syslog() itself calls async-signal-unsafe functions (for example, malloc() and free()): an unauthenticated remote code execution as root, because it affects sshd's privileged code, which is not sandboxed and runs with full privileges. We have not investigated any other libc or operating system; but OpenBSD is notably not vulnerable, because its SIGALRM handler calls syslog_r(), an async-signal-safer version of syslog() that was invented by OpenBSD in 2001.
It seems that non glibc-based systems also could be vulnerable, but they have not yet tried to demonstrate it yet (or have tried and not been successful).
And OpenBSD wins again it seems.
I would vote for docker as well. The last time I had to inherit a system that ran on virtual machines, it was quite a pain to figure out how the software was installed, what was where in the file system, and where all the configuration was coming from. Replicating that setup took months of preparation.
By contrast, with Docker, all your setup is documented. The commands that were used to install our software into the virtual machines and were long gone are present right there in the Docker file. And building the code? An even bigger win for Docker. In the VM project, the build environment for the C++ portion of our codebase was configured by about a dozen environment variables, none of which were documented. If it were built in Docker, all the necessary environment variables would have been right there in the build environment. Not to mention the build commands themselves would be there too, whereas with VMs, we would often have developers build locally and then copy it into the VM, which was terrible for reproducibility and onboarding new developers.
That said, this all comes down to execution - a well-managed VM system can easily be much better than a poorly managed Docker system. But in general, I feel that Docker tends to be easier to work with than a VM. While Docker is far from flawless, there are a lot more things that can make life harder with VMs, at least from my experience.
Do you know how vim has distributions like lunarvim, lazvim, nvchad, etc.? Simply installing something like lazyvim can quickly and easily convert vim from a text editor to a full blown IDE.
I think Gnome needs something like this. A curated set of plugins that are easy to install and maintain compatibility with different versions of Gnome - something that would deal with the API churn in Gnome while maintaining a stable, usable desktop environment.
I don't know if this is feasible, because I haven't used Gnome since 2.x, but I think it would really help make it an actual full blown DE.
I doubt that you're interested in arguing in good faith, but if by some miracle you do care about having an informed opinion before opening your mouth, how would you respond to things like this?
This essentially killed my (EU-based) startup in the project management and collaborate space. Before MSFT bundled Teams with O365 we were rapidly growing and closing enterprise customers in the automotive, energy and education industries with high retention rates. Right around the time the Teams bundling started our retention dropped, churn went through the roof, growth slowed down, we failed to raise our next round because of it and had to drastically downsize the company, causing even more churn (about 80% net churn in 2 years). This move by the EU is good, but too little too late - 99% of the companies that were hurt by this have already shut down, and the ones still running will take years to recover...
Interesting! Sorry, I don't know why I thought you were using swipe keyboards, it must have been stuck in my memory from reading other comments. I definitely agree that pressing the buttons was a little annoying, but manufacturers could probably make softer buttons if they were willing to put the money into developing them.
Anyway, I really miss the phone I had from about 2008-2010. It had two sliders that moved in orthogonal directions. One of the slide directions revealed a standard 12-button phone pad, while the other had a 4-row keyboard. And yet, I'm pretty sure it was under 1.5cm, so not too large. It was definitely easier to keep in my pocket than current phones!
If it weren't for reading Lemmy/RSS feeds and a camera, I'd probably be going back to dumb phones for my next one...
I just use the lazy plugin manager (not to be confused with lazyvim) to set up a few plugins for my environment. I followed this guide and just chose only the plugins and configuration that I like. I've used vim for over 15 years now but have only used plugins for the past 2-ish years, so I don't like it when distributions mess up existing keybindings and other default behaviors. Lazy makes it very easy to set up your own environment and I was able to learn how to do it in a relatively short time with some guides and tutorials.
It's not for the faint of heart, but for me, I think the personal customizability is worth it, as well as not having plugins installed that I don't want/need. A lot of the time, they're more modern, but they would also require unlearning my existing habits and learning new ones, which I would rather not do, so I prefer doing it this way.
But I will say that it can be helpful to look at existing distributions to see how they implemented configurations when I run into trouble with my own configurations. Sometimes I'll steal their keybindings and maybe adjust them to my own preferences. It's also a great way to explore new functionality and configuration options as well.
But what's the error rate? I could type at 200 words per minute (even on a phone!!) if I didn't care about how many typos I was making. And swiping keyboards get confused incredibly easily. The error rates are especially bad when you're writing words that only use a single row of keys - on QWERTY keyboards for example, try writing something like "type", and you could get that, or you might get something else, like wipe/write/ripe. Other groups could include things like tip/top, pit/pot, wit/wire and the selected word will be wrong almost as frequently as it's right. And autocorrect systems can't really correct for things like when you mean to press enter and hit the backspace key instead. Plus, their suggestions are generally just very stupid. So while buttons take longer to press on physical keyboards, the reduced error rate makes typing speed about the same in my experience.
Plus, with physical buttons, you get tactile feedback, so you can tell when your fingers are slightly off and adjust them, whereas on a flat surface, you have no idea whether you pressed the correct button or not. You have to stare straight at the screen to make sure every press is correct, which is exhausting and bad for your eyesight. I feel a lot more eyestrain from simply typing on phones, whereas with physical buttons, I didn't even have to look at the screen, and I could look at something else around me while typing. And don't get me started on how many calls I've missed because I accidentally hit the hang-up button, or couldn't find the accept call button - not a problem when you have physical buttons!
Regarding screen real estate, all you need is a slide-out keyboard. They work great!
There are a few downsides to physical keyboards, but in my experience, they're far superior to non-keyboard devices. But what can you do - in the 21st century, practicality never matters, it's just all about aesthetics and nothing else....
Just in case this comment didn't make it explicitly clear, you can just invoke the python binary inside your venv directly and it will automatically locate all the libraries that are installed in your virtual environment.
To show how this works, you can look at the sys.path variable to see which paths python will search for modules when you run import statements. Try running python3 -c 'import sys; print(sys.path)' using your system python, and you will only see system python library paths. Then, try running it again after replacing python3 with the full path to the python3 binary in your venv, and you will see an additional entry in the output with the lib directory in your venv, which shows that python will also look there for modules when an import statement is executed.
Can I interest you in links?
Or how about lynx?