FizzyOrange

joined 2 years ago

I think this could have been about 1/4 the length. Fairly basic stuff by modern standards and you don't need so many words. It is all correct at least, as far as I could see!

[–] FizzyOrange@programming.dev 2 points 4 days ago

I mean yeah I guess that's its primary purpose if you totally ignore the fundamental thing it's meant to be doing.

It's like saying the primary purpose of a seatbelt is to be easy to fasten and unfasten.

[–] FizzyOrange@programming.dev -1 points 4 days ago (3 children)

Of course I wouldn't write in raw machine code, or even assembly. We invented higher level languages that are more powerful and easier for humans to use...

But the purpose is still to make machines so stuff!!! I'm not just writing code so that other humans can marvel at my algorithms.

This is so freaking dumb.

[–] FizzyOrange@programming.dev 1 points 5 days ago

Make computers do stuff for what purpose?

For whatever task you're trying to get them to do. Predict the weather, solve an equation, format a document, etc. Computers can do useful things. We program them so that they do those things.

This is the most ELI5 thing I've ever written. If you actually understand programming and you don't realise that it exists to make computers do things then you're surely just being deliberately obtuse.

[–] FizzyOrange@programming.dev -2 points 5 days ago (7 children)

This is stupid. The whole point of programming is to make computers do things. Before computers, "code" was just hand wavy equations. Sum from 1 to n stuff.

Yes it is designed so that humans can understand it, but the point is to make computers do stuff. Very obviously.

[–] FizzyOrange@programming.dev -5 points 5 days ago (9 children)

Code is primarily to communicate from human-to-human, and only incidentally for computers to execute

Uhm what? No. That is a stupid thing to say. It is primarily intended for computers to execute, but in a way that humans can understand.

[–] FizzyOrange@programming.dev 8 points 6 days ago (1 children)

Yeah... I mean they should have just copied whatever video conferencing platforms do because they all work fine behind corporate proxies and they also don't suffer from this "increasing delay" problem.

I haven't actually looked into what they do but presumably it's something like webrtc with a fallback to HLS with closed loop feedback about the delay.

Though in fairness it doesn't sound like "watching an AI agent" is the most critical thing and mjpeg is surprisingly decent.

[–] FizzyOrange@programming.dev 4 points 6 days ago (1 children)

That is not actually a "data race". It is a race condition for sure, but a data race is a very specific thing - where two threads access the same location at the same time and at least one is a write.

That could be unsafe in Rust because it might lead to reading "impossible values" like an enum that isn't equal to any of its variants. Therefore safe Rust must prevent it or there's a soundness hole.

[–] FizzyOrange@programming.dev 20 points 6 days ago (4 children)

Doesn't say anything you didn't already know. Probably written with AI.

Also the conclusion is wrong:

Neither approach is universally superior.

The Rust approach is obviously superior.

[–] FizzyOrange@programming.dev 1 points 6 days ago

Squarespace is very different to Wordpress.

But also you didn't really specify how serious this site is. Is it meant to be a proper business or just someone's personal site? For the latter Squarespace would be fine. E.g.

As for maintainability, it depends on whether the customer wants to pay you again every time they need to modify things. Many wouldn't want to.

[–] FizzyOrange@programming.dev 1 points 6 days ago (2 children)

Uhm no? What makes you say that?

[–] FizzyOrange@programming.dev 1 points 1 week ago (4 children)

Yeah I wouldn't necessarily recommend wordpress. Probably Squarespace is better.

25
submitted 9 months ago* (last edited 9 months ago) by FizzyOrange@programming.dev to c/linux@programming.dev
 

Edit: rootless in this context means the remote windows appear like local windows; not in a big "desktop" window. It's nothing to do with the root account. Sorry, I didn't come up with that confusing term. If anyone can think of a better term let's use that!

This should be a simple task. I ssh to a remote server. I run a GUI command. It appears on my screen (and isn't laggy as hell).

Yet I've never found a solution that really works well in Linux. Here are some that I've tried over the years:

  • Remote X: this is just unusably slow, except maybe over a local network.
  • VNC: almost as slow as remote X and not rootless.
  • NX: IIRC this did perform well but I remember it being a pain to set up and it's proprietary.
  • Waypipe: I haven't actually tried this but based on the description it has the right UX. Unfortunately it only works with Wayland native apps and I'm not sure about the performance. Since it's just forwarding Wayland messages, similar to X forwarding, and not e.g. using a video codec I assume it will have similar performance issues (though maybe not as bad?).

I recently discovered wprs which sounds interesting but I haven't tried it.

Does anyone know if there is a good solution to this decades-old apparently unsolved problem?

I literally just want to ssh <server> xeyes and have xeyes (or whatever) appear on my screen, rootless, without lag, without complicated setup. Is that too much to ask?

 

Does anyone know of a website that will show you a graph of open/closed issues and PRs for a GitHub repo? This seems like such an obvious basic feature but GitHub only has a useless "insights" page which doesn't really show you anything.

 

Very impressive IDE integration for Dart macros. Something to aspire to.

view more: next ›