<?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 Julian Martinez on Medium]]></title>
        <description><![CDATA[Stories by Julian Martinez on Medium]]></description>
        <link>https://medium.com/@julianmartinez?source=rss-2108ba7b4f2f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*O5SCFmbNxmWaFVCX.jpg</url>
            <title>Stories by Julian Martinez on Medium</title>
            <link>https://medium.com/@julianmartinez?source=rss-2108ba7b4f2f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 04:05:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@julianmartinez/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[Releasing Our Code]]></title>
            <link>https://medium.com/currentcoin/releasing-our-code-6fa22aa18c65?source=rss-2108ba7b4f2f------2</link>
            <guid isPermaLink="false">https://medium.com/p/6fa22aa18c65</guid>
            <dc:creator><![CDATA[Julian Martinez]]></dc:creator>
            <pubDate>Tue, 13 Jul 2021 23:32:40 GMT</pubDate>
            <atom:updated>2021-07-22T22:43:29.754Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>E-commerce using MetaMask, with Ethereum and CurrentCoin</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HwpbwJTCsVy1NEOzkpXL2w.png" /><figcaption>UI shown.</figcaption></figure><p>CurrentCoin’s goal is to make digital servces that use crypto fast, affordable, and accessible for all.</p><p>With that in mind, we’ve open sourced our first code repo in a long time: an ecommerce marketplace integrated with MetaMask, where you can pay for services using CurrentCoin and Ethereum.</p><p>We’re distributing this to everyone and anyone who wants to use it, for use in their own app.</p><p><a href="https://github.com/CurrentCoin/ecommerce-react-metamask">CurrentCoin/ecommerce-react-metamask</a></p><p>You can see it live here.</p><p><a href="https://www.ccoin.live/">https://www.ccoin.live/</a></p><p>We plan to create and release the code for more practical projects like this, in order to create value for the community and more use cases for CurrentCoin.</p><p><strong>Our Code</strong></p><p>The code linked above is for an ecommerce site integrated with MetaMask.</p><p>This means that, if you have the MetaMask crypto wallet installed, and you have crypto in it, you can use this app to pay for services.</p><p>We have 2 sample products for sale, in addition to a working contact form. This code really works, so please don’t confirm a purchase unless you want to buy them.</p><p>If you want to use this for your own purposes, you can swap out the pictures, addresses, and text, to advertise and sell anything you want using Ethereum (ETH) or CurrentCoin (CUR).</p><p>Major libraries used are: axios, Google’s Material UI, Web3, ethers, and react-router-dom.</p><p>You can run this git cloning the repo, then typing ‘yarn install’ and ‘yarn start’.</p><p>Do that, and you can have your own local e-commerce site running too, with ready payment methods available through MetaMask.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6fa22aa18c65" width="1" height="1" alt=""><hr><p><a href="https://medium.com/currentcoin/releasing-our-code-6fa22aa18c65">Releasing Our Code</a> was originally published in <a href="https://medium.com/currentcoin">CurrentCoin</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CurrentCoin’s Tokenomics]]></title>
            <link>https://medium.com/currentcoin/currentcoins-tokenomics-eadc55b0ac43?source=rss-2108ba7b4f2f------2</link>
            <guid isPermaLink="false">https://medium.com/p/eadc55b0ac43</guid>
            <dc:creator><![CDATA[Julian Martinez]]></dc:creator>
            <pubDate>Tue, 13 Jul 2021 06:41:14 GMT</pubDate>
            <atom:updated>2021-07-13T06:41:14.665Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*YHAYr0GZXajBBPp2waWh0w.jpeg" /></figure><p>We wanted to explain our tokenomics for our users, and our token distribution.</p><p>CurrentCoin is an ERC-20 coin on the Ethereum network.</p><p>All CurrentCoin tokens were created and distributed during our ICO in late 2017.</p><p>100 billion coins were minted, upon instantiation of our smart contract, which you can see here.</p><p>0x347a29ea126a746c70e1ead570fddf438e66231a</p><p>Of those, approximately 15 billion were distributed at the time of the ICO.</p><p>Today, the bulk of CurrentCoin’s tokens, 85 billion, resides with its creators. They are in cold storage and safely secured.</p><p>Most coins in circulation today are being traded on the BitMart exchange.</p><p><a href="https://www.bitmart.com/">https://www.bitmart.com/</a></p><p>You can also use CurrentCoin to purchase online services, as shown below.</p><p><a href="https://www.ccoin.live/">https://www.ccoin.live/</a></p><p>You can see CurrentCoin transactions through Etherscan, Ethereum’s blockchain explorer, where every transaction on the Ethereum network is recorded and reported.</p><p><a href="https://etherscan.io/">https://etherscan.io/</a></p><p>You can also track information about CurrentCoin on the page where our information is listed on CoinGecko.</p><p><a href="https://www.coingecko.com/en/coins/currentcoin">https://www.coingecko.com/en/coins/currentcoin</a></p><p>For answers beyond this, we would refer you to our blog posts, or to Etherscan again, for transaction activity deep dives.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eadc55b0ac43" width="1" height="1" alt=""><hr><p><a href="https://medium.com/currentcoin/currentcoins-tokenomics-eadc55b0ac43">CurrentCoin’s Tokenomics</a> was originally published in <a href="https://medium.com/currentcoin">CurrentCoin</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[JavaScript GET Requests: A How-To]]></title>
            <link>https://medium.com/@julianmartinez/javascript-get-requests-a-how-to-abecd48e7bb7?source=rss-2108ba7b4f2f------2</link>
            <guid isPermaLink="false">https://medium.com/p/abecd48e7bb7</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[github]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[api]]></category>
            <dc:creator><![CDATA[Julian Martinez]]></dc:creator>
            <pubDate>Mon, 08 Jun 2020 18:46:25 GMT</pubDate>
            <atom:updated>2022-07-23T16:37:17.536Z</atom:updated>
            <content:encoded><![CDATA[<h3>GET Requests Using JavaScript</h3><p>Want to make a GET request in your JavaScript code, to display some data or information from an API? Here’s how.</p><p>Look at the webpage below. It usually takes a second or so to load, because it’s fetching the data from an API. I didn’t hand-code any of that — it’s all coming from an API.</p><p><a href="https://javascriptpage.s3.amazonaws.com/javascript-get-request.html">https://javascriptpage.s3.amazonaws.com/javascript-get-request.html</a></p><p>This is how you write JavaScript GET requests in JavaScript to make that happen.</p><p>Let’s start with the API. To make a GET request, you have to request it from an API, which stands for Application Programming Interface. It’s an endpoint — a URL — you visit to get something in return.</p><p>Here’s we’re using an API called <a href="https://domainsdb.info/">DomainsDB.info</a>. I decided to use the search term ‘medium’ (which you can see next to ‘domain’ below), to retrieve all webpages that have medium in their name.</p><p><a href="https://api.domainsdb.info/v1/domains/search?domain=medium&amp;zone=com">https://api.domainsdb.info/v1/domains/search?domain=medium&amp;zone=com</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cO9Grgz4xljTZFRzzkCB5A.png" /></figure><p>You can see the API returns just by visiting it in your browser. Click the link; you’ll see text, as in the above screenshot (pretty printed using an extension in my browser).</p><p>It doesn’t look very good and is hard to read, since it’s just text, without styling — that is, without nice-looking HTML and CSS to make it look good.</p><p>This is a common API use case: they dispense plain text. It’s up to you to do the UI work for presentation.</p><p>This is also real-time information, so unlike something that’s hard coded, it won’t go out of date. In other words, this information could change, as the API gets new information.</p><p>Here’s what it looks like, after I style it and insert it in a nice format into my page (showing you the zoomed-out view, so you can see how much information is returned).</p><p><a href="https://javascriptpage.s3.amazonaws.com/javascript-get-request-rows.html">https://javascriptpage.s3.amazonaws.com/javascript-get-request-rows.html</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eL_3azFlAimVXlEWwuFVFQ.png" /></figure><p>The JavaScript code to do this is shown below.</p><pre>const url=’<a href="https://api.domainsdb.info/v1/domains/search?domain=medium&amp;zone=com&#39;">https://api.domainsdb.info/v1/domains/search?domain=medium&amp;zone=com&#39;</a><br> const proxy = ‘<a href="https://cors-anywhere.herokuapp.com/&#39;">https://cors-anywhere.herokuapp.com/&#39;</a><br> fetch(proxy + url)<br> .then(blob =&gt; blob.json())<br> .then(data =&gt; {<br> let items=[];<br> data.domains.map(element =&gt; items.push(element.domain));<br> const lines=data.domains.map((element) =&gt; “&lt;p&gt;”+ element.domain + “&lt;/p&gt;”);<br>...</pre><p>You might wonder why there’s a proxy in there.</p><p>In this case, it’s because the API call wouldn’t work without it. Removing it would result in a <a href="https://stackoverflow.com/questions/43262121/trying-to-use-fetch-and-pass-in-mode-no-cors">CORS error</a>, which is an entirely different ball of wax (see the <a href="https://stackoverflow.com/questions/43262121/trying-to-use-fetch-and-pass-in-mode-no-cors">link</a> for an in-depth explanation). But basically, browsers block front-end code from accessing resources on other servers by default. You use a proxy to get around that error.</p><p>The ‘map’ code above takes the response from the API, and uses it to create an expression that’s ready to be used — a string of &lt;p&gt;<em>text inside…</em>&lt;/p&gt; tags that can be dropped in anywhere in an html page.</p><p>You’ll also notice I used the fetch method. You can use either fetch or xhr (<a href="https://developers.google.com/web/updates/2015/03/introduction-to-fetch#xmlhttprequest">XMLHttpRequest</a>) but I find fetch a little easier to write and reason about.</p><p>This code gets the data. Now that you have the data, you have to show it.</p><p>Here’s the code that attaches it to my specially styled div for this.</p><pre>document.querySelector(“.box”).innerHTML = lines.join(‘’);<br> })</pre><p>Here’s the div where that goes, with the class “box” (how the querySelector identifies it), after I’ve fetched it.</p><pre>&lt;div class=”box”&gt;<br>&lt;/div&gt;</pre><p>Here’s what the code looks like in a one page .html file.</p><p><a href="https://gist.github.com/julianeon/05b054b258b6875e4d6f4c3e0920e289">https://gist.github.com/julianeon/05b054b258b6875e4d6f4c3e0920e289</a></p><p>You can download the file, open it in a code editor, rename it to .html, make changes to it, and see how that changes the page when you re-open the same file in your browser (which will render like a normal webpage).</p><p>You can see the html page live here.</p><p><a href="https://javascriptpage.s3.amazonaws.com/javascript-get-request-rows.html">https://javascriptpage.s3.amazonaws.com/javascript-get-request-rows.html</a></p><p>Here’s a slightly different version, that instead of searching for ‘medium’ every time, allows you to search for specific text through an input box. When you click the button, it runs the search.</p><p><a href="https://javascriptpage.s3.amazonaws.com/javascript-get-request-submit.html">https://javascriptpage.s3.amazonaws.com/javascript-get-request-submit.html</a></p><p>There’s some CSS in there too to make all the colors, and while that’s in the code for you to examine, I won’t go into it here because it’s not essential to the lesson. You could remove all of it and it wouldn’t change the core API/get request.content.</p><p>In fact, just for comparison’s sake, here’s a much simpler version, that just shows black on white text.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/912/1*fPrZlwjDC0eTf4PjFg1m4Q.png" /><figcaption>Same content, different styling.</figcaption></figure><p><a href="https://javascriptpage.s3.amazonaws.com/javascript-get-request-rows-bw.html">https://javascriptpage.s3.amazonaws.com/javascript-get-request-rows-bw.html</a></p><p>So that’s how you do a GET request. It’s that simple! (Well, maybe not that simple.)</p><p>API requests can get much more complicated than this — a common use case would involve an API you have to authenticate against, for example — but this should get the idea across.</p><p>In other words, while the specifics may change, this is the general procedure; you can use GET requests and JavaScript to present information in all kinds of ways.</p><p>Try finding an API of your choice (see this <a href="https://github.com/public-apis/public-apis">list</a>) to experiment on your own. In no time you’ll be able to fill the webpage of your choice with API content, too.</p><p><em>My name is Julian Martinez and I’m a consultant and developer. You can also see a similar </em><a href="https://javascriptpage.com/javascript-get-request-example"><em>tutorial</em></a><em> on my </em><a href="https://javascriptpage.com/"><em>website</em></a><em>. To discuss a project, use my </em><a href="https://javascriptpage.com/about"><em>email</em></a><em> or </em><a href="https://www.reactever.com/contact"><em>contact form</em></a><em>.</em></p><p><em>For more content like this, follow me on </em><a href="https://twitter.com/julianeon"><em>Twitter</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=abecd48e7bb7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Creating a Pitch Deck App: A Side-by-Side, React vs. Svelte, Comparison]]></title>
            <link>https://medium.com/swlh/creating-a-pitch-deck-app-a-side-by-side-react-vs-svelte-comparison-29094f19fd46?source=rss-2108ba7b4f2f------2</link>
            <guid isPermaLink="false">https://medium.com/p/29094f19fd46</guid>
            <category><![CDATA[svelte]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Julian Martinez]]></dc:creator>
            <pubDate>Mon, 18 May 2020 04:13:32 GMT</pubDate>
            <atom:updated>2020-05-31T20:35:27.923Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g7hZXhkJZeXQRI9gy9CEtA.png" /><figcaption>Photo by <a href="https://www.pexels.com/@prismattco?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels">Matheus Viana</a> from <a href="https://www.pexels.com/photo/human-hands-illustrations-3354675/?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels">Pexels</a></figcaption></figure><h3>React vs. Svelte: A Side-by-Side Pitch Deck App Comparison</h3><p>I decided to compare React and Svelte, two JavaScript frameworks, to show the differences between them. To do that, I created a pitch deck app using both frameworks, making them as identical as possible.</p><p>GitHub: <a href="https://github.com/julianeon/pitch-deck-react">React code</a> / <a href="https://github.com/julianeon/pitch-deck-svelte">Svelte code</a></p><p>In the first corner, we have React. React is the dominant JavaScript framework today, holding tight to its (very commanding) lead. While React, created by FaceBook, has had competitors, it’s the JS framework you’re most likely to encounter today at startups, and frequently in job postings.</p><p>In the other corner, we have Svelte. Svelte is an up-and-comer with nowhere near React’s market share, but it’s just getting started. Created by Rich Harris, a New York Times employee, it offers something different: a simplified structure and an emphasis on run-time performance, including things like fast load times.</p><p>They can both manage state, and the app used to compare them basically has one webpage which changes state to the next webpage when you click on it, and changes the style state from fullscreen to letterboxed when you click a button, on the desktop.</p><p>The app doesn’t have a router, because I thought that would’ve obscured the differences overly much. The routing is usually done by libraries, and I wanted to stick to ‘vanilla’ React and Svelte.</p><p>This is the Svelte version, after being deployed to AWS S3.</p><p><a href="http://pitch-deck-svelte.s3-website-us-east-1.amazonaws.com/">http://pitch-deck-svelte.s3-website-us-east-1.amazonaws.com/</a></p><p>This is the React version, after being deployed to AWS S3.</p><p><a href="http://pitch-deck-react.s3-website-us-east-1.amazonaws.com/">http://pitch-deck-react.s3-website-us-east-1.amazonaws.com/</a></p><p>The pitch deck is for a fictional stock photography company called Eye Captain. I created 9 pages, or cards, enough to get the general idea across. While you should feel free to copy this to make your own pitch deck, this is not a real pitch deck, which should only be attempted by professionals (kidding).</p><p>From there user’s perspective, there’s 2 things you can do with the UI. In addition to clicking through the cards sequentially, you can also click on a button to change their formatting.</p><p>In desktop mode, it can either be letterboxed — really, surrounded by blank black space — or fullscreen — meaning the card, and its blue background, stretches to the corners of the screen.</p><p>In mobile mode, there’s less space, so you can only view the cards there in fullscreen mode.</p><p>When you click on a card, it advances the card index plus one, and that index is used to find the next card (unless you’re at the last card, in which case it loops back to the first one). The card index and the styles affecting the cards are all stored within the framework’s state.</p><p>One of the more instructive parts is seeing how React and Svelte separately manage this state.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/464/1*jcrWQfWIghnoM4A4VEQqQA.png" /><figcaption>React on the left, Svelte on the right.</figcaption></figure><p>See the <a href="https://github.com/julianeon">code</a> for details.</p><p><strong>Structure</strong></p><p>I tried to lay out the two apps to be as identical as possible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*72Iaa2nJNjwkiYU6iPDS9g.png" /><figcaption>React on the left, Svelte on the right.</figcaption></figure><p>Both of them have a main app component where the text is defined, and passed as an argument to the component that actually implements the page, called Deck in both apps. In React, it’s Deck.js, and in Svelte, it’s Deck.svelte. When I talk about the ‘app’ here I mostly mean Deck.js/Deck.svelte.</p><p>I’ll start with Svelte.</p><p>In Svelte, at the top, as I’ve written it, you have some script definitions.</p><p>Below that, you have the CSS.</p><p>At the bottom, you have the page content, plus some JavaScript.</p><p>In the case of the React app, it’s a standard React implementation, using hooks.</p><p>Even though the React one has a short code section, it gives you a good sense of the idiosyncrasies you get accustomed to in React, the React way of doing things with camel-cased CSS properties and setState, for example.</p><p>State is important in both versions. To quote the React docs<em>: State is reserved only for interactivity, that is, data that changes over time.</em></p><p>I think of state as the program’s ‘memory’ (note: that’s my personal mental shortcut, don’t say this in a job interview). Just like you use your memory to remember when something has changed locations so you can act on the difference, your program does that too.</p><p>One state variable is for the index.</p><p>It’s purpose is obvious: to show the card associated with that index number, and increment the number on a mouse click. In both programs, a function with the same name, advanceClick, moves the index forward by one, when you click on the screen (onClick in React, on:click in Svelte).</p><p>Another state variable is for, basically, ‘fullscreen’ or ‘not fullscreen’ — which is to say, desktop or mobile.</p><p>The variable is called display. When it’s true, on the desktop, you see the fullscreen version of the site. When it’s false, you see the mobile version. You flip between those versions by clicking on a button which toggles the value of display, with every click.</p><p>A media query checks to see if your screen is desktop or mobile sized. If it’s desktop, you can switch between fullscreen and letterboxed. If it’s mobile, you can only see the fullscreen version. Or, in other words: if you’re viewing this on a mobile phone, you’ll only see a plain click-scrolling app.</p><p>The live <a href="http://pitch-deck-svelte.s3-website-us-east-1.amazonaws.com/">Svelte</a> and <a href="http://pitch-deck-react.s3-website-us-east-1.amazonaws.com/">React</a> app are linked again here for convenience.</p><p><strong>Compare and Contrast</strong></p><p>For the most part, I’d describe myself as a React developer. This was my first time using Svelte, and to me this clearly showed the more intuitive JavaScript-ese of Svelte.</p><p>It seems like every framework promises to be “JavaScript-like,” but there’s no translation to the ‘real JavaScript’ with Svelte (as there is with React and JSX). It really is just JavaScript.</p><p>When looking at the two side by side, I find the Svelte version to be ‘cleaner’ and simpler to understand. I use React all the time and so find it natural to think in React, so for me to find Svelte more intuitive after one use is a pretty strong vote for the framework.</p><p>Svelte reads almost like textbook JavaScript, so if you’re used to React, you can pick up Svelte quickly. If you’re new to them both, the concepts you learn in Svelte will have analogues in React, so I’d still start there.</p><p><strong>When You Should Use Svelte vs. React</strong></p><p>I sometimes see tutorials that say something like, ‘Use the framework that’s best for your situation.’ I find this frustrating, because the question is only asked when that answer is unknown.</p><p>As an analogy, here’s a guide for getting into the medical school, university, or job of your dreams: whenever you are asked a question or face a choice about it, choose the best appropriate answer. Correctly applied, you’ll ace every test, interview, and academic honor, by always choosing the correct answer in context. But how is this useful? It’s just stating a kind of tautology: the right answer is by definition the right answer to the right question.</p><p>So, here is stronger, more useful advice.</p><p>Whenever you can use Svelte, use Svelte. When you can’t, use React.</p><p>You know what’s a common use case for Svelte — meaning a situation where you should use Svelte over React?</p><p>Blogs.</p><p>See this <a href="https://macwright.org/2020/05/10/spa-fatigue.html">article</a>, “Second Guessing the Modern Web,” by Tom MacWright, endorsed by none other than Dan Abramov.</p><h3>Dan Abramov on Twitter</h3><p>This hits the nail on the head. And is 100% matching our long term thinking. Client-side-only is not sustainable. We need to move more stuff to the server, but without sacrificing seamless composition of interactive pieces. https://t.co/O4LX8JacRo</p><p>The relevant part of the essay is this excerpt:</p><p><em>There is a sweet spot of React: in moderately interactive interfaces. Complex forms that require immediate feedback, UIs that need to move around and react instantly. That’s where it excels… The less interactive parts don’t benefit much from React.</em></p><p><em>There is a swath of use cases which would be hard without React and which aren’t complicated enough to push beyond React’s limits. But there are also a lot of problems for which I can’t see any concrete benefit to using React. Those are things like blogs, shopping-cart-websites, mostly-CRUD-and-forms-websites. For these things, all of the fancy optimizations are trying to get you closer to the performance you would’ve gotten if you just hadn’t used so much technology.</em></p><p><em>I can, for example, guarantee that this blog is faster than any Gatsby blog (and much love to the Gatsby team) because there is nothing that a React static site can do that will make it faster than a non-React static site.</em></p><p><strong>Time to Load: A Clear Winner</strong></p><p>For blogs, I think the average developer underestimates the advantage of speed. That’s your main priority! I personally have clicked on developer portfolio sites on my iPhone, only for it to essentially time out while waiting to load. You’re a developer, and the quality of your blog reflects on you. Don’t be that person with the slow site.</p><p>After I finished the React and Svelte versions, I deployed them both to S3. I decided to test them using the Audit feature in Chrome’s Developer Tools.</p><p>The Svelte result is this one.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/973/1*nBUqa6eKIjS1o6OP6c9jWA.png" /><figcaption>Chrome Developer Tools Audit result, Svelte.</figcaption></figure><p>The React result is that one.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/984/1*8FnJhASShPCA9Sr9FTfQHA.png" /><figcaption>Chrome Developer Tools Audit result, React.</figcaption></figure><p>Spoiler: the Svelte results are about twice as good.</p><p>In particular, look at that difference in time to interactive. It’s huge! The React one is more than twice as large — 3.7 seconds vs. 1.7 seconds.</p><p>If you can sidestep that - you should. This comparison app is dirt simple, but as it gets more complicated (like a real app), I’d expect that to creep up.</p><p>So, if you’re doing a blog from scratch, it’s easy: use Svelte.</p><p>If you have more interactivity than we would expect from your average blog, or have some special use case that is React specific, use React — but think carefully, if you don’t really need it.</p><p>Be willing to learn and use Svelte, because the speed difference is worth it.</p><p><em>My name is Julian Martinez and I’m a consultant and developer. You can also see this </em><a href="https://www.reactever.com/pitch-deck-react-svelte"><em>tutorial</em></a><em> on my </em><a href="https://www.reactever.com/"><em>website</em></a><em>. To discuss a project, use my </em><a href="https://www.reactever.com/contact"><em>contact form</em></a><em>.</em></p><p><em>For more content like this, follow me on </em><a href="https://twitter.com/julianeon"><em>Twitter</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=29094f19fd46" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/creating-a-pitch-deck-app-a-side-by-side-react-vs-svelte-comparison-29094f19fd46">Creating a Pitch Deck App: A Side-by-Side, React vs. Svelte, Comparison</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CurrentCoin is Now on IDAX]]></title>
            <link>https://medium.com/currentcoin/currentcoin-is-now-on-idax-84097741ff15?source=rss-2108ba7b4f2f------2</link>
            <guid isPermaLink="false">https://medium.com/p/84097741ff15</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <dc:creator><![CDATA[Julian Martinez]]></dc:creator>
            <pubDate>Wed, 27 Feb 2019 04:11:26 GMT</pubDate>
            <atom:updated>2019-02-27T04:11:26.761Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*lPtg136km8YBYvYR_7qd-w.jpeg" /></figure><p>CurrentCoin is pleased to announce that we are now listed on IDAX, a top 10 exchange by volume, averaging over 400 million dollars worth of transactions daily. You can now buy and sell CurrentCoin through their interface, one of the most intuitive we’ve used. This was the result of close coordination for several weeks, and a business trip to Shanghai.</p><p><a href="https://www.idax.pro/#/">https://www.idax.pro/#/</a></p><p>We’d like to thank everyone on the IDAX side who helped make this possible; they’ve become a major player in a very short time, and with their work ethic and incredible dedication to detail, we’re not surprised. As cryptocurrencies increase in visibility and importance, we expect IDAX will, too.</p><p>If you purchase CUR now, you’ll be eligible to participate in our ongoing promotion, for a limited time.</p><p><a href="https://idax.zendesk.com/hc/en-us/articles/360022940372-Celebrating-CUR-Launch-on-IDAX-Enjoy-10-000-000-CUR-">https://idax.zendesk.com/hc/en-us/articles/360022940372-Celebrating-CUR-Launch-on-IDAX-Enjoy-10-000-000-CUR-</a></p><p>You can read more about CurrentCoin in the IDAX knowledge base here:</p><p><a href="https://idax.zendesk.com/hc/en-us/articles/360021979131-CUR">https://idax.zendesk.com/hc/en-us/articles/360021979131-CUR</a></p><p>Finally, you can see our new video, explaining the concept behind CurrentCoin and our overall vision, at our YouTube Channel.</p><p><a href="https://www.youtube.com/watch?v=dkAEvke8Nt0">https://www.youtube.com/watch?v=dkAEvke8Nt0</a></p><p>We’ll keep developing CurrentCoin until we reach our goals, building value and code day by day, week by week, and year by year. We update our repos every single week, in service of our goal of fully integrated, CurrentCoin-using online marketplaces. We want CurrentCoin to stand for quick payments, great interfaces, and the transformative power of cryptocurrency itself.</p><p>To view our progress, see the rest of our channels and follow us across all our platforms, please see the link below:</p><p><a href="https://github.com/CurrentCoin/information">https://github.com/CurrentCoin/information</a></p><p>We’re working to make 2019 a milestone year for us.</p><p>Join us as we build a better world, together.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=84097741ff15" width="1" height="1" alt=""><hr><p><a href="https://medium.com/currentcoin/currentcoin-is-now-on-idax-84097741ff15">CurrentCoin is Now on IDAX</a> was originally published in <a href="https://medium.com/currentcoin">CurrentCoin</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Work: Today and Tomorrow]]></title>
            <link>https://medium.com/currentcoin/work-today-and-tomorrow-183f0d8fc92e?source=rss-2108ba7b4f2f------2</link>
            <guid isPermaLink="false">https://medium.com/p/183f0d8fc92e</guid>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[life]]></category>
            <dc:creator><![CDATA[Julian Martinez]]></dc:creator>
            <pubDate>Wed, 17 Oct 2018 00:11:10 GMT</pubDate>
            <atom:updated>2021-07-14T19:50:22.005Z</atom:updated>
            <content:encoded><![CDATA[<h3>Keep On Cooking</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZUx3YVwRBiCQu5PaYPEKIA.png" /></figure><p>In cooking as in life, you wait to serve the dish when it’s ready. Until then, you prepare.</p><p>CurrentCoin has a goal: to be listed on several exchanges. We’re working on this, and assembling the pieces that contribute to it.</p><p>First piece: emailing exchanges to make sure they know we’re here, to inform them of our plans.</p><p>Second piece: putting those plans into action, and creating viewable, actionable items that demonstrate those plans in action — and show our success in action.</p><p>Right now, that means a focus on coding.</p><p>Our marketplace isn’t long from being ready now, with items for sale.</p><p>We’re thinking about how we can stock our marketplace, and what will do well in the market.</p><p>Technically, we’re simultaneously working on getting all those pieces into place, and showing them to our potential partners.</p><p>We’re taking it one step at a time, but we’re getting there.</p><p>Because building things one step at a time, is how the greatest things ultimately get built.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*HdxXSFxnO88qbPwA668pGw.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=183f0d8fc92e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/currentcoin/work-today-and-tomorrow-183f0d8fc92e">Work: Today and Tomorrow</a> was originally published in <a href="https://medium.com/currentcoin">CurrentCoin</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Changing Landscape]]></title>
            <link>https://medium.com/currentcoin/on-the-move-a7a82770b436?source=rss-2108ba7b4f2f------2</link>
            <guid isPermaLink="false">https://medium.com/p/a7a82770b436</guid>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[bitcoin]]></category>
            <dc:creator><![CDATA[Julian Martinez]]></dc:creator>
            <pubDate>Tue, 14 Aug 2018 20:18:12 GMT</pubDate>
            <atom:updated>2021-07-14T19:48:08.514Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0D-NSFP3oWH68-HqbdvSbg.jpeg" /></figure><p>In the world of cryptocurrencies, the landscape changes quickly.</p><p>We’ve seen a number of famous cryptocurrencies slip in price. Part of that may be a correction by the market, a financial comment on earlier claims.</p><p>We’ve also seen a number of slip-ups and mistakes. It’s gotten to the point that cryptocurrencies entering nonsense markets have become a punchline.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/574/1*euCnCvRlVetIJ-Jdy284og.png" /></figure><p>Words need to be backed up by actions that support them. Projects have to make good on their claims.</p><p>To that end, here at CurrentCoin, we are working to build value through digital services, in the form of online marketplaces.</p><p>Our team is working behind the scenes to bring these marketplaces to you.</p><p>On the front end side, we’re starting to build those out using JavaScript and Node.js.</p><p>We’re also talking to partners about how we can bring CurrentCoin to market, and improve our standing among cryptocurrencies as a whole.</p><p>Main net work is continuing at the same time, to expand our capabilities.</p><p>Most of all, we want to say: We hear you.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*tE2TX5ulPH7AFIbOzlg8pA.png" /></figure><p>We know that it’s critical for CurrentCoin to go to market and gain traction. We’re working on it, one day at a time.</p><p>In the meantime, you can expect regular updates from us, and hard work, daily, until we reach our goals.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a7a82770b436" width="1" height="1" alt=""><hr><p><a href="https://medium.com/currentcoin/on-the-move-a7a82770b436">A Changing Landscape</a> was originally published in <a href="https://medium.com/currentcoin">CurrentCoin</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Creating Live Apps]]></title>
            <link>https://medium.com/currentcoin/creating-live-apps-d6a57e6393cd?source=rss-2108ba7b4f2f------2</link>
            <guid isPermaLink="false">https://medium.com/p/d6a57e6393cd</guid>
            <category><![CDATA[platform]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[ethereum]]></category>
            <dc:creator><![CDATA[Julian Martinez]]></dc:creator>
            <pubDate>Sat, 23 Jun 2018 01:48:10 GMT</pubDate>
            <atom:updated>2025-08-20T18:09:25.248Z</atom:updated>
            <content:encoded><![CDATA[<p>One quality we emphasize at CurrentCoin is making things real.</p><p>This is why we created our prototype, which you can try at <a href="http://www.currentcoincreate.com/">curentcoincreate.com</a>.</p><p>You can think of this as a preview of our platform, since it costs nothing to use and lets you try our apps in action.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jJsZw3z77poglWCTDb-WxQ.png" /></figure><p>The model is simple.</p><p>On our platform, you’ll be able to use CurrentCoin to enjoy fast, convenient, time-based digital services.</p><p>With the prototype, you can see a simulation of this, covering a range of applications: from informational websites to a chat tool to a simple game.</p><p>But you don’t have to take our word for it — you can try it out for yourself.</p><p>With a car, the best thing you can do is test drive it. We subscribe to the same philosophy; we’re doing everything we can to make the user experience a good one, but ultimately you have the final say.</p><p>Because who knows what you need, better than you do?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*PO5vYmfH1DDvbsOVMBJwgA.jpeg" /></figure><p>For a longer explanation, see the PDF we created below:</p><p><a href="http://docdro.id/LXyBdDy">http://docdro.id/LXyBdDy</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d6a57e6393cd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/currentcoin/creating-live-apps-d6a57e6393cd">Creating Live Apps</a> was originally published in <a href="https://medium.com/currentcoin">CurrentCoin</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Big Cryptocurrency Picture]]></title>
            <link>https://medium.com/currentcoin/the-big-cryptocurrency-picture-1e32c1e86a73?source=rss-2108ba7b4f2f------2</link>
            <guid isPermaLink="false">https://medium.com/p/1e32c1e86a73</guid>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[bitcoin]]></category>
            <dc:creator><![CDATA[Julian Martinez]]></dc:creator>
            <pubDate>Thu, 21 Jun 2018 04:43:48 GMT</pubDate>
            <atom:updated>2025-08-20T18:12:09.732Z</atom:updated>
            <content:encoded><![CDATA[<p>People have asked us how we see ourselves fitting within the universe of cryptocurrencies. It’s a big world out there, and we’ve got to find our place.</p><p>There are some names that everyone recognizes, that have earned their place in the history of cryptocurrency.</p><p>While there are different ways to make the cut, we can start with three, the top of the charts by valuation: Bitcoin, Ethereum, and Ripple.</p><p>You use Bitcoin (currency: Bitcoin) as a store of value, as digital gold. Like gold, it is known for having value, and people trust it as a store of wealth.</p><p>You use Ethereum (currency: Ether) for smart contracts, for the functionality and the platform it provides. The developers and the foundation behind it are top-notch, and its reputation reflects this.</p><p>You use Ripple (currency: XRP) for international payments, and for very fast transaction times. Ripple as a company focuses on cross-border payments, and those advantages all play to its strengths.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*egJLEAIT45_71QBkY0jEmw.png" /><figcaption>How Ripple presents itself (taken from the XRP homepage).</figcaption></figure><p>CurrentCoin is the connector. We give you digital services that are available across multiple cryptocurrencies.</p><p>You can use any of the above and get your website, or your office software, or your game — the template of your choice — using CurrentCoin.</p><p>We’re committed to making a difference. Our community and news functions will bring people together and teach them how to work with cryptocurrencies, using our digital services to enhance their education.</p><p>In this new world of cryptocurrencies, there’s space for many services, and service providers. The established players have already made a name for themselves; now it’s our turn.</p><p>We believe in CurrentCoin based on the strength of the products we make and the community we attract. Join us as we work to make a name for ourselves.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*C3N76A248vZFVrrstJuD3g.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1e32c1e86a73" width="1" height="1" alt=""><hr><p><a href="https://medium.com/currentcoin/the-big-cryptocurrency-picture-1e32c1e86a73">The Big Cryptocurrency Picture</a> was originally published in <a href="https://medium.com/currentcoin">CurrentCoin</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CurrentCoin: Press Release]]></title>
            <link>https://medium.com/currentcoin/featured-in-the-news-b1ce636172a2?source=rss-2108ba7b4f2f------2</link>
            <guid isPermaLink="false">https://medium.com/p/b1ce636172a2</guid>
            <category><![CDATA[public-relations]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <dc:creator><![CDATA[Julian Martinez]]></dc:creator>
            <pubDate>Sat, 16 Jun 2018 16:04:09 GMT</pubDate>
            <atom:updated>2021-07-14T03:11:31.345Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*niFQGbRKk5X1htMXMSBfRg.png" /></figure><p>The press release announcing our project can be seen below:</p><p>Business Wire: <a href="https://www.businesswire.com/news/home/20180524005353/en/CurrentCoin-Announces-Digital-Software-Deployment-Solution-Powered">CurrentCoin Announces Digital Software Deployment Solution Powered by Ethereum Smart Contracts</a></p><p>After this went out, our story was featured by a number of news outlets across the Bay Area:</p><ul><li>Financial Buzz: <a href="http://www.financialbuzz.com/currentcoin-announces-digital-software-deployment-solution-powered-by-ethereum-smart-contracts-1100707">CurrentCoin Announces Digital Software Deployment Solution Powered by Ethereum Smart Contracts</a></li><li>CBS-8: <a href="http://www.cbs8.com/story/38268450/currentcoin-announces-digital-software-deployment-solution-powered-by-ethereum-smart-contracts">CurrentCoin Announces Digital Software Deployment Solution Powered by Ethereum Smart Contracts</a></li><li>WFLX-Fox 29: <a href="http://www.wflx.com/story/38268450/currentcoin-announces-digital-software-deployment-solution-powered-by-ethereum-smart-contracts">CurrentCoin Announces Digital Software Deployment Solution Powered by Ethereum Smart Contracts</a></li><li>Telemundo Kasa: <a href="http://www.kasa.com/story/38268450/currentcoin-announces-digital-software-deployment-solution-powered-by-ethereum-smart-contracts">CurrentCoin Announces Digital Software Deployment Solution Powered by Ethereum Smart Contracts</a></li><li>Silicon Valley Business Journal: <a href="https://www.bizjournals.com/sanjose/businesswire/press_releases/California/2018/05/24/20180524005353">CurrentCoin Announces Digital Software Deployment Solution Powered by Ethereum Smart Contracts</a></li><li>Street Insider: <a href="http://markets.financialcontent.com/streetinsider/news/read?GUID=36361893">CurrentCoin Announces Digital Software Deployment Solution Powered by Ethereum Smart Contracts</a></li></ul><p>We were proud to be spotlighted and plan to do more of this.</p><p>While this is just the beginning for us, it’s good to know that our message is getting out there.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b1ce636172a2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/currentcoin/featured-in-the-news-b1ce636172a2">CurrentCoin: Press Release</a> was originally published in <a href="https://medium.com/currentcoin">CurrentCoin</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>