I realize that the major point of GIMP 3 is the port to GTK3. That said, I feel like colour spaces are what people have been waiting for and probably the most significant deficiency that keeps GIMP from being treated as a professional tool.
If they are really this close, why not set the GIMP 3 release date for when colour management is ready?
Non-destructive editing will be huge as well. GIMP 3 is really going to be a crazy leap forward. It is going to be amazing to finally get access to all this work that has been walled off for decades.
The bug situation sounds terrible. Honestly though, they should just get 3 out and then make bug fixing the number one job until it gets into better shape.
Not only is it a small team but right now there are basically two different projects ( 2 and 3 ). With only one code base, perhaps the pace of progress can improve.
So you're saying: don't release the GTK 3 port until colour spaces are also complete? Why not give people what's ready, and then when colour spaces are ready, cut another release? No need to make people wait who don't need colour spaces.
(Additionally, it's easier to verify that bugs reported before the release of colour spaces are more likely to be related to the GTK3 port.)
Colour spaces are ready. They are saying I may be hard to wire it up in all the right places in a month. Why not take two months and get it in? I mean, it has been over a decade already.
Many people have been waiting for 3.x for literally half their lives. To save a month, they are going to launch 3.x with the big change being the toolkit? Seems like a wasted opportunity.
If it were going to be 6 months or more I would agree with you. From the write-up though, they delay would only be a few weeks.
Absolutely, Pop!_OS is literally made to just work™. I would recommend it in a heartbeat to anyone looking to get into Linux. The out-of-the-box experience is probably second-to-none.
We can do that when it's actually released; blogspam tries to publish on the expected release date before the actual release so it can scoop up the clicks. Release notes should be posted here later: https://www.mozilla.org/firefox/120.0/releasenotes/
When I dual boot Linux and Windows, I like to have two separate drives and not ever mix up the bootloaders. I then use my motherboards boot selector to choose which one, and I leave the main OS as the first priority one.
Works perfectly, avoids Windows overwriting Linux and avoids GRUB breaking for the 11th time this month because it’s a terrible piece of software. The only downside is it takes 10 seconds longer, because whenever I want to change I need to wait for my motherboard to recognize the boot selection key.
I have never had grub break on OpenSUSE in 6+ years. But also i install OpenSUSE after Windows and with its own boot partition. it finds windows and adds a chainloader grub entry. Set OpenSUSE as default in bios. Windows never knows it is chainloaded and leaves your linux boot alone
You can potentially get sudo on Android, but the ability to do so largely depends on the device. I guess there may be some devices which run on Linux and lock the user out from installing their own version or accessing super-user, but that’s a lot less common.
I would say that Android is not Linux, but it is based on Linux. The ACK is a based on the core Linux kernel, but with additions that aren’t found in mainline and a fairly different userspace and lack of a GNU C library. They’re more like cousins than siblings at this point.
Troll post or shill, same account recently asked "why do people dislike google, they're only doing legal data saving for stuff you search" and then ignored every bit of legitimate croticism that was handed to them.
Codeberg is a public non-profit Forgejo instance hosted by the actual maintainers of the tool. They’re compromised with free software and provide their services with no pay walls other than a single limitaiton: only accepting open-source projects in their instance. That shouldn’t be a problem if you want to work on open-source, right?
Forgejo is developed by the people at Codeberg, they just rebranded their own Forgejo instance to Codeberg and added some extra around it (like Pages or the FAQ sections)
GitHub uses Git, and you don’t need any cool interface for Git, just a terminal. But we don’t like terminals, they’re ugly! Issues, pull requests, projects, wikis, actions… thanks to code management.
So, strictly speaking: yes, almost any computer that was ever capable of running Linux should still be capable of running the newest kernel version, with the sole exception of 386s.
Whether it can actually do anything useful beyond getting to a command prompt on a serial terminal is another issue entirely.
They actually discontinued quite a few architectures (in total 15 architectures). But all of them where cancelled, because nobody in their right mind is still running them if not for a youtube video.
Sparc Sun-4, SPARCstation and SPARCserver are probably the best-known ones after 386.
So, strictly speaking: yes, almost any computer that was ever capable of running Linux should still be capable of running the newest kernel version, with the sole exception of 386s.
So the 286 and 8086 are still compatible, then? :P
What about chips from other ancient architectures? Can I run the latest version of Linux on a 6502?
So the 286 and 8086 are still compatible, then? :P
No. My comment was carefully worded: if it could ever run Linux, then it still can (unless it’s a 386). Mainline Linux has always required an MMU, so 8086 and 286 were never capable of running it to begin with! 🤓
This. My spouse is working on an online business and needed a laptop to carry around to do inventory with. I happen to have an old Asus 32-bit Celeron netbook collecting dust, so I gave it a bit of a wipedown, installed the latest version of Debian with XFCE on it, and let them install what they needed from there.
So if you get a 64-bit machine AT ALL, it will absolutely run the latest versions of Linux.
(Why is this a thing?
Lots of computers in industry are very low-spec. They use less power and have fewer requirements. As long as there are people who use that hardware and/or are willing to port fixes and new kernel features to it, it’ll keep getting updates. You only run into the ‘dropped compatibility’ thing when really no one is using it.)
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.