<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Daniel Thompson-Yvetot on Medium]]></title>
        <description><![CDATA[Stories by Daniel Thompson-Yvetot on Medium]]></description>
        <link>https://medium.com/@drthompsonsmagickindustries?source=rss-89913d87cbe6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*teI0b0-9zpKA9NHOdevWFQ.jpeg</url>
            <title>Stories by Daniel Thompson-Yvetot on Medium</title>
            <link>https://medium.com/@drthompsonsmagickindustries?source=rss-89913d87cbe6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 20:08:47 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@drthompsonsmagickindustries/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[TIDEFI Techdive]]></title>
            <link>https://medium.com/@drthompsonsmagickindustries/tidefi-techdive-65be3f024d37?source=rss-89913d87cbe6------2</link>
            <guid isPermaLink="false">https://medium.com/p/65be3f024d37</guid>
            <dc:creator><![CDATA[Daniel Thompson-Yvetot]]></dc:creator>
            <pubDate>Fri, 06 May 2022 14:43:04 GMT</pubDate>
            <atom:updated>2022-05-06T16:38:59.084Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TOy7Cvlee_Wsm6N_ytV4uQ.png" /><figcaption>For the Rustaceans out there: <a href="https://youtu.be/cE0wfjsybIQ">https://youtu.be/cE0wfjsybIQ</a></figcaption></figure><h4>A 10.000-Foot view of what we are building</h4><h3><strong>Introduction</strong></h3><p>Most projects in the blockchain space primarily leverage browsers, browser extensions, and the node.js ecosystem to make their networks accessible to the wider public. While there are agile benefits to using such well-known programming approaches, there are many risks associated with browsers and typical javascript design patterns. For Tidefi we decided to take a more grown-up approach, and this article introduces the services and applications we have built and the building blocks that got us here.</p><p><strong>Open Source</strong></p><p>First and foremost, we are open source champions. Members of our team have not only built the highly popular Rust-based <a href="https://tauri.studio/">Tauri Apps</a> framework, but also designed and built the <a href="https://github.com/iotaledger/stronghold.rs">Stronghold</a> secret management library. We are regular contributors to many ecosystems and only consume well-built and maintained 3rd party libraries that are open source. If we discover that a critical piece of common infrastructure is unmaintained, we will adopt it and take over its maintenance. Over the next few months we will be releasing many of the pieces of our puzzle as open-source libraries — in the hope that others may find them useful.</p><p><strong>Programming Languages</strong></p><p>While many professional software engineers may have preferences for one language or another that are based upon experience or 3rd-party library availability, we chose languages appropriate to the respective features and constraints of the services and applications. When we need better memory-safety and systems-level performance, we have chosen Rust. Some services (like our blockchain and user application) are already built on Rust, so it is an obvious choice. We chose Elixir when we require raw performance, scalability, and time-tested resilience (like in our matching engine). In the few circumstances where we need to do something in a webcontext, we have chosen Typescript because it offers stronger type-guarantees than normal Javascript. In order to interface with the Ethereum blockchain, we have written our smart contracts in Solidity, obviously.</p><p><strong>Security</strong></p><p>Secure software is in our DNA. This doesn’t end with choosing an appropriate language and design, but also influences the way in which software engineering is managed. Not only do we regularly review emerging threats within the rust and js ecosystems with automation, but we also engage third party pentesters and security auditors to give us better confidence in all parts of our software. We use strong cryptography and best-in-class design patterns — because with security there are no viable shortcuts. To top it off, our data-center has ISO-27001 and IS0 9001:2015 certifications. When we launch mainnet, we will also be opening up bug-bounty programs to engage with the larger infosec community.</p><h3><strong>Applications</strong></h3><p>Now that we have introduced our approach to software languages, open-source, and security, we are finally in a place where we can discuss the major applications and services that the TIDEFI ecosystem is built upon.</p><p><strong>TIDECHAIN: The source of Truth</strong></p><p>Distributed and public resilience that serves as a source of truth is accomplished today with a system commonly known as distributed ledger technology, or a blockchain. We built our “don’t call it a database” upon the open-source <a href="https://substrate.io/">Substrate</a> framework, which is a Rust &amp; Wasm based system that has been created and maintained by Parity (the creators of the polkadot network). Not only does this system allow us to make runtime upgrades without forking the chain, it includes a wonderfully extensive system of plugins called pallets that allow us to grow our chain over time as needs evolve.</p><p><strong>Quorum: The Warden of Coin</strong></p><p>In order to deposit and withdraw native tokens like BTC and ETH to and from TIDEFI, we have built a Rust-based system that we call the Quorum. It is a collection of service nodes that listen to events on other blockchains, and then communicate with each other to agree upon the creation (minting) of wrapped tokens and their allocation to the wallet address that is associated with the deposit. The Quorum uses multisig or smart-contracts (depending upon the underlying technology of the remote chain). These enable the holder of wrapped assets to “convert” these wrapped assets back to their remote chain, effectively burning them from TIDECHAIN and releasing them from the Smart Contract or Multisig wallet. This system uses Stronghold as a means of not only tracking historical events, but also for keeping the private keys in a secure vault.</p><p><strong>Oracle: The Matching Engine</strong></p><p>In order to provide market matches, the Oracle is a clustered service that pairs makers and takers, and relays “matches” to the TIDECHAIN to perform the swapping of assets at the price points determined by the Market Makers. It has been written in a combination of Elixir and Rust NIFs, in order to provide a massively scalable and fault-tolerant service with really quite breathtaking performance. The Oracle also uses a Stronghold for its signing needs.</p><p><strong>Client App: Secure and Beautiful</strong></p><p>The Client App is a juggernaut. Since it is the primary means by which people will interact with Tidefi, we have taken special care to make it a beautiful and intuitive user interface. Using the Vue3-based Quasar Framework nestled within a Tauri App that ships with a Stronghold, this app uses a number of fantastic technologies to bring you joy, safely.</p><p><strong>Dex Comparator: Saves you a few Clicks</strong></p><p>In order to make it clear how the TIDEFI exchange holds up with others in the space, we have created a Cloudflare Worker, which regularly queries the advertised value of currencies at other decentralized exchanges. You can see this on the dashboard of the application.</p><h3><strong>Build &amp; grow with us</strong></h3><p>To put this all in perspective: Based on the awesome open-source software mentioned above, some of which we have built ourselves, we have managed to put together a bespoke, secure, and scalable DeFi architecture that we are building out and improving by the day. What’s more, we managed to do so without an ICO or pre-sales. Rather, we are close to releasing our beta and public testnet but are still focused on our approach to build a community-driven and community owned infrastructure from day one and will distribute its ownership broadly to those building and using it. Put simply: We have built something beautiful that you can be part of. You can help shape the future of this financial infrastructure and grow together with us. Sound good?</p><p>To learn more, visit our <a href="https://tidefi.com/">website</a>, follow us on <a href="https://twitter.com/Tidefi_DEX">Twitter</a> to stay up to date with what we do, engage with our community on <a href="https://chat.tidefi.com/">Discord</a>, and stay tuned for the upcoming release of our testnet.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=65be3f024d37" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[IOTA Stronghold]]></title>
            <link>https://medium.com/@drthompsonsmagickindustries/iota-stronghold-6ce55d311d7c?source=rss-89913d87cbe6------2</link>
            <guid isPermaLink="false">https://medium.com/p/6ce55d311d7c</guid>
            <category><![CDATA[techupdates]]></category>
            <category><![CDATA[research-and-development]]></category>
            <category><![CDATA[iota]]></category>
            <category><![CDATA[stronghold]]></category>
            <category><![CDATA[announcements]]></category>
            <dc:creator><![CDATA[Daniel Thompson-Yvetot]]></dc:creator>
            <pubDate>Wed, 29 Jul 2020 16:57:06 GMT</pubDate>
            <atom:updated>2020-07-30T14:21:59.764Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introducing IOTA Stronghold</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mBLCmUr7tvTTycy8yc_aBA.png" /></figure><h4>Stronghold is a collection of multipurpose libraries for securely managing passwords, personal data, and private keys.</h4><h4>The Official Repository: <a href="https://github.com/iotaledger/stronghold.rs">https://github.com/iotaledger/stronghold.rs</a></h4><p>The internet can be a dangerous place, and 2020 seems to be a year where literally anything goes. Whether <a href="https://www.reuters.com/article/us-cyber-deepfake-activist/deepfake-used-to-attack-activist-couple-shows-new-disinformation-frontier-idUSKCN24G15E">deep-fakes</a>, <a href="https://www.theregister.com/2020/06/25/akamai_809mpps_attack/">DDoS attacks</a>, <a href="https://krebsonsecurity.com/2020/07/ransomware-gangs-dont-need-pr-help/">ransomware</a>, <a href="https://www.schneier.com/blog/archives/2020/06/iphone_apps_ste.html">clipboard leaks</a>, <a href="https://www.tomsguide.com/news/zoom-security-privacy-woes">zoom insecurity</a> or the dark-patterns of <a href="https://pixelprivacy.com/resources/browser-fingerprinting/">browser fingerprinting</a> — these risks touch all of our digital lives each and every day. At the IF, we are painfully aware of the extent to which <a href="https://blog.iota.org/trinity-attack-incident-part-1-summary-and-next-steps-8c7ccc4d81e8">third-party dependencies can introduce risks</a>.</p><p>What we have learned from the perpetual attacks on our ecosystem is that security must be a guiding principle in Distributed Ledger Technologies, not an afterthought. We need to be vigilant about our entire stack and operations. The mindset of “security-first” must affect not only our practices but also drive our software design decisions.</p><p>As a foundation committed by charter to the dual notions of contributing to open-source and furthering education, we are morally compelled to put our energies into improving the greater good — not merely our own lot.</p><p>In this context of being a “good digital citizen”, the best thing we can do is to offer a means to enhance the security posture of all types of software, including cryptocurrencies, distributed ledger technologies, and even financial infrastructure like exchanges and custody wallets. Specifically, we seek to strengthen the working environment for developers, enhance the security of applications, and give everyone better options for securely storing and safely using high-value digital secrets.</p><p>There are many challenges involved in securely managing digital secrets like passwords, vehicle access codes, and wallet seeds:</p><ul><li>High-value secrets like private keys need to be encrypted at rest, using modern and secure algorithms</li><li>Such secrets need to be purged from device memory immediately after use</li><li>Users must be able to configure systems to their security needs</li><li>Applications need to run on any type of hardware from phones to cars, where possible leveraging Trusted Execution Environments.</li><li>Must be extensible with hardware security like Yubikey and Ledger Nano</li><li>Must use as few external dependencies as possible</li><li>Must be fully audited by third-party security professionals</li><li>The underlying libraries need to be managed by a reliable and active maintainer</li></ul><p>We spent some time <a href="https://github.com/iotaledger/stronghold.rs/blob/dev/spec/1-SCOPE/project-SCOPE-0000.md#prior-art">investigating existing projects</a>, but unfortunately, we couldn’t tick all the boxes and decided to forge ahead and build the Stronghold to secure all of the above.</p><h3>Stronghold, in a nutshell</h3><p>Stronghold is a secure software implementation with the sole purpose of isolating digital secrets from exposure to hackers and accidental leaks. It uses versioned, file-based snapshots with double-encryption that can be easily backed up and securely shared between devices. Written in Rust, it has strong guarantees of memory safety and process integrity. The high-level developer-friendly libraries integrate the IOTA protocol and serve as a reference implementation for anyone looking for inspiration or best-in-class tooling. The low-level libraries have no notion of cryptocurrency embedded within them and can be used in their entirety without the high-level libraries. In other words, anyone from any industry can use it.</p><p>At IOTA, we will begin rolling out the IOTA Stronghold to secure the new wallet. In the next phase, we will have tight integration with IOTA Identity. We look forward to working with exchanges to discover new patterns of usage for Stronghold and are also excited about the many possibilities it brings to our work with smart contracts.</p><h3>For the Technical Professionals</h3><p>The primary task of Stronghold is to isolate the activity of “privileged” functions from other programs. For example, a primary goal is to create a software enclave where private keys are used to sign messages without revealing those keys to other functions. In the near future, we expect to move the Stronghold stack to Trusted Execution Environments (TEE) and integrate it into custom hardware.</p><p>It is based on a suite of low-level libraries known as Stronghold Engine that provide tooling and algorithms to build secure systems in Rust in a way that can be embedded and deployed to devices regardless of architecture and operating system. This collection of libraries deals with the obfuscation, encryption, usage, and sharing of secrets between devices. It has been in research and development for the past 8 months — beginning at <a href="https://ionary.dev/">https://ionary.dev</a> — and it culminated in a successfully completed grant from the IOTA Ecosystem Development Fund. Its code can be reviewed <a href="https://github.com/iotaledger/stronghold.rs/tree/dev/engine">here at GitHub</a> and its principal author, Tensor, has prepared <a href="https://github.com/iotaledger/stronghold.rs/blob/dev/docs/engine-retrospective.md">both a retrospective</a> about its development as well as an <a href="https://youtu.be/pd-XWaGLIck">introductory video</a>.</p><p>Stronghold is written in stable Rust and has four primary components:</p><p>- low-level, modular libraries for building a secure blackbox of versioned data with a file-backed snapshot-oriented persistence layer that enables users to securely share their data between devices (beta quality)</p><p>- high-level libraries that integrate IOTA with the low-level libraries and expose them in an intuitive way (pre-alpha, currently in active development)</p><p>- an actor-model interface for security-focused applications that use Rust (pre-alpha, currently in active development)</p><p>- FFI bindings to other programming languages like C, Java and Node.js (available soon)</p><h3>What will you do with Stronghold?</h3><p>Because of its composability, there are many exciting applications that can be built using Stronghold — not just cryptocurrency wallets. Its low-level engine is totally use-case agnostic and so flexible that the encryption algorithms can be swapped out at your leisure, composed in new ways, and extended with other parts of virtually any stack. The high-level libraries will be so solid that you can entrust them with doing things the right way.</p><p>Here are just a few ideas of the possibilities to help you get your juices flowing:</p><p><strong>Wallet</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EAAwkdI3mB3KUuWB52z84A.png" /></figure><p>Alice’s IOTA wallet is protected by Stronghold, which she can configure (as seen in the image above) to watch over the activity in her wallet and prevent dangerous events from taking place.</p><p><strong>Exchanges<br></strong>Alice the daytrader and her exchanges can collaboratively use Stronghold distributed key generation and BLS threshold signatures for enhancing the auditability of high-volume IOTA token transfers.</p><p><strong>Password Management Tools<br></strong>Securely scrubbing memory after using a password is a common vulnerability in password managers. Stronghold will help Alice to be safer.</p><p><strong>Multimedia Center<br></strong>Alice rents a movie using her Phone to playback on her Smart TV. The movie is sent to the TV as an encrypted stream and a decryption key is synced to her device’s Stronghold. After 48 hours the key is deleted from her Stronghold by the service and the video can no longer be played.</p><p><strong>GDPR Data Processors and Controllers<br></strong>Instead of storing personally identifiable information in a centralized database that can get stolen in one fell swoop, Alice can choose to share and revoke access to her data directly from her Stronghold-powered application.</p><p><strong>Travel Agency</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dmpTjaI2qnd_LfTlSwNeRg.png" /></figure><p>Alice securely shares her passport information with her travel agent, and because of the way that Strongholds sync with each other, when the travel agent no longer needs the passport data, she can remove his access to it.</p><p><strong>Software Developers</strong></p><p>Using the Stronghold command-line interface or system daemon as a local secret and retrieval system enhances Alice the programmer’s operational security and helps prevent accidental disclosure.</p><h3>The Future</h3><p>Stronghold has not yet been formally audited for security vulnerabilities and is moving toward the next phase of public community engagement. We are now making this work public, in the hopes that the open-source and security communities find the opportunity to review the design and implementation. At any rate, in late Autumn 2020, Stronghold will undergo a full external security audit. After the audit’s conclusion and respective revisions, we will declare the project mature enough to be used in your projects.</p><p>The very first internal test of Stronghold will be in its integration with the forthcoming official wallet built for Chrysalis (which will be externally audited before release). It will be the storage mechanism for securing seeds and personally identifiable information. Stronghold will also enable users to enhance their wallet security with Ledger secure storage and Yubikey access.</p><p>Official Repository: <a href="https://github.com/iotaledger/stronghold.rs">https://github.com/iotaledger/stronghold.rs</a></p><p>Low-Level Video Introduction: <a href="https://youtu.be/pd-XWaGLIck">https://youtu.be/pd-XWaGLIck</a></p><p>As always, you can <a href="https://discord.iota.org/">join our Discord</a> to give feedback, comments, and join the discussion.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6ce55d311d7c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Branding and Rebranding]]></title>
            <link>https://medium.com/tauri-apps/branding-and-rebranding-c16daaf03070?source=rss-89913d87cbe6------2</link>
            <guid isPermaLink="false">https://medium.com/p/c16daaf03070</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[rust]]></category>
            <category><![CDATA[tauriapp]]></category>
            <category><![CDATA[graphic-design]]></category>
            <dc:creator><![CDATA[Daniel Thompson-Yvetot]]></dc:creator>
            <pubDate>Sat, 14 Sep 2019 11:44:13 GMT</pubDate>
            <atom:updated>2019-09-14T11:44:13.064Z</atom:updated>
            <content:encoded><![CDATA[<h4>Tauri has had a few facelifts, but we think we nailed it this time.</h4><h3>Proton</h3><p>The first name for Tauri was Proton, because we wanted to pick a fight with Electron. (We don’t anymore, btw. Electron is super awesome!)</p><p>At the time, we were incubated at the Quasar Framework, so it made sense to riff off of the Quasar logo. This is what we had:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/240/0*5gkk_5e_jcX0Cgle.png" /></figure><p>So as (bad) luck would have it, every single particle from physics already had a javascript project associated with it, and to our dismay it turned out that Proton-Native was also a thing.</p><h3>Quasar-Tauri</h3><p>So we spent about a week discussing a new name, and came up with Tauri, named after the Binary Star type.</p><p>This made sense because of the way we were planning to build Tauri apps. So we removed one of the sub-particles from the Proton logo and ended up with this nice little guy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/240/0*TU2iqpVtfmQKQciM.png" /></figure><p>One of the comments from the community was that it was cool how the logo seemed to riff off of the Gear from Rust. This was totally unintentional though, because Quasar’s logo is for a pure JS project, and the “gear” is more of a stylized vortex.</p><h3>Post Quasar</h3><p>At any rate, after we left the incubator to spin up our own organization, we had to make another logo because we couldn’t justify using the former design basis. One of the early ideas was to make a logo with more “bite”, so I put together an example using a <a href="https://geargenerator.com/index.php#475,425,50,2,1,2,367363.9000002474,3,1,32,10.666666666666666,3,26,0,1,0,0,0,0,0,13,4.333333333333333,3,26,-130,0,0,0,0,0,0,13,4.333333333333333,3,26,50,0,0,0,0,0,1,3,239">real gearset</a> that I prototyped over at <a href="https://geargenerator.com/">https://geargenerator.com</a> — and the author Abel Vincze even comped us a download. (Fun fact: the Rust logo has the same number of teeth as both healthy adult humans and giraffes: 32.)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/434/0*KNr3kcEYLlV_P14W.png" /></figure><p>But the two inner gears just made it seem too aggressive, and then a third gear was added:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/827/0*sUMp4IOxe6i9KY6h.png" /></figure><p>But it all just seemed a bit off. So, after about a week of discussion and some deep thinking about the name Tauri, we ended up with a graphic stylization of <a href="https://en.wikipedia.org/wiki/Theta_Tauri">Theta Tauri</a>, a real binary star whose abbreviation is θ Tau.</p><p>What I loved about that is that the theta symbol could be an impulse for the design, so I found an image of <a href="https://upload.wikimedia.org/wikipedia/commons/b/b0/Hyades_cluster.jpg">Theta-Tauri</a> in the Hyades Cluster, and after a bit of back and forth in the Working Group for Media, we ended up with this, our latest design:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/0*0G-8oupNg8YkvO9g.png" /></figure><h3>Takeaways</h3><p>Coming up with a design is hard work. Redesigning things seems to take more time, especially when there are a lot of stakeholders. But it is still a valuable exercise in team communication and transparency.</p><h3>Get in Touch</h3><p><strong>Tauri</strong> apps aren’t quite ready for prime-time and there is a lot of work needed in the codebase and the governance structure to get to that point. Nevertheless, in our quest for transparency and community involvement, we are taking this opportunity to invite everyone from the Rust, Appsec and Dev communities to come around and find out where the project is at, where it is going and how to get involved in the working groups.</p><p><strong>Tauri</strong> is an organization that seeks to follow the best practices of the SFOSC <a href="https://sfosc.org/docs/principles/">principles</a>. It is our duty and pleasure to humbly invite you to visit our public <a href="https://github.com/tauri-apps">GitHub project page</a>, hang out at our <a href="https://discord.gg/SpmNs4S">Discord chat server</a>, donate money at our <a href="https://opencollective.com/tauri">Open Collective</a> page or simply follow our <a href="https://twitter.com/tauriapps">Tweets</a>.</p><h4>About the Author</h4><p>Daniel Thompson-Yvetot is the principal architect and security engineer behind <a href="https://github.com/tauri-apps">Tauri</a>. He has been an open source evangelist for the last 13 years and is an active member of the Sustainable Free and Open Source Communities (<a href="https://sfosc.org/">SFOSC</a>).</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c16daaf03070" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tauri-apps/branding-and-rebranding-c16daaf03070">Branding and Rebranding</a> was originally published in <a href="https://medium.com/tauri-apps">tauri-apps</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[We want smaller, faster, more secure native apps]]></title>
            <link>https://medium.com/tauri-apps/we-want-smaller-faster-more-secure-native-apps-77222f590c64?source=rss-89913d87cbe6------2</link>
            <guid isPermaLink="false">https://medium.com/p/77222f590c64</guid>
            <category><![CDATA[development]]></category>
            <category><![CDATA[rust]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[appsec]]></category>
            <category><![CDATA[cross-platform-apps]]></category>
            <dc:creator><![CDATA[Daniel Thompson-Yvetot]]></dc:creator>
            <pubDate>Thu, 05 Sep 2019 20:57:20 GMT</pubDate>
            <atom:updated>2019-09-05T20:57:20.829Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Situation Room</h3><p>In 2019, the manufacture of native-apps from compile-to-javascript user-interface frameworks has become easier and more accessible than ever before. All the same, beginners and seasoned developers alike are confronted with tough choices in a rapidly changing landscape of security and privacy. This is especially true in the semi-trusted environment of user devices, where vendors fragment the already diverse ecosystem with their proprietary “solutions”.</p><p>The fragmentation of the app landscape doesn’t end with devices though, as there are not only innumerable front-end frameworks like React, Angular, Vue and Svelte … but also a range of packagers like Capacitor, Electron, Proton-Native and others popping up daily. Multiply this with insecure dependency management and incomplete vulnerability remediation, and we are left with a fractured ecosystem where the winners are merely the lucky ones who haven’t gotten hit — yet.</p><p>The fact is that most of these frameworks were never conceived to exist outside of the browser sandbox and have been suddenly thrust into a very hostile environment where development teams resort to applying workarounds like shipping shared certs, hacking on-device registries or stooping to the unfortunately common integration of localhost servers on the devices themselves.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xTF7jcqAcP7IPqn_gYDnEA.png" /></figure><h3>A Paradigm Shift</h3><p><strong>Tauri</strong> approaches these issues head on, as it was designed from the ground up to embrace novel patterns for secure development and creative flexibility that leverage the language features of Rust and enable you to grow your app using any front-end framework you like. And all of that in a much more secure distribution environment.</p><p>With <strong>Tauri</strong> as a component in your toolchain, you will be able to design, build, audit and deploy tiny, fast, robust and secure native applications for the major Desktop and Mobile platforms in record time. You can do all this within your preferred dev environment, using any framework and without even needing to know the Rust programming language. If you know Rust, however, you will be empowered to make even more amazing integrations with the underlying operating system and hardware.</p><p>The <strong>Tauri-Team</strong> has already completed some initial proofs of concept using WebViews (with really encouraging results such as &lt; 3MB binaries on MacOS, Windows and Linux). At the moment we are finalizing the API, preparing smoke-tests, investigating cross-compilation tools and even building a binary evaluation harness. However, we are not totally satisfied with the WebView approach, and are investigating alternatives like Servo and Webkit.</p><h3>Get in Touch</h3><p><strong>Tauri</strong> apps aren’t quite ready for prime-time and there is a lot of work needed in the codebase and the governance structure to get to that point. Nevertheless, in our quest for transparency and community involvement, we are taking this opportunity to invite everyone from the Rust, Appsec and Dev communities to come around and find out where the project is at, where it is going and how to get involved in the working groups.</p><p><strong>Tauri</strong> is an organization that seeks to follow the best practices of the SFOSC <a href="https://sfosc.org/docs/principles/">principles</a>. It is our duty and pleasure to humbly invite you to visit our public <a href="https://github.com/tauri-apps">GitHub project page</a>, hang out at our <a href="https://discord.gg/SpmNs4S">Discord chat server</a>, donate money at our <a href="https://opencollective.com/tauri">Open Collective</a> page or simply follow our <a href="https://twitter.com/tauriapps">Tweets</a>.</p><h4>About the Author:</h4><p>Daniel Thompson-Yvetot is the principal architect and security engineer behind <a href="https://github.com/tauri-apps">Tauri</a>. He has been an open source evangelist for the last 13 years and is an active member of the Sustainable Free and Open Source Communities (<a href="https://sfosc.org/">SFOSC</a>).</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=77222f590c64" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tauri-apps/we-want-smaller-faster-more-secure-native-apps-77222f590c64">We want smaller, faster, more secure native apps</a> was originally published in <a href="https://medium.com/tauri-apps">tauri-apps</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Quasar 1.0 — Sneak Peek]]></title>
            <link>https://medium.com/quasar-framework/quasar-1-0-sneak-peek-727b4e490899?source=rss-89913d87cbe6------2</link>
            <guid isPermaLink="false">https://medium.com/p/727b4e490899</guid>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[quasarframework]]></category>
            <category><![CDATA[vuejs]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[cli]]></category>
            <dc:creator><![CDATA[Daniel Thompson-Yvetot]]></dc:creator>
            <pubDate>Wed, 12 Dec 2018 20:36:56 GMT</pubDate>
            <atom:updated>2018-12-15T10:53:34.043Z</atom:updated>
            <content:encoded><![CDATA[<h3>Quasar 1.0 — Sneak Peek</h3><h4>Coming January 2019</h4><p>With the full release of the <a href="https://busy.org/@quasarframework/the-quasar-framework-joins-forces-with-utopian-io-and-the-steem-community">Quasar-Framework v1.0</a> at the end of January 2019 (and the first RCs coming sooner), we wanted to take the opportunity to highlight some of the things that we are really excited about, some of the things that might not make the cut (but are nevertheless slated for release after 1.0) and finally spend a moment discussing how we plan to support users of the legacy codebase.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/516/1*Lkmp0k97aoufvvquB1zOWQ.png" /></figure><p>Before we dive into it though, first a few words about what 1.0 will mean for you as a developer. Our contract with you (and the code) is that there will be no more breaking changes: The API will be stable — which we understand to mean that refactoring will remain within the black box and we will only make additive modifications. This forward compatibility will bring you peace of mind and enable you to safely build your projects for the long term — and grow with Quasar!</p><h3>Front and Center</h3><p>We’ve gone through ALL of the over 120 components, and curated each and every of them in order to unify their properties with the intention of making everything faster and cleaner. In some of our tests, the new components render <strong>7x faster</strong> and just feel snappier. This is due to more logical, minimal and consistent component design.</p><p>We can’t stress this enough: every component has been rewritten from scratch, curated for runtime speed, enhanced with new features (almost all components have more features) and they will be easier to customize.</p><p>We are also going to be introducing new components, such as (naming only a few) QCircularProgress, QAvatar, QSpace, QSeparator, QMarkupTable, QBar, QSlideItem, QSplitter and QImg. That’s right — you are going to be getting responsive images!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8sKlbnF39J0h8eJeJNUnLA.png" /><figcaption>Responsive Images, Focal Ripple, QDialog Card!!!</figcaption></figure><p>While adding new components, we’ve also thought about how to make Quasar even <strong>easier</strong> and <strong>faster</strong> to use. So for example, instead of having a lot of QCard sub-components or QItem subcomponents, we’ve collapsed them into fewer subcomponents. Instead of having QCardActions, QCardMain, QCardMedia, QCardSeparator and QCardTitle now you will only need QCardActions and QCardSection. The same goes for QItem: QItemSection and QItemLabel (instead of QItemMain, QItemSeparator, QItemSide, QItemTile). And these are just two examples…</p><p>One of the most adored features of stock Quasar is that we have always paid close attention to the Material Design specification. You will be happy to know that we are continuing this tradition by sanding off all of the rough edges and will provide pixel perfect and spec-consistent Material 2.0 design — out of the box.</p><p>In general, you will find that it has become easier to customise the styling of your apps and it will be easier to write them. Furthermore, we have adopted the consistency of <a href="https://github.com/sturobson/BEM-resources">BEM class naming</a>, so that implementation of styling is easier and more logical.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xWLWKm9WlV0DQS7F7j93Bw.png" /><figcaption>BEM, stylish breadcrumbs, QBanner</figcaption></figure><h3>Details?</h3><p>In the lead-up to the launch, we will be publishing a weekly series of articles by Scott that go into depth about the new components. The miniseries is called “Have You Seen” (HYS) and you’ll be able to read all about it on our Steem and Medium blogs. The two images above are from two of the first installments in this series.</p><h4>Behind the Scenes</h4><p>The first thing that you will notice is that we have switched to our brand new NPM organisation for packaging: <strong>@quasar</strong></p><p>We have split the old <strong>quasar-cli</strong> into <strong>@quasar/cli</strong> &amp;&amp; <strong>@quasar/app</strong>. To be clear you will get: <br>- an optional global install package <strong>@quasar/cli</strong> — which is used to create new projects and brings the convenience of having quasar commands globally available<br>- the local package <strong>@quasar/app</strong> — which is what will “live” within your project</p><p>By splitting these two, we want you to enjoy a faster install of both the global CLI as well as the local package — and fewer dependencies within your project. To be clear: <strong>@quasar/cli</strong> defers to the locally installed <strong>@quasar/app</strong> in each project. Finally, <strong>@quasar/cli</strong> will also support the current “quasar serve” command along with “quasar create” (replacing “quasar init”).</p><p>What you should never notice, however, is that in order to make sure that our packages are safe and don’t introduce regressions, they will be run through a CI that includes unit, snapshot and e2e testing. This means that we won’t even be able to publish stuff that breaks.</p><h4>Speaking of testing…</h4><p>We have been working really hard to configure testing harnesses that not only cover units deeply within node.js, Vue and Quasar contexts, but also effortlessly run e2e tests for web, cordova and electron.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*b144eSxeNhAYfcPaifN99A.png" /><figcaption>Test all the things.</figcaption></figure><p>The best part about the experience that we have gained in testing is that it will be made available to you as well. To profit (and install your preferred testing framework), you will merely need to add the respective package(s) from the <strong>@quasar/testing</strong> monorepo, such as: <br>- <strong>@quasar/testing-unit-jest</strong> (with sample tests and istanbul coverage)<br>- <strong>@quasar/testing-e2e-cypress</strong> (extended with quasar methods)<br>- <strong>@quasar/testing-e2e-webdriver</strong> (prerigged for all modes)<br>- <strong>@quasar/testing-quality</strong> (with lighthouse)<br>- <strong>@quasar/testing-security</strong> (with snyk and XSStrike)<br>- <strong>@quasar/testing-loader</strong> (manage &lt;test&gt; templates within your SFC’s)</p><p>As time goes on, we will be introducing community-built testing harnesses — so if your favourite is missing, you will be able to fork the monorepo, construct a new package and make a PR. After vetting, it will become available to everyone else — and you will be our newest hero!</p><h4>Code Quality and Safety</h4><p>By the way, one of the tools we used to help us generate the test primitives was our new d.ts typescript definitions (which we in turn actually generate from the codebase). The great part about this is that you can use these typedefs yourself and immediately gain all the benefits of strongly typed code in your own project (should you choose to go the **ts** route…) This is one of the first steps in Quasar’s eventual transition to using typescript internally, keeping in-line with the Vue roadmap. (More about typescript below…)</p><h4>The Docs</h4><p>Probably sooner than later, you will discover that the docs website has been completely reinvented. For starters, we are using Quasar SSR to serve these pages — which means that it is less complicated to keep the docs up to date. Also, there are embedded code-pens — where you can actually play with the code. We hope that using the docs becomes a great pleasure!</p><p>Further, because we have such an enormous global audience, we have partnered up with DaVinci via Utopian.io and are using the crowdin translation service to translate all the docs into a bunch of different languages.</p><h3>After the launch…</h3><p>…is before the launch. There are a lot of little (and not so little) things that didn’t absolutely need to be released with 1.0, but that we are really excited about anyway — and are “coming soon”!</p><p><strong>Upgrading<br></strong>One of the first things that we will do after 1.0 launches is to create a guide that will assist you in upgrading your projects. We really want you to be successful with this undertaking, so please join us on the Discord channel and let us know where your pain points are.</p><p><strong>Typescript<br></strong>As hinted at above, we will be refactoring all of the components to use typescript, which will assuredly make many of you happy (and keep Quasar in step with the direction that vue itself is taking.) [EDIT: You will not have to use Typescript to build your own projects, you CAN still use ecma if that’s your thing…]</p><p><strong>Snippets<br></strong>Up until now, you have had to search through the Discord server, wade through questions on the forums or hope that there is an up-to-date solution floating around stackoverflow. Usually people just need a perfect snippet, and we are working on a website specifically for this where you can post your solutions for the benefit of the community (and of course also your convenience of knowing where to look for the answers you personally wrote).</p><p><strong>Theming<br></strong>Making and changing themes has been notoriously tricky in legacy Quasar — often involving countless CSS overrides and using DOM element inspection to figure out what to target to match your pixel-perfect layout. Merely changing colors cannot be called theming, which is why we will be releasing a system for creating, using and sharing themes.</p><p><strong>Lots of starter kits<br></strong>We are already working together with Byteball to create a cryptocurrency focussed starter-kit that will be the very first official “extended starter kit”. This pattern will let you get even faster scaffolding of common things you need to get your project into active development. (This will be perfect for themed hackathons, by the way…)</p><p><strong>i18n</strong><br>Internationalization has always been a real pain to set up and get right, and we have some battle-tested ideas about how to help you rig your project, manage your translation strings and assist with invaluable lazy-loading on massively multilingual projects. For SSR getting your translation hooked on prefetch is a must for your SEO, so stay tuned to find out how much you’ll love what we are bringing to the multi-culti dinner party!</p><p><strong>a11y</strong><br>Remaining accessible is a must for any serious interface — and this concern needs definite attention with hyper-reactive front-ends. To help you (and your users) we will be enhancing all of the components with accessibility properties and empowering you to run **a11y** audits alongside your other quality controls in your production pipeline.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*PnfJFej-xtpYK05HHLw8Dw.png" /></figure><p><strong>Icons</strong><br>The icon-factory is a long-awaited addition to the Quasar Framework, with which you will be able to create all the icons you need for your application, whether Cordova, Electron or SPA. It is delivered as a webpack plugin that will create the assets that you specify (or configure) whenever the source image changes.</p><p><strong>Media Player<br></strong>We are also excited to be publishing a new component for media playback by Hawkeye64. This HTML5 component will let you stream audio or video files to all browsers — using local or remote resources. It has tons of configurations — and it comes ready to integrate subtitles and even overlays (like channel icons)!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*rdRZAzPlunH99Nn5UaAREA.png" /></figure><h3>Legacy Quasar</h3><p>With absolutely everything being refined and in some cases entirely redesigned, you might be asking yourself the following: Will there be compatibility issues with my pre-1.0 Quasar apps?</p><p>If you have been sticking it out with Quasar for a while, you might remember some of the bellyaches around the transition to Babel 7 and Webpack 4 that we undertook with the launch of 0.16. We know that keeping up with Quasar has taken a lot of effort, and that is why we froze development on 0.17 so we could get 1.0 out the door. Those of you who stay up to date will have noticed that we still managed to put out a few updates to 0.17 to fix issues that cropped up.</p><p>Migrating will be tricky, but as always we will create and maintain a migration documentation page that will help you navigate your way to 1.0. If, however, you are unable to spend the dev-cycles to port to 1.0, we want to reassure you that we plan to continue this pattern of back-porting bugfixes and keeping all of the dependencies up-to-date.</p><blockquote>Our promise to you: We will maintain legacy Quasar at least until the end of 2019, so that you can take your time to transition to the best edition of the best framework out there.</blockquote><h4>THANKYOU</h4><p>I would like to give special thanks to our staff:<br>- pdandan<br>- nothingismagick<br>- smolinari<br>- PhearZero<br>- francesco<br>- Hawkeye64<br>- AlphaRolo<br>- KevinMarrec<br>- murbanowicz<br>- a46ae<br>- ross<br>- Neven<br>- Ross<br>- MaxMatteo<br>- GastroGeek</p><p>Also big thanks to the sponsors and donors who have stuck with us over the past several years! You are awesome!!!</p><p>And last, but not least, thanks to every single member of our awesome community of open-source afficianados. You are the inspiration behind Quasar!</p><h4>Razvan Stoenescu</h4><p>If you need more information about Quasar itself, here are a few links for your consideration:</p><p>PATREON: <a href="https://www.patreon.com/quasarframework">https://www.patreon.com/quasarframework</a><br>COMPONENTS: <a href="https://github.com/quasarframework/quasar">https://github.com/quasarframework/quasar</a><br>CLI: <a href="https://github.com/quasarframework/quasar-cli">https://github.com/quasarframework/quasar-cli</a><br>THE DOCS: <a href="https://quasar-framework.org/">https://quasar-framework.org/</a><br>DISCORD: <a href="http://chat.quasar-framework.org/">http://chat.quasar-framework.org/</a><br>FORUM: <a href="https://forum.quasar-framework.org/">https://forum.quasar-framework.org/</a><br>TWITTER: <a href="https://twitter.com/quasarframework">https://twitter.com/quasarframework</a><br>STEEM: <a href="http://steemit.com/@quasarframework">http://steemit.com/@quasarframework</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=727b4e490899" width="1" height="1" alt=""><hr><p><a href="https://medium.com/quasar-framework/quasar-1-0-sneak-peek-727b4e490899">Quasar 1.0 — Sneak Peek</a> was originally published in <a href="https://medium.com/quasar-framework">Quasar Framework</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Quasar is not just a bunch of components]]></title>
            <link>https://medium.com/quasar-framework/quasar-is-not-just-a-bunch-of-components-282362d1ec65?source=rss-89913d87cbe6------2</link>
            <guid isPermaLink="false">https://medium.com/p/282362d1ec65</guid>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[webpack]]></category>
            <category><![CDATA[vuejs]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[quasarframework]]></category>
            <dc:creator><![CDATA[Daniel Thompson-Yvetot]]></dc:creator>
            <pubDate>Fri, 14 Sep 2018 07:16:01 GMT</pubDate>
            <atom:updated>2018-09-14T07:16:01.984Z</atom:updated>
            <content:encoded><![CDATA[<h4>We have to set the record straight.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/242/1*Eh4By2nN8nqvtGJ2fC8UwQ.png" /></figure><p>It seems a lot of people think that <strong>Quasar</strong> is just a collection of well-made, material-design-compliant components for vue.js — and although we do deliver bulletproof pieces that you can drop into your project and extend with other plugins like axios and vue-i18n, quasar is <strong>MUCH, MUCH</strong> more!!!</p><p>On our Discord server, we get this question a lot:</p><blockquote>Should I make a quasar-cli app, take the UMD version or use it as a plugin with the vue-cli?</blockquote><p><strong>Quasar</strong> is all about solving the puzzle of the development experience — which means that most of the effort has been put into building a node.js based command-line-interface that considers all the needs of a modern dev.</p><p>For starters, it takes your project and renders a live development server with webpack. Whether you are making an SSR app, a PWA or even targeting Electron, it works tirelessly in the background to rebuild the project cache and hot-reload your browser / electron window / cordova emulator — while you are making changes to your code. You don’t have to even reload the browser.</p><h3>I am going to let that sink in for a moment.</h3><p>When you are done working on the code and it comes time to build your app, Quasar will construct everything with the exact same appearance, but does a lot of things under the hood to streamline your project. For one thing, if you pay attention to what you are doing, an SSR &amp; PWA app built with quasar-cli will make it possible for you to get that coveted 100% Lighthouse score. (Fun fact: not even the Lighthouse page at Google achieves 100%.)</p><p>You can leverage the awesome electron-builder to make picture-perfect desktop apps for all platforms (even with the super nice app logo instead of the stock Electron one). And of course if you want mobile apps in the stores, the Cordova build pipeline has you covered.</p><p><strong>Did we mention that this is all from the same codebase?</strong></p><p>No matter which target or targets your artefacts are built for, quasar-cli does tree-shaking of your imported modules. This not only reduces the size of the final asset collections, it also reduces the surface area for possible attackers. It helps the end-user’s device to leverage lazy-loading so that assets are delivered as they are needed, not in one nail-biting and suspenseful initial load.</p><p><strong>FAZIT</strong>: Suspense is nice in Hitchcock movies, but do you really want your users to think the words “<em>dramatic and mysterious</em>” while waiting for your page to load? Quasar takes the mystery out of web development — and saves you time too.</p><p>If you need more information about Quasar itself, here are a few links for your consideration:</p><p>COMPONENTS: <a href="https://github.com/quasarframework/quasar">https://github.com/quasarframework/quasar</a><br>CLI: <a href="https://github.com/quasarframework/quasar-cli">https://github.com/quasarframework/quasar-cli</a><br>THE DOCS: <a href="https://quasar-framework.org/">https://quasar-framework.org/</a><br>DISCORD: <a href="http://chat.quasar-framework.org/">http://chat.quasar-framework.org/</a><br>FORUM: <a href="https://forum.quasar-framework.org/">https://forum.quasar-framework.org/</a><br>TWITTER: <a href="https://twitter.com/quasarframework">https://twitter.com/quasarframework</a><br>STEEM: <a href="http://steemit.com/@quasarframework">http://steemit.com/@quasarframework</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=282362d1ec65" width="1" height="1" alt=""><hr><p><a href="https://medium.com/quasar-framework/quasar-is-not-just-a-bunch-of-components-282362d1ec65">Quasar is not just a bunch of components</a> was originally published in <a href="https://medium.com/quasar-framework">Quasar Framework</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Quasar Framework joins forces with Utopian.io]]></title>
            <link>https://medium.com/quasar-framework/the-quasar-framework-joins-forces-with-utopian-io-a6fb8c77a75e?source=rss-89913d87cbe6------2</link>
            <guid isPermaLink="false">https://medium.com/p/a6fb8c77a75e</guid>
            <category><![CDATA[steemit]]></category>
            <category><![CDATA[utopianio]]></category>
            <category><![CDATA[vuejs]]></category>
            <category><![CDATA[quasarframework]]></category>
            <dc:creator><![CDATA[Daniel Thompson-Yvetot]]></dc:creator>
            <pubDate>Wed, 29 Aug 2018 07:01:01 GMT</pubDate>
            <atom:updated>2018-08-29T07:01:01.490Z</atom:updated>
            <content:encoded><![CDATA[<h4>and the Steem Community</h4><p>Over the weekend we announced our new partnership with <a href="https://utopian.io/">utopian.io</a> on Steem. Here is the<a href="https://busy.org/@quasarframework/the-quasar-framework-joins-forces-with-utopian-io-and-the-steem-community"> Original article on Steem</a>. We are very excited about this collaboration and look forward to it growing into a model where shared interests lead to mutually assured evolution.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FfK8ZEXaODfLEPyY3qQ6yw.png" /></figure><h3>What is Utopian?</h3><blockquote>Utopian is the only platform rewarding contributions to Open Source projects by utilising a decentralised, vote-based reward system built on top of the STEEM Blockchain.</blockquote><p><a href="https://signup.utopian.io/">https://signup.utopian.io/</a> &gt; use this to register and link your github account. It will help you to skip the 3-day wait time for new accounts on Steem.<br><a href="https://join.utopian.io/guidelines">https://join.utopian.io/guidelines</a> &gt; this page talks about how utopian works<br><a href="https://busy.org/">https://busy.org/</a> &gt; the best steem post editor out there<br><a href="https://busy.org/@utopian.edu">https://busy.org/@utopian.edu</a> &gt; introductory videos to utopian and steem</p><h3>Utopian and Quasar</h3><p>As fate would have it, two teams with similar visions of empowering open source have decided to join forces. Utopian.io is building their new platform with Quasar, and Quasar is looking to be a lighthouse in the very solitary ocean of web development. We are proud to be technical partners, which means that our two teams help each other to learn and use each other’s platforms by leveraging knowledge and experience. Sharing best practices through direct lines of communication is not only an exciting way to make sure that things get done right, but it is also a catalyst for collaborative innovation — such as our forthcoming Vue-centric and Quasar-themed webinar about publishing on Steem with Utopian, or Quasar’s soon-to-launch <a href="https://busy.org/@fundition">@fundition</a> campaign. (Don’t worry — you’ll hear about it all when the time comes!!!)</p><h3>Quasar and Utopian</h3><p>Quasar will be publishing contributions on Utopian in order to keep everybody up to date with development status, to share blog articles about awesome projects made with Quasar, to give tutorials about best practices, and even hints about new features in the documentation. As Quasar gathers power on Steem, we will start publishing tasks regarding important areas of the project where we need insight and contributions, such as translations, test-writing, bug-fixing and even copy-writing. Along the way we will mentor developers using Quasar in how they can use the same approach for their projects. Also, we expect to contribute our deep knowledge of design to help graphic designers and artists take on Quasar-specific tasks.</p><p>If you need more information about Quasar itself, here are a few links for your consideration:</p><p>COMPONENTS: <a href="https://github.com/quasarframework/quasar">https://github.com/quasarframework/quasar</a><br>CLI: <a href="https://github.com/quasarframework/quasar-cli">https://github.com/quasarframework/quasar-cli</a><br>THE DOCS: <a href="https://quasar-framework.org/">https://quasar-framework.org/</a><br>DISCORD: <a href="http://chat.quasar-framework.org/">http://chat.quasar-framework.org/</a><br>FORUM: <a href="https://forum.quasar-framework.org/">https://forum.quasar-framework.org/</a><br>TWITTER: <a href="https://twitter.com/quasarframework">https://twitter.com/quasarframework</a><br>STEEM: <a href="http://steemit.com/@quasarframework">http://steemit.com/@quasarframework</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a6fb8c77a75e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/quasar-framework/the-quasar-framework-joins-forces-with-utopian-io-a6fb8c77a75e">The Quasar Framework joins forces with Utopian.io</a> was originally published in <a href="https://medium.com/quasar-framework">Quasar Framework</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Quasar Census — 2018]]></title>
            <link>https://medium.com/quasar-framework/the-quasar-census-2018-32db8172aee3?source=rss-89913d87cbe6------2</link>
            <guid isPermaLink="false">https://medium.com/p/32db8172aee3</guid>
            <category><![CDATA[quasarframework]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[steemit]]></category>
            <category><![CDATA[qcensus2018]]></category>
            <category><![CDATA[vuejs]]></category>
            <dc:creator><![CDATA[Daniel Thompson-Yvetot]]></dc:creator>
            <pubDate>Mon, 27 Aug 2018 08:31:39 GMT</pubDate>
            <atom:updated>2018-08-27T08:31:39.661Z</atom:updated>
            <content:encoded><![CDATA[<h4>Using Quasar? Tell us!!!</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Txl7m60aXLb6okp6cS5uvQ.png" /></figure><p>With over <a href="https://github.com/quasarframework/quasar">7000 stars on Github</a> and a growing list of projects on our <a href="https://github.com/quasarframework/quasar-awesome">awesome-repo</a>, we know that many developers are using the open-source Quasar Framework to make great experiences for and with their communities. We also know from private conversations that most professional developers are so happy with its rendering speed, flexibility and documentation that they don’t need to stop by and ask for help. But as we close in on our 1.0 release, we want to connect with everyone who is using Quasar — because we have some <strong>big announcements to make</strong>.</p><h3>The Quasar Census</h3><p>Do you use the Quasar Framework for your project, are you planning to or do you think it could be a good idea? Are you a student, developer or agency who made the switch to Vue and Quasar? Wish you could support us but don’t have the money? Do you just want some free publicity for your Quasar project?</p><p>If any of the above are true, let us know about it! Use this template in a comment below, tweet it or post it on steem with the#qcensus2018 #quasarframeworkhashtags. If you really want to tell us but prefer to keep your skunkworks project secret until launch day, we get it — but we still want to hear from you and will keep your info off the record. Send an email or ping us on Discord.</p><pre>********************* <br>#qcensus2018 template <br>********************* <br>%What You Call Your Project / APP / Site% <br>https://yourwebsite.tld <br>%git repository% (must be public if you have one) <br>%elevator pitch% <br>%comments% (anything you would like us to know about your project) <br>*********************</pre><p>If you need more information about Quasar itself, here are a few links for your consideration:</p><p>COMPONENTS: <a href="https://github.com/quasarframework/quasar">https://github.com/quasarframework/quasar</a><br>CLI: <a href="https://github.com/quasarframework/quasar-cli">https://github.com/quasarframework/quasar-cli</a><br>THE DOCS: <a href="https://quasar-framework.org/">https://quasar-framework.org/</a><br>DISCORD: <a href="http://chat.quasar-framework.org/">http://chat.quasar-framework.org/</a><br>FORUM: <a href="https://forum.quasar-framework.org/">https://forum.quasar-framework.org/</a><br>TWITTER: <a href="https://twitter.com/quasarframework">https://twitter.com/quasarframework</a><br>STEEM: <a href="http://steemit.com/@quasarframework">http://steemit.com/@quasarframework</a></p><p><a href="https://steemit.com/utopian-io/@nothingismagick/qcensus2018-campaign-graphics-breakdown">About the image</a> used in this campaign.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=32db8172aee3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/quasar-framework/the-quasar-census-2018-32db8172aee3">The Quasar Census — 2018</a> was originally published in <a href="https://medium.com/quasar-framework">Quasar Framework</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I Joined the Quasar Framework Team]]></title>
            <link>https://medium.com/quasar-framework/how-i-joined-the-quasar-framework-team-d0671d014193?source=rss-89913d87cbe6------2</link>
            <guid isPermaLink="false">https://medium.com/p/d0671d014193</guid>
            <category><![CDATA[vuejs]]></category>
            <category><![CDATA[steem]]></category>
            <category><![CDATA[programming-tips]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[quasarframework]]></category>
            <dc:creator><![CDATA[Daniel Thompson-Yvetot]]></dc:creator>
            <pubDate>Thu, 23 Aug 2018 09:34:35 GMT</pubDate>
            <atom:updated>2018-08-23T13:26:46.261Z</atom:updated>
            <content:encoded><![CDATA[<h4>(and why you should too)</h4><p><em>tl;dr; How I became an open-source developer and member of the Quasar team.</em></p><p><em>eli5: Sharing isn’t stealing. Help people to help you. Everyone can be a programmer.</em></p><p>If you know me personally, you also know that I belong to that specific class of lazy people who would rather spend weeks building the perfect tool to do something that would have gotten done in minutes were I that other kind of person: that kind who doesn’t get bored doing the same thing over and over.</p><p>For me, it is exciting when it’s new — and I don’t like having to do something the same way a third time. For example, I solve problems by making tools such as an <a href="https://github.com/nothingismagick/VTT-Editor">automatic video editor</a> for batch editing short films, designing an approach for declaring the <a href="http://ionary.org/openness/">“degree of openness”</a> of open-source artefacts, using set-theory to figure out what people mean when they <a href="http://ionary.org/i-dont-know-art-but/">say something silly</a>, or even assembling an artistic reflection of the state of our modern world, like the following photograph of one of my sculptural installations…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/644/0*exeeu4uwd3N95XkM.jpeg" /><figcaption>Kulturerbe (Cultural Heritage) — 2007 — Installation view, Galerie Eigenheim (Weimar)</figcaption></figure><p>Tools are applied culture, because not only do they help us interact with our world in efficient and/or fun ways, their use also tells us a lot about who we are. Programming, as a form of communication, has always been about the automation of logical tools: input, condition, step, action, output.</p><p>Automation is a great thing, because if you do it right it really takes all of the boredom out of your life and lets the machine do the stuff you can’t be bothered with. In the 1980s, I wrote my very first program in Basic on a Commodore 64 to help me quickly generate NPC’s and Monsters for the role-playing games of Dungeons &amp; Dragons that my friends and I would play. For me the sounds of a dot-matrix printer and the clattering of D6’s are permanently melded into one acoustic memory…</p><p>I suppose that I too am also a product of the epoch in which I live, just another one of those creatures that fights the staleness of entropy with every breath (and keystroke). Look at all of the extreme athletes who go to the absolute unit of their limits and sometimes even die in search of the thrill, the sport, the excitement. Look at all of the prolific Instagrammers being driven to distraction by social media; being trained to thirst for the new and the fresh. Look at all of the hipster developers who hopscotch from stack to stack because the only good is the new. Am I all that different?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*XxufJ1NStkY6mcvN.jpg" /><figcaption>Machine Learning — 2015 — Installation view, Galerie Speckstrasse, Gängeviertel (Hamburg)</figcaption></figure><p>You could be forgiven for thinking that I am romanticising too much when I say that coding as a form of sport is actually the thing that I love the most: The challenges of unifying an idea with algorithms, of designing architectures, of deploying code to hardware. I love seeing things arise, “Die Entstehung der Dinge” as some of Quasar’s German staff in Hamburg would say. I love building tools to make these things, but this isn’t where the Quasar Framework enters my story — not yet.</p><h3>The Adventure Begins</h3><p>In hindsight, I can’t really say that my life with open-source started on accident, but it wasn’t intentional either. It all began one cursed Monday about ten years ago, when I came back from vacation to discover that the intern had managed to infest my Windows work laptop with what seemed like every virus out there at the time. It wouldn’t even boot! The problem was that I had some files that absolutely had to go to the printer — that afternoon.</p><p>I remembered that a good friend had passed me a Knoppix live-cd months earlier. I was always hesitant to use Linux, because my training in the 1990s as a graphic designer had forced my hand with regard to software “choices” for 2D and 3D work. But this was an emergency, and I was shocked at how utterly simple it was for me to use Linux and dig into the Windows folder structure. In fact, I was literally in awe of the power I had over Windows: the user password didn’t matter…</p><p>Upon returning from the print-shop, I actually installed Knoppix and then Gimp because I couldn’t find the Windows DVDs. It sucked really hard, but I sensed the challenge and had heard about this thing called imagemagick… Soon I transitioned from Knoppix to Ubuntu, from Debian to Raspian, from Mint to Arch, from Kali to Parrot etc. I learned to use GIMP, Blender, Inkscape, graphicsmagick, ffmpeg, sox, ssh, netcat, rysnc and even bash. I came to learn what file headers were, what the Magic SysRq key was, how to flip the framebuffer and how to pipe.</p><p>My time with Linux was also peppered with moments of deep frustration — like when the interrupted system upgrade bricked the PC because someone in the flat tripped the circuit breaker, or the crushing realisation of losing one specific strong passkey, the one that I would have used to recover those 300 bitcoins from 2010. And yet, there was never an experience I cherished more than getting things to work the way I planned.</p><h3>Levelling Up</h3><p>Along this mostly stony and unfortunately repetitive path-of-most-resistance, I learned four lessons that are so important and applicable to everyday life &amp;&amp; programming, that I am going to segue for a moment and get preachy:</p><pre>1. Know what to call the thing being dealt with.<br>2. If it can&#39;t be understood, it shouldn&#39;t be used.<br>3. Track progress and write documentation.<br>4. Never steal ideas, tools or other people&#39;s time.</pre><ol><li>If I am incapable of describing what it is I am talking about, not only will I never be able to communicate it, but can I even be sure I understand it? Will I know that I have found what I have been searching for? Will I be able to report the crux of the matter as an issue so that others can understand me? This truism is even more applicable when looked at from a systems-design perspective: Design the data first, because there are no mutations without proper invocations! Getting this locked-down from the beginning will <strong>make the system more resilient and legible</strong>.</li><li>Being able to fix things when they break is not the only reason to understand the entire ecosystem of the thing you are working on. Like the old saying goes: “If all you have is a hammer, everything looks like a nail.” Modern software development is an extremely delicate and fragile ecosystem composed of development environments, versioned interdependent transpilers, renderers, builders and target platforms. Even though Quasar takes much of the pressure off of programmers, it does not change the way TCP, HTML, CSS, JS and JSON work. Having a mastery of the fundamentals (including reading the SPECs) literally <strong>changes problems into creative opportunities</strong>.</li><li>For me, writing has always been a tool to achieve understanding. I give myself a task, and through the process of writing about it, I come to understand it better. Some people (especially the Typescript gurus) say that great code is self-documenting, and if this is true, then the best documentation of code is its evolution. This is what git repositories give you for free — an entire history of all changes “published” to the repository. When combined with the iterative documentation of a semver-based API and its functionally reactive classes’ properties, it becomes easy to talk about the project in its current state. Just remember: <strong>without a history, nothing ever happened</strong>.</li><li>Using cracked software and stolen fonts for creative work always felt dirty, but it was what everyone else at the university was doing. We told ourselves that it was ok, because we were learning. After a decade of working only on Linux systems and collaborating on open source, I have little sympathy for software thieves and prefer not to work with people who steal software. Especially as developers we have to serve as role-models for the rest of humanity. Even though I work on a Mac system, I only use software for which I have a viable license and I prefer to use non-proprietary software whenever possible. Be excellent and militant in this regard, because everyone in the open-source universe should be honoured to <strong>give and receive this mutual self-respect.</strong></li></ol><h3>The Black Hole</h3><p>Technically, “quasar” is a word for the collection of a century’s-worth of observations about the luminous secretion of energy around the super-massive black-holes at the centre of many galaxies. In the Milky-Way, we call that super-massive centre (maybe someday soon a quasar) Sagittarius A. In the javascript ecosystem, we call it node_modules.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/990/0*Wwj_YectPQaW5aFj.png" /><figcaption>Image memed by Reddit User <a href="https://www.reddit.com/user/xaxaxa_trick">xaxaxa_trick</a></figcaption></figure><p>Before I discovered Vue.js and the Quasar Framework, my software projects were generally hobbled together from snippets I had collected along the way and my repositories were heavier than node_modules. I never really found a framework that I immediately stuck with, and I tried more than a few. Don’t get me wrong, I did make some exciting art installations and archives, but what I had done could never be called “best-practice” because it felt like I was always learning something new. As long as it worked for me then I was happy. I can’t count the number of times I told people: “You just have to use the latest Chrome browser.” Looking back and in comparison with how I work today, the pessimist in me feels that most of what I had done was really a collection of edge-cases glued together by stack-overflow answers plopped into a nested folders copied from found repositories…</p><h3>Less is More</h3><p>One day I was looking for a way to efficiently build an app for a side-project, and I decided to take Quasar for ride. It sounded like an “<a href="https://en.wiktionary.org/wiki/eierlegende_Wollmilchsau">eierlegende Wollmilchsau</a>” — the kind of thing that was too good to be true and served too many purposes. Much of my education as an artist and designer trained me to trim the unimportant and focus on the central issue. But after thinking about it, even for its broad scope, Quasar would let me write less code and be more productive…</p><p>I was shocked when I built my first test project with Quasar. For one, I really wasn’t expecting the browser to refresh as I made (non-exceptioning) changes to the code. It really didn’t seem like it should be possible to build Cordova, Electron apps and a Website from the same code base. That quickly? Material design compliant? The build process finished already? Um… ok. I was seriously impressed. (Months later I would write an official article about this called <a href="https://medium.com/quasar-framework/the-quasar-method-e19daf9abb5f">The Quasar Method</a>.)</p><p>If you are like me, you generally check out the readme, make sure you can live with the license and then just install the thing and see what happens. When you run into trouble, then you start reading the manual. The thing was, I didn’t really run into trouble with Quasar.</p><h3>¯\_(ツ)_/¯</h3><p>I merely used the online guide to discover all of the things that the Quasar Framework brought to the table. And there is a lot of great stuff. A LOT. So much that it doesn’t even all fit on one table… I started building that side project with it, and in so doing I discovered the Discord community, because at a certain point in serious (side) projects it is just a good idea to ask other people how they solved their issues and compare notes. The competence and friendly nature of the community on Discord seemed like a fairy tale — and I was hooked.</p><h3>The Genie’s Toll</h3><p>As with anyone granted three wishes, I immediately began dreaming about all of the things I could do with this framework. Native apps with access to the file system and the ability to call system binaries. Not having to handcraft multiple versions of the same app in order to distribute to both the mobile and desktop app stores. Quick and dirty control systems for hardware projects. Electron-based encryption-key generators. Massive networks of connected apps sharing a distributed P2P filesystem and database…</p><p>Somebody had spent a lot of time building Quasar according to the very principles that I live my life by — and the feeling of empowerment was intoxicating. Soon I found that I was answering almost as many questions on the Discord server as I was asking. In the process I slowly got to know that “somebody” behind the Quasar Framework. Razvan Stoenescu — a programmer that belongs to that rare and specific class of people who is never lazy — in fact he is THE model of programming diligence.</p><p>Over the months I became more and more acquainted with the framework — and witnessed the infectious fervour with which the git-updates bot on Discord was posting messages about Razvan. He. Was. Always. Working. I also discovered on the Discord channels and in the forum that there were a few types of questions that were asked repeatedly. Questions about <strong>testing</strong>, about <strong>icon sizes</strong>, about <strong>typescript</strong>, about ways to use <strong>Sketch</strong> and even how to follow accessibility standards like <strong>a11y</strong>. Questions that needed to be addressed because they were questions that bothered me too…</p><h3>+1 Pencil of Wisdom</h3><p>One day I discovered a tiny little icon of a pencil at the upper right hand corner of one of the doc pages. I clicked it and was teleported to an editable fork of the page I was reading — and suddenly saw a spelling mistake. I changed what had bothered me, committed it and made a PR. It was really so utterly easy that it became a little infectious. I started seeing little mistakes everywhere, and then I sat myself down and went through all of the doc pages and made a big PR from the comfort of my IDE. This is an exercise I wholly recommend, because not only did I help the community, I also learned a great deal about Quasar’s inner workings.</p><p>At some point I suggested an improvement to the language of the Patreon page, the landing page of the website, the wording of some CLI messages. And then Razvan and I discussed starting a <a href="https://medium.com/quasar-framework">blog at Medium</a>. I made a proposal for a <a href="https://github.com/quasarframework/quasar-testing">testing mode of quasar-cli</a> and a cross-platform webpack plugin as a <a href="https://github.com/quasarframework/quasar-icon-factory">factory for creating all of the icon types</a> ever needed by Quasar artefacts. After some initial guidance I started working on these projects, and their releases are now part of the roadmap to Quasar 1.0. We began having strategic meetings, finding technical partners and discussing who to invite to our staff and what tasks we should give them…</p><blockquote>People who stand out on the Discord channel are those who are not only helpful and friendly, but also creative problem solvers with both a drive to do things right the first time and perseverance to see things through. Having a few successful pull-requests is also a great way to show commitment and awareness of what makes Quasar unique.</blockquote><h3>Holding Pattern</h3><p>Every day is different, but there are similarities. Today, for example, I sent Razvan the weekly reminder of things on my list that I need him to take care of. I helped someone in our Patreon chat understand why a specific package is installed by quasar-cli even though we don’t consume it directly. I reviewed the structural composition of a proposal for our new issue-reporter. I solved a tricky layout problem using SVG markup in CSS using clip-path: polygon(). I gave specific advice to one of our technical partners about collecting a Github authentication token. I answered a question about licensing in one of our repositories. I iterated on some logo and font proposals for our upcoming relaunch. And I wrote this article about how I joined the Quasar team.</p><p>It may be obvious to you, dear reader, that I haven’t the time to work on any of my old side-projects anymore. I want Quasar to be perfect before I do any of them. They’ll still be around. Even though I don’t have as much time for side-projects as I would like, when 1.0 stabilises I expect that I will be getting back into more creative things. Like putting together a 2-way binding of Sketch master files with Quasar…</p><h3>Happily Ever After</h3><p>If you are still interested in joining us after reading my story, if you feel qualified to get involved and you truly love open source software — please get in touch. We are specifically looking for contributors to assume task-ownership in the following working groups: Testing, Continuous Integration, Art Department and Media Outreach.</p><p>If you want to find out more about Quasar, please consider:</p><ul><li>GITHUB: <a href="https://github.com/quasarframework/quasar">https://github.com/quasarframework/quasar</a></li><li>THE DOCS: <a href="https://quasar-framework.org/">https://quasar-framework.org/</a></li><li>DISCORD: <a href="http://chat.quasar-framework.org/">http://chat.quasar-framework.org/</a></li><li>FORUM: <a href="https://forum.quasar-framework.org/">https://forum.quasar-framework.org/</a></li></ul><p><a href="https://steemit.com/quasarframework/@nothingismagick/how-i-joined-the-quasar-framework-team-and-why-you-should-too">This article was originally published on STEEM.</a> If you are a STEEM user, please <a href="https://steemconnect.com/sign/account-witness-vote?witness=utopian-io&amp;approve=1">Vote Utopian.io for witness!</a> They are using Quasar for the next version of their Website!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d0671d014193" width="1" height="1" alt=""><hr><p><a href="https://medium.com/quasar-framework/how-i-joined-the-quasar-framework-team-d0671d014193">How I Joined the Quasar Framework Team</a> was originally published in <a href="https://medium.com/quasar-framework">Quasar Framework</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Quasar — In Real Life: #003 (Keyzy.io)]]></title>
            <link>https://medium.com/quasar-framework/quasar-in-real-life-003-keyzy-io-a56494c8f20c?source=rss-89913d87cbe6------2</link>
            <guid isPermaLink="false">https://medium.com/p/a56494c8f20c</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[vuejs]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[iot]]></category>
            <category><![CDATA[quasarframework]]></category>
            <dc:creator><![CDATA[Daniel Thompson-Yvetot]]></dc:creator>
            <pubDate>Mon, 06 Aug 2018 07:01:02 GMT</pubDate>
            <atom:updated>2018-08-06T07:01:02.149Z</atom:updated>
            <content:encoded><![CDATA[<h4>In this series of mini-articles, developers using the Quasar Framework explain their motivations for and use-cases of some really awesome thing that they have done with Quasar.</h4><h3>Case Study</h3><p><strong>WHO</strong>: <a href="http://www.keyzy.io/">Keyzy, LLC</a><br><strong>WHAT</strong>: Keyzy is a software / IoT license-manager in the cloud<br><strong>HOW</strong>: Quasar Framework frontend interface to software</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5xw6a5CGeQt8LC2H7ZYY5Q.png" /></figure><blockquote>We call Keyzy the “painless license manager”. It generates, deposits and activates licenses for software and IoT products. We enable this license data to be integrated with marketing tools and with e-commerce stores as well — in fact Keyzy can be used with any software. Even with web apps (like Sendy for example).</blockquote><blockquote>As an example, a software / IoT company that needs to manage many licensed artifacts can use Keyzy for their big blow-out sale to automatically send marketing messages with an integrated licensing solution — almost without writing any code. They just need to include our easy-to-use client library for C++ (other languages will be supported too).</blockquote><blockquote>In order to help our customers manage their products, we needed a single page application for the administration interface. We determined that our front-end interface must:<br>- make it straightforward to manage the licenses<br>- be dead-simple to configure<br>- have a variety of well-tested components<br>- look good while getting out of the user’s way</blockquote><blockquote>It was hard to find a framework that delivered all of these requirements, but then we discovered Quasar. Our devs love to build with this Vue.js based system, especially because its components are extremely solid, trivial to combine and have a modern look: All of the inputs, check boxes, combos and others are quick to style and position because of its Flexbox CSS solution.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RwLODzk5jPa-fLrLr0RyVA.png" /></figure><blockquote>Maybe I forgot to write here that <strong>Quasar Framework is very easy to use</strong>. Its CLI makes scaffolding, linting, building and extending very easy. Its dev-build process uses Webpack that you can even extend, and its live-reload really speeds up development iterations. Normally, we would need to spend days just to start a simple project with all of these features. By using Quasar, this super boring job doesn’t even take 5 minutes (and always gets it technically perfect!). It looks stylish and great even with the default settings. You don’t have to be a designer or have a designer to have a decent frontend from the very beginning of your project. Quasar helps you with that. It looks NEW and it’s multi-platform. Razvan, his team and the entire community are doing a very good job, we really appreciate it.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/100/1*u8eO3Ou8dji69i46uKZ45A.png" /></figure><p>If you want to find out more about the Quasar-Framework, please consider:</p><ul><li>GITHUB: <a href="https://github.com/quasarframework/quasar">https://github.com/quasarframework/quasar</a></li><li>THE DOCS: <a href="https://quasar-framework.org/">https://quasar-framework.org/</a></li><li>DISCORD: <a href="http://chat.quasar-framework.org/">http://chat.quasar-framework.org/</a></li><li>FORUM: <a href="https://forum.quasar-framework.org/">https://forum.quasar-framework.org/</a></li></ul><p><a href="https://medium.com/u/89913d87cbe6">nothingismagick</a> is part of the Quasar Framework team.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a56494c8f20c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/quasar-framework/quasar-in-real-life-003-keyzy-io-a56494c8f20c">Quasar — In Real Life: #003 (Keyzy.io)</a> was originally published in <a href="https://medium.com/quasar-framework">Quasar Framework</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>