#mvc controller
Explore tagged Tumblr posts
Text
This is a huge gamble, but does anyone on here know how to work with passing JWTokens back and forth inside of HttpOnly cookies between a C# ASP.NET Web Api backend project and an ASP.NET Web MVC (Model-View-Controller) application frontend project (utilizing JavaScript and C#)???? I'm trying to work on a term project for an Advanced Web class, but I think I've blown it slightly out of proportion. I'm following tutorials, but having some difficulty wrapping my head around it.
#zer0pal's pen#student's gambit#hoping this pays off#csharp#asp.net#javascript#api#mvc application#model view controller#advanced web development#jwt
0 notes
Text
Understanding MVC Architecture in ASP.NET
MVC (Model-View-Controller) is a software architectural pattern that divides an application into three main components: Model, View, and Controller. ASP.NET, developed by Microsoft, leverages this architecture to create scalable, maintainable, and testable web applications. In this article, we’ll explore the MVC architecture in ASP.NET, how it works, and why it's a preferred pattern for developers.
What is MVC Architecture?
The MVC architecture separates an application into three interconnected components:
Model: Represents the application’s data and business logic. It directly manages the data and rules of the application, usually interacting with the database in ASP.NET MVC applications.
View: Responsible for displaying the data from the Model to the user. In ASP.NET, Views are typically Razor Pages or HTML markup that dynamically render content based on the data from the Model.
Controller: Acts as a bridge between the Model and View. It handles user requests, processes them (interacting with the Model as necessary), and decides which View to render. In ASP.NET MVC, Controllers are C# classes that manage the flow of data and handle business logic.
How MVC Works in ASP.NET
The request/response cycle in an ASP.NET MVC application follows this pattern:
Routing: The ASP.NET routing engine processes the user’s request and maps it to the correct Controller and action method.
Controller: Receives the request, processes it, and may interact with the Model to retrieve or update data.
Model: Contains the logic for data fetching, updating, or processing.
View: After processing the data, the Controller selects a View, which renders the data and generates an output (typically an HTML page).
Response: The generated View is returned to the user as an HTTP response.
This clear separation ensures that each component focuses on its own responsibilities, resulting in clean and maintainable code.
Key Components of ASP.NET MVC
Models in ASP.NET MVC
Models are responsible for representing the data and business logic of the application. They typically interact with the database, apply validation, and execute business rules. ASP.NET MVC models can use plain C# classes or the Entity Framework for database operations.
Example of a simple Model:
Views in ASP.NET MVC
Views present the data to the user and are generally Razor pages (.cshtml files) that combine HTML and C# code. Razor syntax allows developers to generate dynamic content while maintaining clean code.
Controllers in ASP.NET MVC
Controllers handle user input, processing the data, and determining which View to display. Each action method in a Controller corresponds to a specific endpoint.
Advantages of MVC Architecture in ASP.NET
Separation of Concerns: The business logic (Model), user interface (View), and input logic (Controller) are separated, making the application easier to manage, develop, and test.
Testability: Each component can be independently tested, improving the reliability of the application.
Scalability and Maintainability: As the application grows, features can be added without affecting existing functionality.
Extensibility: ASP.NET MVC is highly extensible, allowing developers to customize components like routing, filters, and dependency injection.
Better Control Over HTML and URLs: MVC gives developers full control over HTML and URLs, essential for building SEO-friendly applications.
MVC in ASP.NET vs. WebForms
Before ASP.NET MVC, developers commonly used WebForms, which followed an event-driven model. While WebForms is easier for beginners, it hides much of the complexity of HTTP, leading to less control over HTML and URLs. MVC, on the other hand, provides full access to underlying web protocols, giving developers more flexibility and control for building modern web applications.
ASP.NET MVC provides a powerful, flexible framework for building web applications with a clear separation of concerns. By leveraging the Model-View-Controller pattern, developers can build scalable, maintainable, and testable applications. Whether for simple websites or complex web applications, ASP.NET MVC offers the tools and structure for success.
For developers transitioning from older frameworks or starting fresh, MVC simplifies development while laying a solid foundation for modern and scalable applications
1 note
·
View note
Video
Nestjs MVC Project Tutorial for JavaScript Beginners| Model View Controller Full Video Link - https://youtu.be/UDR57jw38LA Check out this new video about Nestjs MVC Project on the CodeOneDigest YouTube channel! Learn nestjs project setup with dependencies to create MVC application. Create MVC web application in nestjs framework. #mvc #nestjs #modelviewcontroller #microservices #api #nodejs #javascript #codeonedigest #mvc
1 note
·
View note
Text
Xmas in the ER
*Hello there everyone, and merry Christmas to those who celebrate! As promised, here's my latest story. I hope you all enjoy the story as much as I do, and feel free to shoot me a message, comment, or leave me asks if you have any questions! I will also be posting another story sometime on New Year's Eve.*
As the old saying goes, Christmas is the most wonderful time of the year. The holiday is a great opportunity to spend time with loved ones, exchange gifts, and make lifelong memories. But for Dr Lindsay, this year’s Christmas was just another Wednesday where she was tasked with holding down the 7pm to 7am overnight shift in our ER. Naturally, Lindsay was bummed out about the idea of having to work on Christmas, but the emergency department is a 24/7 operation! Little did she know, she’d still have a holiday she’d never forget!
That night, the weather was awful. It was dark, freezing cold, and snowing heavily. Visibility was limited, and the roads were covered in a fresh coat of snow and ice. “Jeez… I bet we’ll have a couple of MVCs tonight.” Lindsay thought to herself shortly after she started driving, trying her best to carefully make her way to work through the frozen, wintery landscape. Fortunately for Lindsay, the roads were mostly empty, most people in the area opting to stay indoors. Even though the roads were empty, the conditions were less than ideal, so she felt the best move was to drive slowly.
Despite Lindsay doing everything in her power to arrive safely at the emergency department, fate had other plans for the cute, sporty tomboy doctor! On the highway about 10 minutes or so from her destination, Lindsay’s car slipped on a patch of ice on the road. The car almost immediately lost control, redirecting the doctor’s vehicle towards a cement barrier in the median of the highway. Lindsay’s heart raced as she white-knuckled the steering wheel, frantically attempting to regain control of the errant vehicle. But it all happened so fast! There was only so much Lindsay could do in those few seconds. Lindsay was unable to stop or change the trajectory of her car and slammed head on into the cement median.
CRUNCH! The windshield shattered, glass fragments flying everywhere inside the vehicle acting almost as little bits of shrapnel. Lindsay raised one arm to attempt to cover her face from the glass shards, but a few nicked her face and neck. The steering column was forced inwards, slamming Lindsay in her chest with tremendous force before being blown back a second or so later when the airbag deployed. “AHHH!” Dr Lindsay yelped, feeling something pop inside her chest. Even with the vehicle stopped after the impact, the momentum generated from the accident caused Lindsay to be thrown around a bit. Just like that, the roles were reversed, and now Lindsay found herself in need of assistance in the ER.
Upon arrival at the emergency department, Lindsay was awake, alert, and doing anything and everything she could to fight through the pain. While being wheeled in through the main entryway of the ER, she was laid out on a backboard atop a gurney with a c-collar around her neck. Lindsay was stripped barefoot, down to just her black sports bra and scrub pants. EKG electrodes and wires were stuck onto her torso, while IV lines were set up in each arm. A blood pressure cuff was wrapped around her left bicep, and a pulse oximeter was on her left index finger. The ER doc’s body was in relatively good shape, but she had some cuts and scrapes on her face and neck from the glass shards.
While being wheeled in, Dr Lindsay was experiencing a weird déjà vu of sorts. She’s walked through those same entryway doors more times than she could count, but she never saw the emergency department from that angle. She couldn’t wrap her mind around the idea of being brought in as a patient. Her pretty blue eyes scanned her surroundings, attempting to make sense of the nonsense. “33 year old female, blunt chest trauma, single car MVC. BP 60 over palp, heart rate’s 140 and climbing, pulse ox down to 90. Got IVs going on scene and started fluids, but her vitals aren’t looking too good.” Lindsay heard a female medic rattle off while wheeling the stretcher down the hall towards trauma room one. “Ok, thank you. Let’s get her over to trauma one. I’m gonna start her on the MTP and get a chest x ray.” A familiar voice replied to the medic. “who is that?” Lindsay thought to herself. “Dr Sarah maybe? I know she was supposed to work the day shift today.” Lindsay answered, still thinking to herself.
The gurney was still being wheeled towards the trauma bay. Dr Sarah leaned over, coming into Lindsay’s line of sight and lowered a stethoscope onto her chest. Sarah didn’t look down at Lindsay’s face, so she didn’t immediately realize who her next patient was. “Diminished breath sounds on the left side, we might need a chest tube.” Sarah observed, pulling her stethoscope away after a brief listen. Dr Sarah then looked down at the gurney, her eyes locking with Lindsay’s. Sarah’s eyes could be seen widening behind her glasses, absolutely stunned at what she was looking at. Sarah gasped, unable to get a word out. “Sarah….?” Lindsay whimpered, her voice weak and breathy. “OHMYGOD, Linds?! What happened?” Marveled Dr Sarah, still processing the concept of Dr Lindsay- a friend and coworker, being her next patient. Lindsay’s lip quivered, her eyes started to moisten. “my car… it just slipped… I don’t know what happened…” Lindsay explained to Sarah, her voice wobbly, now on the verge of tears. “It’s ok Linds, it’s gonna be ok! We’re gonna take a good look at you!” Consoled Sarah, gently grabbing Lindsay’s right hand, her voice a bit panicked.
Once in the trauma room, the stretcher was lined up parallel to the table, where Nurses Heather and Nancy waited. “LINDSAY?!” Heather exclaimed the instant she recognized who the patient was. “Hunny?! What happened?!” Nurse Nancy chimed in, equally surprised. Lindsay didn’t answer, but the familiar voices certainly comforted her through the terrifying uncertainty she was experiencing. “Let’s get her on the table on my count! One… Two… THREE!” Sarah barked out. The trio of beautiful ladies picked up the backboard and carefully moved their coworker onto the table while the paramedics took their stretcher back and exited the room. “Ah….” Winced Lindsay, feeling some pain inside her chest while being placed down on the table. Dr Lindsay squinted, the bright, fluorescent overhead light practically blinding her. “BPs 60 over palp and dropping. Hang 4 units of O-neg and prep Lindsay for a chest tube.” Ordered Dr Sarah, her voice urgent. “Linds? I have to put in a left chest tube. You know how bad they hurt, but be strong for me, ok? I promise I’ll be fast.” Dr Sarah kept Lindsay in the loop about her treatment. Lindsay hesitated for a moment, trying to mentally prepare for the pain she was about to endure. But the logical, doctor side of her took over, realizing that the brutal, painful procedure had to be done. Dr Lindsay’s eyes looked up at Sarah, and she nodded. “Go ahead.” Permitted Lindsay, giving Sarah the green light to begin chest tube placement.
Lindsay laid on the table in the supine position, her left arm raised above along her head. The normally calm and collected Dr Lindsay had a nervous expression on her face. The doctor turned patient’s lips were pinched tight, her forehead puckered, her icy blue-grey eyes looking in the direction of her left ribcage where the tube was to be inserted. She watched Dr Sarah insert a needle full of lidocaine to numb the skin. Lindsay felt a quick pinch, but nothing too worrisome. Sarah then sterilized the incision area with an alcohol wipe. “Ok Linds… Here we go…” The cute, nerdy redhead doctor told Lindsay, reaching for a 10 blade scalpel that sat on an equipment tray beside the trauma room table. Sarah took the scalpel and made a 1 inch cut at the intersection of the 4th intercostal space and anterior axillary line. Lindsay could feel the cold, sharp blade’s every move as it effortlessly slashed her skin apart. Lindsay saw stars, her eyes rolling back in pain. After the cut was made, Sarah attached a Kelly clamp to the proximal end of the chest tube, then bluntly inserted it into Lindsay’s chest cavity. “YAHHH!!!!” Yelped Lindsay, her eyes shooting wide open. Dr Sarah continued the procedure, guiding the tube further into Lindsay’s chest cavity into the pleural space. “AHHHH!!!” Lindsay let out a blood curdling scream, in absolute agony, her eyes tearing up, both her hands making tight fists, feeling the plastic tube forcing its way deeper inside her chest. There was a hiss of air once the tube reached the correct location from trapped air vacating Lindsay’s chest cavity. Lindsay gasped loudly and dramatically, then attempted to sit up. “whoawhoawhoa!” Nurse Heather stepped in, gently laying Lindsay back down on the table. “Stay still for us Linds. So far so good hunny.” Nancy chimed in, gently stroking Lindsay’s hair. Sarah lowered her stethoscope onto Lindsay’s chest and had a listen. “Tube’s in.” Sarah nodded.
Although Lindsay’s breathing improved following the chest tube placement, her vital signs continued to drop. Dr Sarah started another round of blood products and upped Lindsay’s meds, but that didn’t seem to be doing the trick. Lindsay began to shiver dramatically. Her long legs trembled and shook, and at the far end of the bed, her toes were scrunched up hard, showing off the white and red candy cane themed nail polish on her toes, along with the thin, wavy, prominent wrinkles that permeated the soles of the big, size 12 feet Lindsay was always so self conscious of. “Mmmmm…” Lindsay moaned. Dr Lindsay began taking rapid, shallow breaths, continuing to moan. “Shhh. It’s ok Linds. Hang in there a little longer for me…” Nurse Nancy’s calm, soothing voice told Lindsay. “I…I…” Lindsay babbled. “You what sweetie?” asked Nancy. “I just… I can’t believe I’m gonna die on Christmas…” Replied Lindsay, an impending sense of doom consuming her. The trio of caretakers in the room stood there frozen for a second, taken aback by Lindsay’s response. Nobody could believe that words like that were coming from Lindsay’s mouth. “You’re not dying hunny! We need you here New Year’s Eve! You know how we get slammed every year!” Nancy tried to encourage, her tone of voice upbeat and positive. “New Year’s Eve? Pshhh…” Lindsay scoffed, continuing to shiver. “I’m gonna be toe tagged and under a sheet in a little while…. Forget New year’s…” continued Lindsay. “No hunny, don’t say that! We’re gonna fix you up!” Nancy reassured, her voice getting a bit wobbly, upset by how Lindsay was talking about her own fate.
Before Lindsay could even answer, she started gasping loudly, taking deep, dramatic gasps. The heart monitors began beeping louder and faster, playing an almost ominous tone. “She’s crashing…” Heather announced. “linds? Stay with us hunny!” Nurse Nancy said to Lindsay, holding her right hand for a second. Again, Lindsay didn’t answer. Her frantic hyperventilating continued, her eyes WIDE open. “We need to intubate. 8.0 ET and a laryngoscope!.” Ordered Sarah, her voice roaring through the room. “Lindsay? I’m gonna intubate you, ok?” Sarah told Lindsay, moving to the head of the bed. Dr Lindsay looked up at Dr Sarah, their eyes locking for a moment. Lindsay looked like she was trying to mouth something, but couldn’t get the words out. “What’s up Linds?” asked Sarah. Lindsay didn’t answer. Her eyes shifted away from Sarah’s. Lindsay’s eyes remained wide open, but became locked at the ceiling. It was like a switch was flipped. Lindsay’s shivering and gasping came to an abrupt stop. The monitors began to alarm at that point. “V-fib! Starting compressions!!!” Nurse Heather shouted out. Heather immediately began chest compressions, pushing down on Lindsay’s chest hard and fast. Nancy swooped in, snipping off Lindsay’s sports bra, exposing her small breasts and hard nipples. At the head of the bed, Sarah got right to it, beginning rapid sequence intubation. The nerdy redheaded doctor carefully navigated the flexible plastic tube into her friend’s airway. Lindsay’s head bobbed and lolled around from the residual force of Heather’s hearty compressions, creating a moving target for Sarah- nothing that Sarah couldn’t handle! The breathing tube was navigated further into Lindsay’s airway, ending up in the correct depth and location in a matter of seconds. “I’m in!” Sarah confidently announced, taping the tube in place.
Post-intubation, the trauma team decided to shock Lindsay. The defibrillator paddles were charged to 200 joules, gelled, and pressed up against Lindsay’s bare, flat chest. “Alright! Everyone…CLEAR!” Sarah shouted, sending the first shock into the patient once everyone backed away. “MMMPH!” Lindsay moaned, as if she felt the shock. The first defibrillation didn’t do the trick, onto the second one! The defibs were recharged to 250 joules, and shock #2 was promptly delivered. “Mmm….” Moaned Lindsay, again, almost as if she knew what was being done to her. Shocks one and two didn’t do the trick, but third time’s the charm, right? The paddles were charged up to 300, and Lindsay was shocked. Her chest shot up and her back arched. She held that position for a second or two before plopping down onto the orange backboard. “Damn it, no change! Shocking again at 360. Everyone… CLEAR!” Barked Dr Sarah. KA-THUNK! Lindsay’s 6’1 frame was tossed around effortlessly by the stronger shock, but like before, v-fib persisted. With the paddles still pressed up against Lindsay’s bare chest, Sarah shocked Dr Lindsay again at 360 joules. At the far end of the table, Lindsay’s feet kicked up, slamming back down hard half a second later, wrinkling the soles of her big feet once again.
Following the fifth shock, the trauma team switched gears, giving CPR and ambu bagging another try. Heather placed the heel of her gloved hand on the middle of Lindsay’s chest and began pumping away hard and fast. Lindsay’s chest caved in, and her toned belly with abs rippled and jiggled out from the sheer force of the chest compressions. Heather felt Lindsay’s ribs break, but nonetheless, she kept up her life saving efforts. At the head of the bed, Nurse Nancy attached the ambu bag to the ET tube, puffing the light blue bag every few seconds or so, sending critically needed oxygen directly into the coding doctor’s lungs. Dr Sarah stood off to the side of the table injecting the first doses of epinephrine and atropine into Lindsay’s IV line in hopes of stimulating positive cardiac activity. While waiting for the meds to kick in, Heather kept at it, brutally going to town on her coworker (now patient’s) chest. Heather looked down at Lindsay’s face while continuing CPR. Lindsay’s head bobbed and bounced around in sync with each individual compression. Her eyes were WIDE open, her face locked in a full-blown death stare. The ET tube hung out the side of Lindsay’s mouth, taped in place, hugging her pale lips. Heather couldn’t believe a familiar face was in such dire shape. “The ones with their eyes open never make it…” Heather thought to herself. Back at the head of the table, Nancy continued ambu bagging. “You’ve got a long life ahead of you… We all love you and need you here Linds…” Nancy whispered into Lindsay’s ear, as if she was trying to convince Lindsay to not die.
Over the coming minutes, Lindsay’s chest began to take an absolute beating. A nasty bruise started to form in the center of her chest on top of the breastbone. Mid code, Lindsay’s chest tube began to drain a substantial amount of blood seemingly out of nowhere. “What the hell?...” A surprised Dr Sarah thought out loud. In the blink of an eye, a couple liters of blood drained through the tube. “She’s bleeding somewhere in her chest. Maybe a cardiac chamber or great vessel injury.” Speculated Sarah, trying to explain away what she was seeing. “I’m gonna do an echo. Let’s see what her heart’s doing. Maybe that’ll give me something to work with.” Sarah went on. With CPR ongoing, Sarah squirted a little bit of clear, conductive ultrasound gel onto Lindsay’s bare chest. She turned on the ultrasound monitor screen and lowered the wand onto the portion of Lindsay’s chest where the gel was and began moving it around for a second or two to spread it out a bit. Sarah then moved the ultrasound wand over Lindsay’s heart and eyes the monitor screen. “….oh Lord…what a mess in there…” Uttered Sarah. “Hmm?” Heather overheard. “Massive tamponade.” Sarah shook her head. “Pericardiocentesis?” asked Heather, wondering what the next step was. “I don’t think that’ll do the trick. We need to crack her chest and see what’s really going on in there. I’m gonna set up a thoracotomy tray.” Sarah explained to Nurse Heather. Nurse Heather’s eyes went wide once she heard the word “thoracotomy.” That was a last ditch effort, hail Mary procedure used in the most critical patients. Heather has seen many patients get their chest cracked during her time as a nurse in our ER, but the idea of a friend, coworker, and familiar face being the recipient of such a procedure really bothered Heather at a deeper level.
Betadine was splashed across the left half of Lindsay’s chest. The strong, chemical scent of antiseptic hit everyone’s nostrils in less than a second. Sarah picked up the scalpel, making a crude, but decisive incision. The cut started just to the left of Lindsay’s sternum, extended laterally across her chest, underneath her left nipple, and concluding just shy of her left armpit. Heather halted CPR while Sarah worked to separate the underlying tissue and muscle to make way for the rib spreader. With an adequate space created, the metal rib retractor was placed, and Lindsay’s chest was forcefully pried open. A loud popping and cracking sound echoed around the room while Sarah turned the knobs on the spreader. Upon entry to Lindsay’s chest cavity, there was a massive rush of blood. “Suction! SUCTION!” Shouted Sarah, packing handfuls of surgical sponges into the fresh incision area. Heather lowered a suction tube into Lindsay’s chest cavity and began removing the excess blood to create a good line of sight for Sarah. The suction tube made a wet slurping sound as it removed the blood. Meanwhile, Sarah incised the fibrous lining of the pericardium to relieve the tamponade and placed a vascular clamp on the descending aorta in order to redirect blood flow and quell any arterial bleeding- at least temporarily. Heather continued to apply suction every few seconds or so, the line of sight clogging up with blood like clockwork. “Starting cardiac massage.” Announced Sarah, reaching into Lindsay’s chest, beginning to vigorously massage away at Lindsay’s strong, athletic heart. Sarah’s gloved hands were wrapped firmly around the beautiful tomboy doctor’s heart, squeezing much needed blood to the rest of her body. A wet, rhythmic squishing sound was produced from Dr Sarah’s internal resus efforts. “Come on… come on Linds…” uttered Sarah under her breath.
Sarah squeezed and squeezed, but her multiple cycles of cardiac massage failed to restart Dr Lindsay’s heart. Next up, the team opted to give the internal paddles a try. The internal paddles were charged to 20 joules and lowered into Lindsay’s chest around her erratically twitching heart. THWACK! Lindsay’s heart tensed up for a second before going right back to v-fib. Sarah sighed. “No change, going again at 30. Everyone… CLEAR!” Sarah shocked again. Lindsay’s torso jolted sharply in response to the shock, but v-fib remained. “Hitting her again at 40!..... CLEAR!” Sarah’s voice surged. “Mmm….” Lindsay moaned in reaction to the shock. “she’s still in v-fib, let’s go again…. CLEAR!” Sarah yelled out passionately. A dull, wet thump was heard, however, Lindsay’s heart still couldn’t be shocked out of v-fib. “AGAIN!... CLEAR!” Yelled Sarah, lowering the blood soaked internal paddles back onto Lindsay’s cracked open chest. “Still nothing. Recharging the internal paddles to 40!” Sarah announced, her tone of voice growing more and panicked. The high pitched, electrical whirring sound of the paddles recharging bounced around the room. “Ok…. CLEAR!” Sarah defibbed Lindsay again. Almost instantly after the shock, the heart monitors flatlined. Lindsay’s heart sat completely motionless in plain sight. Dr Sarah removed the large, spoon shaped paddles and gently set them back on the crash cart. Sarah began removing her gloves and eyeing the clock on the wall. “It’s over. Time of death, 19:35.” Sarah called out, abruptly terminating the code.
The trio of caretakers stood there shell shocked for a moment while the high pitched hum of the flatlined monitors droned around the room. Nancy removed the ambu bag, a small amount of air quietly hissing out. Heather switched off the monitors, making the once loud, chaotic room eerily silent. Nobody said a word, but knew exactly what to do next. The IV lines were taken out of each arm. The EKG electrodes were disconnected. The BP cuff was taken off Lindsay’s left bicep. The pulse oximeter was taken off her left index finger. A blue surgical drape was hastily tossed on top of the thoracotomy site. Lindsay’s eyes remained wide open as her body was covered, appearing as if she watched the sheet get pulled over her head. Last but not least, a toe tag was filled out and placed on the big toe of Lindsay’s left foot. The tag dangled in front of Lindsay’s hot, wrinkly soles, serving as a harsh reminder that no Christmas miracles would be taking place that night. In this alternate reality, Lindsay was now the latest beauty who found herself toe tagged and under a sheet in our emergency department.
74 notes
·
View notes
Note
Hello, how are you doing? I’ve come with more questions >:3
1. Since cannonly Graves’ died in MW2, how is he alive? Did some cute girl/boy/enby necromance him or something? Or was it something more reasonable and realistic. Hell, was he even in the area when he was supposedly killed.
2. Is MW3 cannon in the ShadowDadlderverse? I hear it’s really really bad and not many or everyone considers it to be not cannon. This question goes hand in hand with the former
3. How did Graves’ feel when he realized that his dad wasn’t a hero? Did his finding out happen to coincide with Bell? Or is Graves still blind to what Addler did to Bell?
4. Since the Shadows are notably close in their verse, they most likely have game night. What games and movies do they play while together? What games and movies are banned?
5. Since I cannot go five questions without asking about fantasy and dnd, what would Graves character sheet look like? Class, race, backstory, spells, weapons, etc.
6. why is last name Graves? Is it his mother’s last name? Does like 7-11 call him Phillip A. Grave when pissed or something?(i definitely need to dig into the gas station man)
7. What is relationship with Laswell? And maybe if you’re feeling extra extra dangerous, maybe say what you picture Laswell’s wife to look like.
8. Also how old do you think Graves is? He can easily be seen as like 25-41. Or how old you think he is in your Au?
I know I am definitely asking some pretty deepish questions when it comes to your Au, but I like to learn. I especially like to learn about characters. And since your interpretation of Graves’ is currently scratching the itch I am internally inclined to ask these questions.
Stay safe!
Okaay here i gooo
1. I rly believe that tank was an unmanned vehicle that Graves controlled remotely while Soap ran around frantically XD hurling insults and a Shadow thumping him on the shoulder when he got carried away.
2. The only canon a peel off of mw3 and slap onto the Shadowdadler verse is that Makky is at large and Graves flew off into the sunset|
3. It depends on how he found out. If Graves knew what his father did at an early age, it’s be less of a shock. If Adler was honest about why a masked man was lurking somewhere nearby, told his son that he hurt one person for the sake of millions, it’d be better than if he tried to hide his actions. It wouldn’t surprise me if adult Graves grew to have a similar mentality as his father.
4. Game night’s full of multiplayer games (snash bros, mario party, MvC, etc). There’s a DnD session off to a corner. Ruined jenga towers litter the floor. A circle if Shadows play charades. Monopoly is DEFINITELY banned, too many fights break out. Any high shakes gambling on card games is also prohibited (there Shadows who are talented at card counting and sleight of hand). Any and all genres of movies are watches, with the exception of the Star Wars sequels. Those are unanimously banned.
5. I’d die if Graves was still the leader of a mercenary group but classed as a bard XD high charisma definitely. Still human. Idk enough about DnD as a whole to say what spells he’s gonna use but I like ghe idea of him boosting his part members that do the fighting
6. Ok so in one of my Dadler comics, Adler fights off and kills enemy agents that wanna target him and lil Phillip. He buries them in their backyard. Phillip learns one day that there are dead bodies there. Learns that they had to die for him to keep living. He’s looking at graves. The memory would stick with him. Lol 7-11 calls Graves Sir when the commanders being stubborn ir reckless 🤣 (funny, the Lt. can be just as stubborn and reckless)
7. Oh! I like her and the role she plays. I liked the sneaky sneaky part she had~ Her wife? I picture her a bit taller than Laswell. She’d be a brunette, soft featured, a bit tanned, down to earth and honest about her thoughts and feelings, something Laswell appreciates as someone used to subterfuge.
8. I got Graves at a solid 40. A tiny bit seasoned to be out in the field, but still young enough to be effective. He ages gracefully 🥰 hehehe
#that was an interview lmaoo i had fun!!!!#and thanks for asking!!#ask#call of duty#phillip graves#shadow company#mw2#mw3
20 notes
·
View notes
Text
(I realized on the second or third read that this is quite heavy on the angst so fair warning)
"Am I heartless?"
The words echoed in Legend's mind as he stood in the bathroom staring at himself in the mirror. Sky's voice screamed in his head, loud and soft, accusatory and questioning, hurt and resigned.
The person staring back at Legend wasn't really someone he seemed to know anymore. Tired eyes, skinny face (when had he lost so much weight? Had he always been this thin?), dry hair. He'd finished an eight night work stretch and it showed. He wasn't hungry, but he knew he hadn't eaten in twenty-four hours. He'd only had an energy drink as his entire sustenance at work last night. He'd worked a code, magically healed someone's stubbed toe, dealt with a family member snapping at him for taking too long to get test results that he couldn't even control, cleaned up someone's excrement four times, treated someone's migraine, told a creep that he could hold use the urinal just fine without Legend's help, saved another nurse from getting hit on by yet another creep, taken care of two teenagers who were coming from an MVC, and told someone that she'd miscarried.
And then he'd gotten off shift, driven to Sky's place since his friend had offered him a quiet place to decompress, slept, woken up, and read a book like it was a normal day. And then that evening Sky had the gall to ask if he was heartless. As if Legend hadn't just spent the night grumbling and laughing and making jokes with Warriors, teasing Hyrule whenever he saw him, and making dark comments about the entire situation.
Legend had long since accepted he was an ass. He'd accepted he was bitter and hurt, he'd accepted that he coped through keeping everyone at arm's length and laughing at the darkness around him. It's how they all coped.
He'd accepted that he was heartless. He had to be.
Sky's insistence on that being untrue healed something in his heart he hadn't even known was broken. He wondered if his other coworkers felt similarly. It was hard to tell - emergency personnel often didn't talk about what bothered them. They just laughed at it.
Why did it matter, whether he could feel things or not? Why did it matter that work bothered him but didn't? Why did it matter that he could watch someone die and crack a joke that would make people's heads snap towards him within the same minute?
Just how broken was he? Was it worth fixing? Why could he be having a good day and then all it took was one idiot to sour his entire opinion on humanity? Why did he get so angry, so hurt, so bitter? Why did the mistakes, the idiocy of one person make him distrust all people? Why were people just awful?
Why was he like this?
Legend reached up to his face, his fingers finding his earlobe and messing with the little hole where an earring would usually sit. He remembered the small, delicate hands that pierced them, the smell of the sea and laughter in the wind, the music and the fun nights, and the times when he did actually have some joy in his life.
He remembered the sand mixed with blood, the taste of bitterness and regret, the heavy decisions made in a single day.
He remembered all the emergency departments he'd finished, the poor management, the overworked staff, the entitlement of some patients, the desperation of other patients, the fear over being able to afford getting basic life saving care, the anger at how broken the system was, the frustration that could only be taken out on healthcare staff. He remembered the cases of abuse he'd reported, the anger in Hyrule's eyes when he brought in a drunk woman who survived a crash that she'd caused while the young mother she'd hit had been killed, the assault victims he'd treated, the frequent flyers who would just come for a sandwich but would cause a scene if they had to sit in the waiting room while actually sick people were taken back, the anger and hurt and bitterness and why were people like this?!
But it wasn't always bad. It wasn't. So he shouldn't just focus on the bad. He shouldn't just remember the bad. Why was that all he fixated on?
"What's wrong with me?" he muttered, leaning his head against the cool mirror on the wall.
"Am I heartless?"
No. No, Sky wasn't heartless. Sky had gone through a war, had seen things he refused to talk about, and he still had a warmth to him that Legend couldn't even fathom. Legend hadn't fought in a war, and yet here he was, being bitter about life.
You've fought in a war and you damn well know it, he reminded himself. As if the emergency department wasn't a war zone in its own right, as if he hadn't seen things that people weren't meant to see.
Ravio's words echoed in his mind next, insisting in how he was a hero, how all healthcare workers were heroes. It wasn't a new sentiment - many said it. But it didn't sink in. He didn't feel much like a hero. He just felt broken.
Maybe Sky was right. Maybe Legend wasn't actually heartless. Maybe he was just heartbroken.
#lu in healthcare#writing#lu legend#don't worry he gets therapy eventually#this got a lot angstier than I intended lol but oh well
81 notes
·
View notes
Text
✨️Duotale FAQ✨️
Just in case peeps ask questions a lot lol. Will add more as we go.
•What exactly is this AU about?
Its just a funny little AU where not all monsters were locked underground and some went into hiding instead. Some species of monster in this AU can take on human form with their magic, hence why this is possible. Of course, this doesnt stop kiddos, human or monster, from climbing that darn mountain though.
•When is the next page?
Duotale updates every month on a random date. Time varies but I try to keep it between 10am and 12pm EST. If we are busy (we currently are due to moving countries) the updates will be anywhere from 1 to 3 months.
•Why is this AU called Duotale?
Because the two main characters are twins, hence the Duo in Duotale. Ok they aren't twins, but they are siblings, born a few months apart. Yes, Strawberry is the Older one.
•Is the player a thing in this AU?
Maybe, maybe not. Depends on the AUs in the Citadel. No one is controlling the Duotale cast though. They've had their own mind and actions from the start. Underplayer is in the Citadel though, if you count them as a player.
●Can my AU be featured in your comic?
Why yes. Just refer to the link in the Masterpost labeled "how to get your AU into the comic". Follow the rules, answer the questions, and you'll be in where we can fit you! Do note that we will try to spread everyone out through different MVC visits, so please, don't be upset if your appearance isn't automatic! You will be seen eventually before the story's end! Scene art and asks are a different story though.
•Will Kris make an appearance?
Yes :3. I'll leave it at that. Ralsei will make an appearance in asks or art, Susie may or may not be in the comic itself. Here's the boi. During the comic he's a lil toddler. (Gender explaination is below btw for those that care.)
•Is Kris gonna be Frisk or Luci's counterpart?
No. Neither. They will be their own person.
●Is Clover gonna make an appearance?
Like Kris, the cowboy ghost will be there, but unlike Kris, you won't see him in comic til the end. He will (and has already) pop up on our blog, like Dalv or Star sherrif boi, but in comic, sorry, hes in Asgore's castle and that's so far away right now lmao. But here's how he looks. Yes, he knows the fox stole his hat. He does not know where his gun is, though.
●Will xxx color soul child also be in this AU?
Depends. We already have the Yellow soul decided (obvi). If There's another colored child you wanna see pop up as a canon-to-duotale ghost at the end of the comic you can ask, but so far only Clover and MAYBE Marine(Patience soul) but the lore is off that comic might contradict yellow or ours so that's undecided. Any other kids so far would be only seen in the MVC. We're trying not to pick kids in full existing sets so thats why Clover and maybe Marine are our only choices so far. We are more likely to make up the rest tbh. No more red souls though beyond cameos. Red souls work a special way in our AU and there's not a lot (if any) that can fit that requirement.
•Can other ghosts see Chara/Luci?
Yes. And she can see said other ghosts. Strawberry can only see those that she summons and Blackberry can see ghosts as well. Frisky can sense spirits near him but obviously cannot see them.
●Why do some characters have rings around them?
That just means they're dead. Ghosts. Spirits that didn't move on to heven or hell. The ring color matches the color of their soul and doesn't change. Luci, Blackberry, Dalv, and Kris have special rings though. They change color based on emotions. This color changing mood ring is only available to one species and it starts becoming visible around puberty. Luci is fullblooded, hence why her ring is always visible and changing like a rainbow, though Blackie and Kris aren't fullblooded, so their rings might be a bit faultly ha. If you're every curious what the colors mean, you can refer to the link labeled "Luci's mood ring" on the master post. Or a more simplified list ca be found on her teen ref.
•What exactly are the main cast's species?
Blackie is is a halfbreed kitsune vampire, Luci is a purebreed vampire with demonic powers, Strawberry is a tanuki who practices witch magic, and Frisky is a human. He just has a magical scarf to give him wings like redbull. As for Kris... you'll figure it out. No spoilers, sorry lol.
•How did you come up with the idea of Duotale?
Originally this story was gonna be a comic of our own runs in Undertale, showing how they clash and would effect each other. Kinda like thise PMD comics and Nuzlocke animations people make. But somewhere between writing the script and making the first cover art, we changed our minds and made a whole AU instead.
•Is fanart allowed?
Yes uwu. You can find character info and all current ref sheets in the Masterpost, last section at the bottom :3 If ya tag me, I can reblog it in my main account so peeps can see it, and an account I have specifically for or art made by others so I wont lose it. Main account is @oatmealkitty . That is where all non ask/comic art goes.
•What ships are in this comic/blog?
Oh boy a hard question to answer. Ignoring any cameos, out of our own and JUST our own characters this is the list. I'm probably missing a LOT though as these are off the top of my mind.
☆Friskyberry (Frisk x Blackie) | ☆Charaberry (Luci x Strawberry/Peaches) | ☆Charisk (Sugartale) | ☆Chariel (Luci x Cristal; in the past before adoption, though nothing comes of this.) | ☆Pappyton | ☆Soriel (They break up post story on mutual terms) | ☆Torgore (They break up before the story and never get back together.) | ☆Kingdings (Asgore's relationship post comic) | ☆Sansby (After Sans and Tori split) | ☆Alphyne | ☆Kris x Ralsei
•What are the pronouns of each character?
You will find all information on the masterpost, last section. If someone is missing we just didnt finish the refs yet. Apologies. Since I know MK, MTT and Blooky will be asked about due to lack of refs, they are all he/him here but Blooky and MK accept They/Them. Remember that this is an Alternate Universe, as in not sticking to the game's lore to a T. So please dont start a fuss over this. If canon versions of the characters ever speak or are spoken to in the Citadel, they will be referred to by the genders Toby (NOT THE FANDOM) placed on them, so be happy with that smh.
A note to avoid confusion since I KNOW this will cause issues if I don't give a bible explanation: WITHIN the comic, Kris' pronouns will be he/him, hence me calling the younger one he/him. Personally, I can't see a literal 3 year old toddler changing his gender or even caring about that. I know I sure didn't back then lol. I didn't care till damn near the end of highschool tbh. Soo, He starts requesting people use they/them (if possible) in his late teens as thats what I personally experienced. Sorry to anyone who wants out of the womb non binary/trans babies. Oh and when he's spoken to or about in another language, regaurdless of age, it will be male pronouns bc languages. Sorry, can't fix that either. That's just how languages work. So yeah, Tldr: In comic=he/him. In asks=they/them (he/him if non english language).
𖤐~~~~~~𖤐~~~~~~𖤐
✨️Asks✨️
•You can ask LITERALLY anything to ANYONE. Even the mods.
•All questions will go to the cast as they are in the comic, unless we allow asks for the adults for some reason. All asks starting in chapter 2 are considered canon.
•You can ask spoiler based questions, but they will either be heavily censored or answered in a joking manner as to not give away everything that happens in the story. Depending on the question, we may not be able to answer it at all though.
•All asks that seem like spam will be ignored. I know we answered them before jokingly but after a while it becomes too much. Also! We will ignore asks about religion (offensive/forcing), racism, sexism, stuff like that.
#Duotale#FAQ#undertale#deltarune#undertale au#undertale blog#undertale ask blog#undertale art#undertale community#undertale askblog#undertale alternate timeline#undertale yellow#uty clover#utmv fanart#utdr fanart#utau fanart#ut yellow
25 notes
·
View notes
Text
Laravel Là Gì?
Laravel là một framework PHP mã nguồn mở được thiết kế để phát triển các ứng dụng web theo kiến trúc MVC (Model-View-Controller). Ra mắt lần đầu vào năm 2011 bởi Taylor Otwell, Laravel nhanh chóng trở thành một trong những framework phổ biến nhất trong cộng đồng lập trình PHP nhờ sự đơn giản, mạnh mẽ và linh hoạt.

Laravel cung cấp một loạt các công cụ và tính năng hữu ích, giúp tăng tốc và tối ưu hóa quá trình phát triển phần mềm. Một số tính năng nổi bật của Laravel bao gồm hệ thống định tuyến mạnh mẽ, ORM (Eloquent) để làm việc với cơ sở dữ liệu, hệ thống migration để quản lý database, và các công cụ tích hợp như Artisan CLI (dòng lệnh) hỗ trợ tự động hóa nhiều tác vụ.
Ngoài ra, Laravel còn hỗ trợ việc bảo mật với các cơ chế như xác thực người dùng, mã hóa, và bảo vệ ứng dụng khỏi các lỗ hổng bảo mật phổ biến (CSRF, SQL Injection). Đặc biệt, Laravel đi kèm với Blade – một công cụ tạo giao diện thân thiện và hiệu quả.
Với hệ sinh thái phong phú như Laravel Forge, Nova, và Envoyer, framework này không chỉ phù hợp cho các ứng dụng nhỏ mà còn mạnh mẽ đủ để phát triển các hệ thống lớn, phức tạp. Laravel là lựa chọn lý tưởng cho các lập trình viên PHP muốn xây dựng các ứng dụng nhanh chóng và chuyên nghiệp.
Nguồn: https://thuegpu.vn/laravel-la-gi-cai-dat-va-cau-hinh-laravel-voi-nginx-tren-ubuntu/
2 notes
·
View notes
Text
The next installment of Marvel Vs Capcom is here!
And it’s made by fans!
…Wait, what?
It’s been quite some time since the last game we got from the series. As many know, Marvel Vs Capcom Infinite left much to be desired; however, despite this slight stumble in the history of these games, everyone continues to enjoy the saga. Yes, everyone, there is not a single person who doesn’t love the MvC titles.
Due to this undeniable fact and the lack of new VS games, it was only a matter of time before a group of (super)heroes took control of the situation. Thanks to their great efforts and dedication, one of the best things that could happen in recent times manifested itself: mods! But not just any mod, these are for the favorite of many: Ultimate Marvel Vs Capcom 3.
It hasn’t been easy to get to this point. Unlike other games, UMVC3 had too many restrictions, and creating a mod seemed almost impossible a couple of years ago. The tools were few, the options limited, and at most, only small aesthetic changes could be made, nothing that would catch the public’s attention outside of the most hardcore fans; not to mention that the PC version was released in 2017, six years after the original on consoles! Today, words are lacking to describe how much these dedicated modders have achieved.
In this post, we will review the timeline of UMVC3 mods, a task that started as a dream and is now a reality, and what a reality it is. Grab some popcorn and keep scrolling, there’s a lot to see!
For a better experience, I recommend reading and watching the videos in the order presented.
Level 1: Cool!
The first mods were simple. Not many changes could be made. As expected, the most basic was to change colors, textures, and music. In the following images, we can compare the original alternate colors of Akuma versus the colors modified by user BruicidalBleathMetal on Gamebanana, on April 13, 2017.
(Akuma, original alternate colors. Ultimate Marvel Vs Capcom 3).
(Akuma, modified colors. Source: BruicidalBleathMetal, Gamebanana).
————————- 0 ————————-
Level 2: Great!
During this time, it was believed to be difficult to do anything beyond colors. Extra characters? New modes? Yes, sure… modifying the game was almost impossible. But then a light began to fall from the sky and it looked closer and closer and closer… No wait, it wasn’t a light, it was Doom doing a FOOT DIVE.
This is when it was discovered that some VERY small edits to movements could be made; as small as saying that if a projectile went to the right in the original game, now it could be changed to go in a random direction, wow!
youtube
(Arthur’s projectiles here should go forward, but they were changed to be launched in any direction).
This discovery was important; being able to modify movement statistics meant making them better or worse. Where does this lead? To balancing the game! (something that Capcom didn’t seem too interested in, cough cough). UMVC3 is notorious for having very powerful characters. This inevitably resulted in the first major mods focusing on balance, such as UMVC3 Arcade Edition, Project Mahvel, UMVC3EX, among others; different mods with the same goal: nerfing Morrigan, Vergil, and Zero (lol).
youtube
(UMVC3 Arcade Edition gameplay).
————————- 0 ————————-
Level 3: Awesome!
Well, we’ve modified movements, can we do anything else with them? Yes! We can alter their properties, swap them between characters, compile them into one. We can give Doom’s missiles to Chun-Li…
Chun-Li with missiles? That sounds familiar…
Here’s how the first “original” characters appeared: Shadow Lady over Chun-Li, Lilith over Morrigan, Orange Hulk over Hulk, and Evil Ryu over Ryu. Unlike previous mods, these characters were not the originals with balance alterations; no, these were unique characters and functionally different from their counterparts, a concept seen in earlier games in the series like Marvel Vs. Capcom 1. These became known as “palette swap” characters (or PS from now on).
youtube
(The first developed Palette Swap characters).
————————- 0 ————————-
Level 4: Wonderful!
The beginning of greatness. Let’s get straight to the point; finally, we see our first completely original character*: Captain Marvel, created by Tabs, one of the most important modders in the scene.
*IgnoringthefactthatsheappearedinMVCInfinite,sonotTHAToriginal.
youtube
(The first look at Carol Danvers, Captain Marvel, using the Phoenix model as a base).
This could be considered the true beginning of the scene. The importance of Captain Marvel was considerable, as it would lead to the discovery and development of techniques that resulted in the creation of other original characters like Ken, Cyclops, Thanos, and more.
These techniques involved taking animations and movements from other characters and putting them in one place since creating them from scratch was impossible. You can clearly see how we could have new characters, but still using resources from the same game:
youtube
(First look at Cyclops, using C. Viper as a base).
However, by only being able to use these resources, some… interesting results occurred. C. Viper was used because she already has a movement in reference to Cyclops’ “Optic Laser.” After editing the model and some textures, this is how our favorite laser pointer turned out:
(Cyclops… your arms…).
But hey! If you squint your eyes, it kinda looks similar, right? (coping).
I can’t help but mention one of the most iconic side effects of this experiment: a hip movement that is quite…*sweats*.
(Shakira who?).
————————- 0 ————————-
Maximum Level?!: Viewtiful!
Cyclops and the others can now shed their old skin and show off their glorious designs they’ve always had. This is thanks to a model importer that was developed. Gone are the days of taking and editing existing models; now, everyone can look as we know and love them.
(Model importer announcement screenshot).
Here’s a trailer of how the game was looking at the time with all the aforementioned improvements:
youtube
(Gameplay trailer of PS characters with their new models).
————————- 0 ————————-
Level 6: Uncanny!
Okay, okay, I know seeing these characters in this way is amazing, but calm down; we’re not done yet, there’s something very important missing in this journey.
Because the modified characters replace their original counterparts, pairs like Cyclops and Viper or Frank West and Ultron couldn’t exist on the same team. Is it because these pairs are enemies who secretly love each other and that’s why they can’t be together? Yes No, the PS characters use the space of an original character, meaning both cannot coexist within the game at the same time. Even if you wanted to have them together, it’s simply impossible.
Or it was! At this point in the timeline, modder Gneiss developed a tool called the “Clone Engine,” allowing him to create new spaces independent of those used by the original cast. Now you CAN have Frank West and Ultron together, the pair of your dreams.
A fun fact about this section is that YouTuber Maximilian Dood, known for his fighting game content, put a bounty for anyone who could develop this tool, and as you can guess, Gneiss was the one who claimed it. Here’s Max offering the reward and here awarding it to Gneiss.
youtube
(Gneiss showing that it’s possible to have two characters using the same space on the same team).
————————- 0 ————————-
Level 7: Crazy!
We have everything we need, what more could be missing after so much?
Well… the PS characters are still based on movements from others. Believe it or not, the animations you’ve seen in the previous videos are still not created from scratch by the modders but continue to use the technique of taking animations from the base characters and combining and editing them to create new ones. In their early stages, this resulted in what happened with Cyclops, but after much trial and error, it was hardly noticeable that this wasn’t official game content.
This video from CaliKingz, another important modder for the scene, shows the immense progress made as months passed. He has created characters like Gambit, IceMan, Captain Commando, and many more.
youtube
(Gambit gameplay).
However, now it’s no longer necessary to do this only, and the process is much simpler (at least in comparison), as we finally have:
(First trailer of PS characters with custom animations).
————————- 0 ————————-
Level 8: Unstoppable!
FINALLY! We’re almost at the end of our story, for now. The last thing to mention is that people are working on the next big barrier: creating a stable online mode using Rollback netcode.
Did you play UMVC3 online? Or maybe other games like Smash Bros. or Street Fighter IV? If the answer is yes, then you know that playing them online was like trying to fight underwater, unless maybe you lived near your opponent. That’s what this mod is trying to change.
If you don’t know, in very basic terms, Rollback is a system that makes playing online feel the same as playing offline, without delay when pressing a button, no matter where your opponent is. The system instantly handles latency between both players, making “predictions” of where the characters are when a button is pressed. Yes, it’s somewhat complicated, but the important thing is that it results in a much smoother experience. Games like Mortal Kombat 1, Street Fighter VI, and many more use this system.
Not everything goes as one would like, however. Twitter user HkHaan96 was working on this mod, but then gave us the latest update on this project in November 2023. Despite having successful tests, he announces that he will no longer work on it, and other people would take his place. To date, we haven’t had any news about this, but let’s hope that someday we can have something that gives UMVC3 the online mode it deserves. We thank Hk for his dedication!
(Demonstration that both versions can be synchronized with Rollback).
————————- 0 ————————-
And thus, we arrive at the present, quite a long journey, isn’t it?
Now we can enjoy something that was only fantasies years ago. Remember in the ‘90s when you played MVC1 for the first time in the arcade, and that made you think, “What if in the future I could make Doctor Wily fight against Doctor Octopus?” No, just me? Well, but now it could happen!
It’s a matter of waiting and seeing what more these dedicated and hardworking modders do. Who knows, maybe you can become one and create that dream character. The possibilities are truly “Infinite.”
Thanks to:
- Tabs, for their help with information about the first PS characters. Subscribe to their YouTube channel or follow them on Twitter to see their latest mods.
- Marvel Modded, for their help confirming the mods timeline. Follow them on Twitter to stay updated on the biggest mod “Community Edition,” a project that aims to unite all mods made by the community.
- All modders in the scene, for their great efforts that will keep this game alive for many years to come. The list would be endless if we included everyone, but please know you are all extremely appreciated!
#marvel vs capcom#umvc3#gaming#marvel#capcom#fgc#fighting game#youtube#writing#Youtube#featured#article
8 notes
·
View notes
Text
4 notes
·
View notes
Text
Comparing Laravel And WordPress: Which Platform Reigns Supreme For Your Projects? - Sohojware
Choosing the right platform for your web project can be a daunting task. Two popular options, Laravel and WordPress, cater to distinct needs and offer unique advantages. This in-depth comparison by Sohojware, a leading web development company, will help you decipher which platform reigns supreme for your specific project requirements.
Understanding Laravel
Laravel is a powerful, open-source PHP web framework designed for the rapid development of complex web applications. It enforces a clean and modular architecture, promoting code reusability and maintainability. Laravel offers a rich ecosystem of pre-built functionalities and tools, enabling developers to streamline the development process.
Here's what makes Laravel stand out:
MVC Architecture: Laravel adheres to the Model-View-Controller (MVC) architectural pattern, fostering a well-organized and scalable project structure.
Object-Oriented Programming: By leveraging object-oriented programming (OOP) principles, Laravel promotes code clarity and maintainability.
Built-in Features: Laravel boasts a plethora of built-in features like authentication, authorization, caching, routing, and more, expediting the development process.
Artisan CLI: Artisan, Laravel's powerful command-line interface (CLI), streamlines repetitive tasks like code generation, database migrations, and unit testing.
Security: Laravel prioritizes security by incorporating features like CSRF protection and secure password hashing, safeguarding your web applications.
However, Laravel's complexity might pose a challenge for beginners due to its steeper learning curve compared to WordPress.
Understanding WordPress
WordPress is a free and open-source content management system (CMS) dominating the web. It empowers users with a user-friendly interface and a vast library of plugins and themes, making it ideal for creating websites and blogs without extensive coding knowledge.
Here's why WordPress is a popular choice:
Ease of Use: WordPress boasts an intuitive interface, allowing users to create and manage content effortlessly, even with minimal technical expertise.
Flexibility: A vast repository of themes and plugins extends WordPress's functionality, enabling customization to suit diverse website needs.
SEO Friendliness: WordPress is inherently SEO-friendly, incorporating features that enhance your website's ranking.
Large Community: WordPress enjoys a massive and active community, providing abundant resources, tutorials, and support.
While user-friendly, WordPress might struggle to handle complex functionalities or highly customized web applications.
Choosing Between Laravel and WordPress
The optimal platform hinges on your project's specific requirements. Here's a breakdown to guide your decision:
Laravel is Ideal For:
Complex web applications require a high degree of customization.
Projects demanding powerful security features.
Applications with a large user base or intricate data structures.
Websites require a high level of performance and scalability.
WordPress is Ideal For:
Simple websites and blogs.
Projects with a primary focus on content management.
E-commerce stores with basic product management needs (using WooCommerce plugin).
Websites requiring frequent content updates by non-technical users.
Sohojware, a well-versed web development company in the USA, can assist you in making an informed decision. Our team of Laravel and WordPress experts will assess your project's needs and recommend the most suitable platform to ensure your web project's success.
In conclusion, both Laravel and WordPress are powerful platforms, each catering to distinct project needs. By understanding their strengths and limitations, you can make an informed decision that empowers your web project's success. Sohojware, a leading web development company in the USA, possesses the expertise to guide you through the selection process and deliver exceptional results, regardless of the platform you choose. Let's leverage our experience to bring your web vision to life.
FAQs about Laravel and WordPress Development by Sohojware
1. Which platform is more cost-effective, Laravel or WordPress?
While WordPress itself is free, ongoing maintenance and customization might require development expertise. Laravel projects typically involve developer costs, but these can be offset by the long-term benefits of a custom-built, scalable application. Sohojware can provide cost-effective solutions for both Laravel and WordPress development.
2. Does Sohojware offer support after project completion?
Sohojware offers comprehensive post-development support for both Laravel and WordPress projects. Our maintenance and support plans ensure your website's continued functionality, security, and performance.
3. Can I migrate my existing website from one platform to another?
Website migration is feasible, but the complexity depends on the website's size and architecture. Sohojware's experienced developers can assess the migration feasibility and execute the process seamlessly.
4. How can Sohojware help me with Laravel or WordPress development?
Sohojware offers a comprehensive range of Laravel and WordPress development services, encompassing custom development, theme and plugin creation, integration with third-party applications, and ongoing maintenance.
5. Where can I find more information about Sohojware's Laravel and WordPress development services?
You can find more information about Sohojware's Laravel and WordPress development services by visiting our website at https://sohojware.com/ or contacting our sales team directly. We'd happily discuss your project requirements and recommend the most suitable platform to achieve your goals.
3 notes
·
View notes
Text
Getting into fighting games now is wild since I picked up both Marvel vs Capcom 3 and MvC Infinite and I am shocked that Infinite is the newer game when it has worse everything, worse graphics, worse controls, worse roster, worse music, why does an Xbox 360 game look better then an Xbox One game?
5 notes
·
View notes
Text
자바 → 고언어
예전에 고(go) 언어 얘길 한 번 써서 올리긴 했으나 왜 이거에 관심을 두게 됐는지를 빼 먹고 지나친 것이 기록 강박이 있는 사람으로서 영 찜찜해 적어놔야 겠기에. 원인은 자바로 개발하기가 넘 싫었기 때문. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
지난 십 년 넘게 나를 먹여 살린 프로그래밍 언어는 자바(JAVA)였지만, 아이러니하게도 내가 그동안 접한 언어 중에서 제일 싫어하는 거기도 하다.
구구절절 이유를 나열하기보다 총체적으로 한 줄 요약하면, 어릴 적 세운 상가 길바닥에서 처음 배우면서부터 즐겼던 프로그래밍하는 재미를 빼앗아 갔다. 하지만 한국 IT 업계는 자바가 대세라 이걸로 짜야 돈 준다는 데 별 수 있냐, 꾹 참고 했지.
자바는 '객체 지향' 강박이 매우 심한 언어다. 그 시절엔 이 기법이 프로그래머를 구원할 궁극의 진리 같은 느낌으로 여기저기에서 떠받들었던 기억이 내게도 있기 때문에 이해는 함. 그래서 "Hello World" 한 줄 찍으려고 해도 class부터 만들어야 한다.
EJB는 "엔터프라이즈 자바 빈"의 약자로 대규모 웹페이지 만들 때 썼던 거. 복잡하기가 개미지옥 같아, 자바의 대표 흑역사랄 수 있다. 대안으로 스프링(Spring)이라는 프레임웍이 나왔다. 자바 프로그래머들이 무척 좋아했다. 바로 이 부분이 열나 어이없는 거. 스프링은 EJB에 비해 편리하단 것일 뿐, 여전히 짜증 나는 물건이거든.
이 프레임웍의 핵심은 의존성 주입(=Dependency Injection)이라고 한다. 말은 거창하지만 인터페이스(interface)를 써서 코딩하는 짓을 과대 포장한 거. 내가 보기에 여러 개발자 집단 중 유독 자바 쪽 인간들이 허장성세가 심한 편인 거 같다. 이런 점도 거슬려하는 부분 중 하나.
'전자 정부 프레임웍'은 한국 정부가 강제로 정해 놓은 스프링 기반 개발 스펙이다. 이걸 적용해 DB에서 데이터를 꺼내 오려면, Controller → Interface → Implement → DAO 무려 4단계를 거쳐야 한다.
내가 보기엔 규모가 크지 않은 웹페이지의 경우 Controller와 Implement만 있어도 됨. 이 두 개가 꼭 있어야 하는 이유는 Implement에서 트랙잭션이 발생하기 때문에.
DAO는 Implement가 흡수할 수 있기 땜에 진짜 필요 없다. Interface는 애매하다. 만약 비교적 최근 등장한 go언어, 파이썬처럼 덕 타이핑(Duck Typing)을 지원한다면 당연히 처음부터 필요한 게 아니다. 자바가 클래스에 집착하는 언어인 데다 스프링 개발한 놈들이 자랑해 마지않는 의존성 주입을 포기할 수 없어 계속 이렇게 갈 듯.
이 인간들은 자바 패밀리 중 JSP를 병적으로 싫어한다. 왜 그러는지 이해 가는 면이 있긴 하다. JSP는 (PHP처럼) 그 자체로 하나의 개발툴이기도 하니까. 너무 많은 기능을 내장하고 있다 보니 JSP를 허용하면 MVC(Model - View - Controller)의 토대가 흔들리면서 뒤죽박죽인 코드를 양산할 우려가 큰 거. 그래서 기능을 제한한 JSTL이라는 템플릿으로 뷰(View) 화면을 만들라고 강요한다.
스프링으로 개발할 땐 심지어 컴파일 시간마저 짜증을 유발한다. 사소한 거 하나만 수정해도 프로젝트 전체를 빌드해야 해 결과 나올 때까지 멍때려야 하는 시간 낭비가 크다. 그만큼 개발 속도가 상당히 더디다.
설상가상 가상 머신(=JVM)에서 돌아가기 때문에 느리다. 초기엔 이거 덕분에 컴파일 한 번 해서 여기저기에 다 쓸 수 있다는 명분이 있었지만, 지금은 그 규칙도 사실상 깨져버린 상태. 장점은 느릿느릿하긴 해도 안정적인 거 같긴 하다. 오늘날까지 자바가 살아남은 결정적 요인은 하드웨어 성능이 올라갔기 때문일 듯.
예전에 자바 안에 파이썬 소스를 포함해야 할 일이 있었다. 구글 검색하니 '자바 + 파이썬 = 자이썬'이란 게 있다길래 함 써봤다가 너무너무 느려서 바로 폐기. 그래서 파이썬을 따로 만들어 서버에 저장하고 자바에서 리눅스 쉘 스크립스트를 실행하게 하는 약간 촌스런 방법을 썼다.
자바는 설계 구조상 메모리도 많이 잡아 먹을 수밖에 없다. C처럼 포인터를 지원하지 않기 때문에 함수 호출할 때마다 파라미터와 리턴값을 통째로 복사할 수밖에 없거든. 종종 클래스 전체를 주고받을 때마다 '아, 이게 뭔 뻘짓인가' 자괴감마저 들곤 한다.
그러던 중에 고(Go) 언어를 살펴 보니 진짜 맘에 쏙 들었던 거. 우선 자바와 달리 무척 컴팩트하다. 개발자가 허풍을 안 깐다. 게다가 핵심 인물 중 한 분이 내 닉네임과 같은 켄(=Ken Thompson)이다.
당연히 포인터 있다. 하지만 C/C++처럼 포인터 연산은 지원하지 않는다. 이것이 '버퍼 오버플로우' 같은 버그를 일으키는 원인이란 판단 때문이었을 듯. 진짜 좋다.
고언어는 자바처럼 객체 지향에 집착하지 않는다. 대신 구조체와 인터페이스를 이용해 동일한 성능을 낼 수 있다. 이거는 나도 예전부터 생각했던 거였으나 삼류 개발자라 자신 있게 주장하진 못했는데, 정말로 ���는 거였다니…
병렬 처리가 기본인 시대에 태어난 언어답게 쓰레드 처리가 무척 간단하다. 문장 앞에 'go'만 붙이면 되니까. 다만 자기 손을 떠난 쓰레드를 제대로 관리하지 않으면 먹통이 된다. 그래서 '채널'이란 걸 잘 써야 하던데 아직까진 능숙하지 못하다. 실무에 써 보면 감을 잡을 수 있을 거 같긴 한데.
그러나 고언어가 아무리 좋으면 뭐하냐. 아직까지 한국은 "Hello JAVA World"인걸… -_-;; 하루속히 고언어가 쭉쭉 성장했으면 좋겠다. 그럼 고언어 전문가인 척 구라까고 돈 받으면서 공부해야지.
2 notes
·
View notes
Text
java full stack
A Java Full Stack Developer is proficient in both front-end and back-end development, using Java for server-side (backend) programming. Here's a comprehensive guide to becoming a Java Full Stack Developer:
1. Core Java
Fundamentals: Object-Oriented Programming, Data Types, Variables, Arrays, Operators, Control Statements.
Advanced Topics: Exception Handling, Collections Framework, Streams, Lambda Expressions, Multithreading.
2. Front-End Development
HTML: Structure of web pages, Semantic HTML.
CSS: Styling, Flexbox, Grid, Responsive Design.
JavaScript: ES6+, DOM Manipulation, Fetch API, Event Handling.
Frameworks/Libraries:
React: Components, State, Props, Hooks, Context API, Router.
Angular: Modules, Components, Services, Directives, Dependency Injection.
Vue.js: Directives, Components, Vue Router, Vuex for state management.
3. Back-End Development
Java Frameworks:
Spring: Core, Boot, MVC, Data JPA, Security, Rest.
Hibernate: ORM (Object-Relational Mapping) framework.
Building REST APIs: Using Spring Boot to build scalable and maintainable REST APIs.
4. Database Management
SQL Databases: MySQL, PostgreSQL (CRUD operations, Joins, Indexing).
NoSQL Databases: MongoDB (CRUD operations, Aggregation).
5. Version Control/Git
Basic Git commands: clone, pull, push, commit, branch, merge.
Platforms: GitHub, GitLab, Bitbucket.
6. Build Tools
Maven: Dependency management, Project building.
Gradle: Advanced build tool with Groovy-based DSL.
7. Testing
Unit Testing: JUnit, Mockito.
Integration Testing: Using Spring Test.
8. DevOps (Optional but beneficial)
Containerization: Docker (Creating, managing containers).
CI/CD: Jenkins, GitHub Actions.
Cloud Services: AWS, Azure (Basics of deployment).
9. Soft Skills
Problem-Solving: Algorithms and Data Structures.
Communication: Working in teams, Agile/Scrum methodologies.
Project Management: Basic understanding of managing projects and tasks.
Learning Path
Start with Core Java: Master the basics before moving to advanced concepts.
Learn Front-End Basics: HTML, CSS, JavaScript.
Move to Frameworks: Choose one front-end framework (React/Angular/Vue.js).
Back-End Development: Dive into Spring and Hibernate.
Database Knowledge: Learn both SQL and NoSQL databases.
Version Control: Get comfortable with Git.
Testing and DevOps: Understand the basics of testing and deployment.
Resources
Books:
Effective Java by Joshua Bloch.
Java: The Complete Reference by Herbert Schildt.
Head First Java by Kathy Sierra & Bert Bates.
Online Courses:
Coursera, Udemy, Pluralsight (Java, Spring, React/Angular/Vue.js).
FreeCodeCamp, Codecademy (HTML, CSS, JavaScript).
Documentation:
Official documentation for Java, Spring, React, Angular, and Vue.js.
Community and Practice
GitHub: Explore open-source projects.
Stack Overflow: Participate in discussions and problem-solving.
Coding Challenges: LeetCode, HackerRank, CodeWars for practice.
By mastering these areas, you'll be well-equipped to handle the diverse responsibilities of a Java Full Stack Developer.
visit https://www.izeoninnovative.com/izeon/
2 notes
·
View notes
Text
Soft Crayons tech solutions provide the Angular Java script course at offline institute. Enhance your skill set with the advance technological course like Agular js course. Soft crayons provide one to one training at the center and also in online class where you can connect to us regardless of your region and country. Learning Angular js can offer numerous benefits like marketability which make it a valuable skill in the job market and MVC- Model View Controller which is fundamental in modern web development. Join the Angular js course at Soft crayons now and boost up your career and performance.
2 notes
·
View notes
Text
The Laravel framework is widely utilized by top Laravel development companies. It stands out among other web application development frameworks due to its advanced features and development tools that expedite web development. Therefore, this article aims to provide a list of the top 10 Laravel Development Companies in 2024, assisting you in selecting a suitable Laravel development company in the USA for your project.
#Laravel Development Companies#top 10 Laravel Development Companies#top 10 Laravel Development Companies in USA#Laravel Web Development Companies#Laravel Web Development Services
3 notes
·
View notes