FizzyOrange

joined 2 years ago
[–] [email protected] 2 points 4 days ago (1 children)

Yeah there's more stuff that runs in the shell. But pretty much all the things you mentioned would work on a VT100 from the 70s. This is about modernising the terminal itself.

Hell, Linux terminal emulators don't even have a "clear screen & scroll-back" keyboard shortcut like Command-K on Mac. There's no command output history, there are no auto-complete popups, editing commands is still extremely basic (no multiline input for example). The command prompt doesn't even have the text editing capabilities of Notepad.

[–] [email protected] -1 points 5 days ago (3 children)

No the point of terminals is not to make people that dislike mice happy. They simply were created before mice were common and haven't been updated at all. This is an attempt to do that.

[–] [email protected] 4 points 5 days ago (1 children)

I don't think this is intended to fundamentally change what a terminal/shell does - it doesn't even go as far as Nushell. It's just about modernising the interface.

[–] [email protected] 4 points 5 days ago

I would add this to the Wikipedia page for .mu, so at least other people don't use it. You can site this discussion as a source.

[–] [email protected] 5 points 5 days ago

Sure, but there are a gazillion forum websites already. I'd just use an existing one. The one D uses is the best I've ever used. I think it's actually written in D, which is a very niche language but way nicer than Ruby.

[–] [email protected] 9 points 5 days ago

Yes, use them. One big advantage is if you hover something in an IDE it will show you the docstring.

If you're writing Python you should be using Pylint (or Ruff) and it has a lint to ensure you write them.

The exception I usually make is for class member variables because it's super weird that the docstring comes after the variable. I think that's very confusing for people reading the code so I normally just use comments instead.

[–] [email protected] 1 points 6 days ago

What on earth are you talking about? I honestly can't even understand what objection you're trying to make.

Wait, wait! Are you under the impression that .at() is a function call and operator[] is ...not? What?

[–] [email protected] 3 points 6 days ago

So much AI. I just want them to make the Process Viewer work so I can figure out what uses all my CPU.

[–] [email protected] 2 points 1 week ago (2 children)

Bounds checks are not punishing you. Obviously the right way to do this would be to make operator[] be bounds checked by default but only if you use -std=c++29 or whatever, and then also add a .at_unchecked() method for when you want to opt out of the bounds checks.

[–] [email protected] 3 points 1 week ago

Any way to do that other than backing them up to another machine/USB drive is too risky IMO.

[–] [email protected] 3 points 1 week ago

The vast majority of people use smartphones for music.

view more: ‹ prev next ›