I tried coding on a Chromebook for 7 days

Adrian Twarog
22 Mar 202212:56

Summary

TLDRIn this video, the creator explores the feasibility of using a Chromebook as a primary coding device. Starting with a budget-friendly Lenovo Duet 5, they delve into the setup process, enabling developer mode, and installing essential tools like VS Code and Node.js. Despite initial challenges with hardware compatibility and setup, they successfully configure the Chromebook for coding. The video highlights the device's performance with web development tasks, its portability, and battery life, concluding that while Chromebooks are not ideal for complex projects or mobile app development, they are a cost-effective option for beginners and for basic coding tasks.

Takeaways

  • 💻 The author experimented with using a Chromebook as a primary coding device to determine its feasibility and experience.
  • 💰 Chromebooks are considered due to their affordability compared to high-priced MacBooks or Windows laptops.
  • 🔍 The Lenovo Duet 5 was chosen as a test device, costing around $400.
  • 📝 Chromebooks run on Chrome OS, which is based on Linux, allowing the potential to run Linux applications.
  • 🖥️ The keyboard quality is highlighted as crucial for coding, and the author was satisfied with the Chromebook's keyboard.
  • 🛠️ Developer mode was enabled to access the shell and customize the Chromebook.
  • 🌐 Internet connectivity issues were faced initially, but resolved by resetting the router.
  • 💾 Installing VS Code was challenging due to processor differences, but was made possible by enabling Linux development environment on the Chromebook.
  • 🔧 The author found that setting up the Chromebook for coding required additional time and effort compared to traditional laptops.
  • ☕ The performance of the Chromebook was sufficient for basic coding tasks and running a Create React App.
  • 🔆 The screen's brightness was insufficient for outdoor use, and the device was not comfortable for lap use.
  • 🔋 The battery life was impressive, and the device was portable for on-the-go use.

Q & A

  • Is it possible to use a Chromebook for coding?

    -Yes, it is possible to use a Chromebook for coding. The script details the process of setting up a Chromebook for programming tasks, including installing necessary software like VS Code.

  • What is the first thing the author did after getting the Chromebook?

    -The first thing the author did was to enable developer mode, which allows access to the shell and the ability to input commands and install applications.

  • Why did the author choose a Chromebook over a MacBook or Windows laptop?

    -The author chose a Chromebook because it is more affordable compared to MacBooks and Windows laptops, which can be expensive, especially for someone starting out in programming.

  • What challenges did the author face while trying to install VS Code on the Chromebook?

    -The author faced challenges due to the Chromebook's ARM-based processor, which required a custom version of VS Code. They also had to enable the Linux development environment on the Chromebook.

  • How did the author overcome the issue of installing VS Code on the Chromebook?

    -The author overcame the issue by enabling the Linux development environment in Chromebook settings and downloading the ARM64 version of VS Code from the official website.

  • What was the author's experience with the Chromebook's keyboard?

    -The author was quite happy with the Chromebook's keyboard, which they connected via a USB-C cable and used for coding.

  • How does the author describe the process of setting up the Chromebook for coding?

    -The author describes the setup process as time-consuming but also as an opportunity to get to know the device better. It involved enabling developer mode, setting up the Linux environment, and installing necessary software.

  • What was the author's experience with the Chromebook's performance while coding?

    -The author found the Chromebook's performance to be impressive for a device of its cost, allowing them to build React applications and use VS Code effectively, although they noted it was slower for loading larger projects.

  • How did the author use the Chromebook outside of a traditional office setting?

    -The author used the Chromebook on the go, for tasks like checking emails, browsing, and working on scripts. They also found it useful for client meetings and showcasing project demos.

  • What limitations did the author find when using the Chromebook for coding?

    -The author found limitations in the Chromebook's screen brightness and camera quality, and it was not ideal for use on the lap or in direct sunlight. Additionally, it might not be suitable for building mobile applications with React Native or Flutter due to its processing power.

  • What was the author's overall impression of using a Chromebook as a primary coding device?

    -The author was surprised and impressed with the Chromebook's capabilities as a coding device, especially considering its low cost. They found it suitable for web development and learning to code but noted its limitations for more resource-intensive tasks.

Outlines

00:00

💻 Exploring Chromebook for Coding

The speaker begins by expressing the high costs of computer hardware and decides to explore the possibility of using a Chromebook as a primary coding device. They purchase a Lenovo Duet 5, a relatively inexpensive Chromebook, to test its capabilities for programming. The speaker highlights the unique Chrome OS operating system, which is based on Linux, and expresses hope that it can run Linux applications. They also discuss the importance of the keyboard quality and their initial setup process, including updates and creating an account. The speaker then addresses the challenge of enabling developer mode to access the shell and customize the Chromebook, which involves disabling security features.

05:02

🛠️ Setting Up Development Environment

The speaker's goal for the next day is to get Visual Studio Code (VS Code) running on the Chromebook. They encounter an initial issue with the internet connection but manage to resolve it by resetting the router. The speaker then researches code editors available for Chromebooks, dismissing web-based editors in favor of installing VS Code directly. They attempt to download the Linux version of VS Code but face challenges due to the Chromebook's ARM-based processor, which lacks support for the standard VS Code build. The speaker explores solutions, including enabling a Linux development environment in Chromebook settings and finding a custom version of VS Code suitable for ARM64 processors.

10:03

🌟 Chromebook as a Mobile Coding Device

After successfully installing VS Code and Node.js on the Chromebook, the speaker takes it on the go to test its performance outside the home office. They find that while the device's portability is excellent, the screen's brightness and reflectivity make outdoor use challenging. However, the battery life is impressive. The speaker also notes that the Chromebook's form factor is not ideal for use on the lap but could work well in a car for emergency coding situations. They reflect on the Chromebook's capabilities, concluding that it is suitable for learning to code and performing basic development tasks, but might not be powerful enough for more resource-intensive projects like mobile app development in React Native or Flutter.

Mindmap

Keywords

💡Chromebook

A Chromebook is a laptop that runs on Google's Chrome OS. It's designed for people who spend a lot of time on the internet and is known for its simplicity and affordability. In the video, the presenter explores using a Chromebook as a primary device for coding, which is typically done on more traditional operating systems like Windows or Mac.

💡Chrome OS

Chrome OS is the operating system used on Chromebooks. It's based on the Linux kernel and is designed to be lightweight and fast, primarily running web applications. The video discusses enabling a developer mode in Chrome OS to access the shell and install applications, which is not possible in the standard user mode.

💡Developer Mode

Developer Mode on a Chromebook is a setting that allows users to access the device's full capabilities, including the Linux shell and the ability to install Linux applications. This is crucial for the video's theme as it enables the presenter to install necessary tools for coding, such as VS Code.

💡VS Code

VS Code stands for Visual Studio Code, a popular source code editor developed by Microsoft. It supports a wide array of programming languages and is extensible with extensions. The video details the process of installing VS Code on a Chromebook, which is a central part of the presenter's exploration into coding on this platform.

💡Linux

Linux is a type of operating system that is open-source and widely used for servers and developers' machines. The video mentions that Chrome OS is based on Linux, which allows the presenter to install a Linux development environment and run applications like VS Code.

💡ARM Processor

An ARM processor is a type of CPU architecture found in many mobile devices and some Chromebooks. The video discusses the need for a custom version of VS Code for ARM-based Chromebooks, highlighting the differences in software compatibility between ARM and Intel processors.

💡Node.js

Node.js is a JavaScript runtime that allows developers to run JavaScript on the server side. In the video, the presenter installs Node.js on the Chromebook to demonstrate the device's capability to handle server-side JavaScript applications.

💡Create React App

Create React App is a tool used to set up new React applications. React is a popular JavaScript library for building user interfaces. The video shows the presenter using Create React App to start a new project, indicating that the Chromebook can handle modern web development tasks.

💡Git

Git is a version control system used by developers to manage changes in code. The video includes a segment where the presenter installs Git on the Chromebook to clone a repository, which is a common task in software development.

💡Portability

Portability in the context of the video refers to the ability to use the Chromebook in different locations, such as on the go or in a car. The presenter evaluates the Chromebook's portability and finds it suitable for certain scenarios like quick fixes or client meetings.

💡Performance

Performance in this video pertains to how well the Chromebook handles coding tasks compared to traditional laptops or desktops. The presenter assesses the Chromebook's performance by running applications, building projects, and using it for everyday coding activities.

Highlights

The price of computer hardware is expensive, prompting consideration of alternative coding devices.

Coding on a Chromebook is explored as a potential cost-effective alternative.

Lenovo Duet 5 Chromebook was chosen for its affordability at around $400.

Chromebooks run on Chrome OS, which is based on Linux, potentially allowing for Linux applications.

The keyboard quality of the Chromebook is praised as important for coding.

Developer mode on Chromebooks provides access to the shell for command-line operations.

VS Code installation on Chromebooks requires enabling Linux development environment.

Different processors on Chromebooks may affect software compatibility, such as VS Code.

Custom version of VS Code is needed for ARM-based Chromebooks.

Setting up a Chromebook for coding requires additional time and effort compared to traditional laptops.

VS Code runs successfully on the Chromebook after enabling Linux mode and installing ARM64 version.

Node.js installation on Chromebook is straightforward through terminal commands.

Create React App can be used on a Chromebook to build and host web applications.

Git needs to be installed separately on the Chromebook to clone repositories.

Performance of the Chromebook is sufficient for small to medium-sized coding projects.

The Chromebook's portability is beneficial for on-the-go coding and client meetings.

The screen brightness and reflection issues make outdoor use challenging.

Battery life of the Chromebook is impressive, lasting through multiple hours of use.

Chromebook's camera quality is adequate but not exceptional.

Chromebook is a cost-effective option for learning to code and basic web development.

For more resource-intensive tasks like mobile app development, a Windows or Mac might be necessary.

Transcripts

play00:00

these days the price of computer

play00:02

hardware is ridiculously expensive so

play00:04

it's worth considering what coders

play00:06

actually need to get the job done to

play00:08

that end i wanted to find out if coding

play00:11

on a chromebook is possible and even if

play00:13

it could be my primary coding device so

play00:16

i picked up this chromebook to use for a

play00:18

period of about a week or two and during

play00:20

that time i'm going to answer some

play00:22

fundamental questions like can a device

play00:23

like this even be used for programming

play00:26

if it can what is that experience like

play00:28

and would i recommend it to people

play00:30

learning to code and even continuing

play00:32

their coding journey let's find out the

play00:34

first thing i needed to do was get a

play00:35

chromebook so i jumped on google and

play00:37

went for the cheapest one this was the

play00:39

lenovo duet 5 which only comes in at

play00:41

around 400 so i ordered it and it

play00:44

arrived if you're not aware chromebooks

play00:46

are essentially just like laptops but

play00:47

instead of using something like windows

play00:49

or mac they have a special operating

play00:51

system called chrome os and this is also

play00:53

based on chromium os which is also based

play00:56

on linux but what i'm hoping here is

play00:58

that i should be able to run some linux

play00:59

applications on this operating system

play01:01

for me one of the most important things

play01:03

for a device like this is the keyboard

play01:05

and i was quite happy with this one i

play01:06

plugged it in with a usbc cable and i

play01:08

got started creating my account this is

play01:10

actually the very first time i've used a

play01:11

chromebook so i'm not too sure yet what

play01:13

to expect i downloaded some updates and

play01:15

then i logged into my account after

play01:17

which it did some more updates so i

play01:19

decided it was lunch time and i decided

play01:20

now that i have a mobile device like

play01:22

this i might as well take it with me on

play01:24

my way to grab some food you might be

play01:26

thinking why did i pick a chromebook

play01:27

well the macbooks and windows laptops

play01:29

these days are expensive like four

play01:31

thousand dollars or more i wanted

play01:32

something cheap because when i started

play01:34

out in my programming journey i didn't

play01:35

have much money and i actually picked up

play01:37

a secondhand laptop alright great so

play01:39

i've got the setup more or less done

play01:40

here but i'm having a bit of a problem

play01:42

because right now i can only open up

play01:44

google chrome so i did some digging on

play01:46

google and found out that you can

play01:48

actually enable a developer mode and

play01:50

that's the very first thing that i did

play01:51

the developer mode disables all security

play01:53

for the chromebook but it comes with the

play01:55

benefit of letting you access the shell

play01:57

so now with this i can start actually

play01:59

inputting my own commands like pinging

play02:01

or installing applications and really

play02:03

customizing my chromebook to work how i

play02:05

want okay let's move to the next day

play02:06

because i actually want to start

play02:08

utilizing this chromebook and seeing

play02:09

what it's capable of so today's goal is

play02:12

quite simple i just want to get vs code

play02:14

running on this chromebook of course

play02:16

life is never that simple the very first

play02:18

issue i had was no internet connection i

play02:20

needed to connect up to my wifi which

play02:22

wasn't even working the other thing i

play02:23

can do is connect it to my mobile phone

play02:25

using bluetooth and tethering which is

play02:27

always a good option instead what i

play02:29

decided to do is head over to my

play02:31

internet router and while i'm no it

play02:33

expert what i decided was to keep

play02:35

turning it off and on again until it

play02:37

came back online now that i'm connected

play02:39

let's have a look at some of the code

play02:41

editors available for the chromebook

play02:42

some of the easiest to get started with

play02:44

are web-based editors like code sandbox

play02:47

which allows you to have a vs code like

play02:49

interface on your browser but this isn't

play02:52

really what i'm after what i really want

play02:53

to do is open up vs code on the

play02:55

chromebook directly and have some files

play02:57

and even maybe a hosting server on here

play02:59

so let's find out how we can do this as

play03:01

a windows user i thought i'd just

play03:02

install it and went to vs code.com which

play03:04

actually isn't the website so i went on

play03:06

google and found out it's actually

play03:07

code.visualstudio.com

play03:09

now that we're on here i'm going to

play03:11

select to download the deb version which

play03:13

is the linux version which i assume

play03:15

that's what i'm running and hopefully it

play03:17

just works and it doesn't just work well

play03:20

this is starting to become a nightmare i

play03:22

thought originally that all i had to do

play03:24

is download it but there is apparently a

play03:27

difference between intel processors and

play03:29

maybe arm based processors where the arm

play03:32

ones just don't have support for vs code

play03:35

i'm gonna have to do some more digging

play03:36

to find out if it's actually possible to

play03:38

run a vs code on here because i don't

play03:40

wanna really give up i do want vs code

play03:42

running on here and there's gotta be

play03:43

some way to do it so i headed over to my

play03:46

favorite website youtube and here i'm

play03:48

gonna search for hopefully a tutorial on

play03:50

how to install vs code on a chromebook

play03:53

i'm sure there's someone out there who's

play03:54

done it and after some searching i did

play03:56

find a few different examples what i

play03:58

learned is that chromebooks can run on a

play04:00

number of different processors and i'm

play04:01

using an rm64 based processor this means

play04:04

i need a custom version of vs code and

play04:06

on top of that i also need a custom

play04:08

version of linux distro running on this

play04:10

chromebook luckily this is quite easy to

play04:13

set up and all i have to do is head over

play04:15

to the chromebook settings and then

play04:17

enable a special mode called the linux

play04:19

development environment this installs

play04:21

all the extra unnecessaries that i need

play04:23

to get this up and running and i guess

play04:25

this is my first bit of feedback about

play04:26

the chromebook while it's a cheap device

play04:29

it does mean that you have to spend some

play04:31

additional time setting it all up to

play04:32

work the way you want for some people

play04:34

that might be a relaxing experience

play04:36

where you get to know your device a

play04:37

little bit better whereas for other

play04:39

people that might be a little bit

play04:40

frustrating i now have access to the

play04:42

shell and i did some more digging on the

play04:44

vs code website and found there was an

play04:46

actual guide on how to be installed on

play04:47

chromebooks which i really should have

play04:49

followed but having a look at this guide

play04:50

i can see that first i need the linux

play04:52

mode enabled which i've already done and

play04:54

then i need to execute a couple of

play04:56

commands that will allow me to install

play04:57

new applications i ran the commands and

play04:59

then jumped back on to vs code and

play05:01

downloaded the damp version of arm64 and

play05:04

now i'm ready to install it and the

play05:06

installation is successful

play05:08

yes vs code's up and running loading it

play05:11

up it looks exactly the same as my

play05:13

version on the mac as well as on the

play05:15

windows so i guess the very first thing

play05:17

is to customize my settings and maybe

play05:19

even log into github and it's also time

play05:21

for lunch so what i'm gonna do is take

play05:23

this chromebook with me on the go and

play05:25

we're gonna see how it performs out and

play05:28

about in the wild whenever buying a

play05:30

device like this you wanna use it to its

play05:31

maximum potential and if i was just

play05:33

gonna be working at home i might as well

play05:35

buy a computer in my case i'm always

play05:37

taking my son out to different locations

play05:38

and being able to continue to work and

play05:40

do some stuff while he's playing always

play05:42

makes life a lot easier here i continued

play05:44

my sign into github and as soon as it

play05:46

authenticated my vs code was ready and

play05:48

not only that it actually installed all

play05:50

the same extensions that i'm using on my

play05:52

other devices which is great today is

play05:54

day three and i want to get into some

play05:56

real coding today this means i need a

play05:58

real shot of coffee and i'm hopefully

play06:00

going to get a real server up and

play06:01

running that might host a website on a

play06:03

development board other things that i

play06:05

think are important are just being able

play06:07

to download repositories maybe run up

play06:09

databases and do some builds to see the

play06:11

difference in build time between a

play06:13

device like this and a windows device i

play06:15

want to install node.js i had a look at

play06:17

some articles and it looks a lot easier

play06:19

than installing vs code of course i've

play06:22

been wrong before so let's do some quick

play06:23

digging to see what's involved and how

play06:25

we can install it i headed over to the

play06:27

node.js website and i got a couple of

play06:29

options for downloading it for windows

play06:31

but that's not what i'm on so i'm gonna

play06:33

select other downloads and have a look

play06:34

if there's an arm version there is

play06:36

there's an arm version seven and version

play06:38

eight so i'm not too sure which one to

play06:39

use and i think i need to do a little

play06:41

bit more research to find out which

play06:42

option to select i googled chromebook

play06:45

with nodejs to see what other people

play06:47

might have done and from what i can see

play06:49

most of them actually installed it

play06:50

through the terminal there is an actual

play06:52

command that allows you to install

play06:53

node.js so i'm going to install node

play06:55

version 14. i then copy-pasted this

play06:57

command straight into my terminal to

play06:59

execute just like any good developer but

play07:01

of course i did do double check and from

play07:02

what i could see it was downloading

play07:04

straight from the node website and

play07:05

running a sudo bash to actually execute

play07:08

that node installation this might take a

play07:09

while but once it's done i should be

play07:11

able to simply open up node by typing in

play07:13

node and then i should have access to

play07:15

the shell so i can write in some

play07:17

javascript commands success this worked

play07:20

and i've got node up and running so now

play07:22

not only can we code using vs code we

play07:24

can also run up an application on

play07:26

node.js and i'm thinking maybe we'll

play07:28

start off with a create react app just

play07:30

to get us started since i've got node up

play07:32

and running i can run npx command so i

play07:34

typed in npx create react app and my app

play07:38

here i want to find out if i can

play07:39

actually host a web server with create

play07:41

react app as well as run it up in vs

play07:43

code and start making some changes

play07:45

success looks like create react app

play07:47

installed along with all its node

play07:49

modules this means i can open it up in

play07:51

vs code which i've done and it's ready

play07:53

for me to start hosting as a web server

play07:55

as well so let's give this a shot i'm

play07:57

going to close down the terminal and

play07:58

expand out my instance of vs code

play08:00

because i usually prefer to run with the

play08:02

terminal inside vs code then i'll run

play08:04

npm start and we'll kick off this

play08:06

application one thing i immediately

play08:08

notice though is that these terminal

play08:10

fonts are terrible i think my coding

play08:11

fonts didn't carry across to the

play08:13

chromebook and i'll have to do that

play08:14

later but the application is up and

play08:16

running now so i can officially say that

play08:18

you can build react applications using

play08:20

the chromebook which i'm quite pleased

play08:21

to see it seems to work just like normal

play08:24

with the port 3000 being used for the

play08:25

web server as well as real time changes

play08:27

whenever i make them in vs code i think

play08:29

it's time for a real project now i

play08:31

previously created an rpg game with

play08:33

astradb so i'm going to clone this

play08:35

project i jumped into github to copy the

play08:38

syntax for its url and went to git clone

play08:40

it but i just realized something i don't

play08:42

actually have git installed so i better

play08:43

install that first since i'm running

play08:45

this linux distro any linux command

play08:47

should work so i'm gonna run a sudo app

play08:49

get space install space kit okay that

play08:52

ran successfully and now it's actually

play08:54

time to clone our project so i'm gonna

play08:56

do a git clone space and i'm gonna paste

play08:59

in the url of my project here in github

play09:01

but just as i was doing this i realized

play09:03

i didn't actually set up a private key

play09:04

to actually talk to github on this

play09:06

device this will take a little bit of

play09:07

work so what i'm thinking is just

play09:09

downloading the files manually npm

play09:10

installing them and giving them a run to

play09:12

see how they go once they were

play09:14

downloaded i was happy to see that i

play09:15

didn't have to download any unzipping

play09:17

software and i could simply drag and

play09:18

drop them straight into my computer i

play09:20

can open them up now in the terminal and

play09:22

browse into them and hopefully npm

play09:23

install all the packages i need to get

play09:25

them up and running since i want to see

play09:26

the performance of this machine i can

play09:28

definitely tell you that it takes a

play09:29

little bit longer to load up projects on

play09:31

this device while the drawback is that

play09:33

it's a little bit slower the benefits

play09:34

are that if you're someone new to web

play09:36

development you're not going to be

play09:37

running up large projects and most of

play09:39

them should be able to be installed and

play09:40

built quite simply well that is unless

play09:42

you install the wrong version of node.js

play09:44

and your project doesn't build

play09:45

successfully in my case i was running a

play09:47

very old version of a lot of the files

play09:49

which were probably compatible with node

play09:50

version 8 and i don't really want to

play09:52

update so i'm going to run up a

play09:53

different project to test it out and

play09:55

what i found was that it actually took

play09:56

about the same time on my computer as it

play09:58

did on this device be aware i don't have

play10:00

as many node modules or plugins as other

play10:03

repos might have but at least for a

play10:05

beginner project this is quite useful

play10:06

then i also tried building the project

play10:08

and even though it's a small project it

play10:10

still took about the same amount of time

play10:11

as my computer so quite impressive to be

play10:13

honest i'm pretty impressed so far with

play10:15

the chromebook today is the fourth day

play10:17

and i want to try to use this device

play10:19

outside one of the things i noticed

play10:21

though was that the screen isn't that

play10:23

great in terms of brightness it's

play10:24

actually kind of difficult to see vs

play10:26

code on the device and i find that this

play10:28

sunlight actually reflects quite a lot

play10:30

so i tried to go under a tree to see if

play10:32

i can get some shade and hopefully view

play10:34

the screen a little bit better the

play10:35

battery however has been quite good so

play10:37

far i've never had to really worry about

play10:39

the battery charge and i've had quite a

play10:41

few hours of usage every time i've gone

play10:43

out to use it activities i've done so

play10:45

far included things like checking emails

play10:47

using chrome browsing youtube as well as

play10:49

doing some of the scripts for this video

play10:51

one problem i did find with the device

play10:53

is that it didn't really fit on my lap

play10:54

very well sometimes i tried to

play10:56

reposition to see if i can fit it better

play10:58

but it just didn't work quite well while

play11:00

it's a tablet device and i can use my

play11:02

fingers for it i think i much prefer

play11:03

using this just on a simple desk

play11:05

generally speaking i probably wouldn't

play11:07

be coding with this device outside but

play11:09

if i'm going to be programming inside of

play11:10

a car this is something that i can

play11:12

probably do but if you need to make some

play11:14

last minute changes before you meet a

play11:16

client or you've accidentally pushed

play11:17

some faulty code to github that's

play11:19

crushed the entire system and deleted

play11:21

all the backups then this might be a

play11:22

useful way to make those changes quickly

play11:24

and of course i've never done anything

play11:26

like that and i'm gonna say that i'm not

play11:28

gonna recommend coding in the car so

play11:29

let's move on i've been using this

play11:31

chromebook for just about everything

play11:33

this includes a lot of meetings

play11:34

especially over zoom using the camera

play11:37

which unfortunately isn't that great but

play11:39

at least it gets the job done i also

play11:41

found it quite useful to take with me to

play11:43

client sites because showcasing demos of

play11:45

projects i'm working on is much more

play11:47

effective than trying to explain them

play11:49

so this chromebook really impressed me i

play11:52

came in with really low expectations but

play11:54

everything from the keyboard to the fact

play11:56

that i can get vs code up and running on

play11:58

here and use it to learn programming

play12:00

really was surprising for a device of

play12:03

this cost for just about three or four

play12:05

hundred dollars i can do everything from

play12:07

jump on free code camp and learn how to

play12:08

code two even build react applications

play12:11

or angular or schveldt and build up a

play12:13

web server and have access to all the

play12:15

kind of stuff we normally do in a

play12:17

liganox terminal i think if this is the

play12:19

device you're looking for and this is

play12:20

the area you're in it's just enough to

play12:22

get up and running but if for example

play12:25

you're looking at building mobile

play12:26

applications on react native or flutter

play12:29

this might not be able to serve those

play12:31

needs because it would need a little bit

play12:32

more power and that's where you might

play12:34

need to jump into windows or mac

play12:35

territory but hopefully this gave you a

play12:37

really good idea of what i use this

play12:39

device for how i used it and what the

play12:41

experience is like with it i hope you

play12:43

guys enjoyed this video if you have

play12:45

feedback and ideas on how i can improve

play12:47

the next one like this then let me know

play12:49

in the comments below otherwise i hope

play12:51

you guys hit like and subscribe and i'll

play12:53

see you in the next one thank you

Rate This

5.0 / 5 (0 votes)

Etiquetas Relacionadas
ChromebookCodingVS CodeLinuxBudget LaptopDeveloper ModeNode.jsWeb DevelopmentMobile CodingProductivity
¿Necesitas un resumen en inglés?