And they switched to a resolution one that can’t even Integer-scale, and, even worse, isn’t even the correct aspect ratio.
Personally, I’ve seen a few people doing similar things, and to me it’s always an indicator that the person needs to get their eyes checked. Any person with good eye sight or well adjusted glasses should immediately notice that the text actually becomes blurrier and harder to read despite the increased text size.
It’s so weird. I can kind of understand this level of ignorance on other platforms, but here? The platform a majority of the people actively sought out because they saw what happens when a walled gardens starts turning against its users?
At the very least, I would’ve expected better arguments than “I don’t want this, so I oppose other’s from having that option.”
Yup. Even assuming this would actually work as advertised, who would actually buy this over a regular printer?
Like, how often do you run into a situation where you need something 3D-printed while on the go, but simultaneously have enough free time to set this thing up in a protected area and wait a long time for the print to finish? Not to mention that you just happen to have brought with you the proper filament as well.
Furthermore, this thing…:
Not sure what you’re seeing there. The Bedrock edition is also available on PC and the rest is a direct quote for the reasoning why that version gets it before the Java version.
It’s not like they’re forbidden from acknowledging the existence of other devices either. It’s just not their target audience.
In the README there’s also instructions for Docker Compose, although it’s quite the compose file, with SIXTEEN containers defined. Not something I’d want to self-host.
Oof. I’m already put off when I see a compose file that has more than like 3 containers, but that one really takes the cake. Two message brokers, two proxys, three webservers, two daemons and another handful of other containers? That’s, indeed, truly insane.
Just because it’s now easy to deploy giant stacks of server software doesn’t mean you should.
Not necessarily. A good architecture could allow for crossplay between different kinds of accounts. They’re just taking the easy way out.
I just run some self hosted servers. I most definitely run more than ten services, not few of the consisting of multiple containers. With this change I’d basically hit the limit every time I do maintenance and pull the latest versions of all the images I run.
Yup. I hate to admit it, but the only reason why I’m currently running a custom firmware again is because my current banking app plays well with GrapheneOS. Otherwise I’d probably not bother. Being able to use a banking app is just too convenient (for me personally).
So, this “advanced protection” mode prevents me from installing apps from non-PlayStore sources and developers could design their app in a way that requires this mode? So if someone is reliant on a single app requiring this mode then they would essentially have to get rid of all “unwanted” apps? Why do I think this “advanced protection” isn’t actually intended to protecting the user?
I really hope these checks can be circumvented, but even more that this will get them some EU lawsuits.
Can recommend as well. I recently checked what’s out when it comes to anything terminal-related and for the multiplexer I landed on zellij. Works well, looks neat, is easy to learn and well configured out of the box.
My current stack looks like this:
Depends. There’s also the included archinstall script, which skips all of that. Just some minimal configuration you find on most distros (Language/Time Zones/Mirrors…) and that’s it.
So yeah, nowadays it’s totally possible to end up with a working Arch installation without knowing anything about it besides that one command.
Exactly. When purchasing any modern device I ask myself as to how much a company can screw me if they turn hostile out of nowhere. If I can’t handle that risk, I don’t purchase that product. Not having open source firmware that’s connected to the internet is a huge red flag.
You would think that everybody owning a 3D printer would at least be somewhat of a tinkerer and therefore oppose this. Looking around however I’ve already seen a frustrating amount of people ridiculing the people calling this out. You’re probably right though and the people who don’t care will probably mostly have gathered around Bambu.
If anything I’d say that the lesson to be learned from this should be the exact opposite: No company is safe forever, so you should choose based on how easy it is to switch.
Chaining yourself to a single company all the way from the services you use down to the OS and even the hardware is only making it worse. Particularly when Apple is already aggressively anti-consumer on a lot of fronts.
Why did somebody actively edit out her name?
In this case it was most likely she herself. The original black and white comic has the name, but the colorized version was most likely been taken from her shop (link), which doesn’t feature the name.
I’m however impressed by how utterly the person copying the picture messed up the picture. Not only is the crop completely awful, but they also tried to “restore” the comic by giving it a digital look, over-saturating everything in the process, including the JPEG artifacts of the original photo.
On the other hand, NVIDIA has started to consolidate all these technologies as the NVIDIA DLSS suite a few months ago for some reason.
So it’s DLSS Super Resolution and DLSS Frame Generation, DLSS Ray Reconstruction and so on, with the exception of DLAA. Probably because that would get too stupid even for them.
Ok, I’m intrigued but looking it up there’s apparently a few GitS things in 3D/VR:
I’m guessing you’re talking about the live movie, but now I also want to know how an anime would look like in 3D.
Year-based version numbers are pretty neat IMO, particularly for applications. Not only can you quickly estimate how up-to-date any particular application is, it also avoids the version number racing problem between competing applications, because some people equate lower version numbers with a less developed application.
For programming libraries though semantic versioning is still the good ol’ reliable.
I’d be wary of that fork. It’s run by a former Thunderbird dev that got banned for his toxic attitude and hasn’t really improved since. Just take a look at the projects website. Being so unrespectful towards your upstream project should have no place in open-source.