V2ex

v2ex

It all started with my trusty laptop, my faithful companion through thick and thin. But one day, it decided to play a little game with me. It refused to charge! Can you believe it? I had to twist and turn the charger, like a Rubik's cube, just to get it to work. I thought I had won, but oh no, this was just the beginning. The next day, I strutted into the office, ready to conquer the world. But lo and behold, my laptop had a surprise waiting for me. It was charging just fine, with no complaints whatsoever! I shrugged it off, thinking maybe my laptop was just having a bad day yesterday. But oh no, my friends, this was just the beginning of the chaos. I worked from home the next day, and guess what? The same problem popped up again. I played the charger-twisting game once more, and voila, it worked like a charm. But the real kicker was yet to come. I was all set to go on a well-deserved vacation, but my laptop was not on board with the plan. It decided to be extra finicky, sometimes charging just fine, but other times making me fidget and fiddle with the charger like a magician with a deck of cards. I even blew air into the USB-C port, like some sort of laptop exorcism, but to no avail. Desperate for a solution, I turned to a colleague for help. He kindly lent me a new charger, and I thought I had struck gold! The new charger worked like a charm throughout my entire vacation. But as soon as I came back, the laptop decided to be a total diva. The borrowed charger refused to charge my laptop at all, while the old charger worked only after some coaxing and pleading. At this point, I was ready to throw in the towel and send my laptop back to the manufacturer. But then I had a stroke of genius, or at least I thought so. I marched into the laptop store and begged them to measure my devices, like some sort of laptop doctor. Maybe they could figure out which one had the problem, I thought. You know that pesky, intermittent problem that only happens sometimes, like a mischievous fairy playing games. It comes when you're alone at home, but decides to work fine and dandy when the repairman looks at it. As the woman in the laptop store took my laptop and charger, I felt a glimmer of hope. Maybe, just maybe, this frustrating saga would finally come to an end. With a patient smile, the woman listened to my tale of woe and took a closer look at my laptop and charger. She plugged in my charger to my laptop, and...nothing. The darn thing still wouldn't charge! At least the problem was consistent, I thought to myself. But instead of playing the same old game with the charger, the woman had a different approach. She took the charger apart into two parts, the charger itself and the cable. From a shelf behind her, she produced a different cable and plugged it into my charger. No luck. Then, she tried her own charger with my cable, and it worked like a charm. She looked up at me with a knowing smile. "Your charger is the culprit," she said. "The cable is fine, but the charger part is faulty." I was equal parts relieved and annoyed. Relieved because there was finally an answer to my problem, but annoyed because it had taken so long to figure out. I couldn't help but wonder why my laptop had been so finicky with the charger all this time. Had it been trying to tell me something? But at least now I knew what to do. I thanked the woman profusely and bought a new charger right then and there. On the way back to the office, I summarized the lessons I had just learned: Don't ignore the warning signs: When your device starts acting up, take notice and investigate the problem before it gets worse. Break it down: When faced with a complex issue, break it down into smaller, more manageable parts to find the root cause. Distrust the unpredictable: When a component of your device behaves unpredictably, it's best to assume it's faulty. Test separately: To identify the source of a problem, test each component separately to isolate the issue and find a solution. As a note to myself, I can learn a valuable lesson from even the most annoying incidents, whether they happen in my personal life or in my work as a software developer. I will keep these lessons in mind the next time I encounter a bug in my code that needs to be debugged.

Charging Up Your Debugging Skills

LONDON, United Kingdom, November 9th, 2023/Chainwire/--Design chosen by VEXT community to appear at Extreme E season finale in Chile. Veloce Racing will be fighting for the Extreme E Season 3 championship title in style with a special one-off chrome livery. VEXT As part of the recently launched VEXT, token holders were given a choice to cast their vote between three unique designs which will feature as the team’s livery at the Antofagasta Minerals Copper X Prix in December (2-3). The winning chrome design will be applied to Veloce Racing's ODYSSEY 21, and accompanied by a VEXT-inspired purple team kit. VEXT enables and encourages its growing community to vote on decisions that impact both real-world and virtual assets within the , allowing fans to be increasingly integrated and engaged within the Veloce eco-system. Veloce Media Group With tangible influence on the direction of assets, token holders are also able to transact across games and interactive sports features, with rewards such as tokens, early access to merchandise, and experience of real-world events. The were invited to have their say on Veloce’s Extreme E team as it continues to progress in the motorsport world, in this instance by voting for the British squad's livery for the final X Prix of the 2023 campaign. VEXT community This activation around Veloce Racing’s Extreme E livery is one of several community voting proposals already introduced via VEXT, and marks an innovative example of Web3 and real-world racing coming together. It marks another stage in Veloce taking steps towards achieving its ambitious vision of becoming a community-owned global sporting, entertainment and , where fans are invited to become a part of the Veloce journey and have influence on the direction of the groups future and its vast range of real-world sporting assets. media group https://www.youtube.com/embed/f89kZB5qIBw?si=O13hXYs2qIQtNyJN The reflective chrome livery will be on display in Chile for the final Extreme E double-header of the season, where Veloce Racing’s bid for the title reaches an exciting conclusion. The team currently sits third in the Extreme E championship standings, with drivers Kevin Hansen and Molly Taylor just 21 points off the top of the standings with plenty of points up for grabs in Rounds 9 and 10. Rupert Svendsen-Cook, Co-Founder and Chief Executive Officer at Veloce, said: "It has been amazing to see the progress of VEXT so far, and the engagement we had with this governance vote is testament to the work we’re doing to evolve Veloce through Web3." “Integrating our community with proposals like this one marks another step towards our ultimate ambition, which is to become a fully decentralised global sporting group." “VEXT token holders have chosen a unique chrome livery for our Extreme E team in Chile. We can’t wait to see the virtual come to life in a real-world racing team, during a milestone weekend for Veloce and our fans as we also fight for the championship title.” The Veloce Groups network attracts over 35 million subscribers and nearly one billion monthly views across multiple digital platforms. With a focus on gaming and purpose-driven motorsport, the group is perfectly positioned to drive Web3 adoption. To start having a meaningful impact on the Veloce ecosystem, community members need to hold at least 1 VEXT. Find out more about VEXT and how to get involved here. About Veloce Media Group Founded in 2018, Veloce is a multi-pillared gaming and sports media group operating across some of the most innovative, fast-growing, and future-focused sectors in the UK. Headquartered in London, the Veloce brand comprises the industry-leading gaming and racing platform, Veloce Esports, and race-winning outfit, Veloce Racing, currently competing in the renowned Extreme E championship. As the world’s largest digital racing media network, Veloce has so far attracted over 35 million subscribers and nearly one billion monthly views with a focus on esports, gaming, purpose-driven motorsport, and Web3. Veloce is partnered with a number of high-profile teams from across the globe, running multiple gaming and esports team operations, including Mercedes AMG, Ferrari, and Yas Heat. Well established JV sub-brands, including Lando Norris’ gaming and lifestyle brand Quadrant, make up another key aspect of Veloce’s vast global network. For more information: | | | | | | | | | | | | | | Website Telegram Group Telegram Channel Twitter Discord Instagram YouTube CoinMarketCap CoinGecko ByBit MEXC Toobit Poloniex DigiFinex WhiteBIT Contact Head Of Digital Marketing Louis Broomfield hi@velocemediagroup.com This story was distributed as a release by Chainwire under HackerNoon’s Business Blogging Program. Learn more about the program . here

Veloce Racing's Unique Chrome Livery Chosen By VEXT Community For Extreme E Finale in Chile

ভেলোস রেসিংয়ের অনন্য ক্রোম লিভারি চিলিতে এক্সট্রিম ই ফাইনালের জন্য VEXT সম্প্রদায় দ্বারা বেছে নেওয়া হয়েছে

Die einzigartige Chromlackierung von Veloce Racing wurde von der VEXT-Community für das Extreme-E-Finale in Chile ausgewählt

La exclusiva decoración cromada de Veloce Racing elegida por la comunidad VEXT para la final de Extreme E en Chile

La livrée chromée unique de Veloce Racing choisie par la communauté VEXT pour la finale Extreme E au Chili

चिली में एक्सट्रीम ई फिनाले के लिए VEXT समुदाय द्वारा वेलोस रेसिंग की अनूठी क्रोम लाइवरी को चुना गया

Veloce Racing のユニークなクローム カラーリングがチリのエクストリーム E フィナーレで VEXT コミュニティによって選ばれました

VEXT 커뮤니티가 칠레 익스트림 E 피날레를 위해 선택한 Veloce Racing의 독특한 크롬 상징

Pintura cromada exclusiva da Veloce Racing escolhida pela comunidade VEXT para Extreme E Finale no Chile

Уникальная хромированная окраска Veloce Racing выбрана сообществом VEXT для финала Extreme E в Чили

Veloce Racing'in Benzersiz Krom Görünümü VEXT Topluluğu Tarafından Şili'deki Extreme E Finali İçin Seçildi

Màu sơn Chrome độc đáo của Veloce Racing được cộng đồng VEXT lựa chọn cho vòng chung kết Extreme E ở Chile

VEXT 社区为智利 Extreme E 决赛选择了 Veloce Racing 独特的 Chrome 涂装

LONDON, United Kingdom, September 8th, 2023/Chainwire/ VEXT is now available (10 a.m. UTC) on , a highly established global centralized exchange. listing on the MEXC exchange represents a significant milestone for VEXT's journey. MEXC VEXT's Users are invited to visit via to access exclusive rewards and bonuses currently on offer. MEXC this link This pivotal moment offers users the chance to play an integral role in shaping the future of VEXT. https://www.youtube.com/embed/f89kZB5qIBw?showinfo=0 About Veloce Media Group Founded in 2018, Veloce is a multi-pillared gaming and sports media group operating across some of the most innovative, fast-growing, and future-focused sectors in the UK. Headquartered in London, the Veloce brand comprises an industry-leading gaming and racing platform, Veloce Esports, and a race-winning outfit, Veloce Racing, currently competing in the renowned Extreme E championship. As the world’s largest digital racing media network, Veloce has so far attracted over 35 million subscribers and nearly one billion monthly views with a focus on esports, gaming, purpose-driven motorsport, and Web3. Veloce is partnered with a number of high-profile teams from across the globe, running multiple gaming and esports team operations, including Mercedes AMG, Ferrari, McLaren, and Yas Heat. Well-established JV sub-brands, including Lando Norris’ gaming and lifestyle brand Quadrant, make up another key aspect of Veloce’s vast global network. Users should stay tuned for some exciting updates in the near future! To lean more visit Veloce's: | | | | | | | | | | Website Telegram Group Telegram Channel Twitter Discord Instagram YouTube CoinMarketCap CoinGecko ByBit MEXC Contact Head Of Digital Marketing Louis Broomfield Veloce Media Group hi@velocemediagroup.com This story was distributed as a release by Chainwire under HackerNoon’s Business Blogging Program: https://business.hackernoon.com/business-blogging?ref=hackernoon.com

VEXT Is Now Available On MEXC

LONDON, United Kingdom, September 4th, 2023/Chainwire/--Veloce, the world’s largest digital racing media network, has just launched (10 am UTC) its governance and utility token, VEXT, exclusively on ByBit, one of the global top leading centralized exchanges. Users can head over to ByBit now by CLICKING HERE so they don’t miss out on the exclusive rewards and bonuses up for grabs! Users who don't have a ByBit account can sign up here now! This is a defining moment where users have the opportunity to be part of shaping the VEXT future. Veloce appreciates the support of all its users; more exciting news is coming soon! About Veloce Media Group Founded in 2018, Veloce is a multi-pillared gaming and sports media group operating across some of the most innovative, fast-growing, and future-focused sectors in the UK. Headquartered in London, the Veloce brand comprises the industry-leading gaming and racing platform Veloce Esports and race-winning outfit Veloce Racing, currently competing in the renowned Extreme E championship. As the world’s largest digital racing media network, Veloce has so far attracted over 35 million subscribers and nearly one billion monthly views with a focus on esports, gaming, purpose-driven motorsport, and Web3. Veloce is partnered with a number of high-profile teams from across the globe, running multiple gaming and esports team operations, including Mercedes AMG, Ferrari, McLaren, and Yas Heat. Well-established JV sub-brands, including Lando Norris’ gaming and lifestyle brand Quadrant, make up another key aspect of Veloce’s vast global network. To learn more, please visit: https://www.velocemediagroup.com/ Contact Chief Executive Officer Rupert Svendsen-Cook Veloce Media Group hi@velocemediagroup.com This story was distributed as a release by Chainwire under HackerNoon’s Brand As An Author Program. Learn more about the program . here

VEXT Is Live On ByBit Now

LONDON, United Kingdom, September 1st, 2023/Chainwire/--Veloce, the world’s leading digital racing media network, will be launching its Utility and Governance token, VEXT, on September 4th, 2023. VEXT will be launching exclusively on ByBit, a top three global crypto exchange. Veloce has collaborated with Polygon Labs, an international software development company building Ethereum scaling architecture, which facilitates swift, cost-effective, and secure transactions across the Polygon protocols. Veloce Media Group CEO, Rupert Svendsen-Cook, will be on stage at Korea Blockchain Week alongside Mike Blank, COO at Polygon Labs, to talk about the VEXT integration with Polygon (September 4th). Veloce’s token, VEXT, empowers holders to become part of the Veloce ecosystem, which will have substantial influence over decentralized assets within the Veloce Media Group, encompassing its multiple gaming and real-world teams, creators, leagues, and content. https://youtu.be/f89kZB5qIBw?si=SlrnD5q4c7a6yvOT With the launch phase already offering multiple features and a roadmap introducing game-changing utility, Veloce will harness all of its resources to build a truly future-facing sports and media group on the Blockchain. VEXT's launch brings an evolving user experience with voting and proposal features, six gamified staking pools, and integrated games and will evolve the platform to offer product and merchandise privileges and token holder event access, with interoperability across all features. Rupert Svendsen-Cook, Chief Executive Officer at Veloce Media Group, said: “ ” To build the first decentralized global sporting group and ultimately evolve our entire ecosystem into Web3, we needed the ultimate blockchain architecture - the Polygon blockchain is exactly that. Leveraging the Polygon protocols combined with our incredibly engaged community and utility will be a formidable combination for the industry. Aishwary Gupta, Head of Payments & Fintech at Polygon Labs, said: " We are thrilled by Veloce's decision to harness the power of the Polygon blockchain for their visionary Web3 project. Their ambition for the future of sports and gaming is truly inspiring.” As Veloce continues to be a pioneer, we eagerly anticipate the seamless integration of their well-established Web2 community into the thriving Polygon ecosystem”. About Veloce Media Group Founded in 2018, Veloce is a multi-pillared gaming and sports media group operating across some of the most innovative, fast-growing, and future-focused sectors in the UK. Headquartered in London, the Veloce brand comprises the industry-leading gaming and racing platform Veloce Esports and the race-winning outfit Veloce Racing, currently competing in the renowned Extreme E championship. As the world’s largest digital racing media network, Veloce has so far attracted over 35 million subscribers and nearly one billion monthly views with a focus on esports, gaming, purpose-driven motorsport, and Web3. Veloce is partnered with a number of high-profile teams from across the globe, running multiple gaming and esports team operations, including Mercedes AMG, Ferrari, McLaren, and Yas Heat. Well-established JV sub-brands, including Lando Norris’ gaming and lifestyle brand Quadrant, make up another key aspect of Veloce’s vast global network. To learn more, please visit: https://www.velocemediagroup.com/ Contact Chief Executive Officer Rupert Svendsen-Cook Veloce Media Group hi@velocemediagroup.com This story was distributed as a release by Chainwire under HackerNoon’s Brand As An Author Program. Learn more about the program here. Also published . here

Veloce Launches Vext On Polygon, Becomes First Decentralized Global Sporting Group

Anne of Green Gables by L. M. Montgomery, is part of the HackerNoon Books Series. You can jump to any chapter in this book here . Vanity and Vexation of Spirit CHAPTER XXVII. Vanity and Vexation of Spirit MARILLA, walking home one late April evening from an Aid meeting, realized that the winter was over and gone with the thrill of delight that spring never fails to bring to the oldest and saddest as well as to the youngest and merriest. Marilla was not given to subjective analysis of her thoughts and feelings. She probably imagined that she was thinking about the Aids and their missionary box and the new carpet for the vestry room, but under these reflections was a harmonious consciousness of red fields smoking into pale-purply mists in the declining sun, of long, sharp-pointed fir shadows falling over the meadow beyond the brook, of still, crimson-budded maples around a mirrorlike wood pool, of a wakening in the world and a stir of hidden pulses under the gray sod. The spring was abroad in the land and Marilla’s sober, middle-aged step was lighter and swifter because of its deep, primal gladness. Her eyes dwelt affectionately on Green Gables, peering through its network of trees and reflecting the sunlight back from its windows in several little coruscations of glory. Marilla, as she picked her steps along the damp lane, thought that it was really a satisfaction to know that she was going home to a briskly snapping wood fire and a table nicely spread for tea, instead of to the cold comfort of old Aid meeting evenings before Anne had come to Green Gables. Consequently, when Marilla entered her kitchen and found the fire black out, with no sign of Anne anywhere, she felt justly disappointed and irritated. She had told Anne to be sure and have tea ready at five o’clock, but now she must hurry to take off her second-best dress and prepare the meal herself against Matthew’s return from plowing. “I’ll settle Miss Anne when she comes home,” said Marilla grimly, as she shaved up kindlings with a carving knife and with more vim than was strictly necessary. Matthew had come in and was waiting patiently for his tea in his corner. “She’s gadding off somewhere with Diana, writing stories or practicing dialogues or some such tomfoolery, and never thinking once about the time or her duties. She’s just got to be pulled up short and sudden on this sort of thing. I don’t care if Mrs. Allan does say she’s the brightest and sweetest child she ever knew. She may be bright and sweet enough, but her head is full of nonsense and there’s never any knowing what shape it’ll break out in next. Just as soon as she grows out of one freak she takes up with another. But there! Here I am saying the very thing I was so riled with Rachel Lynde for saying at the Aid today. I was real glad when Mrs. Allan spoke up for Anne, for if she hadn’t I know I’d have said something too sharp to Rachel before everybody. Anne’s got plenty of faults, goodness knows, and far be it from me to deny it. But I’m bringing her up and not Rachel Lynde, who’d pick faults in the Angel Gabriel himself if he lived in Avonlea. Just the same, Anne has no business to leave the house like this when I told her she was to stay home this afternoon and look after things. I must say, with all her faults, I never found her disobedient or untrustworthy before and I’m real sorry to find her so now.” “Well now, I dunno,” said Matthew, who, being patient and wise and, above all, hungry, had deemed it best to let Marilla talk her wrath out unhindered, having learned by experience that she got through with whatever work was on hand much quicker if not delayed by untimely argument. “Perhaps you’re judging her too hasty, Marilla. Don’t call her untrustworthy until you’re sure she has disobeyed you. Mebbe it can all be explained—Anne’s a great hand at explaining.” “She’s not here when I told her to stay,” retorted Marilla. “I reckon she’ll find it hard to explain that to my satisfaction. Of course I knew you’d take her part, Matthew. But I’m bringing her up, not you.” It was dark when supper was ready, and still no sign of Anne, coming hurriedly over the log bridge or up Lover’s Lane, breathless and repentant with a sense of neglected duties. Marilla washed and put away the dishes grimly. Then, wanting a candle to light her way down the cellar, she went up to the east gable for the one that generally stood on Anne’s table. Lighting it, she turned around to see Anne herself lying on the bed, face downward among the pillows. “Mercy on us,” said astonished Marilla, “have you been asleep, Anne?” “No,” was the muffled reply. “Are you sick then?” demanded Marilla anxiously, going over to the bed. Anne cowered deeper into her pillows as if desirous of hiding herself forever from mortal eyes. “No. But please, Marilla, go away and don’t look at me. I’m in the depths of despair and I don’t care who gets head in class or writes the best composition or sings in the Sunday-school choir any more. Little things like that are of no importance now because I don’t suppose I’ll ever be able to go anywhere again. My career is closed. Please, Marilla, go away and don’t look at me.” “Did anyone ever hear the like?” the mystified Marilla wanted to know. “Anne Shirley, whatever is the matter with you? What have you done? Get right up this minute and tell me. This minute, I say. There now, what is it?” Anne had slid to the floor in despairing obedience. “Look at my hair, Marilla,” she whispered. Accordingly, Marilla lifted her candle and looked scrutinizingly at Anne’s hair, flowing in heavy masses down her back. It certainly had a very strange appearance. “Anne Shirley, what have you done to your hair? Why, it’s green!” Green it might be called, if it were any earthly color—a queer, dull, bronzy green, with streaks here and there of the original red to heighten the ghastly effect. Never in all her life had Marilla seen anything so grotesque as Anne’s hair at that moment. “Yes, it’s green,” moaned Anne. “I thought nothing could be as bad as red hair. But now I know it’s ten times worse to have green hair. Oh, Marilla, you little know how utterly wretched I am.” “I little know how you got into this fix, but I mean to find out,” said Marilla. “Come right down to the kitchen—it’s too cold up here—and tell me just what you’ve done. I’ve been expecting something queer for some time. You haven’t got into any scrape for over two months, and I was sure another one was due. Now, then, what did you do to your hair?” “I dyed it.” “Dyed it! Dyed your hair! Anne Shirley, didn’t you know it was a wicked thing to do?” “Yes, I knew it was a little wicked,” admitted Anne. “But I thought it was worth while to be a little wicked to get rid of red hair. I counted the cost, Marilla. Besides, I meant to be extra good in other ways to make up for it.” “Well,” said Marilla sarcastically, “if I’d decided it was worth while to dye my hair I’d have dyed it a decent color at least. I wouldn’t have dyed it green.” “But I didn’t mean to dye it green, Marilla,” protested Anne dejectedly. “If I was wicked I meant to be wicked to some purpose. He said it would turn my hair a beautiful raven black—he positively assured me that it would. How could I doubt his word, Marilla? I know what it feels like to have your word doubted. And Mrs. Allan says we should never suspect anyone of not telling us the truth unless we have proof that they’re not. I have proof now—green hair is proof enough for anybody. But I hadn’t then and I believed every word he said implicitly.” “Who said? Who are you talking about?” “The peddler that was here this afternoon. I bought the dye from him.” “Anne Shirley, how often have I told you never to let one of those Italians in the house! I don’t believe in encouraging them to come around at all.” “Oh, I didn’t let him in the house. I remembered what you told me, and I went out, carefully shut the door, and looked at his things on the step. Besides, he wasn’t an Italian—he was a German Jew. He had a big box full of very interesting things and he told me he was working hard to make enough money to bring his wife and children out from Germany. He spoke so feelingly about them that it touched my heart. I wanted to buy something from him to help him in such a worthy object. Then all at once I saw the bottle of hair dye. The peddler said it was warranted to dye any hair a beautiful raven black and wouldn’t wash off. In a trice I saw myself with beautiful raven-black hair and the temptation was irresistible. But the price of the bottle was seventy-five cents and I had only fifty cents left out of my chicken money. I think the peddler had a very kind heart, for he said that, seeing it was me, he’d sell it for fifty cents and that was just giving it away. So I bought it, and as soon as he had gone I came up here and applied it with an old hairbrush as the directions said. I used up the whole bottle, and oh, Marilla, when I saw the dreadful color it turned my hair I repented of being wicked, I can tell you. And I’ve been repenting ever since.” “Well, I hope you’ll repent to good purpose,” said Marilla severely, “and that you’ve got your eyes opened to where your vanity has led you, Anne. Goodness knows what’s to be done. I suppose the first thing is to give your hair a good washing and see if that will do any good.” Accordingly, Anne washed her hair, scrubbing it vigorously with soap and water, but for all the difference it made she might as well have been scouring its original red. The peddler had certainly spoken the truth when he declared that the dye wouldn’t wash off, however his veracity might be impeached in other respects. “Oh, Marilla, what shall I do?” questioned Anne in tears. “I can never live this down. People have pretty well forgotten my other mistakes—the liniment cake and setting Diana drunk and flying into a temper with Mrs. Lynde. But they’ll never forget this. They will think I am not respectable. Oh, Marilla, ‘what a tangled web we weave when first we practice to deceive.’ That is poetry, but it is true. And oh, how Josie Pye will laugh! Marilla, I cannot face Josie Pye. I am the unhappiest girl in Prince Edward Island.” Anne’s unhappiness continued for a week. During that time she went nowhere and shampooed her hair every day. Diana alone of outsiders knew the fatal secret, but she promised solemnly never to tell, and it may be stated here and now that she kept her word. At the end of the week Marilla said decidedly: “It’s no use, Anne. That is fast dye if ever there was any. Your hair must be cut off; there is no other way. You can’t go out with it looking like that.” Anne’s lips quivered, but she realized the bitter truth of Marilla’s remarks. With a dismal sigh she went for the scissors. “Please cut it off at once, Marilla, and have it over. Oh, I feel that my heart is broken. This is such an unromantic affliction. The girls in books lose their hair in fevers or sell it to get money for some good deed, and I’m sure I wouldn’t mind losing my hair in some such fashion half so much. But there is nothing comforting in having your hair cut off because you’ve dyed it a dreadful color, is there? I’m going to weep all the time you’re cutting it off, if it won’t interfere. It seems such a tragic thing.” Anne wept then, but later on, when she went upstairs and looked in the glass, she was calm with despair. Marilla had done her work thoroughly and it had been necessary to shingle the hair as closely as possible. The result was not becoming, to state the case as mildly as may be. Anne promptly turned her glass to the wall. “I’ll never, never look at myself again until my hair grows,” she exclaimed passionately. Then she suddenly righted the glass. “Yes, I will, too. I’d do penance for being wicked that way. I’ll look at myself every time I come to my room and see how ugly I am. And I won’t try to imagine it away, either. I never thought I was vain about my hair, of all things, but now I know I was, in spite of its being red, because it was so long and thick and curly. I expect something will happen to my nose next.” Anne’s clipped head made a sensation in school on the following Monday, but to her relief nobody guessed the real reason for it, not even Josie Pye, who, however, did not fail to inform Anne that she looked like a perfect scarecrow. “I didn’t say anything when Josie said that to me,” Anne confided that evening to Marilla, who was lying on the sofa after one of her headaches, “because I thought it was part of my punishment and I ought to bear it patiently. It’s hard to be told you look like a scarecrow and I wanted to say something back. But I didn’t. I just swept her one scornful look and then I forgave her. It makes you feel very virtuous when you forgive people, doesn’t it? I mean to devote all my energies to being good after this and I shall never try to be beautiful again. Of course it’s better to be good. I know it is, but it’s sometimes so hard to believe a thing even when you know it. I do really want to be good, Marilla, like you and Mrs. Allan and Miss Stacy, and grow up to be a credit to you. Diana says when my hair begins to grow to tie a black velvet ribbon around my head with a bow at one side. She says she thinks it will be very becoming. I will call it a snood—that sounds so romantic. But am I talking too much, Marilla? Does it hurt your head?” “My head is better now. It was terrible bad this afternoon, though. These headaches of mine are getting worse and worse. I’ll have to see a doctor about them. As for your chatter, I don’t know that I mind it—I’ve got so used to it.” Which was Marilla’s way of saying that she liked to hear it. About HackerNoon Book Series: We bring you the most important technical, scientific, and insightful public domain books. This book is part of the public domain. L. M. Montgomery (2008). Anne of Green Gables. Urbana, Illinois: Project Gutenberg. Retrieved https://www.gutenberg.org/cache/epub/45/pg45-images.html This eBook is for the use of anyone anywhere at no cost and with almost no restrictions whatsoever. You may copy it, give it away or re-use it under the terms of the Project Gutenberg License included with this eBook or online at www.gutenberg.org , located at https://www.gutenberg.org/policy/license.html . The lead image was generated using HackerNoon's Stable Disffusion Al Image Generator feature, via the prompt "Anne of Green Fables".

Vanity and Vexation of Spirit

With this article, we begin a series of publications about Vue.js technology and try to make out the application development and all its components from different practical sides. In this part, we will tell you what the Vuex library is and analyze in detail such components as a store, state, getters, mutations, and actions. Also, in the second part, we will consider modules, application structure, plugins, strict mode, work with forms, testing and strengths/benefits of Vuex Storage. WHAT IS VUEX, AND WHERE IT USED? VueX is a state management library inspired by Flux, Redux, and Elm architecture, but specially designed and tuned to integrate well with Vue.js and take advantage of Vue’s Reactivity. What is a state management pattern? Let's start with a simple Vue application that implements a counter. This stand-alone application consists of the following parts: State that controls the application; The view is a state display specified declaratively; Actions are possible ways to change the state of the app in response to users interaction with the view. Sometimes several components may appear that are based on the same state: multiple views may depend on the same part of the application state; actions from different views can affect the equal parts of the application state. Solving the first problem, you will have to transfer the same data with input parameters to deeply embedded components. This is often complicated and tedious, but for neighboring elements this will not work at all. Solving the second problem, you can come to such solutions as referring to parent/child instances or try changing and synchronizing multiple state copies through actions. Both approaches are fragile and quickly lead to the emergence of code that cannot be supported. So why not take out the overall general state of the application from the components and manage it in a global singleton? At the same time, our component tree becomes one big "view" and any component can access the application state or trigger actions to change the state, regardless of where they are in the tree! By clearly defining and separating the concepts that arise in state management, and by requiring certain rules that maintain independence between views and states, we better structure the code and make it easier to maintain. This is the core idea of ​​Vuex, inspired by Flux, Redux, and Elm Architecture. Unlike other patterns, Vuex is implemented as a library designed explicitly for Vue.js to use its reactivity system for efficient updates. THE MAIN COMPONENTS AND CAPABILITIES OF VUEX STORE At the center of any Vuex application is a store. The store is a container that stores the state of your application. Two points distinguish Vuex store from a simple global object: The Vuex store is reactive. When Vue components rely on their state, they will be reactively and efficiently updated if the state of the store changes.You cannot directly change the state of the store. The only way to make changes is to cause a mutation explicitly. This ensures that any change in the state leaves a mark and allows the use of tools to better understand the progress of the application. After installing Vuex, a repository is created. It's quite simple, and you need to specify the initial state object and some actions and mutations. store = Vuex.Store({ : { : }, : {
    increment({ commit, dispatch, getters }) {
       commit( )
    },
    decrement({ commit, dispatch, getters }) {
       commit( )
    }
  }, : {
    INCREMENT(state) {
      state.counter++
    },
    DECREMENT(state) {
      state.counter--
    }
  }, : {
    counter(state) { state.counter
    }
  }
}) const new state counter 0 // initial store state actions 'INCREMENT' 'DECREMENT' mutations getters return The reason we are committing a mutation instead of changing directly, is because we want to explicitly track it. This simple convention makes your intention more explicit, so that you can reason about state changes in your app better when reading the code. In addition, this gives us the opportunity to implement tools that can log every mutation, take state snapshots, or even perform time travel debugging. store.state.count STATE. SINGLE STATE TREE Vuex uses a single state tree when one object contains the entire global state of the application and serves as the only one source. It also means that the app will have only one such storage. A single state tree makes it easy to find the part you need or take snapshots of the current state of the application for debugging purposes. The data you store in Vuex follows the same rules as the in a Vue instance, ie the state object must be plain. So how do we display state inside the store in our Vue components? Since Vuex stores are reactive, the simplest way to "retrieve" state from it is simply returning some store state from within a computed property. data Whenever changes, it will cause the computed property to re-evaluate, and trigger associated DOM updates. store.state.count This pattern causes the component to rely on the global store singleton. When using a module system, it requires importing the store in every component that uses store state, and also requires mocking when testing the component. Vuex provides a mechanism to "inject" the store into all child components from the root component with the option (enabled by ) $store Vue.use(Vuex) { : {
    incrementCounter() { .$store.dispatch( )
    }
  }
} export default methods this 'increment' When a component needs to make use of multiple store state properties or getters, declaring all these computed properties can get repetitive and verbose. To deal with this we can make use of the helper which generates computed getter functions for us, saving us some keystrokes: mapState { mapState } ; { : {
    ...mapState({ : state.counter
    }),

    counterSquared() { .pow( .counter, )
    }
  }
} import from 'vuex' export default computed counter => state return Math this 2 We can also pass a string array to when the name of a mapped computed property is the same as a state sub tree name. mapState Note that returns an object. How do we use it in combination with other local computed properties? Normally, we'd have to use a utility to merge multiple objects into one so that we can pass the final object to . However with the object spread operator (which is a stage-4 ECMAScript proposal), we can greatly simplify the syntax as shown above. mapState computed Using Vuex doesn't mean you should put all the state in Vuex. Although putting more state into Vuex makes your state mutations more explicit and debuggable, sometimes it could also make the code more verbose and indirect. If a piece of state strictly belongs to a single component, it could be just fine leaving it as local state. You should weigh the trade-offs and make decisions that fit the development needs of your app. GETTERS Sometimes we may need to compute derived state based on store state, for example filtering through a list of items and counting them. If more than one component needs to make use of this, we have to either duplicate the function, or extract it into a shared helper and import it in multiple places - both are less than ideal. Vuex allows us to define "getters" in the store. You can think of them as computed properties for stores. Like computed properties, a getter's result is cached based on its dependencies, and will only re-evaluate when some of its dependencies have changed. getters: {
  counter(state) { state.counter
  },
  counterSquared(state) { .pow(state.counter, )
  }
} { mapGetters } ; { : {
    ...mapgetters([ , ])
  }
} // In store return return Math 2 // In component import from 'vuex' export default computed 'counter' 'counterSquared' You can also pass arguments to getters by returning a function. This is particularly useful when you want to query an array in the store. Note that getters accessed via methods will run each time you call them, and the result is not cached. The helper simply maps store getters to local computed properties. mapGetters MUTATIONS The only way to actually change state in a Vuex store is by committing a mutation. Vuex mutations are very similar to events: each mutation has a string type and a handler. The handler function is where we perform actual state modifications, and it will receive the state as the first argument. You cannot directly call a mutation handler. Think of it more like event registration: "When a mutation with type "increment" is triggered, call this handler." To invoke a mutation handler, you need to call with its type. store.commit { : {
    incrementCounter() { .$store.commit( )
    }
  }
} export default methods this 'INCREMENT' You can pass an additional argument to , which is called the payload for the mutation. In most cases, the payload should be an object so that it can contain multiple fields, and the recorded mutation will also be more descriptive. An alternative way to commit a mutation is by directly using an object that has a property. When using object-style commit, the entire object will be passed as the payload to mutation handlers, so the handler remains the same. store.commit type Since a Vuex store's state is made reactive by Vue, when we mutate the state, Vue components observing the state will update automatically. This also means Vuex mutations are subject to the same reactivity caveats when working with plain Vue: Prefer initializing your store's initial state with all desired fields upfront. When adding new properties to an Object, you should either - use , or replace that Object with a fresh one. For example, using the object spread syntax. Vue.set(obj, 'newProp', 123) However, using constants to indicate the types of mutations is completely optional, although this may be useful in large projects. One important rule to remember is that mutation handler functions must be synchronous. Imagine we are debugging the app and looking at the devtool's mutation logs. For every mutation logged, the devtool will need to capture a "before" and "after" snapshots of the state. However, the asynchronous callback inside the example mutation above makes that impossible: the callback is not called yet when the mutation is committed, and there's no way for the devtool to know when the callback will actually be called - any state mutation performed in the callback is essentially untrackable! You can commit mutations in components with , or use the helper which maps component methods to store.commit calls (requires root injection) this.$store.commit('xxx') mapMutations $store Asynchronicity combined with state mutation can make your program very hard to reason about. For example, when you call two methods both with async callbacks that mutate the state, how do you know when they are called and which callback was called first? This is exactly why to separate the two concepts. In Vuex, mutations are synchronous transactions. To handle asynchronous operations, should descry Actions. ACTIONS Actions are similar to mutations with a few differences: Instead of mutating the state, actions commit mutations. Actions can contain arbitrary asynchronous operations. actions: {
  signIn({ commit }, payload) { commit( , ); axios
      .post( , { : payload.email
        password: payload.password
      })
      .then( { { user, token } = response.data;
         commit( , token);
         commit( , user);
         commit( , );
      })
      .catch( {
        commit( , error.response.data.reason);
        commit( , );
      })
  }
} // Show spinner when user submit form 'LOGIN_IN_PROGRESS' true // axios - Promise based HTTP client for browser and node.js '/api/v1/sign_in' email ( ) => response const 'SET_AUTH_TOKEN' 'SET_USER' 'LOGIN_IN_PROGRESS' false ( ) => error 'SET_SIGN_IN_ERROR' 'LOGIN_IN_PROGRESS' false Action handlers receive a context object which exposes the same set of methods/properties on the store instance, so you can call to commit a mutation, or access the state and getters via and . We can even call other actions with . We will see why this context object is not the store instance itself when we introduce Modules later. context.commit context.state context.getters context.dispatch In practice, we often use ES2015 argument destructuring to simplify the code a bit especially when we need to call multiple times. Actions are triggered with the method. This may look silly at first sight if we want to increment the count, why don't we just call directly? Remember that mutations have to be synchronous? Actions don't. We can perform asynchronous operations inside an action. Actions support the same payload format and object-style dispatch. commit store.dispatch store.commit('increment') A more practical example of real-world actions would be an action to checkout a shopping cart, which involves calling an async API and committing multiple mutations. Performing a flow of asynchronous operations, and recording the side effects (state mutations) of the action by committing them. You can dispatch actions in components with , or use the helper which maps component methods to calls (requires root injection). Actions are often asynchronous, so how do we know when an action is done? And more importantly, how can we compose multiple actions together to handle more complex async flows? this.$store.dispatch('xxx') mapActions store.dispatch $store The first thing to know is that can handle Promise returned by the triggered action handler and it also returns Promise. It's possible for a to trigger multiple action handlers in different modules. In such a case the returned value will be a Promise that resolves when all triggered handlers have been resolved. It is only a small part of what we are going to tell in our next articles about Vue.js and all of its additional tools and benefits. Next, we continue our review of the Vuex library and components. store.dispatch store.dispatch Also, in our blog, you can read more about Vue.js: https://amoniac.eu/blog/post/why-we-fell-in-love-with-vue-j Previously published at https://amoniac.eu/blog/post/correct-and-efficient-vuex-using-part-i

Correct and Efficient Way to Use Vuex: Part I

is public blockchain platform that mainly targeting Indonesia and South East Asia, different from Bitcoin which is mostly used as a store of value and reserve currency, Vexanium and other blockchain such as Ethereum are both blockchain and Dapp platform where developers can build a decentralized application on top of it, that means there are a lot of type of actions/transactions inside the Dapp. Vexanium What is Dapp or Decentralized Application? A decentralized application is an application that does not need a central authority that runs it. Example of Decentralized app is decentralized exchange, where the exchange does not handle the user funds, they don’t have a central server that controls your funds, but the user handles the funds and transactions. Decentralized application has a lot of potential to bring disruption to the industries (financial, social media, games, content, ecommerce etc) because it enables a new business model. As the biggest blockchain platform in Indonesia, what are the difference between Vexanium and Ethereum? Transaction Model In Ethereum, users have to pay a small amount of Ether every time they make a transaction in the network. Whenever users use the Dapp and want to talk to the smart contract, they have to pay. The burden is on the user. Vexanium uses stake based system to protect the system from spam, you must stake your Vex token to guarantee that your account gets network bandwidth proportional with numbers of Vex token that you stake. Doing staking means committing your resource to Vexanium network. When you stopped using the resource (network bandwidth) you will get your token back. The transaction costs are paid by the inflation cost and Vexanium is not charging per transaction. Consensus Mechanism Ethereum uses Proof of Work (PoW) consensus mechanism and is in the process to move into Proof of Stake (PoS) Mechanism. While Vexanium uses Delegated Proof of Stake (DPoS) consensus mechanism. Proof of Work Characteristics : In a proof-of-work system, a computer or computing power is required to solve a computational problem of a predetermined level of difficulty before it’s allowed to take some desired action (get rewards). Because PoW needs a lot of computing power, it is costly and not efficient. Proof of Stake Character : In Proof of Stake (PoS), you need to stake some amount of cryptocurrency to become block producers, PoS has a lower barrier to entry than PoW for block generation rewards because PoS avoids expensive computations. This makes it more environmentally friendly than PoW In PoW, an attacker would need to acquire 50%+ of the computational power in the network, but in PoS, an attacker would need to acquire 50%+ of the currency within that system. Proof-of-stake eliminates some of the major security issues associated with the Proof-of-work scheme. The most obvious of them is the 51% attack. Delegated Proof of Stake (DPoS) Characteristics : Proof of Stake (PoS) is “direct democratic” while DPOS is representative democratic. Stakeholders elect their delegates to generate and validate blocks. With significantly fewer nodes to validate the block, the block could be confirmed quickly, leading to the quick confirmation of transactions. DPoS consensus mechanism leverages the power of stakeholder approval voting, to resolve consensus issues in a manner which is democratic and fair. Delegated proof of stake uses real-time voting combined with a social system of reputation to achieve consensus. Because Vexanium use DPoS, it needs fewer nodes to validate the block, it has faster transaction per second (2000 tps) compared to Ethereum (20 tps) Why speed of the blockchain is crucial ? Bitcoin has 7 transaction per second. Ethereum has 20 Tps. Vexanium has 2000 Tps but can scale to 100,000 Tps - 1,000,000 Tps in the future. While Spotify now process 1 billion streams everyday. now process 1700 Tps (based on a calculation derived from the official claim of over 150 million transactions per day) . Visa How about IoT ?  Gartner predicted there will be 20 billion IoT devices by 2020, with average 1-5 event records/day, means 60 billion event records per day, it will need 694,000 TpS. For blockchain technology to achieve mass adoption it must have speed/transaction per second that meets the needs of the application such as financial apps, social media apps, music apps and right now it is achievable using Delegated Proof of Stake consensus mechanism. Account Naming Vexanium has a different account structure compared to other cryptocurrency addresses. Vexanium uses account names, a unique human readable name instead of long wallet addresses in Ethereum. Vexanium account names are exactly 12 characters long and may only include the characters 12345abcdefghijklmnopqrstuvwxyz. If an account name isn’t claimed by anyone else, a Vexanium user can create an account with that name. This 12 characters human-readable account system has some benefits. Example, if you misspell the account, your wallet will show an error that it is an invalid address. And checking a 12 character name is easier than 30 – 50 character addresses in other cryptos. The 12 character name is similar to how ethereum or bitcoin public keys work. People use them to transfer funds to other accounts. Vexanium still has random hashes in the form of public and private keys, but Vexanium has the concept of an account. Accounts can be controlled by the owners of a public key. Programming Language Vexanium uses a C++ programming language which is already familiar for a lot of programmers, it already being studied in many universities and has a lot of libraries available so programmers do not need to reinvent the wheel. While Ethereum uses Solidity, it means programmers need to learn new programming language and not many libraries available to reuse. Reinventing the wheel. Here is the comparison of Google worldwide search volume for C++ and Solidity. That is just some comparison of Vexanium blockchain to Ethereum blockchain. The market itself could bring big differences: Vexanium targeting Indonesia and then South East Asia, while Ethereum targeting the international market. It is interesting to see how things are going in the next 3-5 years. As developers or investors, knowing some of these facts will help you to make a favorable decision for you. Rhein - Vexanium team More about Dapps Development in Vexanium here : dev.vexanium.com Vexanium wallet : vexwallet.com

In Depth Comparison Between Vexanium Blockchain & Ethereum Blockchain

Or just a nice MobX tutorial Photo by on Karsten Würth (@inf1783) Unsplash Framework Wars …NOT 😜 I started my journey in the Frameworks fairyland with and series by Laracast. I had heard about React, but back then when I looked at JSX it seemed like an abomination to me! Mixing html tags with JS logic? Haven’t they heard about design patterns and separation of concerns? Why not just use JQuery to make some blinking text for goodness’ sake? Vue this amazing But then I learned JS, not _JQuery JS* (_making tricks with the DOM), but JS as a development language, an elegant expressive tool to manipulate data, a language with beautiful methods to work with Arrays, String, and Objects. And what you can’t do with vanilla JS very likely there’s a for that, or there’s an NPM package. ( Lol!) Lodash for sure npm install make-me-a-sandwich After all that I took another look at React and… I instantly fell in love! Where Vue is sort of like html with added functionality ( ) JSX is plain JS that happens to generate DOM. I’m not actually trying to start a frameworks war here. I currently have Vue and React apps on production and I have been able to find all the tools that I need on both frameworks to do my job. The choice really comes down to a personal preference or your company’s/team’s preference. v-if, v-for... But React… For a beginner in React it seemed like Redux is the default store as is Vuex for Vue thus I decided to learn Redux… and after watching the complete egghead series about 3 times and going over the documentation just as many times, I still felt like I had no clue what I was doing. Anything less than a trivial reducer was a headache to write. Normalized data, relational tables, immutability and DB technology, they all seemed like pre-requirements for Redux! I did learn a lot, but not enough to feel anywhere close to productive with it. Then there are wrappers for Redux and high order functions to generate other functions and reducer recipes… I felt like an intern again, not being able to finish my project because I didn’t know how to have a simple store and make my app to it! 😥 react I’m sure that there are a lot of developers out there smarter than I am that are very productive with with Redux. I look up to you, Sensei! I missed the days of Vuex in which everything just worked, mutable state was not a sin and no matter where I called a store action, the whole app was always in sync. But i liked React a lot too so I started to see if I could use Vuex on React, (apparently not) but in the search I came across . It sure had bold claims: MobX MobX makes state management simple again by addressing the root issue: it makes it impossible to produce an inconsistent state. * Again I headed to egghead to watch the video tutorials. They were nice but tough luck! does not support decorators and you don’t get a lot of examples of how to do things without them. Then there’s which claims to be opinionated (and that’s an understatement!) and then again, I had no clue how to do things or what was going on! The videos taught me how to make a pretty decent counter and felt like I was writing an enterprise banking application, but I couldn’t find a medium difficulty level. create-react-app mobx-state-tree mobx-state-tree I really liked React so I went back to Redux but couldn’t make it work so, again, I reluctantly gave MobX another try... “ And at last I see the light; And it’s like the fog has lifted” Shameless Disney plug! Want I want to do us show you that MobX is easier to use that what you might think. We are gonna use MobX to do more than just count up and down and is simpler than a implementation. mobx-state-tree The Store We are going to make a simple store, extracted from a project I’m currently . In it we are going to have a list of students and a list of courses, and we will be able to enroll and unenroll students from a course. working on The starting point is a clean app and here is : create-react-app store.js 🙄 Don’t let the length scare you, it’s actually pretty straight forward the students’ and courses’ methods are the same. In MobX terminology, there are , stuff that for changes, and , stuff for changes. From there the rest is magic pretty magical! observables is watched observers that watches First we simply declare as the first parameter of . * const store observable() This is how you declare an observable without using the decorator syntax ( _@observable_ ). Inside the object passed to there are three places to put data in: , and and those are defined as . If it’s the first time you have come across a , don’t worry, it’s just a fancy object with a nice way to access the contents in it (setters and getters). In a plain JS object data is accessed like this: or , On a map you’d access it like this: . There are a couple of advantages to this, and in this particular project it saved me from using a lot of and (from Lodash). observable() students courses, enrollment, observable.map() Map object.key1.key2 object['key1']['key2'] object.get('key1').get('key2') _.set() _.assign() Then come the store methods to add, update, and remove students and courses from the store. They are just plain with a some error handling. .set() The next interesting bit comes in the enrollment handling. This idea definitively has a Redux flavor to it ( ) and it’s useful in this case. I’m making a object with the key being equal to the course’s ID and the value being an array of the enrolled students’ IDs. It looks like this: Relationships and Tables {course1: ['student1', 'student2', 'student3'],course2: ['student4', 'student5', 'student6'],} Where the action happens is in the method. Let’s break it down: it returns a function, which is the MobX expression to watch for changes in the elements inside it and to automatically update its value. Nothing fancy there. Next, it gets the element in the enrollment map that matches the ID of the course passed as an argument, which returns an array of the students’ IDs. Then a through the array substitutes each student’s ID for the whole student object. Note that that last lonely is applied to and to get the actual data.Thus the result of method is an array of all the students’ objects enrolled in a particular course, sorry, an so any changes to the data inside the function will update it’s return value and do the appropriate re-renders! 🤩 enrolledStudents computed(() => {...}) .map() .get() computed() enrolledStudents observable array Here’s a simple React component to shows this in practice: This is a pretty standard React components except for the and the . observer store First, a couple of students and a course are defined and added to the store. Then is enrolled in the course. Next we map through the method from the store using the ID of the course for the list of students I want and the results are as expected. student1 enrolledStudents The interesting part happens when you press the button “Enroll Student 2”.In the store, the student ID is added to the array of the corresponding course map, and MobX takes care of keeping it all in sync, correctly the value of and doing the appropriate re-renders. And all of that happens because of L39 where we wrap inside ! compute enrolledStudents , StudentsList observer() Note that your components can get access to the store in a variety of ways. You can import the component from the file just like in the previous example, you can pass it down as a prop from a parent container, or you can use the provider/inject utilities (in my case, I’m fine importing whenever I need to). mobx-react store Conclusion MobX feels indeed a little magical and when I finally made sense of it it was like a gust of fresh air bursting into my React development! (that’s the reference to the top image). Hope you have fun exploring it and keep making cool, awesome stuff!😎

MobX & React for Vuex users

In this tutorial, I’m going to show you how to create a using , , and . It is hosted on the Cosmic JS App Server. We will be using Cosmic JS npm package for implementing the basic CRUD for our objects and to retrieve data and media from Cosmic JS. Let’s get started. Restaurant Menu App Vue2 Vuex Buefy Cosmic JS Download the GitHub repo.! Check out the demo Prerequisites You will be requiring to install Node JS and npm before starting. Make sure you already have them. Getting Started Doing everything using the existing git repo First of all, you have to be sure you have node > 6.x installed, than run the following commands: After successfull completion of the last command browser window will automatically open will look like this. package.json What we’re installing and why We’re going to use and libraries to create components and manage state. vue vuex We’re using package to make async requests to Cosmic JS for deleting media in a loop. async We’re using package to create our layouts using vue components. buefy We’re going to use library to handle our requests to our Cosmic JS bucket. Cosmic JS is used for form validation. vee-validate is used for server side rendering. nuxt Building our app Now we will set up our nuxt.config.js in our root directory where we will change the favicon and set the other basic properties for the app link build properties and linting etc. Also we will include the external CDN’s required for the app. Below is the nuxt.config.js file. Setup default.js default.js in the layouts directory is the starting point in all the app. Here we include master view attributes like navbar and footer. the important thing here is the nuxt tag will initiate all the pages depending upon the route. In the script section in beforeMount we have called the actions that we need to be called when the application loads. Here ‘getMenus’ is worth noting. This action fetches the menu for the current date when application is launched. We have also exposed the store to the vue components. Routing When using nuxt.js we do not need to worry about creating the routes. Nuxt do the job for us. We need to follow the file directory rules described by nuxt and it will create all the necessary routes for us. For more information visit Nuxt documentation Setup index.vue is the first page that will render. I have used buefy components for UI. You can check their documentation . Most important code block here to include landingpage component in the template . This piece of code will render the LandingPage component. \pages\index.vue here Vuex Moving ahead first I will discuss about Vuex and why we should use that. You can obviously use simple state and props for smaller applications. But for large applications we must use some kind of state management like redux in React. Vuex is maintained by vue team and it is widely used. Today we will use that. Below is the Vuex flow diagram that I will explain. There are four main concepts in vuex. State Actions Mutations Getters is where our whole application state/data will be store. So how it will work? For example, you are using this store in you component and want to change some state value. You have to dispatch an . Then will commit the and it will change the state. So why action is needed, we can change state directly in mutation. Action is very important. We need actions when we have to call any async function and then on its success change the state. In case of API we consume request in actions and commit mutation to change state. It is very simple but very import to follow. State action action mutation are simple getter function to get value of state in components. If you need one state value in different components so it is better to create getter for it and use that getter in component as computed property. Getters It is convention to create vuex folder and then create store.js in it. So I did the same and created . store/store.js This is an abbreviated version of “How to Build a Restaurant Menu App”. The full version is available on Cosmic JS. . Click here to view the full article Conclusion This is a basic app for a restaurant menu built using vue , vuex , Cosmic JS and nuxt.js. I hope you liked the tutorial and will be helpfull for you.

Stories, News & Mentions about V2EX

V2ex’s Stories on HackerNoon