Linus Torvalds: 2560x1600 Needs To Be Next Standard


Recommended Posts

Try disabling font anti-aliasing and you'll quickly start seeing individual pixels.

But we have anti-aliasing? Doesn't really answer my question. I suppose I could see AA becoming irrelevant with it, but any gains from turning off AA would be lost with rendering at an increased resolution. So I still don't really see the point unless the performance gain from no AA outweighs the loss from resolution.

I find it hard to believe it makes any actual difference to viewing photos either. Unless it can mysteriously extract additional pixels from the photo data, all it would do is "zoom out" the photo.

He is right, but the OS must be able to scale with the resolution. I don't want everything to be too small to read because of the crazy resolution. Apple and Google seem to be making a good job at scaling iOS and Android to fit any resolution and still being usable.

But yes, when I see that my Galaxy S3 has more pixels than some laptop, it's getting ridiculous.

You could even have a 10000dpi display but until desktop operating systems will do proper DPI scaling on very high resolutions displays it's completely pointless.

Windows scaling starts looking horrible from 200% DPIs and above (cursors and icons all look jagged) and there are still many applications that look horrible or ignore the scaling like Adobe's (also DPI settings seem to be ignored by Metro), OS X cheats by upscaling a lower resolution unless the application is "retina-aware" and Linux is probably the one with most issues but it depends, it can be either somewhat acceptable or horrible depending on the distro/desktop environment.

It is actually quite funny that it was Linus Torvalds complaining about this issue when most linux distributions recommend lowering the resolution on the retina macbooks basically tossing the extra pixels in the trash. If it's not done properly it just becomes a waste of CPU/GPU/power: it would be far better to have a reasonable resolution (1080p minimum?) that works well with the operating system rather than some insanely high-DPI display where everything looks like crap and movies still show with the annoying bars due to weird aspect ratios.

I think Apple approach was the best because they always tried to double the resolutions on their devices to make the transition the least painful they could and on the retina display their use of a whitelist system (only tested applications will work in native mode) has avoided the issues with all the applications that don't render properly. I still wonder why Windows still uses the cheapest scaling algorithms for some parts the UI, it's not like the recent CPUs couldn't scale a 32x32/48x48 cursor.

NOTE: This post is only exclusively about desktop operating systems, not phones or tablets where the UIs have been tailored for DPI scaling from the start.

But we have anti-aliasing? Doesn't really answer my question. I suppose I could see AA becoming irrelevant with it, but any gains from turning off AA would be lost with rendering at an increased resolution. So I still don't really see the point unless the performance gain from no AA outweighs the loss from resolution.

I find it hard to believe it makes any actual difference to viewing photos either. Unless it can mysteriously extract additional pixels from the photo data, all it would do is "zoom out" the photo.

That's kind of the point, we're using anti-aliasing (for nearly everything) because we have such low resolution devices. Increasing the resolution negates the need for anti-aliasing. Photos see an improvement since they're often scaled down for display, showing them at their normal resolution allows for more fine detail.

Compare proper 1920x1080 video to a scaled 960x540 copy, the overall image will be the same, but you'll be missing out on fine detail.

I'm really not sure I understand this trend of squeezing more pixels into the same physical space. Have we suddenly evolved to have mega awesome eyes that can see individual pixels at 5 feet away? :wacko: Using my computer, netbook or phone I can't see the individual pixels unless my eyes are too close to the screen. Maybe I'm not understanding something but it seems like pointless number increases to me, much like camera megapixels.

The point is that breaking the 300 PPI barrier supposedly makes it nigh on impossible to see individual pixels, even at close range. For devices like tablets that are usually used pretty close up it will make a difference.

The point is that breaking the 300 PPI barrier supposedly makes it nigh on impossible to see individual pixels, even at close range. For devices like tablets that are usually used pretty close up it will make a difference.

On a smartphone or tablet it definitely makes sense and you can clearly see the difference. However, I'm using my 27-inch iMac at a comfortable 50 cm away and it already becomes increasingly hard to see the individual pixels. I have no doubt a "retina" iMac will be nicer, but the issue isn't as pressing as on - let's say - an iPhone.

And we'll pay out the rear for it. I can't see a huge difference between my desktop running 1280*1024 (19" CRT) vs my laptop running 1366*768 (15.6"). Maybe it's my need for glasses that blinds me, or it's just a big marketing scam like most crap is.

The standard should be 300ppi for mobile hardware (phones and tablets) and 150ppi for computers (laptops and desktops), considering you're usually not holding the second two close to your face so there's no need to push it as far as mobile devices go. Just think of the clear text and the eyes saved if this was to become a standard.

Right now I'm using a 24" LG @ 1080p, the pixel grid is visible from where I'm sitting if I lean just a bit towards it.

The standard should be 300ppi for mobile hardware (phones and tablets) and 150ppi for computers (laptops and desktops), considering you're usually not holding the second two close to your face so there's no need to push it as far as mobile devices go. Just think of the clear text and the eyes saved if this was to become a standard.

Right now I'm using a 24" LG @ 1080p, the pixel grid is visible from where I'm sitting if I lean just a bit towards it.

I'd argue 330+ for mobile devices, 270+ for laptops, 200+ for desktop displays.

Currently I have:

iPhone 4: 960x640 @ 326ppi (and really good during normal operation)

Nexus 7: 1280x800 @ 216ppi (noticably lower than the iPhone) - this would be better in 330ppi range for day to day usage.

Thinkpad Edge 11: 1366x768 @ 135ppi (unacceptably low) - I would be very happy if this was in the 270ppi range for day to day usage.

Dell U2711: 2560x1440 @ 109ppi (low but marginally better than the Thinkpad) - it would be better if this was in the 200ppi range for day to day usage.

I'm more in line with these later opinions that understand PPI values should vary depending on device type. Resolution is not a simple matter of pixels and PPI. Anyone who establishes their opinion on display standards with just these two values does not understand display ergonomics.

At the lowest level, you want to begin with how far your eyes are from the screen. A smartphone, laptop, desktop, and television are all viewed at different distances--and even then, those distances aren't common for all people. You might sit comfortably anywhere from 1'-2.5' from your laptop display while doing work. Pixel density will have dramatically different effects depending on where you fall in this range.

Once you establish your comfort zone with displays, you need to determine which range of PPI values match it. That is, which PPIs make pixels indistinguishable at the high and low end of this zone (turn off font smoothing if you want to get really serious about it, but at that point you're going beyond what reality will ever throw at you--your choice). Hang on to these two values, because you can map these against the final cost of the display when you make your decision.

Now, take your preference for aspect ratio. Throw it away. It's meaningless. It doesn't matter. It's one of those things people take way too seriously and defend to the death with nothing but flawed anecdotal evidence and studies on FoV they don't even understand. What matters is perceived space. A 24" 16:9 display will have just as much physical vertical space as a 23" 16:10 display, and cost the same or less simply because 16:9 panels are in higher demand. It's not a matter of losing vertical space with 16:9--you're gaining horizontal space.

It's a lot easier to wrap your mind around if you give these two ratios a common denominator. It isn't about 16:10 vs. 16:9 (where the vertical value appears lower). It's 160:90 [16:9] vs. 144:90 [16:10]. This more accurately represents what you get for your dollar.

Now, ask yourself what the vertical height was of the 16:10 display you so fell in love with, and find out what diagonal length a 16:9 monitor has to be to have the same vertical height. Make this your minimum display size.

At this point, you know the physical size of the monitor you want, and the pixel densities to match. Congratulations, you have an informed opinion.

/my 16:9 27" 2560x1440 monitor lets me see more than your 1920x1200 16:10 display ever will, so come off it already. AR doesn't matter.

I think he's right. It's kind of ridiculous to have a 1280x720 (and higher) screen res. on a 4.5" phone, yet have a laptop's 13" screen be only 1366x768px. Maybe the screens don't need to be 2560x1600, but at least have 1600x900 instead of 1366x768.

/my 16:9 27" 2560x1440 monitor lets me see more than your 1920x1200 16:10 display ever will, so come off it already. AR doesn't matter.

The extra space on the top and bottom is useful for us that create and edit 16:9 content. Congratulations, you've completely missed the point of 16:10.

The extra space on the top and bottom is useful for us that create and edit 16:9 content. Congratulations, you've completely missed the point of 16:10.

You're being snarky, but for making it to the bottom of my post, you completely missed the point.

Think, for a second, in terms of actual physical space: actual inches in the physical real world. A 23" 16:10 display gives you extra vertical space to work on 16:9 video, yes. But a 24" 16:9 display gives you the same extra vertical space, PLUS extra horizontal space, while the amount of actual physical space the video takes up on the screen is the same.

THAT is my point. Aspect ratio doesn't matter when the fact is a PHYSICALLY LARGER display is more affordable at 16:9 than 16:10. Let me actually draw a picture for you, because I think this is something people are genuinely having trouble making their brains process. Note that the attached picture is to compare the two aspect ratios where the video frame is given the exact same real-world physical space. You have the exact same space for the video frame, the exact same extra vertical space for editing controls, plus bonus extra horizontal space for whatever you desire, all on a monitor that costs the same price. You only lose the extra vertical work space if you decide to give the video frame more physical area, but at that point you'd need a physically even larger 16:10 display, which would add to the pricetag, and--guess what--a larger still 16:9 display will be available yet again at that same new higher price.

Entirely because of the effect TV panels are having on the cost of displays, it remains economically feasible to always just buy a LARGER 16:9 monitor that can contain the same work space as the smaller 16:10.

This is very, very simple math here. Middle school level stuff. Please, please tell me this isn't still going over your head.

/something to think about: for 2560px wide displays, 16:9 will run you $700, 16:10 will run you $1200. you can either pay $500 dollars for those extra 160px in height, or buy two of the 16:9 monitors. $1200 for 2560x1600, or $1400 for 5120x1440. I would rather buy two slightly shorter displays than be punished with a 50% markup per pixel for one slightly taller display. In pure economical feasibility, telling yourself that 16:10 is the "better choice" is downright lunacy.

post-10281-0-84041300-1351972610.png

It's not about math, it feels unwieldy and doesn't work. You're missing the human element here.

Hang on here. I'm going into extreme detail to communicate my point of view, and all you're going to do is throw out a subjective remark like "it feels unwieldy" and conclude that it therefore "doesn't work"?

I see once you decide to believe something, you completely shut yourself off to even processing contradictory information. Can you even explain why it "doesn't work"? Or do you just say things and expect to be right by virtue of Having Spoken?

Hang on here. I'm going into extreme detail to communicate my point of view, and all you're going to do is throw out a subjective remark like "it feels unwieldy" and conclude that it therefore "doesn't work"?

I see once you decide to believe something, you completely shut yourself off to even processing contradictory information. Can you even explain why it "doesn't work"? Or do you just say things and expect to be right by virtue of Having Spoken?

Your point of view is nonsense, extreme detail, or otherwise. If it doesn't take you 5 seconds to realize the practical benefits of using a 16:10 monitor to edit 16:9 frames, then you're just dense.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Russia was able to invade Crimea because of those people. But my point is that I've personally heard how great it was to be "back in Russia" right afterwards - look how great it is now. I've asked you a question in another comment which you haven't answered, so I'll ask it again: is it better now without "Europrats"?
    • ZimaBoard 2 1664 Starter Kit review: it's a cool and affordable DIY NAS by Steven Parker IceWhale Technology reached out to me asking if I was interested in testing the ZimaBoard 2, and after convincing them to send me the Starter Kit, it arrived at my doorstep in May. A bit of background: it is a Shanghai-based Chinese company founded in 2020, which specializes in single-board servers and personal cloud solutions. From searching around online, user feedback on the company and ZimaOS is mostly positive, so we're off to a good start. In addition, I should probably point out that although they do not have a large portfolio of NAS devices, with just four of what they do offer, they seem to have covered everything from a relatively low-priced entry point with the ZimaBoard 2, right up to the high end, with the ZimaCube 2 Creator Pack that even includes an NVIDIA RTX PRO 2000. Anyway, as already mentioned, what we have today is the ZimaBoard 2 Starter Kit, and here are the full specifications: ZimaBoard 2 Model 832, 1664 CPU Intel Core N150 (4x E Cores/Threads, Max burst up to 3.6 GHz) TDP: 6W (Base) 10W (Max) Graphics Intel UHD Graphics 24 EUs (1.00 GHz) Memory 8 GB, 16 GB DDR5 4800MT/s non ECC SODIMM (soldered) Disk Capacity 60 TB (30 TB x 2) Supported RAID Types TRAID, TRAID +, RAID0, RAID1, RAID5, RAID 6, RAID 10 Storage 2 x SATA 3.0 6Gb/s Ports with Power Bootloader 32 GB, 64 GB eMMC Network 2x RJ-45 2.5 GbE PCIe 1 x PCIe 3.0 (via LPC) USB Ports 2 x USB-A 3.1 (5 Gbps) Display Mini-DisplayPort 1.4 (4K@60Hz) Hardware Transcoding Engine H.264, H.265, MPEG-4, VC-1 Maximum resolution: 4K (4096 x 2160); Maximum FPS: 60 Virtualization Intel® AES New Instructions Intel® Virtualization Technology (VT-x) Intel® Virtualization Technology for Directed I/O (VT-d) Size (H/W/D) 140mm x 83mm x 31mm Weight 0.4 kg (only ZimaBoard 2 device) Power 12v 5A Power Supply Warranty 1 year (Global) 2 Years (EU) OS ZimaOS v1.6.1 MSRP $339, $399 ($548.60) As you can see above, there are two variants of the ZimaBoard 2. The lesser variant has half the eMMC storage and 8 GB less RAM, although it also costs $60 less than the top variant we are testing today. The above pricing is only for the ZimaBoard 2. I put the MSRP of the Starter Kit next to it in brackets, although as of publishing, it is discounted to $534.50. The ZimaBoard 2 started life on Kickstarter and shipped to backers in August last year. It became available via the official website in late 2025 and Q1 2026. This hobbyist NAS contains the still relatively new N150 Intel CPU released in the first quarter of 2025, with support for DisplayPort 1.4, HDMI 2.1, although in this case, the memory is integrated into the board itself, so it will not be possible to upgrade or expand the amount. It also supports AV1 decoding, as well as H.264, VP8, VP9, H.265 (8 bit), and H.265 (10 bit). The different capabilities in the Alder Lake-N (and Twin Lake) series are listed below. Processor E-cores L3-cache Turbo clock GPU GPU-clock TDP Intel N355 8 6 MB 3.9 GHz 32 EUs 1.35 GHz 9 W Intel Core 3 N350 3.9 GHz 1.35 GHz 7 W Intel Core i3-N305 3.8 GHz 1.25 GHz 9 W Intel Core i3-N300 3.8 GHz 1.25 GHz Intel N250 4 3.8 GHz 1.25 GHz 6 W Intel Processor N200 3.7 GHz 0.75 GHz Intel N150 3.6 GHz 24 EUs 1 GHz Intel N97 1.2 GHz 12 W Intel Processor N100 3.4 GHz 0.75 GHz 6 W The CPU is part of the Twin Lake series that sits near the bottom of the N-series, designed for low- powered systems and entry-level laptops, and as such has a base level TDP of just 6W. As I have noted before, we are seeing another NAS with a great amount of RAM. It's important to mention that the ZimaBoard 2's memory is integrated into the base board (which is why they have two variants of it). As a reminder, up until a couple of years ago, it was commonplace to only get 2 or 4GB max on a flagship Synology or QNAP home NAS. Ever since the likes of TerraMaster and more have entered the market with ample RAM sizes included in their NAS offerings, it has gone a long way in forcing the hands of the traditional makers to up their game a bit. First impressions The Starter Kit came in one outer box with several packages inside it (shown above). I forgot to take pics of it because when it arrived, it wasn't clear what was inside, and I had to confirm with my contact that I received the entire Starter Kit. In the box ZimaBoard 2 ZimaBoard 2 HDD Expansion Bracket + PCIe card frame Zimaboard Mini DisplayPort Male to HDMI Female Cable 4K 60Hz Zimaboard PCIe 3.0 x4 to Dual NVMe M.2 SSD Adapter Card Quick guide [full online guide] Limited warranty notice Screws Design Where to start? You'd be forgiven for mistaking it as an SSD enclosure if not for all the ports on it. It is completely made out of metal, and the top is an entire heatsink. It has a premium feel about it, but it definitely looks like a hobby device. As you will see, the completed build looks like it belongs in a server or meter closet rather than as a showpiece on someone's desk. On what I am calling the rear, there's a Mini DisplayPort (1.4), two 2.5 GbE ports, with Type A 3.1 USB ports, and then the barrel connector port. Around the front, there are two SATA6 ports with a power connector in the middle. Left side Right side One side is completely free of ports. On the other there's a slit that allows for the feed of a CPU fan cable, and a PCIe 3.0 X4 slot. Top Bottom The top is entirely made up of a heatsink except for the extended height for the I/O on the rear. Around the other side, you can find the ZIMA branding and some regulatory information stamped near the bottom. As you may see from the bottom of the ZimaBoard 2, it scratches quite easily from just moving it around on my Ikea island. Teardown Before we get started, let's have a look at this thing on the inside. The steps to get to the board are as follows: Remove the four smaller Torx screws on the bottom of the ZimaBoard 2; Remove the four larger Torx screws on the sides of the device; Carefully unstick the CMOS battery from the PCB; Remove two Phillips screws on the PCB; Lift out the PCB. Yes, as you can tell from the instructions, you need three different tools to remove Torx and Phillips screws (10 in total), and unhelpfully, one of the screws is located under the CMOS battery, which is stuck onto the PCB. Building Now comes the fun part. Because the ZimaSpace website does not provide any guidance on how to put the Starter Kit together. They only have guidance for connecting the CPU fan. However, they did upload a video to their YouTube channel that shows the entire process. To install the fan, first remove the four screws on the bottom of the ZimaBoard 2, then on the inside, there is a CPU FAN connector where you can attach the fan, reattach the ZimaBoard 2 frame, and feed the fan cable through the provided slit. Then remove the nearest screw on the side and attach the fan frame to the side of the device using the same screw. ZimaBard 2 screws Aligning the screws Bottom view Remember those four screws we removed to access the CPU FAN? Longer screws are provided in the box with the HDD Expansion Bracket, which is what you will now need to attach the ZimaBoard 2 to it. Helpfully, the orientation on how to attach it is made obvious when the frame can only be screwed on at the same overall length as the ZimaBoard 2. If you do it the wrong way around (which is what I did initially) one side hangs off the frame, and it becomes difficult to attach the PCIe Adapter Card cable. PCIe card frame Other side PCIe slot connector Next, it's time to attach the PCIe card frame, which is fastened with the help of 3.5-inch SATA HDD (3 screws). These are toolless screws that you can just use your fingers to fasten them with. Then it is time to connect the provided PCIe cable with the slot connector on one side of the ZimaBoard 2, feed it through the bottom of the HDD frame, and fasten it with two standoffs. Both bracket options 2280 standoffs with 2x 4TB MP44Q The PCIe 3.0 X4 card comes with a short bracket option, handy if you decide to place it inside a different NAS or rack server, but here we need the long bracket. Oddly enough, the M.2 standoffs were preinstalled into the 22110 position, but extra standoffs are included in the box, which I installed at the 2280 position for our use. I added a couple of MP44Q M.2 PCIe 4.0 SSDs (2 x 4TB) that can be availed on Amazon for $478.99 (the lowest price for 3 months) that TEAMGROUP supplied us with Then we have the almost completed build, you just need to push the card into the PCIe slot. Unfortunately, IceWhale Technologies did not provide a screw for the PCIe card frame (this is also apparent in their own video). Here it is at several different angles, with the last pic showing the SATA Y-Cable connected to the two WD Red Plus 4TB drives. Setup and Usage Next, you connect your cables to the I/O, and the ZimaBoard 2 powers on automatically, as there is no power button on the device. Power is controlled through the Settings in ZimaOS. BIOS The ZimaBoard 2 includes an Aptio BIOS from American Megatrends [1, 2, 3], and you can setup pretty much everything here including the boot order, which is locked to the UEFI OS, however above that choice you can enable or disable booting to a SATA/USB bootloader so this would still allow you to switch to an alternative bootloader and boot from it, or disable it to instead always start from the first disk with an OS installed on it. Initial Setup Upon connecting to the LAN and booting up, the ZimaBoard 2 can be reached by navigating to the IP address (shown if you have a monitor connected), or you can find it using the ZIMA Client desktop application, which is essentially a Zima device finder. Initializing the ZimaBoard 2 The ZimaOS setup process is pretty straightforward, through a wizard, and in full above, it basically consists of setting up an account and some handy tips, and that's that! Post Setup (ZimaOS update) Upon first boot, you are alerted that there is a ZimaOS update from 1.5.0 to 1.6.1, which I applied; the full process is shown above with the changelog. ZimaBoard 2 Storage Setup Next, it is time to set up the storage. ZimaOS actually throws everything onto the eMMC flash drive; it is also the default location of AppData, which is definitely something to be wary about, as the 45GB available storage could fill up quickly. HDDs I first attempted to create a Storage Pool using the two 4TB WD Red Plus NAS drives, and got an error message: After several attempts and then looking online, I discovered it was a bug with ZimaOS where the fix was simply to reboot ZimaOS and then try again, this time I was able to create a RAID mirror using the two drives. SSDs I did the same for the SSDs, as you will see in the above gallery, when I created the second Storage Pool, it only allowed me to select available drives. ZimaBoard 2 AppData ZimaOS comes with an App Store that includes a repository of almost 400 apps, so you will be able to find most of what you'll need for a NAS (although after a quick search, I wasn't able to find a Surveillance Manager), and now comes the important part: moving the default AppData location off the 45GB eMMC and onto a larger volume: Open Settings Then Apps Then, in the Select a new location field, click on the new Storage volume you want to move it to (in my case, the Apps Storage Pool), which is the SSD RAID mirror. Confirm the Migration warning Be praised! You can also do this for Docker (which by default installs onto the 45GB eMMC flash drive) and the User database. Plex Setup Next, I tested the configuration by installing the Plex Server app from the App Store. The library folders must already exist (which I placed into the Storage Pool). Plex Server setup is straightforward and requires very little configuration. In my case, all I had to do was add the media path I just created, which you can also browse to using the folder icon in the path field. In addition, you can now map the new Media library in Windows Explorer using the Zima Client. Oddly enough, it is not possible to access the ZimaBoard 2 over the Network Neighborhood; you must map drives using the client, which is shown in the last image in the above gallery. I watched one of my Blu-Ray rips, which is Dolby Vision with Dolby Atmos, and the content played fine with no stuttering or buffering, which is what anyone needs in this scenario. ZimaBoard 2 Zima Client mobile app There's also a client for mobile. It is pretty barebones, as shown in the above gallery, for example, the Apps screen launches the WebUI for that app, and the Backup must be done manually. On opening Backup, you can select internal storage folders on your phone to backup to the ZimaBoard 2's storage, and although this is constantly scanned, the backup action itself must be manually triggered. There is an option to allow foreground backup (last image in the above gallery), but this basically means the queued backup gets triggered when you manually open the app. Benchmarking SATA PCIe 3.0 X4 A CrystalDiskMark test on a mapped network drive from within a Windows 11 25H2 PC (image above) connected over a 2.5 GbE was well within acceptable ranges. Writes were generally better on the SSD RAID mirror. SATA PCIe 3.0 X1 I also ran the NAS Performance tester, which tests the link speed performance. As you can see, it pretty much maxes out the 2.5GbE connection. Of course, you can also opt to bond the two 2.5 GbE connections for a bit more umph, but I didn't do that. Thermals Top PCIe card SATA HDDs Next, I measured some hotspots while playing content on Plex. It's fair to say this will perform better than a NAS that is enclosed in a metal or plastic case, as almost everything storage-wise is exposed! Anyway, the ZimaBoard 2 did not break a sweat with Plex streaming or disk benchmarks. ZimaOS Factory Reset ZimaOS does not include a factory reset option. Instead, you have to download the ZimaOS image and flash it to the eMMC manually. The flashing process is shown in the above gallery. The steps to do so are listed below: Download the ZimaOS image here; Open BalenaEtcher (Run as Administrator) and select the image; Select your inserted USB drive (min 8 GB) Flash to it; Connect your USB drive, monitor, keyboard, USB hub (optional), mouse (optional), and network cable (recommended) to the ZimaBoard 2; Connect power and press F11 continuously; Select your USB drive starting with UEFI in the boot device menu; Press Enter on the Install ZimaOS option; Select /dev/mmcblk0 (MMC) flash drive as target; Confirm with (three times) to wipe the target disk; Wait a couple of minutes while ZimaOS installs; Remove the USB drive and confirm with a reboot; Your ZimaBoard 2 has been factory reset. However, you don't have to stick with ZimaOS, in fact the company also offers official CasaOS images, that are based on Debian; or as they say themselves, put anything you want on this "hackable single board server" it's up to you. Conclusion I had a lot of fun putting this together. I've custom-built all my own PCs and servers since the 90s, and this is the first time I have had to put a NAS together. Even if the actual base ZimaBoard 2 was already a completed build, it still feels pretty custom. I just wish that IceWhale Technology included a getting-started guide in the box for the Start Kit, which would have really completed this kit. Instead, I had to search for the official video on the YouTube channel to make sure I wasn't doing anything wrong. So who is this for? Definitely the hobbyist who is comfortable building their own PC and servers. It also has a much smaller footprint than its nearest equivalent (in terms of specs), like the Beelink Me Pro, which is another NAS I will be testing soon. Although the Beelink does not come with the PCIe 3.0 X4 expansion, the ZimaBoard 2 Starter Kit suddenly looks to be a great bargain, even if it only offers the two 3.5-inch bays over the four in the other example. It makes a lot of sense to use Intel's N150 chip inside a NAS; it is more than capable of doing what the ZimaBoard 2 is intended for, media streaming and backup. It also looks like the IceWhale Technology staff are quite active in the official forums helping people with issues they come across with ZimaOS and the devices, peer support seems to be good as well, I was quickly able to find why I was not able to create a new Storage Pool in ZimaOS v1.6.1 even though that is quite a serious bug, hopefully it will be fixed in the next update. If you are comfortable with the command line and Docker, you'll be fine. You can do great things with this hardware. This was my first time with ZimaOS. It seems a bit barebones in comparison to the likes of Synology DSM, TOS, and UGOS, but it has a ton of apps to get you started with your home or small business NAS. Where to buy As of publishing, IceWhale Technology is running a discount of up to 5% for the Starter Kit. If you opt to get just the ZimaBoard 2 itself, it does come with a SATA Y-Cable, so you will be able to connect up to two 3.5-inch HDDs to it. ZimaBoard 2 1668 Starter Kit for $534.50 on Amazon US (was $548.60) ZimaBoard 2 832 Starter Kit for $372.88 on Amazon US (was $390.60) Zimaboard 2 1668 (16GB+64GB) for $419.90 on Amazon US Zimaboard 2 832 (8GB+32GB) for $359.90 on Amazon Disclosure: IceWhale Technology provided a free sample without any editorial input or review pre-approval. Good to know The Amazon link is U.S. specific, and not available in other regions unless specified. We only use first-party seller links (at the time of article publishing); ensure that you purchase from a first-party seller link only. Check out Today's Deals on Amazon | or our recent tech deals. Become a Prime member (for Students or SNAP) via Neowin Get Prime Access - Prime for half price (for qualifying Medicaid, EBT, SNAP) Subscribe to Prime Video, Audible Plus, Music Unlimited or Kindle Unlimited via Neowin As an Amazon Associate, when you purchase through links on our site, we earn from qualifying purchases.
    • It's in the Insider's group so yes it's technically beta, though these days it's hard to see much of a difference unless you opt for the most extreme beta builds, which I don't. When I moved here from the Release Preview channel I did so primarily because I wanted to see how well the restored taskbar functionality (restored from Win10, and earlier) is working and whether it was time to finally abandon SAB--and it is--working fine, so far. Not as polished as SAB, but it'll do for me.
    • I've been using MWB Premium for a number of years so that along with Windows updates and updated browser should be fine. Thanks for that.
  • Recent Achievements

    • Week One Done
      flexorcist earned a badge
      Week One Done
    • One Month Later
      Woland13 earned a badge
      One Month Later
    • Week One Done
      Woland13 earned a badge
      Week One Done
    • One Year In
      bernmeister earned a badge
      One Year In
    • Week One Done
      Scoobystu earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      488
    2. 2
      +Edouard
      220
    3. 3
      PsYcHoKiLLa
      147
    4. 4
      Steven P.
      74
    5. 5
      FloatingFatMan
      70
  • Tell a friend

    Love Neowin? Tell a friend!