Phil

> Like come up with whatever you want to do in human language and than translate this into code later?

Is this what would fall under "thinking in semantics?
Like if a process has 5 steps in the way I'm thinking about it, I create 5 functions with the name of each step etc.

To me identifying what a process fundamentally must be to achieve the desired outcome before even starting to code doesn't count as coding, though you could make an argument that it's finding the pseudocode I guess.

@tragivictoria@mastodon.com.pl @thomholwerda@exquisite.social Reading how that PR developed today though, the biggest question I'm developing is why lorbus looks like he has an axe to grind on this topic. I don't think I really get what his position is and what the reasoning for his interference in the issue is.

@tragivictoria@mastodon.com.pl @thomholwerda@exquisite.social

OK, how am i supposed to tell a project's maintainers that I created a fork that fixes most issues?

Why did he feel the need to inform the maintainer of Document Scanner in the first place? Why was just writing an email to them not an option ? It's like... seemingly no thought put into the interaction and how it would be perceived, just the assumption that this must be good.

@karolherbst@chaos.social Somewhat summmarized: Flatpak devs presented that they can make things a whole lot simpler and get subsandboxing for browsers and steam if they reimplement flatpak, this time with rust, better ideas and a plan to outsource work to systemd. Subsequently, somehow people mistook jorge for a flatpak dev since he posted about it and now he's the representation of flatpak "discarding its non-systemd users".

@karolherbst@chaos.social How dare you miss Flatpak-next - systemd-appd dependency drama!

@kevinbowen@hachyderm.io They were too agro, but imo upstream has a point here. If users are taking up time due to bugs on outdated versions, that is an unnecessary resource drain on the project. That is a problem that could be solved by e.g. having a patch that changes the support link to the mint issue-tracker rather than the one to gnome calendar's so Mint can triage and forward issues when they're still relevant.

@nekohayo@mastodon.social From where I'm standing your cause was right, but how the team went about it was too aggro to be productive. Your core ask was to get people to stop giving you outdated bugreports. Framing that as a problem to solve together would've gotten further here imo. That still would've ended up at the "But Debian" part of the convo, but there you could've made a decent number of arguments for them to take care of it that they would have more likely listened to.

@daisy @glyph at the same time you can't easily push those boilerplate code things into a library because there often enough are tiny variations you need to do. You'd end up with either a thousand methods or methods with a thousand configs, that would have been more flexible if instead you'd have chosen an approach that forces a bit more boilerplate upon your users.

@daisy @glyph I share your opinion, and I'd on it working better on well trodden ground/boilerplate. I deal in web frontends and there it genuinely has been useful, because a lot of stuff there can be very cookie cutter. E.g. I've you've decided on making an http request for a featue in angular and use a specific library, the way of typing that out, getting data into stores, accessing those stores etc is all very thoughtless work. Telling it to write that for you works well.

@EineMeh@mastodon.social @echo_pbreyer@digitalcourage.social Da häng ich mich grad mal mit rein, 119 Seiten durchgehen *und verstehen* die v.a. dann nochmal in Jura-Deutsch geschrieben sind ist nicht grad ne schnelle Sache.

@alatiera Correct, the solution can only be to remove the log out option and optimize the entire boot-chain so that we can reboot in 5 seconds max!

@gregkh Free heating!

@LAS yeah I think smartphone support for Linux is like the one thing I'm most worried about.

@matk@mastodon.social @razze@osna.social TIL about the Projects dir! Neat and I would've loved to have had that... 3 years ago or so, but now I already have my own /home//dev dir pattern going so I'll have to stick with that 😅

@sstendahl that's wild and interesting. Any idea what caused these effects? From all I can tell just joining gnome circle itself doesn't immediately make sense to me as a driver for installs/downloads. Is it something they do or becoming more visible on some list somewhere?

@highvoltage@pleroma.debian.social that's been my exact experience. In android it's too much and distracting, on gnome it feels more subtle and informative on comparison

@ojrask Apologies, I meant to reply to @mugentoki and apparently misclicked 😄

@whangdoodler if you want Devs to use semantic CSS I would not use the wcag as an argument. As far as I recall it contains nothing related to that level of style customisation beyond setting global font/text styles. I would focus on advocating for e.g. BEM and technologies/CSS organisation patterns that avoid class name soup. Edit: @mugentoki (I had intended to reply to you)

@molly0xfff that alt text is criminally underselling how adorable he's being