Doods

joined 2 years ago
[–] Doods 6 points 1 year ago* (last edited 1 year ago)

This one in particular I am against. (it's not like it's possible in rust anyway)

[–] Doods 8 points 1 year ago (13 children)

A semi-rolling distribution, with access to Ubuntu's many PPA's, and easily removable extensions that reveal the lovely vanilla Gnome experience, it's great!

Also they are making a Rust desktop, which I am currently running, though not daily driving.

[–] Doods 2 points 1 year ago

Agreed, and upvoted.

[–] Doods -3 points 1 year ago* (last edited 1 year ago) (2 children)

It has a long-lasting C coding standard, they call it the standard since it was the only language anyway. Then, they made a newly conceived Rust standards, which ignore everything the original standard stood for. (Note the strong language in the post's first quote, it's from the original standard)

[–] Doods 5 points 1 year ago* (last edited 1 year ago) (2 children)

having five times more work to use tabs for indentations and spaces for alignment and thus having to use visual whitespace of some kind.

Excuse me. What does that mean? (also see my reply to 1rre)

[–] Doods 5 points 1 year ago* (last edited 1 year ago) (2 children)

The kernel had a consistent style before rust was even an idea! Who do you think has started this inconsistency? (Maybe not, what does someone like me know about the kernel anyway)

[–] Doods 1 points 1 year ago* (last edited 1 year ago)

~~But how else are you going to enforce a specific line size?~~ (I remembered formatters exist, don't mind this)

I was thinking of something else, something better, but I do not know if it exists, I'll say it:

The thing I don't like about space indentation is how you can individually delete and select each space while editing, which is aesthetically unpleasing and error prone, which makes a formatter necessary. Using spaces is also weird in the sense that indentation is supposed to be a block of continuous whitespace, not little things joined together.

However, using tabs creates inconsistent results when copying code to a browser or online view in general.

My idea is: configure your editor - ideally through .editorconfig - to interpret 8 continuous spaces as a tab, and display them as such, and when the time comes to save, you tabs are actually saved as 8 spaces, which solves both the aesthetics and portability problem.

Is this possible? does this already exist? I do not know.

Edit: I forgot your second paragraph

Maybe it's because I use 18.5 inches and 1366x768*, but an 80 character long line already makes me shift my eyes in a way I prefer not to. Low line length is just comfortable.

It's worth mentioning that I recently increased my coding font size to Neovide's default (from 12 -> 14), which made me realize why people do things like Ok(()), sticking parentheses look weird on low font sizes.

I believe that limiting indentation - to 3 - makes code better, an opinion I based on the Linux guide and a video with good animations.

*: I only needed to fix it once in the last 10-14 years; I don't remember anymore. Why change what's working? it'll only make playing video games awkward needing to pipe everything through Wine's FSR.

Speaking of that one repair job, the repairman just replaced all of the monitor's insides with another model's, and now I cant tweak brightness or contrast or use anything but auto adjustment.

which you happen to have configured to 8 spaces locally because you’re some sort of masochis

Edit II:

which you happen to have configured to 8 spaces locally because you’re some sort of masochis

8 space tabs have been the default since the K&R days.

Tabs being 8 spaces has been the norm since the typewriter (actually not)

Despite the fact that five characters were the typical paragraph indentation on typewriters at that time, the horizontal tab size of eight evolved because as a power of two it was easier to calculate with the limited digital electronics available.[citation needed]

Why do people hate them that much nowadays?

Edit III:

I think the intersection between people who have a low resolution, narrow aspect ratio screen and people who code in rust is significantly lower than C or C++

Maybe you're right, I should ignore the sunk cost of reading a 3rd of The Rust Programming Language book, and leave Rust to the cool new generation with their HD displays, and non-DIYed setups)**, and social media usage, and their computers are fast so just write it in javascript and forget about older systems and 3rd world countries and the poor and environment hurting emmisions, and just go learn C. I always felt like I fitted in with people 1 or 2 generations older. (I am not actually going to do that, that's a joke)

**: BTW, my speaker's left channel is an old radio that is connected to my speaker's cable. My left speaker broke when I pushed it off the table, served for a good 8-12 years; I still don't remember anymore.

[–] Doods 14 points 1 year ago* (last edited 1 year ago) (7 children)

My emotions just stopped, so I can now think straight.

There are really only 2 changes that - in my eyes - should be made:

  • 8 space-long, hard tabs.
  • 80 character limit instead of 100.

I don't think a tool like rustfmt can affect most of the original guidelines, and it's generally compatible with the OG style by default.

Edit: I - surprisingly - never actually used rustfmt, so I will go now and test before I say something stupid.

Edit II: I just found this on their repo:

Rustfmt is designed to be very configurable.

Edit III: I tested rustfmt with:

hard_tabs = true

max_width = 80

It's great!

[–] Doods 0 points 1 year ago

Or a source-available model.

[–] Doods 0 points 1 year ago* (last edited 1 year ago)

That's what I hear Pop people saying.

[–] Doods 1 points 1 year ago

If the open AI guy made the training data, the hardware, and every electron, then yes.

[–] Doods 0 points 1 year ago (1 children)

So what should we do then? switch to something else? Host our own email service?

I really don't know.

view more: ‹ prev next ›