[-] orangeboats@lemmy.world 15 points 1 week ago

The C developers are the ones with the ageist mindset.

The Rust developers certainly are not the ones raising the point "C has always worked, so why should we use another language?" which ignores the objective advantages of Rust and is solely leaning on C being the older language.

[-] orangeboats@lemmy.world 14 points 3 months ago

Also, icons. The icons in Windows XP are too recognizable. You need to minimalize them. In fact, minimalize it so hard that not one person could understand what the icon is even referring to.

[-] orangeboats@lemmy.world 14 points 3 months ago

Breaking news: not all parents are good at parenting.

[-] orangeboats@lemmy.world 12 points 9 months ago

There are times when the original standard has zero forwards compatibility in it, such that any improvement made to it necessarily creates a new standard.

And then there's also times when old greybeards simply disregard the improved standard because they are too used to the classic way.

[-] orangeboats@lemmy.world 12 points 1 year ago

Wayland is X12. The people who worked on Wayland were X11 developers too.

[-] orangeboats@lemmy.world 11 points 1 year ago* (last edited 1 year ago)

I feel that the biggest mistake of X11's protocol design is the idea of a "root window" that is supposed to cover the whole screen.

Perhaps that worked greatly in the 1990s, but it's just completely incompatible with multi-displays that we commonly see in modern setups. Hacks upon hacks were involved to make multi-displays a possibility on X11. The root window no longer corresponded to a single display. In heterogenous display setups, part of the root window is actually invisible.

Later on we decided to stack compositing on top of the already-hacky mess, and it was so bad that many opted to disable the compositor (no Martha, compositors are more than wobbly windows!).

And then there's the problem of sandboxing programs... Which is completely unmappable to X11 even with hacks.

[-] orangeboats@lemmy.world 12 points 1 year ago

This is probably family dependent. My family is similar to OP's, we usually text if we want to have casual conversations. Voice calls are limited to serious topics only... unless I text them "hey, let's have a call" or something like that first.

[-] orangeboats@lemmy.world 11 points 1 year ago* (last edited 1 year ago)

Debian is my go-to distro whenever stability is desired.

I use Arch btw (on my desktop), but I would never run it on my server... I feel that I could easily ruin my database (Postgres) if I am not careful enough with the rolling release.

[-] orangeboats@lemmy.world 12 points 1 year ago* (last edited 1 year ago)

As an anecdotal though, I once saw someone simply forwarding (ie. copy and pasting) their exam questions to ChatGPT. His answers are just ChatGPT responses, but paraphrased to make it look less GPT-ish. I am not even sure whether he understood the question itself.

In this case, the only skill that is tested... is English paraphrasing.

[-] orangeboats@lemmy.world 14 points 1 year ago

10+ years of Windows and I still can't say I'm familiar with it.

Linux has a steep learning curve for sure, but if I have to say one good thing about it, it's the openness of Linux.

I dread seeing the message "An unknown error has just occurred" when I use Windows. Tell me, Microsoft, tell me what the error was!

[-] orangeboats@lemmy.world 14 points 1 year ago

I don't think it's possible to encrypt the data.

Say we have a rogue user that sends to the server multiple upvote requests for the same comment, how can the server reject the subsequent requests? After all, we can't let a user upvote a post or comment multiple times.

If that data is encrypted, the server cannot tell whether the user has upvoted a comment before.

view more: ‹ prev next ›

orangeboats

joined 1 year ago