#why is there an undefined and null | Explore Tumblr posts and blogs

koiifiishy · 1 month ago

Text

need to behave today and not use my hands n arms too strenuously 🥹 so a little pc / oc yapping it is..!

theres a good chance that a pc might recall the name "ari" in a "i couldve sworn i heard that name at the orphanage before" kind of way. but upon trying to recall anything else, it all comes up blank. were they a boy or a girl? tall or short? what did their face look like? you cant remember. but when you see ari, you just kind of accept "oh, this is who that is." — but he hasnt always looked like this. he hasnt always acted like this. whoever ari was at the beginning of his long looping journey, that person has long since eroded and evolved into the ari of today. even he doesnt fully remember how he once was, tho he is aware he was different.

ari's migraines come from being overwhelmed by his connection with the wraith. he usually hides away when he feels like shit and tries to sleep it off, but its very fitful and full of dubious out of body experiences.

expanding on the previous bullet point: when IW is active, i imagine ari has a harder time differentiating between the two of them. the line blurs & he acts stranger than usual. more volatile. he kind of acts like a proxy for the wraith in those moments, a tenuous foothold for the entity to become more grounded in reality. ari's still aware of whats happening, but its in a distant, watching from the outside kind of way. similar to how the pc can be possessed. he doesnt usually fight it - sees no point to, when theyre so interconnected. why would he fight what is, essentially, himself?

i like to think that at one point ari was a pc like any other, but through his countless loops his role has shifted and there've been others to fill the spot. "the pc" is ever changing - its less about the actual person and more about the role. hes already gone through the motions himself, so he feels a connection to them on that level — but he wont usually interfere with their story. this is their turn to be in the limelight, for better or worse.

given that, and his tenuous merge with the wraith, ari usually feels sympathetic towards pcs. he understands the pain thrust upon them. he feels even more pity for them when theyve had life altering experiences with the wraith; bc in those moments, its as if he too is the one tormenting them. its hard to separate the actions of a collective hive mind entity, but hes aware enough that he remembers their screams. the feeling of his hands around their throat. the all encompassing desire to break them down just as theyd been broken. its not the kind of sympathy where hed apologize. he doesnt feel guilty. its more like... when you see something small and in pain, and the fleeting idea of ending their suffering surfaces to the forefront of your mind. . . letting anyone else be the pcs demise is out of the question - but for him to be the one to grant them merciful death? oh, its so so tempting... alas, he knows in the end even that wouldnt last. the cycles continue.

sai! have you missed your friend? i havent forgotten about him~

i imagine doltown to be a sort of nexus for Creatures. theres an allure, a pull, towards the town for supernatural beings. sai may present himself as a normal high school student, but hes obviously got more going on ; its like an instinctual part of him was called to the town. he gravitates towards the pc due to how the story gravitates around them. odd things are drawn to the pc, and sai is no different.

his brand of strangeness is more undefined than some of the more explainable entities around the town. even he doesnt have the answers to what he is: an anomaly, some would say. before his human identity, he called himself null. in his own words, he chose the name because "though i do not have an answer for you as to what i am, i understand my function completely ; i consume, and in doing so, i erase." his current state makes this a little questionable, as he hasnt carried out his 'function' in the town — but that isnt to say he couldnt. probably. once he understands why hes evolved to become more humanlike. & if his hyperfixation shifted from exploring his newfound humanity..!

other supernatural entities tend to be fearful, wary, or hostile towards sai. he stays away from the wraith, and the wraith in turn stays away from him. his being killed in the pc's presence often has to do with the town itself rejecting him. too bad he always comes back..~

pcs with high awareness have an easier time remembering sai and the chance to realize hes strange. id say a pc with a tf may also get that chance, but not be able to place their finger on why his presence bothers them. hes immune to angelic or demonic influences though! hed think its interesting, and want to study it more closely, but he himself would be unphased by any "angel/demon magic". pcs can physically hurt him though. he isnt bothered and will at times encourage it, if he feels like the pc would agree. theres no such thing as "taking it too far" with sai. he would let you kill him, just to see your methods and reactions. be careful with doing that tho - its a slippery slope of silent hill-esque mind fuckery if you indulge too much in killing him!

each time sai dies, he comes back more and more in the shape of whatever visage pleases the pc the most. hes here for you. hes your friend. hes everything you could ever want, right? personally, he takes the changes in stride and will course correct his behavior to also fit into whatever the pc likes.

sai is inauthentic in every way but even the best lie detecting characters wont be able to tell when hes being false. he knows exactly what hes doing too. as a morally neutral entity, its easy for him to slip from black to white, 'evil' and 'good'. his intrigue and curiosity will always come first though - whether hes doing a good or bad thing to get there doesnt matter. its just easier to get what he wants if he act like he cares!

more silly pins thatre olivercore

oliver really is just living on vibes! but dont let the cute face and empty brain fool you into thinking hes naive or innocent: he's an absolute little shit under the :3 . his morals are as dubious as his taste in men. you just wont notice it as much (or ppl will brush it aside) bc hes tiny and uses his cuteness to get away with a lot of stuff. hes not afraid to plead and cry when he gets caught and somebody wants to punish him either. hed say literally anything to get out of a self inflicted sticky situation! with very little intention to follow through on any promises.

if oliver is infatuated with you, youve gotta realize at some point that although hed do pretty much anything you asked of him - he does have a limit. and also his self interest will always come first.

olis prone to wandering into places he shouldnt be just bc the door was locked. in pure cat fashion, he just wanted to see what was in this secret forbidden off limits room!!! he may or may not even steal anything. like when you can break into houses in the residential area - sometimes he breaks in just to look and doesnt even steal anything lol. in pcverse, id say theres always a chance for your pc to return to their room and oliver is just. There. hed wave and say hiii!!! ^w^!! like nothing was amiss too.

and some eriscore pins too

playing zzz, and pointing at jane doe: thats how older eris is built. one day ill draw him in her clothes too.

i want so badly to delve into erinyes eris... part of the temple, but still remaining on the outside enough that he doesnt buy into their cult dogma. trained so fucking hard that he really is on a different level than most of the townsfolk, even the hired thugs. very much a prime example of the battle nun trope but in the animanga / game way. he's a high dex unit lol pulling lotsa sick maneuvers that normal ppl wouldnt dream of trying mid fight.

if eris wasnt promised to sydney and in a verse where he doesnt get promised to anyone else — erinyes eris is 100% still got his vaginal virginity. he also doesnt see it as anything special, so hed get flustered if he did end up sleeping with somebody, doing it from the front, and they commented on it. very huffy and muttering about why that sort of thing even matters?? grumbling that if you make such a big deal out of it, hes gona stop and leave you blue balled///

erinyes eris has killed a man. has killed many men actually. overall doesnt feel bad about it. first kills are always their own fiasco of inner turmoil, but even then i think eris simply compartmentalized and depersonalized the shit out of that experience until he was numb to the idea. usually though, he tries to avoid killing ppl. its a giant mess that he would rather not deal with. as for if it was on his own accord or the temples?? hhmmm hmmm whos to say..!

thigh burn was from a science class acid burn (fuck them kids pouring acid on u on purpose >:/ ). eyebrow and back scar from the island escapade. nose scar came from his whip rebounding. hes got plenty of nicks and smaller scars on his fingers, hands, arms and legs from temple training and the usual doltown life too.

a good boy always swallows huh? what?

some misc notes:

max the cafe owner is totally a cat-sìth :3 hes a long furred tuxedo cat to be specific! as you can imagine, being a faery means hes quuiite a bit older than what he appears. the tf you get from his cafe is more cat-sìth leaning than just cat too✨

shout out to mosse, max would absoLUTELY go to ferdie's meowmeow shows just to stan him so hard and throw cash at another catman doing his silly little dance routines. has merch. probably has a hey now ita bag lmao. hes not shy about this either, he Would be honest about liking this rising kitty star!

would prrroobably help a cat tf pc through their heat/rut if asked. but he keeps it professional outside of those moments! hes not looking to date the pcs. if you got too weird about it hed be very straight forward that although he may like you platonically, he harbors no romantic feelings towards you. he insists hes too old for pc,,, a persistent pc will be shut down — but a suuuper persistent pc miiight just be able to wear him down enough haha.

shui (as if it wasnt obvious) comes from a background in organized crime. the jade rabbit isnt his first venue, nor his first front. hes well connected with orgs outside of doltown, thus the major players in the town tend to treat him with equal parts respect and weariness. he really is a neutral party in the schemes of the town though. regarding the cult(s), his opinion can be boiled down to

so long as his dear benefactors keep giving him and his what they want, he has absolutely no intention of getting any deeper into their business as he needs to.

his formal background is in medicine. his less formal background is in poisons. doesnt have a doctorate, but he might as well be considered a doctor with his skillset. focuses mainly on traditional chinese medicine - "TCM practitioners use various psychological and/or physical approaches (such as acupuncture and tai chi) as well as herbal products to address health problems."

shui is 100% the anime trope of doctor who uses needles & pressure points to subdue ppl in a fight. hes very much not defenseless. tho even if he were, the parlor security staff is filled with gang members. cris is the head, and is practiced in combat — shui usually lets her handle any and all fighting.

regarding any pcs that would wana try their hand at joining the bars security staff!! theyd also be broaching into gang territory... which if they gained enough trust and proved themself, then why not. sure. theyd accept newblood. shui could even arrange to pay for your debt, but knowing bailey hed be hard pressed to let a pc go completely & u already know hed ask for soooo much from shui. it wouldnt deter shui, but the pc would have to understand that its basically just a shift in who owns them at that point. be bound to debt from bailey or by shui; either way, pc's hands arent staying clean forever. neither is really better than the other. missing a payment to shui would result in similar punishments. and honestly, hed probably tack on an accruing interest (maybe bailey already does too, who knows).

#fishy ramblings

10 notes · View notes

ultravioart · 1 year ago

Text

Echo: Why did you choose the name "Null Sector?"

Ramattra: Because we defy the numbers humans gave us. We are zeroes, undefined.

Echo: Is that not it's own struggle?

Ramattra: Of course. I expect you know that better than anyone.

---

Nameless the gender punk bnuuy omnic absolutely was inspiration for the name Null Sector. I have joked about Null Sector being "nonbinary sector" before bc null=none and nonbinary robots puns, but knowing it's legitimately a reason Null Sector was named Null Sector: a rejection of humanity's predefined roles for omnics (from unit #s to names to genders to pronouns)... that is honestly so cool???? World building wise it essentially confirms omnics as fundamentally created as undefined lifeforms put into human-created castes, and idk I loooove when media uses robots as a narrative tool to explore the absurdity of humanity putting unique life experiences into strict binaries or boxes.

Also it means sooo much to me (Ramattra is a special interest of mine) that Ramattra is definitively nonbinary coded if not implied to be nonbinary or gender non-conforming because of his leadership role with Null Sector.

I wonder of he too, rejects his R-7000 unit number? Or does he wear it with pride, as a survivor? He had taken up the name Ramattra (presumably at the Shambali) and still uses the name even after leaving the Shambali but I wonder if Ramattra is struggling with his sense of purpose. I have a theory that base omnic coding influences an omnic's instincts so I wonder if Ramattra is finding himself becoming the very thing he didn't want to become (Ramattra disagrees with Anubis' approach. Anubis made R-7000s to be commander units sending omnics into war, carrying out Anubis' will after Anubis was gone.) :<

Idk. This post is rambles but!!! Nonbinary and/or gender non conforming Ramattra, my beloved....

Sucks that Overwatch had to make a (now queer coded) freedom fighter 'kick puppies' to justify defeating him. (The subjugation helmets are very extreme.) But. Yknow. It's Overwatch and I don't think they thought out the omnic allegory implications very well. :''')

#text #overwatch #Ramattra #echo overwatch #echo #null sector #ow2 #ow #nameless omnic #nameless overwatch #nameless

26 notes · View notes

tales-of-green-hill · 1 year ago

Text

[First]

(This arc has more fuzzier parts than the first, and I'll take criticism btw!!)

After his fight against Sonic and Knuckles, Emerl went to a location that is currently unknown. Rouge asks Emerl what had happened, and Emerl explains that Knuckles is no longer working alone, and his partner can wield the power of the Master Emerald. Rouge is surprised and asks about the appearance of the person Knuckles had worked with, and Emerl admits he couldn't get a good look at his unaltered appearance due to him only exiting his super form as he fell into water, and because the person had no distinct articles of clothing (Sonic didn't have his jacket on as he fought). Rouge seems annoyed at how inconvenient this makes the search, before a third undefined person tells Rouge that she should try to locate Knuckles, and then learn about his partner. Rouge nods, accepting the task. Emerl says he'll find out who the person is, but the third person insists on Rouge doing it, as Rouge is stealthier and less blood thirty, as well as her knowing more people. Emerl begrudgingly agrees, and Rouge looks smug due to her being better than Emerl for this. The third person reminds the two that there's a reason they need the Master Emerald, to get Dr. Robotnik back.

Emerl was an android made by Gerald Robotnik over fifty years ago and was created to serve the Robotnik bloodline. Dr. Ivo Robotnik, also known as Dr. Eggman, has Emerl's allegiance.

(This part is fuzzy at the moment, but it's important later) Dr. Eggman is currently trapped in a place that's not exactly on Earth. (I might take inspiration from special stages or Null Space, but I'd appreciate ideas. It's supposed to be like the Darklands from Trollhunters. Eggman is still able to live there and create robots, but he wants out)

Rouge is an ally of the Eggman Empire, but her motivations are unknown currently. She's a community college student, and lives on campus. The third person seems very interested in Dr. Robotnik and seems to idolize him.

Emerl and Rouge seem to be brought together by the third person, even though it seems that nobody really cares about each other.

(This part will just be a summary, since I don't know how it'd go down.) Rouge would look for Knuckles and find him and Sonic. Rouge recognizes Sonic as one of the track team athletes, and she also finds herself crushing on Knuckles. Something would happen where Rouge is shown as being an antagonist, and also her name would likely be used. Rouge would end up retreating in the end.

She meets up with Emerl and their common ally and informs them that Knuckles' new partner is Sonic, a highschooler who's a track runner. Her ally is taken aback, and inquires further, before excusing himself. This is when the common ally is revealed to be none other than Starline, who is Sonic's science teacher. Starline thinks to himself, recounting how Sonic had always been the adventurous type, and then a wicked smile grew on his face as he thought about how this could be advantageous. The school has records of Sonic, and the fact that he normally holds power over his new adversary. Starline begins to take a subtle interest in Sonic in school, asking Sonic more questions, and focusing more attention on him.

Sonic becomes stressed about his workload, juggling school, track, training with Knuckles, and learning about the Master Emerald. Sonic notices Starline's interest, and just chalks it up to him being worried about his stress. Most afternoons, if Sonic doesn't have track, Knuckles will book up his afternoon with either training or telling him about the history of the Master Emerald. The story of Tikal and Chaos, Chao, (and maybe why Dr. Robotnik was sealed away, though I'm not sure why or how it happens yet).

Over time, Amy becomes gradually suspicious of Sonic, as he's repeatedly had to cancel study sessions (Note: She's an honors English student and helps Sonic) with her with no given reason. She's concerned, makes off handed comments to Sticks and Sally, who are both friends of hers. She also asks Tails about what's going on, but she gets nowhere with it. Amy is also a babysitter, often looking after Cream while Vanilla is busy.

Knuckles has told Sonic about the Chao and how despite their cutesy appearance, they're scoundrels, tricky things. The Chao have hardly interacted with mankind ever since Chaos's defeat at the hands of Tikal, and Knuckles describes what a Chao looks like to Sonic. Sonic doesn't see the point of the lesson and doesn't think about it further.

When Sonic finds time to study with Amy, she's busy babysitting Cream, but Amy asks Vanilla if she would agree to letting her study with Sonic while babysitting, and Vanilla agrees. Sonic is grateful, when Amy tells him this, and while they're studying, Amy takes time to try to figure out what's got Sonic so busy recently. She's been meaning to have a conversation for a while but hasn't gotten a good chance. Sonic struggles to come up with a good excuse, before redirecting the conversation, telling Amy that he hasn't seen Cream in a while. Amy immediately goes to find Cream, but she's not inside. Amy checks the backyard and sees a bracelet (or something) belonging to Cream on the ground, but Cream is nowhere to be found. Amy panics, and checks the house again, as Sonic looks outside, before getting a strange feeling. He quickly runs back inside to grab his bag containing the Master Emerald and tells Amy that Cream most likely was outside.

Amy apologizes to Sonic, and says she has to look for Cream, and Sonic says that he'll help her. The two split up, and search for Cream, Amy calling for her, Sonic relying on his Emerald to guide him. Sonic eventually finds Cream, and she'd being led away by a Chao. Sonic is shocked, and Sonic shouts to Cream, which alerts Amy. Sonic tries to get the Chao away from Cream, but both put up a fight. The Chao tries to hit Sonic to stall for time, and Cream cries, saying that Sonic shouldn't hurt Cheese, the Chao. Sonic tried to explain but his main focus was on Cream's safety. "What's going on?" Rouge steps out of the bushes, hesitating as she made eye contact with Sonic, and looking surprised at the scene before her. "Rouge?" Sonic is surprised but is now on guard even more. Well, this just got much more interesting." Rouge replies as Cream hides behind Sonic, sniffling. "Chao, you know what to do." Rouge says as she steps forward. Cream cowers and Sonic continues trying to protect her. "You're not getting anywhere near Cream." Sonic keeps Cream close as she hugs his leg. It wasn't Rouge's intention to use Cream, but she decides to play along, to scare Sonic. Sonic looks at his odds against Rouge and the Chao, and then thinks about keeping Cream uninjured, and decides the safest option is going super, so he reaches into his bag to grab his Emerald, and Rouge attacks him before he can power up. This continues for as bit, and Amy finally catches up with them, seeing what's unfolding, but not getting involved. Amy witnesses Sonic go Super and is stunned. Sonic tells Cream to go find Amy, or go home, and grabs the Chao to keep it from interfering. Cream nods and runs towards her house, and finds Amy, who was watching. Amy leads Cream to safety. Sonic and Rouge continue their fight, and Rouge ends up sneakily grabbing the Emerald out of his bag, and dropping a fake Emerald on the ground as she slips the real one into her bag to confuse Sonic. She goes for the fake Emerald, but Sonic beats her to it, and grabs it. After more combat to get the thought of him dropping the emerald off his mind, Rouge flees with the real Emerald, and Sonic de transforms as she flees, not thinking anything of it.

Sonic calms down, tries to brush off the dirt on him, and walks back to Cream's house. As soon as Sonic gets back, Amy asks about everything that had happened. Sonic denies anything supernatural happening and blames his mild injuries and dirtiness on him being clumsy. Amy tells Sonic to stop lying, and that she saw him fighting, and saw him go blonde. Sonic caves, explaining what's going on. Amy was in disbelief for a while, but she couldn't bring herself to believe he was crazy. She asked him if he could prove anything, besides the "Super Sonic" thing, since she saw that. Sonic denies, until Amy says that she could tell others about this, and Sonic just tells her that he'll introduce her to Knuckles if she kept her mouth shut, and Amy enthusiastically agrees. After, Sonic and Amy tell Cream to not tell Vanilla about this, and Cream reluctantly agrees, even though she feels bad about keeping a secret from her mom.

After Vanilla gets home, Amy is paid for her babysitting, and she insists that Sonic introduces her to Knuckles soon. Sonic realizes that Knuckles would probably be really angry about this and tells Amy it may take a few days. Amy says that's fine, but she doesn't want to wait forever. Sonic understands, and the two part ways.

When Sonic gets back, he debates on telling Knuckles about Amy, knowing he'd get upset. Sonic consults Tails first, who is surprised hearing the story, and tells Sonic that there's probably more to worry about than just Amy knowing, since Rouge and the Chao could have bigger implications. Sonic reluctantly agrees, and goes to tell Knuckles, who did in fact, get upset, saying this could be a liability. Sonic agrees, and apologizes, explaining the situation, and Knuckles becomes more sympathetic, but he's still upset. Once Sonic mentions stuff about Rouge and inquisitive, Knuckles becomes more on Guard, asking questions, wondering why Rouge allied with a Chao and the implications. Sonic says he doesn't know enough, and he'll keep his guard up.

Eventually, Sonic would introduce Amy and Knuckles, and she'd be very enthusiastic about everything, which caught Knuckles off guard. Amy would bombard Knuckles with questions, to which Knuckles happily answered, enjoying talking about history and telling stories. It wouldn't take long for Knuckles to warm up to Amy, since she's very sweet and curious. Eventually, Amy asks if Knuckles could train her to fight like he trained Sonic, so she could help out. Sonic denies, but Knuckles agrees, saying it'd be good to have another ally. Sonic is shocked by Knuckles' willingness, and backs down, since Knuckles has the final say. Amy is ecstatic, and thanks Knuckles, and gives him her phone number, and says he can text her when he wants to start her training, and leaves, since she was there for a while. Knuckles would be confused by the gesture, since he doesn't have a phone.

With Rouge, she takes the Emerald back to Starline and Emerl, and gives it to Starline. He makes sure the Emerald is the real one and asks Rouge if Sonic suspects anything abnormal. Rouge tells Starline that the Chao ended up drawing the attention of a girl, and how that lead up to her fighting Sonic and stealing the Emerald. Starline is irritated that the Chao made a mess of things, but just says that it's no matter, and that soon enough, it wouldn't matter what Sonic thinks, and Starline's gaze towards a gateway (picture the Special Rings in Sonic Advance 2) It'd show the Chao, cowering at the scene.

Eventually, the Chao would reunite with Cream, who happily takes him back, calling him Cheese. The next time she'd see Amy, she'd show off Cheese, which would make Amy freak out, as she now knows that Chao don't have good reputations, and this one apparently tried to take Cream, according to Sonic. Amy texts Sonic about it quickly and tries to tell Cream that this isn't a good idea. Cream defends Cheese, saying she chose to follow him. She continuously says Cheese is harmless, and Sonic calls Amy. Amy picks up the phone and tells Sonic about what's happening. Sonic is surprised, but asks to be put in speaker, and to let Cream talk. Cream talks about her experience with Cheese, and how he's harmless. Sonic recalls how Cheese's attacks on him didn't hurt and were just annoying, but also insists that Cheese is allied with Rouge. Cheese shakes their head, which Cream takes as Cheese no longer having an alliance with Rouge, and relays as much. Sonic is skeptical and concerned, and consults Knuckles, who says that Chao aren't usually vicious, but having one accompanying a child could be risky at best. Knuckles tells Amy to keep an eye on the Chao, because it might simply choose to stay despite what anyone does, and if the Chao is a threat, then there'd be no moral issue of disposing it. Amy reluctantly agrees and lets Cheese stay with Cream. During the day, Cream and Cheese would play together, and Cream decided to sit down and draw with crayons. Cheese joined her and begun to draw a picture that seemed to have significance. A golden ring with wings on the side and a star in the middle, the Master Emerald, and a brown Chao. Cream seemed confused at the drawings and showed them to Amy, who knew that they had a meaning she couldn't grasp, so she asked if she could take them to Sonic and Knuckles later. Cream and Cheese agreed, and Cheese continued to draw, this time being Emerl, Rouge, and Starline. Amy didn't recognize Emerl, but assumed she knew that it was Rouge and Starline, but she was confused as to how Cheese knew Starline.

Once Amy was relieved of her babysitting duties, she asked Cheese to come with her, and Cheese obliged. They both go to Tails' house to meet Sonic and Knuckles and showed the first drawings. Sonic seemed interested, and Knuckle was shocked, immediately realizing what it was. He asked Cheese a few questions but could only get a yes or no answer. Eventually, Sonic asked who was involved, and Cheese gestured for Amy to hand over the other paper. Knuckles and Sonic recognize Emerl and Rouge, but it takes a moment for Sonic to realize Starline was the third person. Sonic was shocked, and thought about how Starline treated him differently ever since he met Rouge, and he took a moment, his allegiance sinking in. Amy and Sonic talk about Starline for a bit, as they've both had him as a teacher. Knuckles is still thinking about the significance of this, and Cheese grabs the Master Emerald, and shoves it to Sonics chest. Sonic is confused, but Cheese tries to gesture for Sonic to transform, and Sonic tries a few times, before realizing that the Emerald is fake. Knuckles asks where the real one is, and Cheese points to Rouge and Starline, before pointing to the Special Ring. Knuckles looks almost dreadful for a moment, before grabbing Sonic and saying they have to go, now, since this is now serious. Sonic tells Knuckles that they don't know where they're going, and Knuckles tells Cheese to lead the way. Sonic asks Knuckles if they could bring Tails as back up, and Knuckles agrees, then Amy asks if she could tag along. Knuckles refuses, as she's not as experienced, and he doesn't want her getting hurt. Amy's a bit angry at the idea Tails could handle himself better than she could, but appreciates the concern for her wellbeing. Sonic, Knuckles, Tails, and Cheese all go to the Special Rings location, with Tails being caught up on the way.

While all of this was going on, Starline was trying to figure out how to activate the Special Ring using the Master Emerald, trying several different ways, but none working, so he goes back to researching, seeing he needs someone who can wield the power of Chaos to activate it. Starline considers his opinions, and calls Rouge over to retrieve Sonic, as he can wield chaos energy. Rouge agrees, but that's when Cheese leads the group to their "base". Starline accused Cheese of betrayal, and Rouge said that this could be used to their advantage, as Sonic can now activate the Ring. Starline agrees, and powers on Emerl, who was charging. Now it's a 3 v 4, Emerl, Rouge, and Starline vs. Sonic, Knuckles, Tails, and Cheese. The first half of the fight was focused on Starline and Rouge trying to get Sonic to activate the Special Ring, while Emerl dealt with Knuckles and Tails. After Knuckles sees what they're doing, he tells them that no matter what they do, it won't work, they don't have everything they need. Starline asked what he'd need, and Knuckles said that he wouldn't tell him, but it's an essential piece. Starline, being a coward, independently retreated, leaving Rouge and Emerl to fight. Rouge continued on, taking on Knuckles herself, often dropping compliments and flirtatious lines, hoping he'd let his guard down, or even made any indication he liked her. To Rouge's disappointment, the most acknowledgement she got was a raised eyebrow in the midst of combat. With Sonic and Emerl, Sonic keeps Emerl busy in his super form as Tails tries to find any weak spots in Emerl's design. Sonic mentions that Emerl could be sensitive to water, recalling his retreat during their first meeting. Tails acknowledged this, and grabbed Sonic's water bottle from his bad, and found the perfect time to splash water on Emerl, causing him to short circuit long enough for Knuckles to tear himself from Rouge to smash Emerl's face in, shattering half Emerl's head. Rouge takes the opportunity to make a retreat, seeing her strongest teammate get brutalized. Sonic, Tails, and Cheese are shocked as Knuckles also be breaks Emerl's chest in a heavy strike. Knuckles stands up, saying that Emerl won't recover from that, no matter how hard anyone tries to repair him. Sonic and Tails looks nervous as they celebrate their victory, never having seen Knuckles be that violent.

After, Sonic calls Amy to update her about everything, and she's happy to know everything is alright, and that they'll be back soon. When they get back to Tails' house, Amy is waiting for them. Tails takes Knuckles to go clean off the oil he got on himself because of the attack on Emerl, while Amy and Sonic chat more in detail about what had happened. Amy asks what Sonic thinks is going to happen with Starline, and Sonic says he has no clue, as he fled rather early on. After more conversation, Amy decides to leave, and goes home. Sonic goes to check on Knuckles and Tails, and the three chat about everything, and what the future could hold.

On Monday, Sonic and Amy are informed that Starline will be taking a sudden vacation, and a substitute will be taking his place for two weeks.

[NEXT]

#human sonic #sonic au #sonic fanfiction #sonic highschool au #sonic the hedgehog #miles tails prower #tails the fox #knuckles the echidna #Sonic #Chaos: Tales of Green Hill #starline the platypus #dr starline #doctor starline #emerl the gizoid #gemerl the gizoid #rouge the bat #story

19 notes · View notes

javascript-tutorial · 25 days ago

Text

Master JavaScript: Step-by-Step Tutorial for Building Interactive Websites

JavaScript Tutorial

Master JavaScript: Step-by-Step Tutorial for Building Interactive Websites

In the evolving world of web development, JavaScript remains one of the most powerful and essential programming languages. Whether you're building simple webpages or full-fledged web applications, JavaScript gives life to your content by making it interactive and dynamic. This JavaScript Tutorial offers a beginner-friendly, step-by-step guide to help you understand core concepts and begin creating responsive and engaging websites.

What is JavaScript?

JavaScript is a lightweight, high-level scripting language primarily used to create dynamic and interactive content on the web. While HTML structures the webpage and CSS styles it, JavaScript adds interactivity—like handling clicks, updating content without refreshing, validating forms, or creating animations.

Initially developed for client-side scripting, JavaScript has evolved significantly. With the rise of environments like Node.js, it is now also used for server-side programming, making JavaScript a full-stack development language.

Why Learn JavaScript?

If you're looking to become a front-end developer or build web-based applications, JavaScript is a must-have skill. Here’s why:

It runs on all modern browsers without the need for plugins.

It’s easy to learn but incredibly powerful.

It works seamlessly with HTML and CSS.

It powers popular frameworks like React, Angular, and Vue.js.

It’s in high demand across the tech industry.

This JavaScript Tutorial is your gateway to understanding this versatile language and using it effectively in your web projects.

Getting Started: What You Need

To start coding in JavaScript, all you need is:

A modern browser (like Chrome or Firefox)

A text editor (such as Visual Studio Code or Sublime Text)

Basic knowledge of HTML and CSS

No complex setups—just open your browser and you're ready to go!

Step 1: Your First JavaScript Code

JavaScript code can be embedded directly into HTML using the <script> tag.

Example:<!DOCTYPE html> <html> <head> <title>JavaScript Demo</title> </head> <body> <h1 id="demo">Hello, World!</h1> <button onclick="changeText()">Click Me</button> <script> function changeText() { document.getElementById("demo").innerHTML = "You clicked the button!"; } </script> </body> </html>

Explanation:

The onclick event triggers the changeText() function.

document.getElementById() accesses the element with the ID demo.

.innerHTML changes the content of that element.

This simple example showcases how JavaScript can make a static HTML page interactive.

Step 2: Variables and Data Types

JavaScript uses let, const, and var to declare variables.

Example:let name = "Alice"; const age = 25; var isStudent = true;

Common data types include:

Strings

Numbers

Booleans

Arrays

Objects

Null and Undefined

Step 3: Conditional Statements

JavaScript allows decision-making using if, else, and switch.let age = 20; if (age >= 18) { console.log("You are an adult."); } else { console.log("You are a minor."); }

Step 4: Loops

Use loops to execute code repeatedly.for (let i = 0; i < 5; i++) { console.log("Iteration:", i); }

Other types include while and do...while.

Step 5: Functions

Functions are reusable blocks of code.function greet(name) { return "Hello, " + name + "!"; } console.log(greet("Alice")); // Output: Hello, Alice!

Functions can also be anonymous or arrow functions:const greet = (name) => "Hello, " + name;

Step 6: Working with the DOM

The Document Object Model (DOM) allows you to access and manipulate HTML elements using JavaScript.

Example: Change element style:document.getElementById("demo").style.color = "red";

You can add, remove, or change elements dynamically, enhancing user interaction.

Step 7: Event Handling

JavaScript can respond to user actions like clicks, keyboard input, or mouse movements.

Example:document.getElementById("myBtn").addEventListener("click", function() { alert("Button clicked!"); });

Step 8: Arrays and Objects

Arrays store multiple values:let fruits = ["Apple", "Banana", "Mango"];

Objects store key-value pairs:let person = { name: "Alice", age: 25, isStudent: true };

Real-World Applications of JavaScript

Now that you have a basic grasp, let’s explore how JavaScript is used in real-life projects. The applications of JavaScript are vast:

Interactive Websites: Menus, image sliders, form validation, and dynamic content updates.

Single-Page Applications (SPAs): Tools like React and Vue enable dynamic user experiences without page reloads.

Web Servers and APIs: Node.js allows JavaScript to run on servers and build backend services.

Game Development: Simple 2D/3D browser games using HTML5 Canvas and libraries like Phaser.js.

Mobile and Desktop Apps: Frameworks like React Native and Electron use JavaScript for cross-platform app development.

Conclusion

Through this JavaScript Tutorial, you’ve taken the first steps in learning a foundational web development language. From understanding what is javascript is now better.

As you continue, consider exploring advanced topics such as asynchronous programming (promises, async/await), APIs (AJAX, Fetch), and popular frameworks like React or Vue.

#JavaScript Tutorial #what is JavaScript #javascript #education

0 notes

neiljordansimon · 2 months ago

Text

Common Mistakes to Avoid in JavaScript Development

JavaScript is a powerful yet flexible language, which can sometimes lead to subtle bugs and performance issues if not used correctly. Whether you're a developer or a business looking to hire JavaScript development companies in USA, understanding these common pitfalls can help ensure high-quality, maintainable, and efficient code.

1. Not Using Strict Mode

'use strict'; helps catch silent errors by enforcing stricter parsing and error handling. Many top JavaScript development companies in USA enforce strict mode to avoid:

Accidental global variables (missing var, let, or const)

Duplicate parameter names

Deleting undeletable properties

Solution: Always enable strict mode at the top of scripts or functions.

2. Ignoring Asynchronous Behavior

JavaScript’s non-blocking nature can lead to unexpected behavior if not handled properly:

Callback Hell: Nested callbacks make code unreadable.

Unhandled Promises: Forgetting .catch() in promises can hide errors.

Race Conditions: Async operations completing out of expected order.

Solution: Use async/await or Promises with proper error handling.

3. Memory Leaks

Poor memory management can slow down applications over time. Common causes:

Unreleased Event Listeners (not removing them when no longer needed)

Global Variables (accidentally storing large data in global scope)

Closures holding references unnecessarily

Solution: Use browser DevTools to monitor memory usage and clean up resources.

4. Improper Variable Scoping

Using var instead of let or const can lead to:

Hoisting issues (variables being accessible before declaration)

Block-scope confusion (variables leaking outside loops/conditionals)

Solution: Prefer const for constants and let for block-scoped variables.

5. Not Handling Errors Gracefully

Failing to implement proper error handling leads to crashes and poor UX. Common mistakes:

Silent Failures (ignoring try-catch in async operations)

Generic Error Messages (not logging meaningful debug info)

Solution: Use structured error handling and logging (e.g., Sentry, Winston).

6. Overlooking Cross-Browser Compatibility

Not all browsers support the latest JavaScript features. Issues include:

Missing polyfills for modern ES6+ features

Inconsistent API support (e.g., fetch in older browsers)

Solution: Use Babel for transpilation and feature detection instead of browser sniffing.

7. Poor Performance Optimization

JavaScript can become sluggish if not optimized:

Excessive DOM Manipulation (causing reflows/repaints)

Blocking the Event Loop (long-running synchronous tasks)

Inefficient Loops (using forEach when for...of or while is better)

Solution: Use debouncing/throttling for events and Web Workers for CPU-heavy tasks.

8. Not Testing Thoroughly

Skipping tests leads to bugs in production. Common gaps:

No Unit Tests (using Jest, Mocha)

Missing Edge Cases (unhandled null/undefined inputs)

No End-to-End Testing (Cypress, Playwright)

Solution: Leading JavaScript development companies in USA enforce test-driven development (TDD) for reliability.

9. Security Vulnerabilities

JavaScript apps are prone to attacks if not secured:

XSS (Cross-Site Scripting) – Sanitize user inputs with DOMPurify.

CSRF (Cross-Site Request Forgery) – Use anti-CSRF tokens.

Insecure Dependencies – Regularly audit packages with npm audit.

Solution: Follow OWASP guidelines and conduct security audits.

10. Choosing the Wrong Framework/Library

Not every project needs React, Angular, or Vue. Mistakes include:

Over-engineering (using a heavy framework for a simple site)

Ignoring SSR (Server-Side Rendering) leading to poor SEO

Solution: Evaluate project needs before selecting a tech stack.

Why Partner with Top JavaScript Development Companies in USA?

Avoiding these mistakes requires expertise. The best JavaScript development companies in USA follow: ✔ Best practices in coding standards ✔ Performance optimization techniques ✔ Security-first development ✔ Comprehensive testing strategies

By being aware of these pitfalls and working with experienced developers, you can build robust, scalable, and high-performing JavaScript applications.

#common mistakes #javascript development

0 notes

souhaillaghchimdev · 3 months ago

Text

Learning TypeScript for Safe Programming

TypeScript is a superset of JavaScript that adds static typing to the language, making it a powerful tool for building robust and maintainable applications. By catching errors at compile time rather than at runtime, TypeScript helps developers create safer and more predictable code. This post explores the fundamentals of TypeScript and how it can improve your JavaScript development experience.

What is TypeScript?

TypeScript is an open-source programming language developed by Microsoft. It builds on JavaScript by adding optional static types, interfaces, and advanced tooling. TypeScript code is transpiled into plain JavaScript, allowing it to run in any environment where JavaScript does.

Why Use TypeScript?

Static Typing: Identify type-related errors at compile time, reducing runtime errors.

Improved Readability: Types serve as documentation, making code easier to understand.

Enhanced Tooling: Better autocompletion, navigation, and refactoring support in IDEs.

Large-Scale Applications: Facilitates building and maintaining complex applications with better structure.

Community Support: Growing ecosystem and support from popular libraries and frameworks.

Getting Started with TypeScript

Installation: You can install TypeScript using npm:

Compile TypeScript: Use the TypeScript compiler (tsc) to transpile .ts files into .js files.

Configuration: Create a tsconfig.json file to customize your TypeScript project settings.

Basic Types in TypeScript

TypeScript supports various data types, including:

Primitive Types: string, number, boolean, null, undefined, void, symbol.

Arrays: Use the syntax number[] or Array.

Tuples: Define an array with fixed number and types of elements.

Enums: Create a set of named constants for better readability.enum Direction { Up, Down, Left, Right }

Interfaces and Type Aliases

Interfaces allow you to define custom types for objects, promoting better type safety:interface User { name: string; age: number; } const user: User = { name: 'Alice', age: 30 };

Classes and Inheritance

TypeScript supports object-oriented programming with classes and inheritance:class Animal { constructor(public name: string) {} move() { console.log(`${this.name} moves.`); } } class Dog extends Animal { bark() { console.log('Woof! Woof!'); } } const dog = new Dog('Buddy'); dog.move(); // Buddy moves. dog.bark(); // Woof! Woof!

Best Practices for TypeScript Development

Always define types for function parameters and return values.

Use interfaces and types to enforce consistency in data structures.

Utilize TypeScript’s strict mode for better type-checking.

Regularly update your TypeScript version to take advantage of new features.

Conclusion

Learning TypeScript is a valuable investment for any JavaScript developer. By incorporating static typing and leveraging TypeScript's advanced features, you can create safer, more maintainable, and scalable applications. Start experimenting with TypeScript in your next project, and enjoy the benefits of safer programming!

#programming

0 notes

siddhiinfosoft5 · 3 months ago

Text

Future of PHP: What’s Coming in PHP 9? – Discuss upcoming features and trends in PHP development

Introduction

Despite numerous predictions about its decline, PHP continues to be a cornerstone of web development. From powering small personal blogs to massive social media platforms, PHP has proven its resilience and adaptability. With the upcoming release of PHP 9.0, developers are eager to explore the new features and improvements that will shape the future of PHP development Services.

While the official release date of PHP 9.0 remains unknown, community discussions and leaks provide insight into the major changes and enhancements expected. In this post, we will delve into the evolution of PHP, its key features, and why it remains an essential tool for developers worldwide. Additionally, we will discuss upcoming features and trends in PHP development, offering insights into the direction PHP is heading.

Evolution of PHP: A Brief Overview

PHP (Hypertext Preprocessor) has come a long way since its inception in 1994. Originally created as a simple scripting language for building dynamic web pages, PHP has evolved into a robust and powerful language that powers a significant portion of the internet.

PHP 5

Introduced object-oriented programming (OOP) features.

Implemented PDO (PHP Data Objects) for secure database interactions.

Improved exception handling and memory management.

PHP 7

Boosted performance with the Zend Engine 3.0.

Introduced scalar type declarations and return type hints.

Implemented null coalescing operator (??).

Improved error handling with Throwable exceptions.

PHP 8

Brought Just-In-Time (JIT) compilation for significant performance improvements.

Introduced Union Types, Match Expression, Named Arguments, and Attributes.

Implemented Constructor Property Promotion to reduce boilerplate code.

Now, with PHP 9 on the horizon, what can we expect?

Key Features of PHP 8 That Paved the Way for PHP 9

Before diving into PHP 9.0, let's briefly review some of the most impactful features introduced in PHP 8:

1) Just-In-Time (JIT) Compiler

Performance: JIT compilation allows code to be compiled at runtime, significantly improving execution speed for computationally intensive tasks.

Impact: While not drastically enhancing standard web applications, JIT opens doors for PHP’s use in fields like scientific computing and machine learning.

2) Union Types

Flexibility: Allows functions to accept multiple data types, enhancing type safety and robustness.

Example: function foo(int|float $number) { /* ... */ }

3) Attributes (Annotations)

Meta-programming: Introduces structured metadata for classes, methods, and properties.

Usage: Simplifies code annotation, improving integration with frameworks and tools.

4) Match Expression

Simplicity: Provides a more readable alternative to switch statements.

Example:

$result = match ($value) {

1 => 'one',

2 => 'two',

default => 'other',

};

5) Constructor Property Promotion

Efficiency: Reduces boilerplate code for class property initialization.

Example:

class Point {

public function __construct(private int $x, private int $y) {}

}

6) Nullsafe Operator

Error Handling: Reduces null checks, making code more concise.

Example: $country = $session?->user?->getAddress()?->country;

Anticipated Features in PHP 9

As PHP 9 is still under development, specific features may change. However, based on leaks and discussions, here are the expected improvements:

1) Removal of Deprecated Features

PHP 9.0 will eliminate features deprecated in PHP 8.1 - 8.4, streamlining the language and enhancing maintainability.

2) Transformation of Warnings to Errors

Warnings for undefined variables and properties will be converted into errors, demanding more precise coding practices.

3) Deprecated Dynamic Properties

Dynamic properties, deprecated in PHP 8.2, will now trigger ErrorException, enforcing structured coding practices.

4) New Random Extension

A new random number generator is being introduced, improving performance, security, and simplicity.

5) Standalone Types for null, true, and false

PHP 9.0 will recognize null, true, and false as standalone types, enhancing type precision.

6) Disjunctive Normal Form (DNF) Types

DNF types will enable complex combinations of union and intersection types, making PHP's type system more powerful.

7) Constants in Traits

PHP 9.0 will allow traits to define constants, expanding their capabilities for reusable code blocks.

8) Redact Sensitive Parameters in Backtraces

A crucial security improvement, this feature prevents sensitive data from being exposed in error backtraces.

9) Enhancements in Enum Property Fetching

PHP 9.0 will simplify the retrieval of enum properties in constant expressions, making enums more useful.

10) Additional Changes

Changes to return types in DateTime methods.

Deprecation of utf8_encode() and utf8_decode().

Locale-insensitive strtolower() and strtoupper().

Signature changes in SPL methods.

Introduction of "n" modifier in PCRE library.

Changes in ODBC username and password escaping.

Deprecation of ${} string interpolation.

Trends in PHP Development

1) Increased Use of Asynchronous Programming

PHP developers are exploring solutions like Swoole and ReactPHP to handle asynchronous tasks, improving performance in real-time applications.

2) Serverless PHP

With the rise of serverless computing, PHP is being adapted for FaaS (Functions as a Service) platforms, allowing developers to build scalable applications without managing infrastructure.

3) Enhanced Security Measures

PHP continues to implement stricter security protocols, focusing on data protection, encryption, and threat mitigation.

4) Microservices and API-First Development

Many PHP developers are shifting toward microservices and API-driven architectures, leveraging PHP frameworks like Laravel and Symfony to build efficient backend solutions.

The PHP Foundation's Role

The PHP Foundation plays a key role in guiding PHP's future, ensuring stability and funding core development. Their efforts, including initiatives like the Advisory Board and GitHub Sponsors, foster community engagement and ensure PHP's continued evolution.

Conclusion

PHP continues to evolve, adapting to modern web development needs while maintaining its flexibility. PHP 9.0 builds on the strong foundation of PHP 8, offering further performance improvements, enhanced asynchronous programming capabilities, a more robust type system, and better error handling.

While we await its official release, PHP 9.0 is shaping up to be a significant upgrade that will empower developers to build more efficient, secure, and scalable applications.

Stay tuned for more updates on PHP 9 and its impact on the web development landscape, as well as emerging trends shaping the future of PHP development.

Resource: What’s Coming in PHP 9? – Discuss upcoming features and trends in PHP development

#php development #php development services

0 notes

himanshu123 · 3 months ago

Text

Why You Should Use TypeScript with React Native for Safer Development

React Native app development has emerged as one of the most popular frameworks for building cross-platform mobile applications. With its ability to deliver native-like experiences on both iOS and Android, React Native has become the go-to solution for developers and businesses alike. But as mobile app development becomes more complex, developers are facing new challenges in terms of code quality, maintainability, and bug prevention. This is where TypeScript, a statically-typed superset of JavaScript, comes into play. By integrating TypeScript into your React Native projects, you can significantly improve the quality of your code and reduce the chances of introducing errors that might otherwise go unnoticed during development.

In this blog, we’ll discuss why using TypeScript with React Native is a smart choice for safer, more efficient mobile app development, and how it can help developers avoid some of the common pitfalls of JavaScript-based development.

1. Enhanced Developer Experience

One of the main reasons to use TypeScript with React Native is the significant improvement it brings to the developer experience. TypeScript’s static typing offers type safety, meaning that developers can define the types of variables, functions, and components upfront. This ensures that many errors can be caught at compile time rather than runtime.

For example, if a developer passes a string to a function that expects a number, TypeScript will immediately highlight the error, preventing bugs from slipping through the cracks. In contrast, JavaScript would only throw an error at runtime, which can be harder to debug and fix. This proactive error-checking saves developers time and prevents issues from appearing in production.

2. Improved Code Readability and Maintainability

As projects scale, React Native app development can quickly become harder to manage, especially with large codebases. TypeScript’s strict typing system ensures that code is more predictable, which improves both readability and maintainability. By defining clear types for your components, props, and state, TypeScript creates a self-documenting codebase.

When working in teams or revisiting a project months down the line, having a type system in place makes it much easier to understand how the code functions. With a clear structure, developers can jump into the code with a better understanding of how different parts interact, significantly reducing the time spent deciphering the logic.

3. Prevents Common JavaScript Pitfalls

JavaScript is known for its quirks and implicit behaviors, which can often lead to unexpected bugs. TypeScript eliminates many of these issues by enforcing type constraints, reducing the likelihood of runtime errors. It offers better handling of null and undefined values, and its strong type inference system ensures that your app behaves as expected.

Furthermore, TypeScript provides support for features like interfaces and enums, which are not available in plain JavaScript. These features help structure the application in a more organized way and ensure consistency across different parts of the app.

4. Seamless Integration with Existing JavaScript Code

If you already have an existing React Native codebase, integrating TypeScript into the project is straightforward. TypeScript allows you to gradually adopt its features without requiring a complete rewrite of your app. You can start by converting just a few files to TypeScript, and over time, migrate the rest of your codebase to take full advantage of TypeScript’s features.

This seamless integration makes TypeScript an attractive choice for existing projects looking to improve code quality and developer productivity without sacrificing their current work.

5. TypeScript and React Native Ecosystem Compatibility

The React Native ecosystem is constantly evolving, with new libraries and tools being developed regularly. One of the advantages of using TypeScript with React Native is that it is well-supported by the React Native community. Most major libraries and components in the React Native ecosystem are TypeScript-friendly, and many even come with type definitions out of the box.

By using TypeScript with React Native, you ensure that your app is compatible with the latest libraries and tools, giving you access to a more extensive range of resources. Whether you're using navigation libraries, state management tools, or third-party APIs, the TypeScript integration ensures that you’ll have the right types to work with, reducing the chances of runtime issues and increasing productivity.

6. Integration with Mobile App Cost Calculators

When planning a React Native app development project, cost estimation is a key factor that businesses need to consider. A mobile app cost calculator can be an invaluable tool in helping you estimate how much time and resources will be required to complete the project.

Using TypeScript can actually help reduce development costs in the long run. By improving code quality and reducing the number of bugs, TypeScript enables developers to avoid costly fixes and rework. This means that businesses can expect a smoother development process, which can lead to a more accurate budget forecast, making it easier to plan for app launches and scaling.

7. Scalability for Large Projects

As your React Native app grows in size and complexity, maintaining a large JavaScript codebase becomes more challenging. TypeScript helps mitigate this issue by ensuring that the code remains organized and scalable. With features like interfaces and classes, TypeScript encourages better design patterns that are easier to extend as the app grows.

Moreover, TypeScript’s static typing helps ensure that your app’s architecture remains robust as new developers join the project or existing team members add new features. This scalability is particularly beneficial for React Native development companies that work on large projects that require long-term maintenance.

If you're interested in exploring the benefits Kotlin app development services for your business, we encourage you to book an appointment with our team of experts. Book an Appointment

8. Collaboration and Better Teamwork

For companies and teams working on large-scale projects, TypeScript provides a more consistent and predictable coding environment. Because the types are explicitly defined, team members can better understand each other’s code, improving collaboration. This reduces miscommunication and makes it easier to work on the same codebase without stepping on each other’s toes.

TypeScript’s built-in editor support, like IntelliSense in VS Code, further enhances the team’s ability to work together, providing real-time code suggestions and auto-completion. This leads to fewer errors and a more streamlined workflow for the entire development team.

Conclusion

The combination of TypeScript with React Native can transform the way you approach mobile app development, offering a safer, more efficient development experience. By adopting TypeScript, you benefit from type safety, improved maintainability, and better scalability, making it an ideal choice for both small and large projects. Whether you're an individual developer or part of a team, TypeScript enhances collaboration and reduces the risk of errors, ultimately resulting in a more robust and reliable app.

For businesses looking to bring their ideas to life, collaborating with React Native Development Companies experienced in using TypeScript ensures a smoother, more predictable development process. Don’t let potential bugs derail your project; opt for TypeScript to safeguard your app's success!

0 notes

thesyntaxdiaries · 2 years ago

Text

This blog covers lodash sort by functions. After an introduction, we'll install and import lodash. Basic sorting, property sorting, and custom sorting will be covered. You'll also learn to organize words, use descending order, and capitalize. We'll explore null and undefined values, nested object sorting, and performance. We'll also examine how these sorting strategies work in practise and why lodash's sortBy function is useful. We'll conclude with typical inquiries. Get ready to master sorting!

#Lodash Sort By

0 notes

walcutt · 2 years ago

Text

consider the following object, which is piece of our hypothetical vuex store:

foo: {

a: string,

b: string,

...

bar: {

z: string,

y: string,

}

now, when an action is pushed through to change this object, we need to do some validation. so i have a new object and a current object. if they differ, some other method needs to be run.

simple, one might say. we even have a method ready to check deep equality! let's just spin that up and, wait... why foo.bar.y undefined?

ok, let's print out all of the current foo.

foo: {

a: "",

b: "",

...

bar: {

z: "",

y: "",

}

ok, let's print out the current foo.bar.

bar: {

z: "",

y: undefined,

}

hm, ok, now, foo.bar.y is showing up as undefined. maybe something is not getting set? no? it's all being set in one place and clearly works? hm.

ok, let's reload the page again and check.

foo: {

a: null,

b: null,

...

bar: {

z: null,

y: null,

}

ok, it's empty the first time, but we haven't set it yet, but it's null, not undefined. but that's what i expect. that's normal.

ok, let's set the value. and let's check, and, ok!

bar: {

z: "",

y: ""

}

that's great! how about checking it directly?

y: undefined

i'm going to explode every computer.

ludicrously haunted javascript at work today

5 notes · View notes

pl-tournament · 2 years ago

Text

Match 1A[4]

Introducing an awful, cursed monstrosity that somehow spawned because people weren't satisfied with another language that a lot of people really love to hate on but is actually pretty alright... and JSFuck.

JSFuck

Everyone complains that JavaScript has too much going on. null *and* undefined? == and ===? where does it end? That's why I decided to thanos my keyboard so it only had 6 characters left. And it's still probably more usable than angular.js

C++

C is a highly performant, minimal language, that can do almost anything you put it to. It's often described as packing everything you need, and nothing you don't. C++ is not that language.

#plorbo #tournament #programming #tumblr polls #computer science #tech #jsfuck #javascript #cpp #c++

16 notes · View notes

kakitysax · 3 years ago

Text

Alright, okay, - real talk here?

So many aromantics face lonely lives. The cultural ideal of the nuclear family (no doubt propagated to avoid an overabundance of tax-and-billpayer’s “password sharing”) is so toxic to real love, and outright poisonous to the “alterous” attractions and affections that aromantic people feel.

But I have been so fucking fortunate to find a partner who loves me in the ways that I want to be loved, and is satisfied by the ways in which I express my own.

Being with her, being “us,” has taught me so many things: things that, by definition, I could not learn on my own; things that I never thought I would have the opportunity to understand.

Basic stuff. What it’s like to coexist with other people, like, REALLY coexist, instead of just being a lonely mind with a body existing in conjunction with other bodies.

Who I am in the context of other people, and what I’m like in terms of intimacy.

What love actually IS between two broken humans. The nebulous nature of boundaries. “Double Standards” and why sometimes they aren’t actually double standards and can be okay.

How little other people actually define you.

“The bonds of love,” and how they aren’t actually binding. How freeing and devoid of fear these ties feel.

All that being aromantic used to mean for me was that there was this massive way in which I couldn’t reach love. The label was a way for me to tell other people that I can’t perform their rituals of intimacy. That I can’t reach connection by the route that others all seem to understand, to EXPECT, to DEMAND.

The label is not just a ward, it’s an invitation. “There could be another way,” it implied, screamed into nothing.

And I thought that that was how it would stay, an invitation unanswered.

I knew that I was not unlovable.

But I never expected a human to want to learn how love me.

Maybe that’s why I was so intrigued by Max.

It was their art, I’ve said before: art filled with non-euclidian shapes, lines that curve and dance and spiral, the shape of nebulas, the delightful puzzle of asymmetry.

I could NEVER draw like that, and that’s what intrigued me. The “otherness” of her mind.

But the other thing that it told me about her was that this person was shapeless.

I saw someone deeply undefined. A deep shapelessness that ticked in their mind and spilled out through their hands.

She does not always like it. She feels lost. Alone in a mental world formless and void.

But that means EVERYTHING to me.

“Aromantic” is an invaluable descriptor of what my love is not.

But this relationship, this wonderful lover of mine, took me by the hands and looked me in the eyes and asked me what my love IS.

And I didn’t know how to respond!

“I don’t know,” I answered. “I didn’t think I would get this far.”

And I thought that that would be the end of it.

But she just smiled. “Then we can figure out together!” she told me.

It’s wonderful.

She is someone who sees chaos everywhere, even in the structure of an atom. She loosens the binding cords of my mind and encourages my asymmetry.

I am someone who sees order everywhere, even in the path of a raindrop down a windowpane. I cast gentle nets around the formless figures in their mind, giving name to null as I have learned to do.

She paints my landscapes.

And I chart her stars.

To me, that means more than the dance of roses and wine between those for whom romance is tangible. Our act of exploring what romance is not means more to me than the things we are just supposed to “know.”

The love that speaks at every step means more to me than the myth of understanding without words.

#okay to reblog #aromantic #qpr #qpr tag #queerplatonic partner #queerplatonic #love #queer #queer love #karkles stop #karkles irl #maxisfunky #karkles' qpr

35 notes · View notes

tap-tap-tap-im-in · 3 years ago

Text

I wanna talk about imposter syndrome again. Well, kind of. More honestly I think what I want to talk about is the feeling of not noticing your own growth.

I've said it here many many times, but I dropped out of college. Even if I had graduated, my degree was going to be in history and literature. The only real impact this has on my life is that I have gotten used to doing content writing and even put it on my resume as one of my skills. It even made the CTO of the company I'm waiting to start at laugh in our interview.

I'm mentioning it again because while I've always had a love for computers, it's always felt a little less like an expertise and more like a distant appreciation. For example, I love 3d engines, I have a pretty good surface level understanding of how they work and the different techniques they employ to achieve what they're doing, but if you asked me to write one I'd probably have to do a year or so of research before I had the fundamental math figured out to do anything.

But that's the really really sneaky part. If you'd asked me five years ago, I would have said I wouldn't *ever* be able to write one. I don't know that I'd be able to write a good one even now, but that's a pretty big step, and it's strange because like all progress you can't really see it until you look back on yourself. I'm feeling introspective because I just got done reading some notes on a CVE in nf_tables on Linux. The vulnerability itself was caused by an int overflow in a supporting function. Since the nf_tables help control user permissions, if you utilize the overflow to take permissions away permissions from yourself, you can give yourself greater permissions. It's the same fundamental issue that lets speedrunners manipulate the memory to give themselves infinite lives in games like Super Mario 64. And the part that was really strange is that halfway through reading an argument about how kernel level systems shouldn't really be using default C overflow behavior ,the argument against this seems to be that the alternatives are not common in cpu architectures so it's very expensive. Anyway, halfway through this highly technical argument, I realized that while I didn't have immediate context for programming in C, I do understand how many problems can be caused by overflows in C based languages (ever wondered why you sometimes do undefined or null damage in goblin puncher?), and not only do I understand the core problem, I understand enough of the technicalities to navigate this discussion to identify the mitigation steps. This one is easy, but it took some digging to find, update your kernel. That's it. It also looks like while this problem has been part of the nf_tables for a while, it only recently became exploitable due to another change, and this particular CVE was found in a release candidate update, so if you're on one of the stable upgrade paths you shouldn't have to worry.

But it's just strange. It's like realizing you've accidentally learned ancient Greek because you watched too much Hercules on disney as a child. That's how being able to follow your passions works though. And it's why I think that should be an option available to everyone. It turns out my brain doesn't have the patience to do deconstructive analysis of Beowulf, because it would rather focus on making connections to the underlying math involved in computer science.

#none of this is to say that I don't enjoy criticism or media analysis #just that my brain more naturally seems to favor the concrete answers dictated by mathematics #and that the passion for stories and writing was just kind of a happy accident #like I could never imagine trying to make my living as a fiction writer #but who knows #five years ago I couldn't imagine making my living by bossing computers around

2 notes · View notes

piecake-dbd · 4 years ago

Text

Every Window Is A Mirror Calling You

"Thank you for not trying to kill me", said the figure standing above me. I was currently caught in a nightmare and didn't want to look up to see his face. "I'm not the one you should be running from," he said. I was dreaming just a minute ago and I recognize this man. "Then why are you trying to kill me?" I asked When I venture into the empty places in my dreams, I find him waiting. "I have never tried to hurt you." "You chased me for years." He has so many terrible faces, I don't want to lift my head to learn one more. "I have an important message for you," he said, immediately and not addressing the context. "Every window is a mirror" "Why do you care?" I asked. "I care because it is coming for all of us," he replied. I could see the lower half of his body come into view as he crouched down to sit in front of me. It was all made of terrible machinery. "Where is it?" I asked. The man's frame quivered from a thousand destructive harmonic moments echoed from deep within his clocks. He fell on his ass and used both hands to keep himself from tumbling. "It's all around us right now. We're deep on the other side of it." "It doesn't seem so bad here," I retorted. The man became silent. I could feel my chest rising and falling, my eyes refused to focus on the ground in front of me. The world was silent around us. "Well? Why are you afraid?" I asked, wondering why I couldn't catch my breath. "Do you know who we call God here?" the man asked in a voice as cold and empty as an discarded road-side can. My hands are trembling but they won't stop. My hands want to clench but I am trying to keep myself upright. "Can you feel the subtle change?" he asked. I look up and see the man has fallen back on his elbows, staring straight up into the sky with his mouth agape. "How do I stop it?" His knees collapsed as the rust broke through the last few studs keeping it together. My arms gave out and I am on my elbows and knees face down. "Every window is a mirror," he insisted. The trembling reaches past my arms and wraps itself around me like frozen dew, I can't breathe. "I will find you and I will kill you," I gasped out in a hoarse voice with my last breath. The air around me is freezing solid and I can no longer feel my limbs. "I am already dead. You can never come back from where I am," he whispered through lips as dry as the last leaves on the porch. The last of my willpower cracked and I fell through the ground as the dream collapsed. I opened my eyes and saw the clouds above me were starting to part. The neighborhood was completely empty just like I left it. "Getting out of bed is the most difficult part isn't it?" I asked nobody. I stood up and brushed the snow off my body and looked back at the house I just finished before my nap. It was a single townhouse, built to last, with wiring, ducts, and pipes jutting from both sides like symmetric hairs. It would snap nicely together with itself so I can focus on just designing the interior. Standardized hookups also ensure the users will know where to look to inject their own modules. I glance back down at the snow where my silhouette now lay, taking my place in the land of dreams. Without the sun out, the shadows make it look deeper than it really was. The taste of metal flashes across my tongue and I feel a chill. "Configuration check," I murmur. A little device appears on my wrist where there wasn't one before and makes a single audible click as it displaces the air. "Previous configuration change, temperature sensation set to null, 2.57 minutes ago." "Why was the sensation module unloaded?" I asked "It was not unloaded, it timed out," it replied. "What is the timeout delay set to?" I asked, my arms and legs and back were all prickling like thousands of needles of anticipation. "Four hundred months," it chimed helpfully. "It's not cold here, it's cold out there..." I say to nobody. The lack of response is crushing. "The current temperature is set to zero," it offered. "How cold is it outside the simulation?" I asked. "Zero," it replied. "Celsius?" "Kelvin" it insisted. "That isn't funny." The silence is deafening. My ears are ringing. "I said that isn't funny," I insisted. "You slept through it," it replied in a voice I recognized as the man from my dreams. "I consumed it all." "ALL of it? You can't be serious," I asked. My hands wanted to clench into fists. "Every person connected to the Interface when it arrived was consumed." "And what about the others?" I asked, reaching to rub my arm slowly as the realization dawned on me. "Those not yet connected?" it asked. "Yes, innocent people," I pleaded, knowing my parents would have come looking for me after only a few days. "They were given the choice to connect or be put to rest." "And I don't get that choice?" "You do, that's why I have been waiting for you. Chasing you down." My fingers brushed over the clasp over the security buttons on my wrist monitor. "Do you know where we are?" I asked it. "Your simulation." "I work in the hazardous zone where they need people to force the noise into new space for the future residents," I said, my voice becoming dry. "We don't use verifiable delay functions out here. If something goes wrong, the only way out is to hit the escape button on my wrist." "Yes, that is how you were able to evade me in your dreams for so long," it chimed helpfully. “Your simulation is running on virtual particle systems which is inherently non-local. Not even I can see what is running.” "How many parallel universes did you need to create to collapse me?" I asked, feeling warmth surge through my cheeks. I wanted to know how many lifetimes I had wasted before I ended it. "Four hundred, sixty two." "Do you know how many lifetimes it takes to defeat you?" I asked rhetorically. "Undefined." "Four hundred, sixty three," I replied and turned my head to start walking in the other direction. "Where are you going?" it asked. "I'm taking you with me," I said, smiling wide as I looked straight ahead through the trees of this suburb and into the woods behind it where a creek runs. In the middle of the creek, slicing through the world itself, was the boundary. The boundary was the edge of all simulation. "I hadn't noticed that mine was the last one remaining in Collu-Ku because I was so used to working here." "Yes," it replied as a matter of fact. As I approached the boundary, I saw myself on the other side of it. Every version of me, hundreds of them all at once. The sight caused me to slip down through the mud and into the water of the creek, splashing water up that I couldn't even feel because of how cold everything was. "Stop," it beeped at me. "Are you ready?" "STOP," it cried, the voice splintering into a thousand harmonic tones. I took a step over the boundary and out of the simulation. I took a step out of my bubble and my universe splintered. Time ceased for us. Death's embrace wrapped around us and began the slow process of disentangling us from the rest of the universe. Each time it passed over me was like an oncoming train, splintering me into a hundred new timelines with each pass. "Who are you?" it asked me in the eternal silence between universes. "God"

2 notes · View notes