136
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 25 Dec 2025
136 points (87.0% liked)
Programming
24051 readers
579 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
This is a really good point.
This post is a great example of what will skipping a research and just trusting the first solution you find lead to.
When you are researching the thing yourself, you usually don't find the solution immediately. And if you immediately have something that seems to work, you're even less likely to give up on that idea.
However, even taking this into account (because the same can probably happen even if you do research the thing yourself - jumping to a first solution), I don't understand how it's possible that the post doesn't make a single mention of any remote desktop protocols. I'm struggling to figure out how would you have to phrase your questions/promts/research so that VNC/RDP, you know - the tools made for exactly the problem they are trying to solve - does not comes up even once during your development.
Like, every single search I've tried about this problem has immediately led me to RDP/VNC. The only way how I can see the ignorance displayed in the post is that they ignored it on purpose - lacking any real knowledge about the problem they are trying to solve, they simply jumped to "we'll have a 60 FPS HD stream!", and their problem statement never was "how to do low-bandwith remote desktop/video sharing", but "how to stream 60 FPS low-latency desktop".
It's mindboggling. I'd love to see the thought and development process that was behind this abomination.