

I spent solid 10min writing an useful answer and then looked up. Now I want my 10mins back.
hint
Just wipe the screen clear from the goo, dummy.
I mean no harm.
I spent solid 10min writing an useful answer and then looked up. Now I want my 10mins back.
Just wipe the screen clear from the goo, dummy.
No mention of KDevelop? ;__;
I like it because it is the pretty much only FOSS graphical IDE where the edit-compile-debug cycle works. I’m been using it for last 10y for C/C++/Python, and it recently gained LSP support. (ported from Kate)
I intended this an sarcastic example; I think it’s worse than putting the main outside of the branch because of the extra indent-level. It does have an upside that the main()
doesn’t exist if you try import this as an module.
Btw, ld.so
is a symlink to ld-linux-x86-64.so.2
at least on my system. It is an statically linked executable. The ld.so
is, in simpler words, an interpreter for the ELF format and you can run it:
ld.so --help
Entry point address: 0x1d780
Which seems to be contained in the only executable section segment of ld.so
LOAD 0x0000000000001000 0x0000000000001000 0x0000000000001000
0x0000000000028bb5 0x0000000000028bb5 R E 0x1000
Edit: My understanding of this quite shallow; the above is a segment that in this case contains the entirety of the .text
section.
I would put my code in a def main()
, so that the local names don’t escape into the module scope:
if __name__ == '__main__':
def main():
print('/s')
main()
(I didn’t see this one yet here.)
Holy hell, thats rough. :D
My favorite so far:
$ gdb -ex 'file /bin/gdb'
run
corrupted double-linked list
Thread 1 "gdb" received signal SIGABRT, Aborted.
I once wrote bind_front()
and move_only_function
likes in C++17. This nearly drove me mad because you cannot refer to a overload set by a name.
On the otherhand, I can now decipher the template error mess that the (g++) C++ compiler spews out.
what the actual fuck. 🤮
$ gdb -ex 'file /bin/gdb'
run
corrupted double-linked list
Thread 1 "gdb" received signal SIGABRT, Aborted.
Yeah, try debug that.
A kernel was released that changed how the hash value got computed for casefolded filenames. (used for better windows compatibility) That kernel then went into production. This unfortunately split some file-systems that supported this into two incompatible versions, breaking the kernel rule 1.
There might now exist file-systems were created/modified with this bug present that the old/fixed kernels can’t understand.
*) The only socially acceptable way for a man to cry. /s
MSRs have negative temperature reactivity coefficient and outlet temps around 700C at atm pressure. PWR is at measly 300C and 150 Bar.
If all control is lost, the salt expands as it heats up pushing the expanded volume out from the reactor core. The fission stops once the fuel is leaves the core region where the moderator is. Reverse is also true: you pull heat off from the loop, so the fuel-salt becomes denser, increasing reactivity. MSRs can naturally “follow” the load, if done right.
If I would drink any coffee in that time, (even worse with/or booze) I would be still up the next day by a large margin. :(
As much as I like at some time before 14:00 'o clock and then none.
Caffeine has about 8hrs half-life and blocks a few key receptors in the brain, so it will only mask the tiredness you build up over the day.
Too much water. And it’s all either fresh, slush or solid.
Because of the lack of salt, we have salmiakki. /s
I was reluctant to take this project, knowing well I would end up deleting nearly all existing code I would have to touch, all while having just mediocre skill writing its successor, if it ever becomes one.
I can no longer escape from this project, nor do have I will to.
deleted by creator
“When you do things right, people won’t notice and it’s like you have done nothing at all.”
Futurama or something something quote likely not word-to-word correct.
Sure it’s terrifying, but you can start a sparky plasma show in a resilient enough container and keep it going for hours and the microwave won’t break. (except maybe overheat.) The microwave will be fine as long as the arcs don’t reach the waveguide cover. (which would risk burning/shorting the magnetron.)
I have done the microwave grape plasma trick myself and started an arc in a microwave. The current between the two objects goes through a very narrow point, which is enough vaporize the contact point to plasma. This then can grow as the microwave continues to pump more energy into the spark.