@dcz@fosstodon.org
@dcz@fosstodon.org avatar

dcz

@dcz@fosstodon.org

Greybeard but revolutionary. 80-char lines are good for museums.

My tech writing (hire me): https://dorotac.eu/
Open bike computer: https://jazda.org
dcz on libera.chat

This profile is from a federated server and may be incomplete. Browse more on the original instance.

yakkoj, to random
@yakkoj@fosstodon.org avatar

using "git pull origin main || git pull origin master" to update git repos

dcz,
@dcz@fosstodon.org avatar

@yakkoj I see you still haven't seen a repo with both branches present.

dantleech, (edited ) to random
@dantleech@fosstodon.org avatar

Emotional rollercoaster of starting new projects:

  • This is cool
  • I've spent 18 hours on this
  • This is awful
  • I'm awful
  • The world is awful
  • This is cool (goto 1)
  • ... weeks pass_
  • Wow this is great.
  • Almost done
  • lose interest
  • Project abandonned
dcz,
@dcz@fosstodon.org avatar

@dantleech Too real...

dcz, to hacking
@dcz@fosstodon.org avatar

Hey Fediversians, is anyone going to https://gulas.ch ? I'm looking for roommates today.

thelinuxcast, to random
@thelinuxcast@fosstodon.org avatar

Is this what the Nextcloud app for Linux is supposed to look like?

dcz,
@dcz@fosstodon.org avatar

@thelinuxcast I hate this, and this keeps happening.

At least I can fix by manually tweaking the style (but why provide "system" if it doesn't work?)

dcz, to opensource
@dcz@fosstodon.org avatar

The feeling when 87.5% of the discussion under your contribution is about : unreliable CI and insignificant .

Congrats, the project has created a barrier to entry for anyone who hasn't been into it for years already.

Hint: give everyone a freaking that satisfies your needs and let us move on to actual work, without having to redo the same stuff 8 times. Sheesh.

dcz,
@dcz@fosstodon.org avatar

@deshipu Good code formatting by my definition is that which makes people not have to think about it - that is, automated.

Intention does not need to be reflected in style, but in the code itself, and in comments.

dcz,
@dcz@fosstodon.org avatar

@deshipu If all quality of the code is in the style, does that mean that it doesn't matter what the code actually does? Nope, that's silly and not what you mean. The ultimate quality signal is what the code does, plus documentation.

For example, the GNU C syntax makes my eyes bleed, but it can still be amazing quality.

"What" and "why" are important for understanding. "What" is in the execution of the code. "Why" is in the documentation and naming. What knowledge is conveyed by altering style?

dcz,
@dcz@fosstodon.org avatar

@deshipu If what you care is effort spent writing then sure, but it's not the same as seeking quality.

If I wanted to filter by effort, I'd rather have people write poems as a requirement, because that at least can be fun.
Style is similarly independent of actual quality.

I don't see how it helps understanding any more than comments, despite all the problems with comments.

Can you explain what knowledge can be conveyed with style that gets erased when linting?

dcz,
@dcz@fosstodon.org avatar

@deshipu Well, you mentioned effoet, but effort is not knowledge. Then you repeated "You can convey a lot of knowledge" but you skipped what exactly.

Sorry if you feel ignored, I am genuinely curious.

dcz,
@dcz@fosstodon.org avatar

@deshipu Well, i run it through a test suite, and read it carefully for architectural descriptions, and make sure that naming is fine.

If I have to reverse-engineer it to understand, then I take off quality points.

If I can't read it due to formatting, I guess I'd run it through a linter, but I don't think it would affect my impression of quality. Hence - I can't really imagine what knowledge I'd lose.

dcz,
@dcz@fosstodon.org avatar

@deshipu No, but I don't see how formatting it with a linter would make it less possible to understand. Therefore, style doesn't carry any knowledge.

dcz,
@dcz@fosstodon.org avatar

@deshipu The semantics: actual code, comments and variable names. Those are preserved by the linters I know.

dcz,
@dcz@fosstodon.org avatar

@deshipu You can use a tool that removes things that carry knowledge just fine. Just to make it clear, I don't consider comments or names part of style (except whether you use CamelCase or whatever).

But I still don't see what you see: the knowledge thats not in the semantics or naming or comments.

dcz,
@dcz@fosstodon.org avatar

@deshipu I agree with you on variable names. But there's a lot more to linting: spacing, indentation, the placement of brackets. Do you think those carry knowledge?

No linters I know touch names in a meaningful way.

dcz,
@dcz@fosstodon.org avatar

@deshipu If the code has inconsistent indentation, then I let the linter fix it :P

I can see your point: the more sources the author uses, the less likely they are well-integrated, and the more scrutiny they require.

I guess that's a valid point.

In the context of my original complaint, the syntax complaints didn't really lead to more feedback about the content, so I don't think those people were following your observation, really :P Now the question is: what are they trying to achieve.

thelinuxcast, to random
@thelinuxcast@fosstodon.org avatar

sshfs is far superior to nfs, imo. It is definitely easier to set up and it doesn't freeze when transferring large files.

dcz,
@dcz@fosstodon.org avatar

@thelinuxcast How do you make it not freeze XD?

It doesn't freeze permanently, but it introduces such lags I have plans for writing a replacement.

dcz,
@dcz@fosstodon.org avatar

@thelinuxcast Not good enough for me, I want to take a look at the contents of other directories while I'm moving stuff around.

I think the SSH protocol is the bottleneck, and I'm surprised that NFS has that problem. Wasn't it running over UDP?

dcz, to Bash
@dcz@fosstodon.org avatar

with which I surprised greybeards at the local hackerspace (which was surprising cause I'm the opposite of a expert):

mv photo{tocheck,supercool}.jpg

is the same as

mv phototocheck.jpg photosupercool.jpg

The shell copies an argument with {,} inside, and each resulting argument has a different part of what's in {}.

rm plan.{md,svg,png,odt}

Have fun!

dcz, to rust
@dcz@fosstodon.org avatar

A part of that doesn't get mentioned but is a ridiculous quality of life boon:

dbg!()

Just #[derive(Debug)] on a struct and print it. Suddenly you get insight into what's going on. Very rarely do you need to write your own print.

Insert a dbg in the middle of anything

let diffi = debug!(diffs).iter();

and you get a message with line number and the name of variable:

[src/lib.rs:192:19] diffs = [16, 86, 11]

Not even has that!

stfn, to random
@stfn@fosstodon.org avatar

With switching from XFCE to KDE, I also switched from X11 to Wayland, and I can't really put my finger on it, but things seem... smoother? There is something different in the way things render

dcz,
@dcz@fosstodon.org avatar

@stfn Wayland is designed to allow proper syncing, so you'll see less tearing and weird split-second states of applications.

jaycruz, to rust
@jaycruz@fosstodon.org avatar

This is a 48 minute long article that's critical of the Rust hype train vs C/C++. The TLDR is that while security is a problem, the Rust vs C choice as the only choice for low-level systems programming is a “non choice”. The author states that Go is a perfectly fine choice. https://medium.com/

#c

dcz,
@dcz@fosstodon.org avatar

@jaycruz I think the article makes a great observation: you always want a memory-safe language rather than C. But that language doesn't always need to be Rust. (The software I'm dealing with right now is in C, but it would not be much better in Rust. It really needs Python.)

Still, Rust's hype train doesn't revolve around the idea that it should replace all C/C++ code, but that it's the closest language which can replace the most low-level use cases of C.

dcz, to ReverseEngineering
@dcz@fosstodon.org avatar

If you like , go ahead and take a look at . It's one of the finest examples of write-only C code bases I've had the displeasure to learn from.

https://dechifro.org/dcraw/dcraw.c

case 274: /* Orientation */
tiff_ifd[ifd].flip = "50132467"[get2() & 7]-'0';

I dig that is now fixing that. And not even because it's in . I can actually follow the code!

https://gitlab.freedesktop.org/libopenraw/libopenraw/-/blob/master/src/panasonic.rs?ref_type=heads#L849

#C

terence, to random
@terence@fosstodon.org avatar

Back to real life with yet another visualisation of the world's submarine cables. Sick of these yet? Too bad. Volcanoes are next, followed by earthquakes over submarine cables, or submarine cables over earthquakes.

adventures, an tale

dcz,
@dcz@fosstodon.org avatar

@terence What projection are you using?

terence, to random
@terence@fosstodon.org avatar

Can't seem to stop so here's earthquakes (> M4.0) of the world, 1923 to 2023. I like how we can see the plates and active fault lines in a compact way.

Have a couple more before I move on so bear with me. 😅

adventures, an tale

dcz,
@dcz@fosstodon.org avatar

@terence This could use some more familiar reference points, like landmass outlines.

deshipu, to random
@deshipu@fosstodon.org avatar

Dead systems have considerably less bit rot, and they are usually super efficient on modern hardware. It's much easier to get to work a program from 50 years ago than a program that was released 5 years ago.

dcz,
@dcz@fosstodon.org avatar

@deshipu What you're describing is the incessant effort by archivists to undo bit rot.

I can't even find any 70's K&R C sources online - they seem to have rotted away completely.

Meanwhile I'm not aware of any sources from 5 years ago that aren't fixable with at most a small effort.

I'm honestly not seeing a difference in favor of older code here.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • Leos
  • mdbf
  • magazineikmin
  • Youngstown
  • everett
  • rosin
  • slotface
  • thenastyranch
  • ngwrru68w68
  • PowerRangers
  • kavyap
  • cisconetworking
  • tsrsr
  • DreamBathrooms
  • anitta
  • tacticalgear
  • khanakhh
  • Durango
  • ethstaker
  • vwfavf
  • InstantRegret
  • modclub
  • tester
  • cubers
  • GTA5RPClips
  • osvaldo12
  • normalnudes
  • provamag3
  • All magazines
    •