I look at them both the same way...and it's the bottom frame

Yes, you CAN stop there, the other qualifiers I added were specifically because C sort of assumes those to be present and while there are C to bf compilers they emulate that functionality on top of the more restrictive, but turing complete, architecture. I was listing the things C assumes/requires the hardware to be able to do for reasonable performance and compilers not emulating features.

These are not language features but features of the C standard library and are only required if you wish to use said library, they have little to do with hardware requirements or the language itself

You aren't wrong but classically a high level language is one that is abstracted from the hardware which is precisely why C is considered high level. You don't have to think about registers, instructions, stacks, etc, you just call functions with arguments and write "high level" code. It's on the lower end compared to modern very high level languages but it's still considered high level. Classically most non-assembly languages are.

Yeah, I get both sides too, I also want Linux to be successful but I'm just disappointed this is what we're resorting to. Although I guess as long as I don't have to use it it's probably for the greater good?

Yeah, that would be a much more consistent setup and I agree with everything you said here. I just don't understand how being less programmable is good, it isn't, I don't see any world in which it is unless there is truly NO firmware involved and it's pure HW.

Why does it look almost identical to iOS, I hate it

YTM has basically always been bundled with premium. They recently raised the prices for grandfathered users but at the time the YTM bundle was introduced the premium price did not increase IIrc.

C is basically high level assembly. It's hardware agnostic high level assembly. I have written both, this is personal experience and also I believe even Linus has said EXACTLY that statement. It is an opinion ofc and you're welcome to disagree but it isn't just me.

I never said it was a policy but it's definitely true. Inline assembly IS still assembly. I'm saying if the code can be written in C it more than likely will be over assembly unless there is a very good reason to write it in ASM. The kernel is 97.97% C and just over 1% ASM. If that doesn't prove what I'm getting at Idk what else will. It's a totally different circumstance than replacing large swaths of C with rust or introducing large amounts of rust in favor of C.

Is that really easier than just responding to clicking things server side? Again I fully understand there are some use cases where that's just not possible but in my, admittedly limited, web development experience you can get a whole heck of a lot done server side with no JS at all

Discord I get because it's real time chat. Gmail I get less so, it has some real time chat stuff but the core functionality could be done with far less JS IMO. Maybe I just feel that way because I'm a JS minimalist. Unless the website's core function needs JS(real time chat etc) I'm a firm believer you should be able to disable JS and the website should not break.

I personally like to start with a debloated install and then install gnome on top rather than the other way round. Honestly to point 4 it slightly baffles me that people use vbox on Linux, KVM with libvirt/virt-manager is so much more powerful while still allowing for fairly straightforward basic setups without introducing 3rd party modules. Seems like a no brainer to me but apparently it isn't.

Cool that they're still running though. I've never setup a Linux system that I then had to turn over. They're all systems I maintain, I'm not entirely sure what my plan would be for a maintenance free machine that I expected other people to use.

I suppose that's true. I also don't install the predefined GUI options. I always install my GUI manually after disabling recommended packages. Recommended packages are my biggest Debian gripe. They're great for users that don't know what they're doing but for power users I find it kinda bloated. I should probably try flatpak again but last time I did it was just annoying and in the way and gave up.