Live data from Hacker News

I'm tired of this anti-Wayland horseshit

drewdevault.com

891–892 of 892 posts

Re: I'm tired of this anti-Wayland horseshit

#891

Earlier quoted context omitted.

The only real option for a high-end Unix workstation with heavily integrated software that still exists seems to be the Mac Pro. Linux is really not comparable to IRIX. People keep saying that Wayland needs to be more of an X replacement but it's never clear what that means. You want 3D graphics over the network, that currently means Vulkan, and if you were going to do that, there doesn't seem to be much reason to ti…

I do not know what it means either. I am just gonna think out loud a bit, because I do care about this stuff. But, am also not currently impacted much. Nice place to be for me at least! In a general sense, Wayland is not Unix like, in the same way systemd isn't. X11 is, as were various init systems. And fact is, at the time those things were done, multi user computing was a thing, and it was all done with those ideas…

There's someone else who thinks like me, and well put. Worth every minute of attention.

I remember my early encounters driving me absolutely mad because I did cut my teeth on that 1 seat 1 user environment.I think where I've ended up going in a different way than most is that over the years I keep cracking away at it because I want to understand it. It's an intuition thing, and you never really appreciate the miracle of it until you sit down and come to terms with what X really did. It was the glue between app logic, state, and a constantly floating set of goalposts represented by every possible set of different hardware.

I haven't even torn into the source. It's taken me so long just to grok the other layers of the problem space. Personally, I think the space X11 occupied is one of the most enticing areas of research open to me, even if I never seem to make the time for it.

Abstraction-wise, we assume we carry context with us everywhere, but an X environment driven over a network breaks you of that quite handily, and I don't think the "Cloud"/SOA solves the real life dilemma jist by lifting everything into a browser.

Re: I'm tired of this anti-Wayland horseshit

#892

Earlier quoted context omitted.

> when a massive part of nvidia’s business is supporting Linux (GPGPU stuff) I've spent the last few months doing GPGPU stuff on Nvidia Jetson devices and my experience has been the complete opposite. I've rarely seen something with such bad support and documentation.

I'd love to hear more. I've only used the datacenter and flagship consumer GPUs, which work great. I hadn't heard of Jetson, but looking it up, it's a bummer to hear that something that looks that cool for hobbies doesn't hold up.

Well, don't get me wrong. I do like my Jetson Nano. For a hobbyist who likes to tinker with machine learning in their spare time it's definitely a product cool and there are quite a few repositories on Github[0, 1] with sample code.

Unfortunately… I'm not a hobbyist, I'm not tinkering and the aforementioned repositories are… about it. There is little documentation about

- how to build a custom OS image (necessary if you're thinking about using Jetson as part of your own product, i.e. a large-scale deployment). Ideally, I would like to do that as part of a CI/CD workflow. What proprietary drivers and libraries do I need to install? Nvidia basically says, here's our custom Ubuntu image with the usual GUI, complete driver stack and everything – take it or leave it. Unfortunately, the GUI alone is eating up a lot of the precious CPU and GPU resources, so using their OS image in production is no option for me.

- how deployment works on production modules (as opposed to the non-production module in the Developer Kit)

- what production modules are available in the first place ("Please refer to our partners")

- what wifi dongles are compatible (the most recent Jetson Nano comes w/o wifi)

- how to convert your custom models to TensorRT, what you need to pay attention to etc. (The official docs basically say: Have a look at the following nondescript sample code. Good luck.)

- how do I automize testing of TensorRT models & code? Why isn't there a compatibility layer which allows executing my models on non-Jetson devices / on a CPU (obviously at lower performance, but I don't mind).

- … (I'm sure I'm forgetting many other things that I've struggled with over the past months)

Anyway. It's not that this information isn't out there somewhere in some blog post, some obscure Github repo or some thread on the Nvidia forums[2]. (Though I have yet to find a wifi dongle that works reliably…) But it usually takes you days or weeks to find it. From a product which is supposed to be industry-grade I would have expected more.

[0]: https://github.com/dusty-nv/jetson-inference

[1]: https://github.com/jkjung-avt/tensorrt_demos

[2]: https://forums.developer.nvidia.com/c/agx-autonomous-machine...

Post reply on HN