Originally published by Michael Uloth at freecodecamp.org
But wait! Your Mac isn’t ready. Before diving in, you’ll need to install a few items to that will save you from confusing errors later. 😩
Before installing any new software, follow these instructions from Apple to upgrade macOS and your current software to the latest version.
Since you’ll be interacting with your Mac using the command line in this article, you’ll need a terminal app.
Any of the following are good options:
If you aren’t sure which one to pick, choose Hyper.
The first thing you’ll need to install from the command line are your Mac’s command line developer tools. Installing these now will prevent weird errors later.
To check if the tools are already installed, type the following command in your terminal app and hit return:
If the result is not a version number, install the tools with this command:
A dialog will appear asking if you’d like to install the tools. Click Install and the package will download and install itself.
When the installation finishes, confirm the tools are now installed by rerunning the first command:
The result should now be a version number.
Instead of installing the next few tools by going to each tool’s website, finding the download page, clicking the download link, unzipping the files, and manually running the installer, we’re going to use Homebrew.
Homebrew is a tool that lets you install, update and uninstall software on your Mac from the command line. This is faster and safer than the manual approach and generally makes your development life easier.
First, check if Homebrew is already installed:
If you don’t see a version number, install Homebrew with this command:
/usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
I promise that’s the weirdest command you’ll see in this article! 😅 Thanks to Homebrew, the rest are simple.
Before moving on, confirm Homebrew is now installed:
Node also includes npm (the Node Package Manager), which gives you access to a giant library of free code you can download and use in your projects.
First, check if Node is already installed:
If not, install it with Homebrew:
brew install node
Finally, confirm Node and npm are now installed:
node --version npm --version
Git is a tool that helps you track changes to your code and work with other developers on shared projects.
Using Git on every project is a great habit to develop and will prepare you for future projects where Git may be required. Some tools (like GatsbyJS) also depend on Git being installed on your Mac, so you’ll need it even if you don’t plan to add it to your workflow.
Once again, start by checking if Git is already installed:
If not, install it:
brew install git
And confirm the installation worked:
Once in a while, run the following command and everything you’ve installed with Homebrew will update automatically:
brew update && brew upgrade && brew cleanup && brew doctor
That one command is all you need to keep your system up to date. 🙌
I usually run it when I start a new project, but feel free to do so whenever you like. (When you run this command, if Homebrew suggests additional commands for you to run, go ahead and run them. If a command begins with
sudo and you are prompted for a password, use your Mac’s admin password.)
That’s it for the command line!
While you can write code in any text editor, using one that highlights and validates your code will make your life much easier.
Any of the following are good options:
If you’re just getting started, choose Visual Studio Code.
As you code, it helps to view the app or website you’re building in a browser to confirm it works. While you can use any browser for this, some include extra developer tools that show you details about your code and how to improve it.
Either of the following are good options:
If you’re just getting started, choose Chrome.
A quick tip here: you’ll want to show the files your Mac hides by default. (For example, git files are automatically hidden, but sometimes you’ll want to edit them.)
The easiest way to show your Mac’s hidden files is with the keyboard shortcut ⌘⇧. (Command + Shift + Period). This will alternate between showing and hiding these files so you can access them when you need them.
You’re all set! 🎉
To prevent confusion, I left out any items that aren’t strictly required. If you’d like to dive deeper into optional ways you can further customize your Mac for web development, check out the links below.
Originally published by Michael Uloth at freecodecamp.org
Best Mobile App Development Company India, WebClues Global is one of the leading web and mobile app development company. Our team offers complete IT solutions including Cross-Platform App Development, CMS & E-Commerce, and UI/UX Design.
We are custom eCommerce Development Company working with all types of industry verticals and providing them end-to-end solutions for their eCommerce store development.
Know more about Top E-Commerce Web Development Company
Originally published by David Gilbertson at https://medium.com
Also known as “no, you’re thinking of Service Workers”.
Before I get into the meat of the article, please sit for a lesson in how computers work:
For the red/green colourblind, let me explain. While a CPU is doing one thing, it can’t be doing another thing, which means you can’t sort a big array while a user scrolls the screen.
This is bad, if you have a big array and users with fingers.
Enter, Web Workers. These split open the atomic concept of a ‘CPU’ and allow us to think in terms of threads. We can use one thread to handle user-facing work like touch events and rendering the UI, and different threads to carry out all other work.
Check that out, the main thread is green the whole way through, ready to receive and respond to the gentle caress of a user.
You’re excited (I can tell), if we only have UI code on the main thread and all other code can go in a worker, things are going to be amazing (said the way Oprah would say it).
But cool your jets for just a moment, because websites are mostly about the UI — it’s why we have screens. And a lot of a user’s interactions with your site will be tapping on the screen, waiting for a response, reading, tapping, looking, reading, and so on.
So we can’t just say “here’s some JS that takes 20ms to run, chuck it on a thread”, we must think about where that execution time exists in the user’s world of tap, read, look, read, tap…
I like to boil this down to one specific question:Is the user waiting anyway?
Imagine we have created some sort of git-repository-hosting website that shows all sorts of things about a repository. We have a cool feature called ‘issues’. A user can even click an ‘issues’ tab in our website to see a list of all issues relating to the repository. Groundbreaking!
When our users click this issues tab, the site is going to fetch the issue data, process it in some way — perhaps sort, or format dates, or work out which icon to show — then render the UI.
Inside the user’s computer, that’ll look exactly like this.
Look at that processing stage, locking up the main thread even though it has nothing to do with the UI! That’s terrible, in theory.
But think about what the human is actually doing at this point. They’re waiting for the common trio of network/process/render; just sittin’ around with less to do than the Bolivian Navy.
Because we care about our users, we show a loading indicator to let them know we’ve received their request and are working on it — putting the human in a ‘waiting’ state. Let’s add that to the diagram.
Now that we have a human in the picture, we can mix in a Web Worker and think about the impact it will have on their life:
First thing to note is that we’re not doing anything in parallel. We need the data from the network before we process it, and we need to process the data before we can render the UI. The elapsed time doesn’t change.
(BTW, the time involved in moving data to a Web Worker and back is negligible: 1ms per 100 KB is a decent rule of thumb.)
So we can move work off the main thread and have a page that is responsive during that time, but to what end? If our user is sitting there looking at a spinner for 600ms, have we enriched their experience by having a responsive screen for the middle third?
I’ve fudged these diagrams a little bit to make them the gorgeous specimens of graphic design that they are, but they’re not really to scale.
When responding to a user request, you’ll find that the network and DOM-manipulating part of any given task take much, much longer than the pure-JS data processing part.
Chucking the data processing over to a worker thread sounds sensible, but the idea struck me as a little, umm, academic.
First, let’s split instances of ‘updating a store’ into two categories:
If the first scenario, a user taps a button on the screen — perhaps to change the sort order of a list. The store updates, and this results in a re-rendering of the DOM (since that’s the point of a store).
Let me just delete one thing from the previous diagram:
In my experience, it is rare that the store-updating step goes beyond a few dozen milliseconds, and is generally followed by ten times that in DOM updating, layout, and paint. If I’ve got a site that’s taking longer than this, I’d be asking questions about why I have so much data in the browser and so much DOM, rather than on which thread I should do my processing.
So the question we’re faced with is the same one from above: the user tapped something on the screen, we’re going to work on that request for hopefully less than a second, why would we want to make the screen responsive during that time?
OK what about the second scenario, where a store update isn’t in response to a user interaction? Performing an auto-save, for example — there’s nothing more annoying than an app becoming unresponsive doing something you didn’t ask it to do.
Actually there’s heaps of things more annoying than that. Teens, for example.
Anyhoo, if you’re doing an auto-save and taking 100ms to process data client-side before sending it off to a server, then you should absolutely use a Web Worker.
In fact, any ‘background’ task that the user hasn’t asked for, or isn’t waiting for, is a good candidate for moving to a Web Worker.The matter of value
Complexity is expensive, and implementing Web Workers ain’t cheap.
If you’re using a bundler — and you are — you’ll have a lot of reading to do, and probably npm packages to install. If you’ve got a create-react-app app, prepare to eject (and put aside two days twice a year to update 30 different packages when the next version of Babel/Redux/React/ESLint comes out).
Also, if you want to share anything fancier than plain data between a worker and the main thread you’ve got some more reading to do (comlink is your friend).
What I’m getting at is this: if the benefit is real, but minimal, then you’ve gotta ask if there’s something else you could spend a day or two on with a greater benefit to your users.
This thinking is true of everything, of course, but I’ve found that Web Workers have a particularly poor benefit-to-effort ratio.Hey David, why you hate Web Workers so bad?
This is a doweling jig:
I own a doweling jig. I love my doweling jig. If I need to drill a hole into the end of a piece of wood and ensure that it’s perfectly perpendicular to the surface, I use my doweling jig.
But I don’t use it to eat breakfast. For that I use a spoon.
Four years ago I was working on some fancy animations. They looked slick on a fast device, but janky on a slow one. So I wrote fireball-js, which executes a rudimentary performance benchmark on the user’s device and returns a score, allowing me to run my animations only on devices that would render them smoothly.
Where’s the best spot to run some CPU intensive code that the user didn’t request? On a different thread, of course. A Web Worker was the correct tool for the job.
Fast forward to 2019 and you’ll find me writing a routing algorithm for a mapping application. This requires parsing a big fat GeoJSON map into a collection of nodes and edges, to be used when a user asks for directions. The processing isn’t in response to a user request and the user isn’t waiting on it. And so, a Web Worker is the correct tool for the job.
It was only when doing this that it dawned on me: in the intervening quartet of years, I have seen exactly zero other instances where Web Workers would have improved the user experience.
Contrast this with a recent resurgence in Web Worker wonderment, and combine that contrast with the fact that I couldn’t think of anything else to write about, then concatenate that combined contrast with my contrarian character and you’ve got yourself a blog post telling you that maybe Web Workers are a teeny-tiny bit overhyped.
Thanks for reading ❤
If you liked this post, share it with all of your programming buddies!
PHP is widely used open-source scripting language it helps in making dynamically easy your websites and web application. Mobiweb Technology is your best technical partner and offering you solution for any kind of website and application...
PHP is widely used open-source scripting language it helps in making dynamically easy your websites and web application. Mobiweb Technology is your best technical partner and offering you solution for any kind of website and application development. To hire PHP developer and web developer at affordable prices contact Mobiweb Technology via [email protected]