I've had a couple of crashes, but nothing major. I just want to know why something has to impede me in some way for me to want it to be optional.
Just like the detailed error screen, I don't want to deal with that. I just want CFW that looks and acts like normal 3DS FW, just with those small behind the scenes benefits. There's no issue in wanting choice.
Here's the thing about Rosalina, and it's been explained before. In the past there were some bugs with it. That's to be expected. However, with the bugs ironed out now, it actually provides a better user experience for a lot of users. Not only that, but the code is cleaner and easier to maintain for the devs. On the note of "impeding" you, here's the thing about it; other than those crashes in the past, which are now
gone mind you, there is literally nothing about it that is impeding. There is a menu, but it is your option to bring it up. Otherwise, it will not affect you in any way that you could imagine. With regards to the exception screen, it actually does provide something convenient; first, and most simply, it provides a fast way to power off the console in the event one of these errors does happen; the 3ds OS actually requires you to hold down the power button for quite awhile, when you'd rather get on with your day. However, more than that, it allows the developers to provide you with a better experience in the case that you experience a crash. It maybe be that there is a bug, and being able to capture it when it happens and provide information on the screen, as well as in a file, is vital for finding and fixing bugs that can make a user's experience bad. In the end, you're free to use whatever version you like. However, if you aren't on latest, the bug may have already been taken care of, yet you're still experiencing it. That's why updating is recommended. It makes your life, as well as the developer's life easier. Imagine, you make something, and then later you discover there's an issue with it. Now, you, being the nice person you are, send out a fix for this issue, along with added things that can enhance the experience for the end user. Now, if the end user doesn't care to use the new features, they don't have to, and it won't affect performance. However, some users notice this new feature and don't like it. They decide to stick with the old version that has the problem. Weeks, months or however long in the future, these users start to experience the flaw that you attempted to fix with your update to the product, however, said users didn't actually use the update. Now those users are mad at you, and constantly filing reports with you. All on something that you had fixed very early. This is why it is recommended to update; because the developers knew that something might become a problem, and as such fixed it, while even adding something to make it better for users who wanted more from the it, while maintaining the status quo with the users who wanted to use it exactly how it was originally intended.Well, these CFW devs experience something similar. But they didn't get paid for their product. They provided hours and hours of work, to you, for free. The least you can do for them is read what they write, understand when they add new features and try to keep yourself up-to-date such that when you have a problem, it hasn't already been solved before, making undue work for the developers.
--------------------- MERGED ---------------------------
You say that like literally anyone can code. I got no idea how this stuff works. All I know is I play a sound file and 5 minutes later I have CFW.
One thing I do know is that variables and booleans and whatnot aren't hard to implement. It can't be hard for a dev to slap together a 'Rosalina Menu Toggle' build.
since this was posted while I was writing my above post, I'd really like to add; there's already a boolean for disabling the menu; it's called isButtonComboHeld. If this boolean is false, then, guess what, no more menu!! Man, if only you'd realized that earlier, maybe that could have quelled some confusion!
@
Sicklyboy:
@
BigOnYa:
