New Leaks of the Lenovo ThinkPad X1 Nano
131–140 of 147 posts
Re: New Leaks of the Lenovo ThinkPad X1 Nano
#132Re: New Leaks of the Lenovo ThinkPad X1 Nano
#133> 13.0 | 16:10 | 2K | 450nits | 100% sRGB | Optional Touch > Ultra-narrow bezel | 85% STB It is very nice move from the Dell [0], and also now Lenovo to bring 16:10 display in laptops. It was always for me strange decision, when laptop manufactures decided to use 16:9 displays for all, even for pricey, high-end models. I am highly enthusiastic to see 16:10 displays back after ten years, when numerous notebooks had 15…
(full disclosure, It's my first non-thinkpad laptop in decades, and I didn't pay for it, my job did).
Re: New Leaks of the Lenovo ThinkPad X1 Nano
#134I'm glad to see a resurgence of 16:10 screens. I'm waiting to see bezels shrink to the point I'll have a nearly 15" 16:10 screen in a 14" laptop body, not to have a number pad.
Sometimes I feel like the only one who likes bezels. They provide a nice, distraction-free buffer between the screen and the background. You can also pick up sturdier laptops by the bezel, without worrying about getting fingerprints on the screen. Of course, I also like more screen space, so it's a wash in the end. And I prefer small bezels in multi-monitor setups. So I guess I understand why they're going out of sty…
Re: New Leaks of the Lenovo ThinkPad X1 Nano
#135Earlier quoted context omitted.
As a programmer I would really like to have more choices of 3:2 or even 4:3 aspect ratio laptops (because of the added vertical space, which is really much more valuable when working mostly with text on fairly small displays). For 3:2 I'm only aware of the MS Surface and Huaewei MateBook laptops, and Thinkpads were probably the last 4:3 laptops(?).
The MateBook really is a nice looking laptop. The folks I've known that have purchased them have all run into reliability issues within a year (non-booting machines, spacebar stops working, other weird things) I looked into them before I bought my Thinkpad X1C. I still like that screen though.
Re: New Leaks of the Lenovo ThinkPad X1 Nano
#136Earlier quoted context omitted.
Or Firefox. (writing this from Firefox on Thinkpad with 16GB of RAM)
funny thing: firefox is using ~433mb of ram with ~15 tabs (including gmail, graphql playground, youtube). slack alone is using 300mb. discord is using another 300mb.
I remember recently I freed 10GB of RAM just by restarting Firefox. I literally looked at Ubuntu's System Monitor. And I keep everything updated.
Tried to play with settings in about:config, made even worse and reset.
Re: New Leaks of the Lenovo ThinkPad X1 Nano
#137Earlier quoted context omitted.
funny thing: firefox is using ~433mb of ram with ~15 tabs (including gmail, graphql playground, youtube). slack alone is using 300mb. discord is using another 300mb.
Just curious, how many extensions do you have? I'm trying not to bloat my browser too much with them, but have 3-4 privacy related extensions and a couple of utility ones. Right now I have 22 tabs and Firefox uses 5-6 GB of RAM. Restart decreases RAM usage, but Firefox slowly eats RAM again. I remember recently I freed 10GB of RAM just by restarting Firefox. I literally looked at Ubuntu's System Monitor. And I keep e…
that's on linux, latest nightly.
Re: New Leaks of the Lenovo ThinkPad X1 Nano
#138i think 1366x768 resolution on 15.6 inch screen is perfect in terms of UI elements size. like its a sweet spot between to small and too large with enought horizontal area. physical width of such 15.6 inch screen is 34.53 cm so it gives you 0,025285037 cm per pixel. so my "perfect" laptop would have 15.6 inch screen and 16:10 aspect ratio. i would double the resolution in order to avoid fractional scaling and use 200%…
Re: New Leaks of the Lenovo ThinkPad X1 Nano
#139Re: New Leaks of the Lenovo ThinkPad X1 Nano
#140Earlier quoted context omitted.
Running Slack.
Haha it's insane why it would need so much RAM for chat. It's truly insane.
But simplicity is not what they're optimizing for. They're optimizing for productivity -- specifically, how fast a typical corporate webdev shop can go from zero to working app. That's really the only thing that matters, because there's no room for something like Qt in today's move-fast-break-things environment. Qt means developing, compiling, testing, and supporting across multiple platforms which a modern webdev shop may not even be able to do if they had the budget for it (which they don't). Hell, there's barely room for any language besides JavaScript.
So hence, we get Electron and we get memory bloat. And it's perfectly reasonable, given the right perspective.