About Chromebooks

Chromebook, ChromeOS and Google Chrome browser news

I bought a new Chromebook with 16 GB of RAM. Should you?

I’ll get this out of the way right up front and answer the headline question: Probably not.

Since you’re reading, however, I’ll explain what I bought and why I bought it for two reasons. First, it should help some folks save money by not buying more hardware they need in a Chromebook. Second, people who have similar use cases to mine might find the information useful for their own purchase decisions.

So, I ended buying an Acer Chromebook Spin 13 with Core i5-8250U processor, 16 GB of memory and 128 GB of flash storage. This is essentially the same device I reviewed back in November, with the only difference being that model has 8 GB of memory and costs $899.

Acer charges $999 for the configuration I just bought so I was going to purchase this from B&H Photo for $959. Then I noticed B&H had a used, “like new” unit for $819, so I pulled the trigger.

If someone did use this Chromebook, I sure as heck can’t tell. It arrived in the original packaging that was previously opened, and all of the paperwork, protective packing and the power cord. It also had Chrome OS 68 installed, suggesting to me that if was used, it hasn’t been for many months. I immediately upgraded it to Chrome OS 76, which just arrived with many new features. That took all of six minutes. Hello, virtual desks!

Why did I get a nearly top-of-the line Chromebook? Note: I say “nearly” because Acer offers a $1,569 configuration with Core i7, as does HP for its Chromebook X360 14 ($1,248) and Lenovo will as well for the Yoga Chromebook C630, but we don’t know the price yet.

As soon as Google announced its minimum recommended Chromebook specs to run Android Studio, I started thinking about a device like the one I just bought. I code for my Computer Science classes with the Pixel Slate and it works well, but as my apps become more complex and/or I need more powerful developer tools, the Core i5 Y-series processor and 8 GB of memory aren’t going to be optimal.

Chrome OS device emulator in Android Studio

Setting the memory difference aside for a second, there are a few variances between the Core i5-8200Y in the Pixel Slate and the Core i5-8250U in the Acer Chromebook Spin 13. You get two CPU cores capable of running four threads on the Pixel Slate, for example. The U-series Core i5 in the Acer has four CPU cores and can handle eight concurrent threads. There are some other small differences in the Intel HD Graphics chips, chip cache and clockspeed, but those are fairly minimal, not influencing my purchase decision.

And as far as the memory? You have to remember that the Linux container – where developers would run IDEs, or integrated development environments for coding – is running at the same time as Chrome OS and any Android apps you might be using. More memory is always welcome in this situation.

Implementing a linked list stack in Java on the Pixel Slate yay

Long story short, if you do use or plan to use a Chromebook for Linux apps and coding environments within Linux, you’ll really want a device that has the U-Series processors. These can be had with 8 GB of memory, but if you can afford it, doubling up on the RAM will go a long way towards happy developing as well as typical Chrome OS browsing and usage.

Not coding or even running any Linux apps on a Chromebook? You’ll be more than happy with the experience of a Chromebook with a less powerful but recent Intel processor even with just 4 GB of memory. That means you don’t have to spend $900, $1,000 or more. Instead, evaluate your options in the $250 to $450 or so price range and focus on the features that mean the most to you: amount of local storage, screen quality and resolution, weight, battery life, digital stylus support, etc…

Before someone asks the expected “Why wouldn’t you wait for the next Pixelbook, likely arriving in October?”, I’ll tackle that too. Near as I can tell, the processors in the next Pixelbook, code-named “Atlas”, aren’t likely to be any better than the chip in the Acer I just bought.

In fact, they could even be the same ones as in the Pixel Slate. I’m fairly confident in the next Pixelbook chip situation and don’t see the point of waiting for something that won’t likely meet my needs any better and will probably cost more. Assuming I’m correct, I decided to pull the trigger now and just sell one of the two Pixel Slates I use today; I’ll keep one for continued testing and news about the first, and last, Made By Google Chrome OS tablet.

author avatar
Kevin C. Tofel

8 thoughts on “I bought a new Chromebook with 16 GB of RAM. Should you?

  1. Hi Kevin C. ,
    Good for you ! I just bought a used Pixelbook i7 , it’s greased lightning compared to my Acer 14 431 .
    Just wanted to say hi and how much I enjoy You and Stacey on the “Leo Show” , been following you since the Kevin C. and the Krout show .

    Cheers ,
    Barry (dinosaur)

    1. Thanks much, Barry! Yup, the Pixelbook i7 is a big step up from the Acer 14. Enjoy it!

  2. Hi Kevin – I’d be interested to hear your thoughts on a performance difference between the Slate & Spin 13. Chur

  3. Nice article, thanks!

    So this chromebook supports crostini ( linux beta ) ?

    Hans Nieuwenhuis

    1. I wouldn’t have bought it otherwise. ? Most older Chromebooks from 2016 or so support Linux and all new ones after this past May will.

  4. I am developing but not compiling code but I multitask a lot so I also use handbrake in Linux to transcode videos, and at the same time multiple Linux programs, and 30 tabs that over 10 of them are content heavy, 3 of them use extensions (Google Keep, Hangout, and LINE), OpenVPN, playing 1080p video using native player (PiP) or Google music Android player (offline list), connecting to Asus 15.6″ external monitor. My i5/8GB Pixelbook was begging for CPU and RAM upgrade. I am going to get the Pixel Slate i7/16GB to replace my Pixelbook once I get my budget ready. Pixel Slate is my dream machine because I am currently using HP Chromebook x2, I love to use it as tablet with stylus (I don’t draw, but we have a lot of moments that we are trying to obtain information with minimal input, reading news is one of them) and when I need it, I turn it back to laptop. Good but m3/4GB is not working for me. Once I opened only 5 tabs, one of them is Google Hangout, 2x Realtor.ca, Google map, and Google sheet, work on it, put it to sleep for 30 mins, open it, resume working for 15 mins, then open native video player to play a 1080p video, choking like no tomorrow! Never happen on my Pixelbook with that little amount of tabs opened.

  5. I bought a Pixelbook with 16GB and core i7 quite a while back. I code in R and do a lot of number crunching. We have a cluster at work, so big jobs go there, but it is useful to be able to test things out small scale before going there. My previous chromebook was a Samsung, I went Pixelbook because of the RAM, which was really limiting (4GB if memory serves) and because of i5/i7 versus arm, which was another limiting factor: RStudio does not come precompiled for arm and compiling from sources was proving to be impossible. The Pixelbook was my sole device for quite some time until I recently splurged for a Dell monster (i9 and 64GB RAM) that I run under linux. The Pixelbook does remain my main everyday machine. I typically run several linux apps (RStudio, TeXStudio, Inkscape, LibreOffice) as well as Android apps (Squid: I haven’t printed a single pdf document since I got the Samsung, I comment all student manuscripts with that) on top of a healthy number of chrome tabs. Only cases where things go bad is if I run parallel code on 3 cores at the same as a bazillion chrome tabs. So, yes, I will go 16GB again, whatever my next chromebook ends up being. (I could definitely use 8 threads, that’s my only gripe with the Pixelbook.)

Comments are closed.

Scroll to top