I'm a 6th-grader who likes coding and lately, I've found myself relying way too much on AI for it, and so I decided to learn a new programming language.

I am already familiar with Python, but I am far from good. My best program was literally just a [yaml shopping list thingie](http://github.com/ItzOratotITA/hyperlister) that only worked when run in its own directory.

First option was JS, since it does play a main role in web dev, and I have a [website](http://www.oratot.com) where I host existing utilities but most of the javascript is AI generated.

But C seemed way too essential. So I tried learning it using ChatGPT's Study and Learn thingie (it was basically my only option). It got confusing very very quickly. And I guess that's the point, C is like the first layer of abstraction after machine code/asm.

Everywhere I went I heard that I should learn C before Rust, but Rust was really really appealing because it is really future proof and had all the C++ features like classes, except it was not a mess, but most importantly there are A LOT of Rust projects (like PommeMC or Paru) that I would really like to contribute to once I reach a certain level of skill. So I tried it.

Both the C stuff and the Rust stuff happened in 1 day (yesterday) and I liked Rust a lot. Basically, my equivalent to hello world when learning a programming language is making a [silly little quiz](http://github.com/ItzOratotITA/quiz), so I have to learn how to do if statements, loops, etc. and that's where C got confusing.

Is the code I wrote there good?

Should I learn another language instead of Rust?

Should I just learn C anyways?

What's a good way to learn Rust?

https://www.gameslearningsociety.org/can-you-play-super-mario-odyssey-on-pc/

{

EDIT FROM 4H LATER: This website once was legit, but the domain changed and now it is an SEO website, but the legit one still gets associated with the old domain. That's why I got worked up about it.

I think the next step is obvious:

Meet Glorbo, the new boss in Super Mario Odyssey

}

This webiste also uses WordPress, and their comment submit page is broken and gives a 404, so I am going to reply here.

1. Most well-known unofficial PC ports (not fan recreations like Super Mario Bros. Remastered) are ports created using the decompiled/reverse-engineered code of the game, as Nintendo's games, which are commercial, are not open source. This means that to decompile the files, lots of people spent years of their lives, and at the end, if you compile the obtained code, it traditionally must match the original game's file. PC ports based on this work can offer major technical improvements, such as higher resolutions, better framerates, widescreen support, improved input options, and modding support, often making them technically superior to the original versions. They are not automatically inferior just because they are unofficial. Even fan recreations, such as Super Mario Bros. Remastered, are widely considered superior to their original version, and people should stop hating on these just because they are unofficial, and instead think about the effort that went into them.
2. Emulators themselves are not inherently illegal, and using a personally dumped copy is legally distinct from downloading ROMs, though laws vary by country and Switch dumping can involve anti-circumvention/ToS issues.
3. Super Mario Odyssey is currently being decompiled, and it is plausible that it will be finished in the next few years. So, the claim is partially correct, as it is not coming in the near future. The writer(s) likely couldn't have known that at the time of this article's release. A game being fully decompiled, though, doesn't mean it will run on PC. A PC port would still require additional porting work after or alongside the decompilation. That said, a future PC port is likely if the decompilation progresses far enough and people choose to build one.
4. The games listed in the table are not officially playable on PC, though the first two do have unofficial PC ports.
5. "64-bit graphics" is not a thing. If referring to the console's CPU architecture, although the Nintendo 64 is a 64-bit console, Super Mario 64 is a 32-bit game like most N64 games. "8-bit" graphics has now become a term to describe an artstyle, but in reality, 8-bit refers to the architecture of the CPU of the device. An example would be the SEGA Master System, which was 8-bit, but had graphics most people associate with 16-bit devices.

TL;DR: This article is more misleading than helpful, and writers should do more research before putting out such an inaccurate article that even calls the outcome of years of work to conserve and improve iconic games inferior to the original.

Here are my mods:
 appleskin-fabric-mc1.21.11-3.0.8.jar
 architectury-19.0.1-fabric.jar
 Axiom-5.4.2-for-MC1.21.11.jar
 BadOptimizations-2.4.1-1.21.11.jar
 better-ping-display-fabric-1.21.11-1.2.0.jar
 betterstats-5.1.0+fabric-1.21.11.jar
 capes-1.5.10+1.21.11-fabric.jar
 centered-crosshair+1.21.11-1.4.0.jar
 chatanimation-fabric-1.21.11-1.1.3.jar
 cloth-config-21.11.153-fabric.jar
 continuity-3.0.1-beta.1+1.21.11.jar
 controlify-3.0.0-beta.3+1.21.11-fabric.jar
 Controlling-fabric-1.21.11-29.0.1.jar
 CrosshairAddons-2.1.0-1.21.11.jar
 cwb-fabric-3.0.0-build.14+mc1.21.11.jar
 dynamic-fps-3.11.6+minecraft-1.21.11-fabric.jar
 effecttimerplus-fabric-2.2.7+1.21.11.jar
 entity_model_features_1.21.11-fabric-3.2.2.jar
 entity_texture_features_1.21.11-fabric-7.1.jar
 entityculling-fabric-1.10.2-mc1.21.11.jar
 Essential_1-3-10-8_fabric_1-21-11.jar
 fabric-api-0.141.3+1.21.11.jar
 fabric-language-kotlin-1.13.11+kotlin.2.3.21.jar
 fast-ip-ping-v1.0.11-mc1.21.11-fabric.jar
 ferritecore-8.2.0-fabric.jar
 Flashback-0.39.5-for-MC1.21.11.jar
 ForgeConfigAPIPort-v21.11.1-mc1.21.11-Fabric.jar
 Gamma-Utils-2.5.10+mc1.21.11.jar
 ImmediatelyFast-Fabric-1.14.2+1.21.11.jar
 iris-fabric-1.10.7+mc1.21.11.jar
 lambdynamiclights-4.9.1+1.21.11.jar
 LeaveMyBarsAlone-v21.11.0-mc1.21.11-Fabric.jar
 lithium-fabric-0.21.4+mc1.21.11.jar
 'Marlow Crystal Optimizer.jar'
 modmenu-17.0.0.jar
 moreculling-fabric-1.21.11-1.6.2.jar
 myresourcepack-1.2.7+1.21.11.jar
 naturalmotionblur-1.4.1+mc1.21.11.jar
 notenoughanimations-fabric-1.12.2-mc1.21.11.jar
 notenoughcrashes-fabric-4.4.9+1.21.11.jar
 packetfixer-fabric-3.3.5-1.21.11.jar
 placeholder-api-2.8.2+1.21.10.jar
 PuzzlesLib-v21.11.12-mc1.21.11-Fabric.jar
 reeses-sodium-options-fabric-2.0.3+mc1.21.11.jar
 'Resourcify (1.21.11-fabric)-1.8.1.jar'
 Scribble-2.0.0-beta2+mc1.21.11-fabric.jar
 Searchables-fabric-1.21.11-1.0.4.jar
 ShieldFixes-2.0.2-1.21.11.jar
 ShieldStatus-4.1.2-1.21.11.jar
 shulkerboxtooltip-fabric-5.2.16+1.21.11.jar
 skinlayers3d-fabric-1.11.1-mc1.21.11.jar
 sodium-extra-fabric-0.8.3+mc1.21.11.jar
 sodium-fabric-0.8.11+mc1.21.11.jar
 StrawStatues-v21.11.0-mc1.21.11-Fabric.jar
 symbol-chat-1.21.11-1.3.13.jar
 tcdcommons-5.1.0+fabric-1.21.11.jar
 totemcounter-1.11.2+mc1.21.11.jar
 ukulib-1.10.2+1.21.11.jar
 ukus-armor-hud-0.10.2+mc1.21.11.jar
 ViaFabricPlus-4.4.12.jar
 voicechat-fabric-1.21.11-2.6.17.jar
 vt-downloader-2.4.1+1.21.11.jar
 WalksyLib-0.9.992+1.21.11.jar
 waveycapes-fabric-1.9.2-mc1.21.11.jar
 xaerominimap-fabric-1.21.11-25.3.12.jar
 xaeroworldmap-fabric-1.21.11-1.40.16.jar
 XaeroZoomout-Fabric-1.21-2.0.0.jar
 xlpackets-1.0.5-1.21.jar
 yet_another_config_lib_v3-3.8.2+1.21.11-fabric.jar
 zoomify-2.15.2+1.21.11.jar

This was copypasted from a ls -1 command so that broken symbol is supposed to be a java logo

I also have a no text version. Would that be better?