BiggestBulb

Hello,
I'm quite new to the idea of dual-booting, and I have a new Lenovo Legion Slim 7 which I would like to dual-boot on.

I definitely know that Thinkpads have better Linux compatibility, but Thinkpads would not meet my main use case for this laptop (hence my choice). It's also got an Nvidia GTX 4060 in it, which will probably not be optimal from what I hear (so any tips on that are much appreciated as well!). At least it has an AMD Ryzen.

That being said, I would love to use Fedora Silverblue / Kinoite alongside Windows. I know the docs say it will come with some difficulties, but I am willing to give it a crack given some of the latest comments on the issue tracker (https://github.com/fedora-silverblue/issue-tracker/issues/284#issuecomment-1869828571).

How would I go about actually shrinking Windows 11 down to make space for Fedora? Is "partitioning" the right word to use here?

It seems there are a million tools out there for this, but I would like to try to avoid extra tools for it unless there is a really reputable and easy-to-use one (just to avoid bloat).

After I shrink the partition, is it then just a matter of running the installer and using automatic partitioning with the unused space left over after shrinking Windows?

I'm a developer, but honestly the simpler you can explain this process, the better (I'm a web developer with very little experience dual-booting anything at all and have no clue how this process should go down).

Thank you!

Edit: I'd also love to know what kind of issues the docs are actually warning about as far as dual-booting. Will Windows wipe the bootloader on update or will Silverblue / Kinoite wipe Windows out somehow? If it's Silverblue wiping Windows out, that may cause me to go with a different distro - but if Windows wipes Silverblue, it'll be annoying but not a deal breaker (I plan to use Silverblue / Kinoite for development exclusively, so everything will be on GitHub).

With the abandonment of Artemis (formerly kmoon), kbin is now only really usable by the mobile site. The site is really not suited for mobile devices however, and there have been minimal user-facing changes in the last few months.

I know Ernest is trying his best, however with the current pace I worry about growth (and I'm not alone, as shown by mbin). If there is another Reddit exodus, for example, or if we get a surge due to the Threads thing, I feel like many will just turn back due to the UI alone. Some of the gripes are below:

• With the "+" button, what is the difference between the four types? I know the answer (as do experienced kbin users) but it is not "newbie friendly"

• When you go back, you are forced to randomly scroll up and down the feed to find the post you were just looking at (this has been an issue for months)

• Images load when they enter the viewport instead of just before (also, images are not cached and as a result they need to load again when you back out of a post, leading to excessive data usage)

• A slight but very noticeable lag when backing out of posts or clicking on them (presumably while data fetching is happening)

... etc. There are more (such as issues with certain HTML / code templating stuff, seeing "span" and other tags instead of the actual code block), but these are the main ones in my eyes. I was assuming that there would be fixes by this point for these sort of issues, but I haven't noticed the interface change for a hot minute and it's seriously hampering the experience (as a solely-mobile user).

When can we expect stuff like this to be addressed? I don't mean to be a downer or belittle the efforts by the kbin contributors (I love kbin, that's why I care enough to make this post!), but this has all been consistent since July and I worry that these will just become cruft that never gets addressed and will simply be something new users need to "deal with" or "learn", when we are the only site that has this unusual flow and these bugs.

Thank you!