nira16-t

[nira16-t]

(Nearly) Never use auto in C++!!!

So I used to be amongst the people who thought "Yeah ok, auto hides the type. But if the type is not really important to understand the code, and was really long and confusing then it is worth it"

Like this: std::vector<std::pair<std::string, Employee>> MyFunction(); To turn it into: auto MyFunction();

And I was wrong. Do NOT use auto to hide that monstrosity. You FIX it. auto hides that awful thing and dumps the problem on the next poor fucker who will use it. ( People writing and using metaprogramming libraries are especially prone to doing this, since their typenames can fill entire screens ).

YOU just looked at YOUR code. Found it confusing... And decided... to HIDE it??? What it is the next person who did NOT write this code going to do when they read this going to do???

No. I beg of you. Use typedef.

You can create aliases of anything and make your code easy to read. And this only "hides" the code as much as auto and you can get the types the alias points to by musing over it. So it is auto... but way better. Because it is a UNIQUE name. Which can DESCRIBE things.

Like, with the horror in the previous example. Let us have a typedef in the .hpp file where "MyFunction" is declared. Now it reads MUCH better:

std::vector<std::pair< Employee_ID, Employee>> MyFunction();

I actually understand what the pair is now! Key value pairs! And screw it. Let us typedef the pair too now that we understand it!

std::vector<Employee_KeyValuePair> MyFunction();

And fuck it. Once more! Typedef the vector too!

Employee_Roster MyFunction();

I will bet most of you reading this only realized what the hell that moster was when you got near the end. BECAUSE THE FIRST THING IS FREAKING UNREADABLE! Fix it. Make your code readable. If you feel the urge to use an auto to hide a typename, it is time to typedef that motherfucker!

[nira16-t]

[nira16-t]

your bf looks like he doesn't even know how to access his appdata folder

[nira16-t]

moment of silence for everyone who relied on AI chat bots for research when it’s going around saying shit like this.

[image description: search that reads “country in africa that starts with K”. the featured snipped is from www.emergentmind.com and reads “While there are 54 recognized countries in Africa, none of them begin with the letter "K". The closest is Kenya, which starts with a "K" sound, but is actually spelled with a "K" sound. It's always interesting to learn new trivia facts like this.” /end ID]

[nira16-t]

main blog with pinned bio: @niratomata

[nira16-t]

I love you people who make open source libraries and release it to the public domain.

I love you people who make open source libraries and make it just one header file.

You are saving my tiny brain from having to comprehend licenses and form having to work with complicated include structures or building libraries.

[nira16-t]

in another timeline, the Starship Enterprise has some of these bad boys.

I board the starship enterprise. I go to a food replicator. I order ‘soup, no bowl’ I leave

[nira16-t]

i see way too many people calling stuff ai when its literally just..... hardcoded pattern recognition......

whoop de doo the thing you made for a specific purpose fufilled that purpose. thats not an ai thats just a program. shut up.

"oh this new ai powered webcam can zoom in on anything with these four squares on it!!" thats not a fucking ai thats image pattern recognition, all it does is scan the visible area for specific patterns, and once recognized, it zooms in. thats it. a fucking qr code scanner is more complex than that. its not ai. shut up.

"this logo maker uses ai to make images" no it doesnt. it randomizes images within the bounds of set fields and assets. its randomization giving a number of results to choose from. thats not fucking ai. shut up.

a real ai is a program that trains itself to respond to inputs "naturally" without instruction using trial and error, for example if an actual ai was to go through a maze,

step one, makes random movements

by making these random movements and bumping into walls, it learns that bumping into walls is an error

step two, explores randomly without touching walls

the ai doesnt know there is an end goal, however it will learn this if moving in a path that isnt directly connected to the exit is an error

step 3, the ai uses what its learned it should not do, and takes the path that is connected to the exit, and the task is complete.

ai is not pattern recognition, its learned pattern adaptation through time. ai is not randomization of assets. it is randomization with consequences that shapes it into a predictable behaviour. shut. up.

[nira16-t]

Tiktok is doing this Minecraft revolution thing. “Here’s a petition, we’re going to revolt and force the lazy Mojang devs to actually do something for once” And I’m like, “do y’all know how a revolution works?”They know the point isn’t to make the ruling party rule better right? It’s to remove the ruling party and replace it with something more preferable for the populace. They claim Mojang are lazy and they’re going to force them to “actually do their jobs” Shouldn’t they be striving to move past the need for Mojang? They’re revolting, they should be getting a team together to make their own 1.21 and add all 3 mobs. Mojang’s lazy right? So why try to make someone do something you believe they’re not doing? Why not make a new team of people that can do the things they believe Mojang should be doing better and faster?

Like it just seems weird to me how hot off the heels of the writer’s strike, 150K people have decided “actually this group of people isn’t working hard enough and they’re being overpaid for something I don’t want to do”

[nira16-t]

everyone bitching about the minecraft mob vote doesn't work in tech and it SHOWS

they're trying to let the fans into the early decisionmaking. The kind of thing that an eng team would otherwise do behind closed doors and the PM would probably make the final call.

They only have enough story points in the next quarter to fully implement ONE (1) new mob. How are we gonna spend that time? Here's a cute idea: let the fans tell us!!

If you don't love how the vote is implemented sure go off or whatever but if your counterargument is "they should just make all three", shut uppppp you must be being intentionally obtuse

"They basically did all the work already but are throwing away 2 of the mobs!!" No they literally didn't. They did a mockup, a short animation, and a one-sentence summary of what each mob does.

"How am I supposed to make an informed vote if they don't give me more details! The vote is meaningless!" I am holding you so tightly and kissing you on the forehead. The vote will determine which mob they actually spend time figuring out the details for. They have not told you the implementation details because they haven't made those decisions yet. You are voting on an idea.

"But modders can implement a new mob in like a week!!1" yeah its almost as if a modder is not held to the same quality standards as a team of engineers employed by Microsoft. You'd pitch a fucking fit if Mojang implemented a buggy new mob, which is exactly what would happen if they tried to make 3x as many mobs in the same timeframe

Minecraft has literally been giving you free updates and new content for over a decade, and on top of that is doing the kindness of letting its fans have a small say in the development decisions. You can easily downgrade to an older version of Minecraft if you don't like the new changes. Quit whining you miserable miserable humans.

[nira16-t]

they hate me for my cryptid-esque swagger and my terribly inefficient c++ code

[nira16-t]

*EXTREMELY LOUD INCORRECT BUZZER*

she object on my programming till i am oriented

[nira16-t]

The modder argument is a fallacy.

We've all heard the argument, "a modder did it in a day, why does Mojang take a year?"

Hi, in case you don't know me, I'm a Minecraft modder. I'm the lead developer for the Sweet Berry Collective, a small modding team focused on quality mods.

I've been working on a mod, Wandering Wizardry, for about a year now, and I only have the amount of new content equivalent to 1/3 of an update.

Quality content takes time.

Anyone who does anything creative will agree with me. You need to make the code, the art, the models, all of which takes time.

One of the biggest bottlenecks in anything creative is the flow of ideas. If you have a lot of conflicting ideas you throw together super quickly, they'll all clash with each other, and nothing will feel coherent.

If you instead try to come up with ideas that fit with other parts of the content, you'll quickly run out and get stuck on what to add.

Modders don't need to follow Mojang's standards.

Mojang has a lot of standards on the type of content that's allowed to be in the game. Modders don't need to follow these.

A modder can implement a small feature in 5 minutes disregarding the rest of the game and how it fits in with that.

Mojang has to make sure it works on both Java and Bedrock, make sure it fits with other similar features, make sure it doesn't break progression, and listen to the whole community on that feature.

Mojang can't just buy out mods.

Almost every mod depends on external code that Mojang doesn't have the right to use. Forge, Fabric API, and Quilt Standard Libraries, all are unusable in base Minecraft, as well as the dozens of community maintained libraries for mods.

If Mojang were to buy a mod to implement it in the game, they'd need to partially or fully reimplement it to be compatible with the rest of the codebase.

Mojang does have tendencies of *hiring* modders, but that's different than outright buying mods.

Conclusion

Stop weaponizing us against Mojang. I can speak for almost the whole modding community when I say we don't like it.

Please reblog so more people can see this, and to put an end to the modder argument.