Hacker News new | past | comments | ask | show | jobs | submit login

Since I've bought the Surface Pro X, I can't go back to laptops with fans and poor battery life. The hardware is great.

But Windows is still bad. It can't even display the good clock, as an example of inacceptable bugs.

If I could find the same tablet-laptop format, with ubuntu support, that would be perfect, well until Android gets proper desktop support.

Wireless Dex by Samsung is very promising, but the perfect portbale monitor isn't there yet.




Yeah, I've been keeping an eye on USB4 and WiFi 6E - and avoiding new devices for the time being - for this exact reason. My dream setup involves a litany of dumb displays in different form factors - VR, tablet, desktop, or whatever else - that I can power from one primary device, rather than buying a slew of discrete systems that'll be compromised on spec in order to accommodate larger screens etc. [1] But the I/O for that won't quite be there until sometime next year.

Add to the mix GKIs; AOSP's recent ability to boot from mainline; and the ensuing implication that all of these new adaptive shells being developed rn for the PinePhone could be reused on an Android device [2]; and the thought of 2021 has me salivating.

[1] Mostly, anyway. Some stuff would still be purpose-built, but realistically the main limiting factor for my phone as a daily driver at this point is the form factor.

[2] Assuming bootloader unlock, at least until we see how DSUs play out.


fwiw, I've been using RDP quite productively on my anemic Thinkpad to remote into my desktop computer which is spec'd for deep learning tasks. The latency is great on my local network, and fine over ZeroTier.


How involved of a setup is RDP if most of your systems aren't Windows? I haven't fallen far down the rabbit hole of remote device management, outside of some basic familiarity with SSH. (One particular use case I've been itching to try, but have no idea where to start, is using one system as a secondary display for another. Can an RDP session do this, or is it limited strictly to mirroring?)

Incidentally ZeroTier is new to me, and an interesting rabbit hole in itself (along with the BSL, which is also a first-time read) since I'm in a similar spot with VPNs.


ZeroTier is a breeze to setup. I'd like to use WireGuard, but it wasn't immediately obvious how I'd achieve a "bridged lan" setup. I had used SoftEther for some time but my configuration was brittle.

I RDP into my Windows desktop from my laptop running Ubuntu and my iPhone without trouble. I use Remmina on Ubuntu[0], and the Microsoft RDP app [1] on iOS.

Before this I was fiddling with TightVNC and a reverse SSH'ing from Window, but ultimately RDP through ZeroTier was (surprisingly) the easiest and most stable way I acheived.

[0] https://remmina.org/

[1] https://apps.apple.com/us/app/remote-desktop-mobile/id714464...


> If I could find the same tablet-laptop format, with ubuntu support, that would be perfect, well until Android gets proper desktop support.

Fedora runs quite well on lots of 2-in-1 pc's (e.g. tablet form factor plus detachable keyboard) these days. I've not really tried Ubuntu, but the hardware tends to be a lot fiddlier than typical laptops or desktops and Fedora has better support for it than Debian-derived distros in my experience. And the GNOME desktop from Fedora works quite well as a "pro" tablet environment.


How is Linux support nowadays? It has an UEFI so a kernel should boot, but last time I checked there were lots of driver issues.


https://github.com/aarch64-laptops/build is where the instructions to run Linux on Windows/arm64 devices. Note however that the Pro X isn't quite supported yet.


What's the clock issue you're having?


My Surface Pro X currently displays 14:31.

I'm in France, it's 13:27. I'm confused about how one can mess so much with this basic feature. It's not even a timezone issue !


Are you dual booting perhaps? I had this issue on my desktop where linux would display the proper time, but windows would be an hour off no matter what I did. It turns out linux wrote the time it got over NTP to the hardware clock as UTC(the correct way). Windows would then read the hw clock but interpret it as UTC+1(my timezone). Here the relevant archwiki entry: https://wiki.archlinux.org/index.php/System_time#UTC_in_Wind...




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: