<?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 Craig Taylor on Medium]]></title>
        <description><![CDATA[Stories by Craig Taylor on Medium]]></description>
        <link>https://medium.com/@techspanner?source=rss-85c70165ad38------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*uI5HzKsKCX29GCSQyzRjCA.png</url>
            <title>Stories by Craig Taylor on Medium</title>
            <link>https://medium.com/@techspanner?source=rss-85c70165ad38------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 12:35:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@techspanner/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[Server Side Rendering vs Client Side Rendering in React: Which one should you choose in 2023?]]></title>
            <link>https://techspanner.medium.com/server-side-rendering-vs-client-side-rendering-in-react-which-one-should-you-choose-in-2023-86f1b589feb1?source=rss-85c70165ad38------2</link>
            <guid isPermaLink="false">https://medium.com/p/86f1b589feb1</guid>
            <category><![CDATA[create-react-app]]></category>
            <category><![CDATA[next]]></category>
            <category><![CDATA[nextjs]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[Craig Taylor]]></dc:creator>
            <pubDate>Tue, 28 Mar 2023 10:32:31 GMT</pubDate>
            <atom:updated>2023-03-28T10:32:31.901Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rjb18IRLo9H3BSLn" /><figcaption>Photo by <a href="https://unsplash.com/@lautaroandreani?utm_source=medium&amp;utm_medium=referral">Lautaro Andreani</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>In the world of React, Server Side Rendering (SSR) and Client Side Rendering (CSR) have been at the center of a heated debate for some time. While Next.js has emerged as the dominant framework for SSR, it’s important to understand that choosing between SSR and CSR is not a decision that should be made lightly. In this article, we’ll explore the pros and cons of each approach and help you make an informed decision.</p><p>If you’re a fan of CSR, you’ve likely enjoyed using Create React App, previously the default way to build a React app, which has now been dropped from it’s documentation entirely. You’ve probably written apps that are quick to respond to user interaction and display visually rich graphical content. CSR has a lot of benefits, especially when it comes to reducing processing costs and delivering faster load times after the initial page load.</p><p>However, there are times when SSR is the better choice. For example, if SEO is important to your app, SSR can ensure that your content is easily crawled by search engine spiders. Additionally, SSR keeps all API calls private, which cannot be monitored by watching the network traffic. With the emergence of Next.js and its App directory, SSR has become more accessible and less clunky to implement, making it a popular choice for many developers.</p><p>Despite Next.js’ popularity, it’s essential to consider your app’s functionality and user interaction before deciding on SSR or CSR. There is a danger of blindly choosing SSR because it’s the latest trend or because the App directory and Next.js make it easy to implement. Similarly, CSR shouldn’t be chosen solely because of its speed and cost-effectiveness. The right choice depends on the unique needs and requirements of your app.</p><p>In conclusion, deciding between SSR and CSR in 2023 is not a no-brainer decision. As a developer, you need to consider various factors such as SEO, user interaction, and processing costs before making a choice. While Next.js and its App directory have made SSR more accessible, it’s important not to overlook the benefits of CSR. In the end, the right choice for your app depends on what you’re trying to achieve and what your users need.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=86f1b589feb1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Benefits and Drawbacks of Adopting TypeScript: A 20-Year Veteran Developer’s Perspective]]></title>
            <link>https://javascript.plainenglish.io/the-main-benefits-and-drawbacks-of-adopting-typescript-in-your-project-34952800059e?source=rss-85c70165ad38------2</link>
            <guid isPermaLink="false">https://medium.com/p/34952800059e</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[computer-science]]></category>
            <category><![CDATA[typescript]]></category>
            <dc:creator><![CDATA[Craig Taylor]]></dc:creator>
            <pubDate>Mon, 12 Jul 2021 15:19:40 GMT</pubDate>
            <atom:updated>2021-07-15T04:32:18.508Z</atom:updated>
            <content:encoded><![CDATA[<h4>A question that repeatedly comes up for me as I join a new team and project — should we adopt TypeScript? Let’s look at the pros and cons.</h4><p><em>“Should we adopt TypeScript?”</em></p><p>As TypeScript further grows in popularity, it is a question that repeatedly comes up for me as I join a new project where the tools and tech are selected from scratch. So, here is an up to date top level, and more in-depth look at the benefits and drawbacks of adopting TypeScript in your project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GqFk9_ReN31td6sB" /><figcaption>Photo by <a href="https://unsplash.com/@kitera?utm_source=medium&amp;utm_medium=referral">Kitera Dent</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3><strong>TypeScript benefits</strong></h3><ul><li>Better integration with text editors</li><li>Types help self document the code</li><li>It is faster to refactor</li><li>Catches bugs before compilation</li><li>Can compile down to a target ES version</li><li>Get early access to future features of JS</li></ul><h3><strong>TypeScript drawbacks</strong></h3><ul><li>Unit tests are no longer instant</li><li>Compilation time is increased</li><li>Build pipelines take longer</li><li>A smaller pool of developers to hire</li><li>Non-TS libraries require types</li><li>Pinning version types to get a working compile</li><li>Typescript is full of quirks that are confusing</li><li>Types are only checked at compile time</li><li>Does not reduce bug density</li><li>Leaving the community-driven JS path for Microsoft lock-in</li><li>Dynamic types are actually useful</li><li>More code needs to be written</li><li>Poor and incomprehensible errors</li></ul><h3>Benefits</h3><h4><strong>Better integration with text editors (benefit)</strong></h4><p>Once TypeScript is set up, there are plugins available for most popular text editors. Visual Studio Code, Atom, Webstorm, etc. The images below are from Microsoft’s Typescript installation tutorial. In the first image, we can see all the available console methods in the IntelliSense modal, now annotated with types to help you select the correct method. The second image shows parameter help when calling a function, it shows the parameter types that are required, and ones that are optional. Neat!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/993/1*sYonGhsmrp1QVBdIklM-Lg.png" /><figcaption>Improvements to IntelliSense in VS Code</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/932/1*U3pAxQWvYyZWt7Y7hlJ7EA.png" /><figcaption>Help with parameters</figcaption></figure><h4><strong>Types help self document the code (benefit)</strong></h4><p><a href="https://dev.to/rocambille/how-typescript-helped-me-to-self-document-my-react-project-3ab5">Here</a> is a really clear and simple example of how static types help self-document code. One of the issues with using a loosely typed language like JavaScript is that you are never entirely sure what each variable is for, and what should be stored where. You could argue that’s an advantage of using JavaScript, but it can lead to hard-to-find bugs when you start borrowing structures to store things where they are not intended. TypeScript prevents this and allows you to use interfaces to properly define structures.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HrUpboAuq9VxiOfdnePW2Q.png" /><figcaption>Only an object that implements the RouteInterface can be added to the routes array</figcaption></figure><h4><strong>It’s faster to refactor (benefit)</strong></h4><p>Refactoring is part of the development process. Keeping the code clean, efficient, and tidy helps it make sense to your colleagues, and to yourself six months down the line and is not something that should be avoided. Spending time refactoring pays dividends to development timescales later down the line. However, it is also an expensive process, and any additional help can only be a good thing. Here we can see additional refactoring options that come to life when TypeScript is installed, in VS Code I can right-click on a variable or function declaration and have the interface extracted for me.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/744/1*gV3zOhjL3Joft8ZwKNvg4A.gif" /><figcaption>Additional refactoring options available in VS Code thanks to the adoption of TypeScript</figcaption></figure><h4><strong>Catches bugs before compilation (benefit)</strong></h4><p>Here is a fundamental example of how certain bugs can be caught by the compiler when using TypeScript avoiding deployment into test … and potentially even slipping into production. There are various estimates around on the internet to the percentage of bugs that can be caught pre-compile by TypeScript, with some figures as high as 15%. I’m not convinced this is the case from my experience of using TypeScript and the fact the bug density does not reduce (explained later).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QB645irqkGPBPwHC13LdrQ.png" /><figcaption>Incorrect parameters can no longer be passed once TypeScript is adopted</figcaption></figure><h4><strong>Can compile down to a target ES version (benefit)</strong></h4><p>Once a project is set up with TypeScript it has a .tsconfig file where options can be configured. One of which is the target.</p><p>Setting this to ES6 is a common value for this setting, as all modern browsers support the ES6 standard. However, if you want to support older browsers, you can change this value to an earlier version of the ES standard and the code will compile down into JavaScript that plays nicely with browsers implementing the target standard. If you have this requirement in your project, TypeScript will cut out the need to write browser-specific code.</p><h4><strong>Get early access to future features of JavaScript (benefit)</strong></h4><p>I remember this being a pretty big selling point for TypeScript when it first materialized in late 2012. The ECMAScript (ES) standards of JavaScript are a little slow-moving, due to the fact that they are community-driven. For a change to be made to ES, it must be approved by the majority of the community and then be announced, and browsers must start to interpret those features too. It can take a while. Classes were an example of this in 2012, JavaScript developers knew that classes were coming soon and that they would be useful to them, but could not access this feature until it was released. By adopting TypeScript, developers gained access to the use of classes, and then the TypeScript compiler would simply compile the code down to JavaScript that was backwards compatible. This is less prominent now, ES has sped up significantly and Babel solves this kind of problem to allow JavaScript developers to basically add any syntactical feature they can imagine to their development flow.</p><h3>Drawbacks</h3><h4><strong>Unit tests are no longer instant (drawback)</strong></h4><p>Although TypeScript is often quoted as catching bugs that would get missed without it, unit tests are the best option for this. TDD and unit testing reduce the bug density in a codebase and should become part of the default workflow for a project at some stage. TypeScript gets right in the way here, by adding a transpiling step before unit tests can be run, the running of those unit tests is no longer an instantaneous process. I want my tests to run instantly, I want to make alterations and quickly run them again. Transpiling may only add a small delay to the code-test-code-test workflow, but it’s a small delay that gets annoying very quickly.</p><h4><strong>Compilation time is increased (drawback)</strong></h4><p>A similar and closely coupled drawback to unit tests no longer being instant; It takes slightly longer for me to run my project. In React I would probably have a hot reload workflow in place, but this is also slowed down by the transpiling step. With hot reload and TypeScript setup, I change a line of code or markup, hit save, and endure a very slight delay before the screen updates. It might not seem like much but rapid workflows encourage rapid development so I do not want any slowdowns here.</p><h4><strong>Build pipelines take longer (drawback)</strong></h4><p>Another problem a transpiling step introduces is a longer wait for build pipelines to complete. The production build takes longer, and when you have a queue of builds and a bunch of developers waiting, this can be costly. Too many delays of this kind and you’ll end up with builds timing out, and getting familiar with the rerun button in your favourite Git solution.</p><h4><strong>A smaller pool of developers to hire (drawback)</strong></h4><p>I quite often see this listed as a positive for TypeScript.<br> <strong><br></strong>“TypeScript is JavaScript, you can hire any JavaScript developer to do TypeScript and the learning curve is shallow and smooth” (or something to this effect)</p><p>This is not my experience at all. Having worked on several large projects set up with TypeScript, bringing in JavaScript developers, and then getting them to spend a day on TypeScript docs and expecting them to have no troubles is not how things usually work out. Constantly looking at TypeScript documentation for every minor thing, and trawling through incomprehensible errors, and littering the keyword any throughout the codebase is my experience of a JavaScript developer “running and gunning” with a TypeScript project. Therefore, ideally, you will want to hire an experienced TypeScript developer for your project, and you just reduced the talent pool by 42.3%, a <strong>huge</strong> loss.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oz3W8hBrG2PZIlZ9SsiCYA.png" /><figcaption><a href="https://insights.stackoverflow.com/survey/2020#most-popular-technologies">https://insights.stackoverflow.com/survey/2020#most-popular-technologies</a></figcaption></figure><h4><strong>Non-TS libraries require types (drawback)</strong></h4><p>If you are using JavaScript for your project, chances are you will be using a package manager like npm or yarn and taking advantage of the abundance of libraries available to make your life much easier as a developer. If you are using TypeScript, the JavaScript libraries don’t necessarily come with types. Usually, one of two things happens here to get a library written in JavaScript to work in a TypeScript project.</p><p>1. The developers of the library produce a types package with its own version as an afterthought, they are quite often really flaky and get little support. The library itself could see a series of releases before the types are updated.</p><p>2. Someone, not working on the library wants the types so they write a type library themselves and add this to npm, and then never update it as the JavaScript library is updated. So you are using an old typing library and end up with head-scratching, almost unresolvable errors.</p><h4><strong>Pinning version types to get a working compile (drawback)</strong></h4><p>I’ve been in this situation with a large team on a sizeable codebase with many npm dependencies in a react project. There were about 25 type libraries brought in to accommodate those packages. Leaving the dependencies versioned in the default manner … something like ^4.0.1 is a way of telling the package manager that you will accept any minor updates that are non-breaking changes. This is preferable as small bugs and even security problems get fixed in those packages frequently and the minor version is bumped up. One developer would merge in a feature with a bumped version, which worked fine for them, then when you eventually pulled the updated package.json and tried to re-run your new code you would be faced with compile errors. You would find it was either because the type library was not in sync, or the JavaScript library had new changes that caused the TypeScript compiler to error. Eventually, you would resolve this by pinning the version numbers and dropping the ^ symbol in the package.json either against the type library or the package itself. I don’t want to do this, I want the latest versions.</p><h4><strong>Typescript is full of quirks that are confusing (drawback)</strong></h4><p>My journey into TypeScript is one from a backend developer. Over a decade of C# and Java. A lot of other developers have come from a front end or JavaScript learning path, so TypeScript should be less natural for them, and I am probably one of the programmers that should really appreciate the type system that comes with TypeScript. But I don’t, TypeScript doesn’t make JavaScript strongly typed, it just bolts on rules to make it sometimes behave like a strongly typed language, but in other cases leaves you confused and wondering why weird quirks within TypeScript are the way they are. Here are a few examples.</p><p>Additional attributes are only okay … dependent on your syntax</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TwDvox85RDhFbbTbwwsBLg.png" /><figcaption>Valid TypeScript, no problems here</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*okIgpmVnUUJTl6z-E7kftA.png" /><figcaption>This doesn’t work with inline objects for some reason</figcaption></figure><p>You can pass any old object to a function requiring a specific type, so long as it has the right attributes. So is this strongly typed or not …. well, neither.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Rtf5QssSmbHosoMM8yE-Ig.png" /><figcaption>Valid TypeScript, use a Cat as a Dog, all good</figcaption></figure><p>You can use the | union symbol, to determine a variable as one type or another. But beware.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/938/1*QWw0L7_o4NiFT3A78xvY1w.png" /><figcaption>Nice use of a union … the bark attribute is accessible without casting</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vflc_-vAgcn7WQ0DzQ2T9A.png" /><figcaption>Invalid use of a union</figcaption></figure><h4><strong>Types are only checked at compile time (drawback)</strong></h4><p>This is kind of an important distinction to make. At runtime, there are no type checks available. TypeScript is transpiled to JavaScript at which point the type safety is gone. Network calls, platform-specific APIs, non-typed libraries have no type safety. When writing JavaScript you must write code to check for specific types (a commonly quoted reason for using TypeScript is the ability to remove this code from your codebase). With TypeScript, you rely on the compiler to do this for you, but it cannot check everything. You could of course write similar type checking code to what you do in JavaScript to get some kind of runtime safety, but then what was the point in using TypeScript in the first place? Interpreted languages, cannot check types at runtime.</p><h4><strong>Does not reduce bug density (drawback)</strong></h4><p>There is an in-depth look at this <a href="https://labs.ig.com/static-typing-promise">here</a>. Static typing does not reduce overall bug density within a project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HSkpo-_8X9HjeSk484GpSQ.png" /><figcaption>Low bug density for a non statically typed language.</figcaption></figure><h4><strong>Leaving the community-driven JS path for Microsoft lock-in (drawback)</strong></h4><p>JavaScript is a community-led, community-driven project now. Since the introduction of ES standards, changes are discussed and widely collaborated on before being released. If you have strong feelings about a feature you want to see you can contribute.</p><p>Although TypeScript has been labeled by Microsoft as being ‘open source’, in this case, that just means you are able to browse and read the repo. You won’t be getting any changes or suggestions though. The JavaScript community may also go down a different path to the Microsoft one … and all those thousands of non TypeScript libraries will follow. By selecting TypeScript you take on additional risk and you accept being locked-in by essentially one corporation that makes all decisions about that particular tech.</p><h4><strong>More code needs to be written (drawback)</strong></h4><p>Another difficult thing to put an accurate measurement or metric against. But from my own experience, you have to write at least 20% more code. I really like having codebases DRY, and find a lot of pleasure in removing duplication and unnecessary logic. Less code in the codebase, less code for bugs to exist within. TypeScript requires interfaces, types, casting, and generics to compile. There is no way of avoiding it, you will have to write additional code you would not need if you did not have a TypeScript setup.</p><h4><strong>Poor and incomprehensible errors (drawback)</strong></h4><p>I’ve been a developer commercially for over 20 years. I’ve used so many different technologies. From interpreter code to run on DVD players, OO code to compile down to run only on Windows, mobile applications, and a whole bunch of web tech that has come and gone. None of which have ever stumped me with errors I couldn’t understand more than TypeScript.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AED7FaH0mF40CZlf4WhFdA.png" /><figcaption>Obvious … isn’t it?</figcaption></figure><p>When new developers join the team, unless they have been a TypeScript dev for a few years, the same pattern occurs, hours are wasted on the docs and almost every error possible within the system is a question on stack overflow many times over as they pop up in seemingly incorrect or baffling ways.</p><h3>Will I be adopting TypeScript on my new project?</h3><p>In short, no.</p><p>In my opinion, the drawback still very much outweigh the benefits and TypeScript has never been something I have enjoyed working with, and I do not see any one of the benefits I listed as being something either I cannot live without, or something I can solve in other, non-TypeScripty ways.</p><p><em>More content at </em><a href="http://plainenglish.io/"><strong><em>plainenglish.io</em></strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=34952800059e" width="1" height="1" alt=""><hr><p><a href="https://javascript.plainenglish.io/the-main-benefits-and-drawbacks-of-adopting-typescript-in-your-project-34952800059e">The Benefits and Drawbacks of Adopting TypeScript: A 20-Year Veteran Developer’s Perspective</a> was originally published in <a href="https://javascript.plainenglish.io/">JavaScript in Plain English</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Is Binance banned in the UK?]]></title>
            <link>https://techspanner.medium.com/is-binance-banned-in-the-uk-d190c0d1351d?source=rss-85c70165ad38------2</link>
            <guid isPermaLink="false">https://medium.com/p/d190c0d1351d</guid>
            <category><![CDATA[banned]]></category>
            <category><![CDATA[crypto-exchange]]></category>
            <category><![CDATA[uk]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[binance]]></category>
            <dc:creator><![CDATA[Craig Taylor]]></dc:creator>
            <pubDate>Sun, 27 Jun 2021 14:50:52 GMT</pubDate>
            <atom:updated>2021-06-27T21:15:08.360Z</atom:updated>
            <content:encoded><![CDATA[<h4>Today a series of news articles appeared online claiming that Binance had been banned in the UK. Immediately my thoughts turned to withdrawing my funds. But is it actually banned?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GNSkYoohAxBs1guY" /><figcaption>Photo by <a href="https://unsplash.com/@executium?utm_source=medium&amp;utm_medium=referral">Executium</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>TLDR; no</p><p>The headline from Financial Times article couldn’t be worded more clearly …</p><h4><a href="https://www.ft.com/content/8bc0e5e0-2705-496d-a265-acccaffaee87">Financial watchdog bans crypto exchange Binance from UK</a></h4><p>Financial Times, Sunday 27th June 2021</p><p>However, when you read past the click enticing headline. It’s not half as dramatic as it suggests.</p><blockquote>The UK’s financial watchdog has ordered Binance to stop all regulated activities in Britain and imposed stringent requirements in a stinging rebuke of one of the world’s biggest cryptocurrency exchanges.</blockquote><p>OK, so it’s not banned then. It’s banned from regulated activities. That’s something entirely different. The UK financial watchdog in question is the FCA. I don’t expect any cryptocurrency assets or products I own to be regulated by the FCA anyway. That’s the point isn’t it? It’s decentralised and free from regulation. This begs the question, what is meant by ‘regulated activities’ in this case? Futures and derivative are, so may be affected. Spot/cryptocurrency is unregulated.</p><blockquote>The exchange has until Wednesday evening to confirm it has complied with the watchdog’s demands, and removed its advertising.</blockquote><p>Right. We’ve gone on quite a tangent here haven’t we FT? We started at ‘Binance is banned’ and now it’s ‘Binance must remove advertising’ for presumably regulated financial products by Wednesday …. or else?</p><p>Further in the article we can find an unreferenced quote.</p><blockquote>“Binance Markets Limited is not permitted to undertake any regulated activity in the UK,” the FCA said, adding, “no other entity in the Binance Group holds any form of UK authorisation, registration or licence to conduct regulated activity in the UK.”</blockquote><p>Binance Markets? Is that a subsidiary then? I found the answer to this myself. Yes, it’s a subsidiary. It’s a London based company. Binance are in the process of developing and launching Binance UK. By operating out of London, the FCA will have to give this new arm of Binance the nod. At the moment the Binance UK website is still a placeholder ‘coming soon’ page. <a href="https://www.binance.co.uk/">https://www.binance.co.uk/</a></p><p>The unreferenced quote above, just required a quick Google search to find its source. It is taken from an announcement by the FCA which <a href="https://www.fca.org.uk/news/news-stories/consumer-warning-binance-markets-limited-and-binance-group">can be found here</a>, and is almost certainly the source material to back this article. The FCA’s statement relating to Binance in its entirety reads…</p><blockquote>Binance Markets Limited is not permitted to undertake any regulated activity in the UK. This firm is part of a wider Group (Binance Group). Due to the imposition of requirements by the FCA, Binance Markets Limited is not currently permitted to undertake any regulated activities without the prior written consent of the FCA. No other entity in the Binance Group holds any form of UK authorisation, registration or licence to conduct regulated activity in the UK. The Binance Group appear to be offering UK customers a range of products and services via a website, Binance.com.</blockquote><p>Reading this statement, to me it seems this is entirely an issue with the London based subsidiary Binance Markets, which was advertised on binance.com. The statement around Binance Group, is not news. I am aware Binance is not regulated by any UK entity, it is based in the Cayman Islands and I have weighed up the risks and understand that my crypto assets have no insurance, no FSCS protection and no FCA regulation. I knew that before I made my first deposit.</p><p>The Financial Times article actually confirms this a little further on.</p><blockquote>the FCA has restricted Binance from offering services in the UK, British citizens can still access Binance’s services in other jurisdictions.</blockquote><p>Yes, I can still access services via the app, or the website which are based outside of the UK.</p><p>Typically, when news breaks, other news companies just copy … and we now have a wave of these articles, which all relate to the same thing.</p><h4><a href="https://www.coindesk.com/binance-isnt-allowed-to-be-operating-in-the-uk-watchdog-warns">Binance Isn’t Allowed to be Operating in the UK, Watchdog Warns</a></h4><p>Coindesk, Sunday 27th June 2021</p><h4><a href="https://www.reuters.com/world/uk/financial-watchdog-orders-crypto-exchange-binance-stop-regulated-activities-uk-2021-06-27/">Financial watchdog orders crypto exchange Binance to stop regulated activities in UK</a></h4><p>Reuters, Sunday 27th June 2021</p><h4><a href="https://www.bloomberg.com/news/articles/2021-06-27/u-k-financial-regulator-bars-crypto-exchange-binance">U.K. Financial Regulator Bars Crypto Exchange Binance</a></h4><p>Bloomberg, Sunday 27th June 2021</p><p>Update : Tweets from Binance confirm the above</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hHwf_sR0Qmz0LvkZiEO3-Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qN07bYxtEGI4QgMYBPoEbw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OnEEqUT7gj4pHlMh3TV6fA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d190c0d1351d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is the monthly cost of an on-demand EC2 box?]]></title>
            <link>https://techspanner.medium.com/what-is-the-monthly-cost-of-an-on-demand-ec2-box-e6e71f53aea8?source=rss-85c70165ad38------2</link>
            <guid isPermaLink="false">https://medium.com/p/e6e71f53aea8</guid>
            <category><![CDATA[saving-money]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[ec2]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Craig Taylor]]></dc:creator>
            <pubDate>Tue, 15 Jun 2021 11:13:55 GMT</pubDate>
            <atom:updated>2021-06-15T11:15:01.734Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>The AWS EC2 on demand pricing page has a lot of variables, and is priced by the hour. Where can I provision boxes for development projects at the lowest monthly cost?</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pn1xWlf1Aurn0NYW" /><figcaption>Photo by <a href="https://unsplash.com/@homajob?utm_source=medium&amp;utm_medium=referral">Scott Graham</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>It’s very clearly listed on AWS EC2 Pricing page <a href="https://aws.amazon.com/ec2/pricing/on-demand/">https://aws.amazon.com/ec2/pricing/on-demand/</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UmmfW3gvIZAOZgeIP3u1hA.png" /><figcaption>Well this is a bit useless isn’t it?</figcaption></figure><p>The problem with these prices is that I want to know at-a-glance, how much the box costs to run per month? I know ‘on-demand’ means I can switch it on and off when I feel like it and be billed by the hour, and that reserved instances offer better value with percentage discounts given for longer term commitments on the box I’m hiring.</p><blockquote><em>I want to know at-a-glance, how much the box costs to run per month?</em></blockquote><p>Spot instances can work out even cheaper, but it’s a very specific use-case and most of the apps I write are not suited to be run ad-hoc.</p><h3>Monthly cost calculation</h3><p>At the start of a new project there are so many unknowns that I just want to spin up a bog standard EC2 box, because the reality is; it’s probably going to be left running until it gets replaced or retired. Living in the UK also gives an extra annoyance with the variable of the exchange rate. Today’s exchange rate is 1 USD = 0.71 GBP.</p><p>From the price list in the image above, the cost of a T4G nano EC2 box per month provisioned in London can be approximated by doing the following calculation.</p><p><strong>hourly rate X hours per day X days per month X exchange rate<br>0.0047 X 24 X 30 X 0.71 = £2.40 per month</strong></p><p>What incredible value! Now I remember why I love AWS so much. Yeah, okay so that machine has the processing power of a household vacuum cleaner, but most of my projects start this way, and it’s enough to get going.</p><p>But I have lots of these boxes running. Different types, different purposes and different regions. When I spin a new box up I almost always use London or Ireland. The thinking being, that these are the closest locations to me so the latency will be lower. Whilst this is correct, the latency isn’t usually any kind of hindrance during the development stage of an app, and my own testing gave rapid latency results regardless of which region I used. Sure, deploy your production ready app at the location closest to where most of your users will be, but for development; perhaps cost should be the focus?</p><h3>Regional variance</h3><p>With just a small play on the EC2 pricing page, it is noticeable that the cost of hiring boxes differs across regions. This makes sense as electricity prices, the cost of hiring staff and renting premises also change for Amazon.</p><p>So what does the same T4G box cost in other regions?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZuDbEMXmWRiJCjsJf-faTQ.png" /><figcaption>The monthly cost of a t4g.nano across different regions</figcaption></figure><p>Mumbai has T4G EC2 instances available for considerable cheaper than anywhere else. Paris, Milan, Los Angeles, Bahrain and Osaka do not have the newer T4G nano boxes available, so I’ve used the nearest equivalent box, a T3 nano.</p><blockquote><em>Mumbai has T4G EC2 instances available for considerable cheaper than anywhere else</em></blockquote><p>Spinning up EC2 boxes for development in Mumbai rather than my default choice of London would save me a huge 40% on cost. Each box I provision in London instead of Mumbai is costing me £1.02 per month more than I need to spend. It’s only £1.02 but with lots of clients and lots of projects …. A free coffee is a free coffee.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ptHDaRMsH-Lu-2GE" /><figcaption>Photo by <a href="https://unsplash.com/@claybanks?utm_source=medium&amp;utm_medium=referral">Clay Banks</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e6e71f53aea8" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>