FizzyOrange

joined 2 years ago

In my experience a lot of these old projects really go out of their way to dissuade contributions anyway. Lots of naysaying "it's always been like that", ancient infrastructure - e.g. insisting on git send-email patches, etc.

Usually the only way it gets resolved is when someone writes a more modern competitor and it starts gaining traction. Suddenly all those improvements that people tried to do and were told were impossible and stupid aren't such a bad idea after all.

I don't think that's the case with Unity but it probably is with things like GCC, sudo, sysvinit, X11, etc.

I remember when this is how browser zoom always worked. It was super janky, everyone hated it and the current "zoom everything" system was seen as a big improvement.

I guess opt-in makes sense. Probably nobody is going to bother though.

Rust doesn't have inheritance like in traditional OOP languages because it doesn't have virtual methods. You have to manually implement methods to delegate to base classes.

Also what is this trash meme?

They don't really let you do anything you couldn't do in Python, they just let you write more elegant code.

Personally I find ML-style languages to be difficult to read. They deliberately leave out a lot of the punctuation that makes code readable leading to code that just looks like a stream of words.

Rust is I think the best option here - it steals most of the good ideas from functional programming but has saner syntax.

Also you seem to be conflating pure languages with functional languages. I also made this mistake because Haskell is probably the best known functional language and it's also pure... But they're different things. OCaml is functional and not pure. You can use mutable variables to your heart's content.

TL:DR learn Rust not Haskell or OCaml.

[โ€“] FizzyOrange@programming.dev 7 points 5 days ago (1 children)

Given the quality of your average Python code this sounds like a terrible idea.

So perfect that everyone uses TeX, and no successors to it were ever developed.

Pretty huge. Going to have to give this another try. I wonder if this will become as successful as Blender.

Also they need to cut the Apple-style quips for every item ("It's written in bold", "Dock your heart out" etc.). It even says "teamwork makes the dream work" at the end. 100% cringe.

Ah that's way more progress than I thought! Last I heard they were still in "you're wrong for wanting this" territory.

[โ€“] FizzyOrange@programming.dev 11 points 1 week ago (3 children)

How are those namespaces getting on?

Using a function is strictly worse than figuring out the formatting at compile time (something Zig also does).

The derives are just shortcuts. You can write everything out long-hand like you would in C++ or Python too if you really want.

Honestly both of these complaints are essentially "why does Rust use macros to make writing code better/easier?".

[โ€“] FizzyOrange@programming.dev 3 points 2 weeks ago (1 children)

Honestly this looks like it sits in the useless middle ground between "proper CI that has all the features you expect" and "just write a Python/Deno script or whatever". I can't see what you gain.

Also you say "no painful YAML pipelines" but it uses YAML??

[โ€“] FizzyOrange@programming.dev 2 points 2 weeks ago (1 children)

TCL & CMake are fully stringly typed. Both pretty terrible languages (though TCL can at least claim to be a clever hack that was taken far too seriously).

25
submitted 10 months ago* (last edited 10 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 โ€บ