If you have a fever.
deleted by creator
Is there any situation where you’d want to remember the opcodes? Disassemblers should give you user-friendly assembly code, without any need to look at the raw numbers. Maybe it’s useful to remember which instructions are pseudo instructions (so you know stuff like jz
(jump if zero) being the same as je
(jump if equal) making it easier to understand the disassembly), but I don’t think you need to remember the opcode numbers for that.
Edit: Maybe with malware analysis where the malware in question may be obfuscated in interesting ways to make the job of binary analysis harder?
What do leaf blowers do that rakes don’t? I don’t remember the last time I saw or heard a leaf blower.
This one, if by unix he also means modern linux systems. Nowadays you can simply use tar xf my-file.tar.whatever
and it should work on most linux systems (it worked on every modern linux system I’ve tried and every compressed tar file I’ve tried). I don’t think it is hard to remember the xf
part.
they break with monospacedness
The IDEs I’ve used had the ligatures be of the same character width as the original operator.
Why are you casting to void*
? How is the compiler supposed to know the size of the data you are dereferencing?
Due to its reduced instruction set; it uses less power in general
If that is true I don’t think it can be attributed to it being RISC
What I find interesting is that my bank has kind of the opposite stance. It allows you to do a lot more things if you login via their website and I think they overall trust your actions more if you do it over the browser, but you are required to pass a lot more security checks, while on the app a PIN is enough, but it also doesn’t allow you to do as much.
I wouldn’t trust ChatGPT with teaching me about some tool. It in my experience very convincingly spews out stuff it invented, and if one is still learning I can see it being hard to spot those errors. I use it to fix syntax errors in SQL queries, though, since I can’t be bothered to try understanding the not-so-helpful error messages I get with my queries, and because if chaptgpt tells a lie it will be caught by my syntax checker.
So, I guess you can use it, if you always assume it to be trying to mislead you until proven to the contrary.
Watt is the amount of water flowing out at the end
Shouldn’t it instead be the sum of the kinetic energy of all water molecules that come out the other end per unit of time (ie. total amount of energy you use move your volume of water with a certain pressure in a second)?
I never got the pipe analogy. Since liquid water can’t be compressed, wouldn’t the amperes be directly proportional to the volts and to the size of the pipe, assuming there are no air bubbles? Also, supposedly resistance only reduces current, but when I think of hair in a pipe, the pressure after the obstruction would also be lower (because pressure is directly proportional to the amount of water that flows)
Is xml really that unreadable for machines? I enjoy xml as a format, because I can generally just convert it to an s-expression and easily manipulate it as a tree.
I don’t remember the last time I had to worry about the compression. I simply run tar xf myfile.tar.whatever
and it works every time.
These vpns seem to be quite a good target since at least the one my university uses is run as a setuid executable, so if there is a vulnerability in there, you can execute code as root that wasn’t intended to be executed as root.
As TonyTonyChopper this thread said, sometimes that obscure software is what you are required to use in your institution, or they don’t offer support for anything else.
a beginner friendly distro should have the convention to install apps be by GUI instead of TUI, and guides should be updated to reflect this
It is a lot harder (and less helpful) in a written guide to tell someone to press a button in menu such-and-such; telling someone to open the terminal and copy paste a command is easier.
In addition (though I do not know if it applies so much to gui package managers) GUI apps also have the tendency to not have a stable interface, so a blender 2 tutorial will often not be useful for someone using blender 3, because the interface will have changed and buttons that were once in one place now are somewhere else or no longer exist. CLI programs for some reason are a lot more backwards compatible in my experience.
I think GUI apps should ideally be designed to be usable without the user knowing where something is beforehand (though that is not always possible, like in complex software handling a lot of stuff a new user may not be familiar with, when they only want to achieve a certain specific goal), making mentioning how the UI works almost superfluous in those cases.
You can also do
git diff --cached
to see all changes you added to the index.