unhrpetby @ unhrpetby @sh.itjust.works

Posts

0

Comments

106

Joined

5 mo. ago

These error messages are never (sic) used on data validation issues.

You are incorrect. I have had issues that were exactly that. Such as a password that was failing to be accepted and then giving generic error responses, which I then had to trial-and-error brute force to find which part of my password they weren't allowing on the backend.

You stance might become easier to defend if you avoid absolutes.

By nature of software consisting of a client and a server, there are certainly errors that can be bypassed on the client side.

Server side software does not mean "there is literally no errors that are dependent on client input." That's ridiculous to think, but pervasive in this comment section it seems.

Do show a big scary error message. I would like to understand what is going on.

"Majority of software" source your claim.

If you use your computer as a bootloader for Google chrome, maybe. Local software and SASS both benefit from error messages because you cannot assume every error you can do nothing about.

An error about parsing my password and a stack trace? I can possibly deduce to limit the length, remove special characters, or add special characters and try again.

"Something went wrong." is lazy and nontransparent.

Blanket "99%" statements are unfounded. I have had countless issues I was able to fix through error messages and some without.

Source your claim.

Same logic as "keep it closed source for security".

Ridiculous take. I have debugged countless issues. Those that spit detailed error messages are typically far easier to debug than those that don't.

For example, returning nothing but exit code 1 to indicate failure. This gives zero information about the reason behind the failure, and only could be acceptable if your program is so simple as to only have very few failure modes.

I have solved issues by cloning the source code and reading it to understand the issue.

Don't relegate everyone to the same fate as those so utterly ignorant they can't look up an error code.

As for the bugs you can't fix? Why do you think Cloudflare tells you when its the website having an issue, and not your browser or them? Knowing the issue isn't something you can change, avoids spending time trying to fix an issue that you have no control over.

People who can will write up a bug report anyway

And report what exactly? Your program gives zero information has to why it failed? Now you have dropped the responsibility of figuring that out from the code, which tends to know far more about its failure state, to someone observing from afar. Its inefficient and ridiculous.

I disagree with you across the board.

I need to see body camera footage, but their claim is that she had a butcher knife and approached an officer who was backed into a closet, all while carrying the infant.

This doesn't seem like a simple "bad cop" moment.

"Meant to" and "do" are quite different.

I have, not once, ever had an issue caused by a update while the system was online. And if someone did, they could likely reboot to fix it.

I will stick to the online, instantaneous, and unobstructing updates.

I would like to see some real-world numbers and examples of problems that offline updates fix.

Its possible: Link

I'll take a program that isn't getting updates anymore or simply wasnt working in my modified environment using slightly more ram and storage over it not working at all.

I have firsthand experience with videogames made for one flavor of Linux not working on my machine due to dependency hell.

This is a good reason for static linking. All the dependencies are built into the binary, meaning it is more portable and future proof.

We don't need flatpak for this!

Yes. Using kexec.

Though this is irrelevant for majority of users: I've never seen it as the default.

That +

WARNING: Use with caution! Kernel crashes, spontaneous reboots, and data loss may occur!

gives me the idea that its likely safer to just do a proper reboot, if your alternative is kernel patching or loading a completely different kernel.

Plus, its likely that not every single bit of firmware running on your devices support live patching. Thus you will be rebooting eventually, unless you are fine with avoiding the updates.

Generally no. There are some parts of your system that you will have to reboot for (like the kernel). But apps? Installing a new service?

No.

Most systems you just install the app you want, and run it.

There are some immutable distros the require things that are installed as part of the base system to only be available after a reboot, but they provide ways to install things without making it a part of the base system. Thus no reboot required.

Is what necessary?

I had to update a Chromebook-like machine that was running Windows not to long ago. It was excruciating. The restart progress bar on one update after reboot took ~30 minutes to reach 3%.

Keep in mind that the computer is unusable during this time, and all it takes is one poweroff to brick the machine. Ask me how I know :) . I had to leave it plugged in overnight to finish.

If this comment is referring to Windows reboots after update, I will call it confidently incorrect.

Discord servers are just groups. Lemmy "instances" are actual separate instances of Lemmy communicating.

Or communicate that you aren't listening. I would want to know, as the speaker, that my words are going in one ear and out the other.

They have also had this issue open for 20 years.

And this amounts to just allowing the user to specify a different directory for Firefox on Linux (~/.mozilla is terrible).

Frankly unacceptable.

We can use dinit, s6, runit, and openrc.

There are more, but these are all top contenders.

I switched to dinit recently, it uses declarative service management (like systemd unit files). Very clean, fast, lightweight, and portable.