info proc mappings should show you the memory regions mapped for stack and heap, then you can compare the address of your variable to those.
It is almost always that.
Or idk maybe people have a job where it's useful to hone your tools? This meme doesn't make any sense.
There is a highly NSFL video of it on the c/news megathread.
What an idiotic suggestion. Hetero men everywhere will rejoice in you shutting the fuck up right now.
Funnier without the text/caption.
I'm perfectly happy to build my own NAS with NixOS and ZFS on it. I think it's mostly a matter of getting the right hardware.
There are plenty of good resources online. Here are some topics you probably wouldn't see in an intro algos course (which I've actually used in my career). And I highly recommend finding the motivation for each of these in application rather than just learning them abstractly.
- bloom filter
- btree
- b+ tree
- consensus algos (PAXOS, RAFT, VSR, etc)
- error correction codes (Hamming, Reed Solomon, etc)
- garbage collection (mark+sweep, generational, etc)
- generational arena allocator
- lease (i.e. distributed lock)
- log-structured merge trees
- min-cost + max-flow
- request caching and coalescing
- reservoir sampling
- spatial partition (BVH, kd-tree, etc)
- trie
- write-ahead log
The fastest marathon time for men is 2 hours 1 minute and for women it is 2 hours 14 minutes.
It's an unacceptable leap in logic to infer (from that statement) anything about populations of men and women. You've picked only a single sample from each population and chosen that highly biased representative.
That really is one hell of a hot take
Yea well most of the comments in here are lukewarm takes so... there you go.
I for one really love the zoomed out preview on the right that has become popular in recent years.
I almost never navigate code based on its order or "shape" in the file. LSP-based symbol tagging or searching is way faster than scrolling. I guess you can click the spot on the preview that you need, but I refuse to reach for my mouse while editing text.
Really hard to do in a terminal. If you have errors you can see very fast where they are located/clustered in the file and can already tell just by the shape of the program where it is.
I use LSP integration to see a complete list of errors/warnings and jump to them.
Another example: GUI color picker directly in my editor as a tooltip above color values in css/html templates.
That's for design, not text editing ;)
inline preview of latex or Template fragments.
I will use a latex or markdown language server that renders to a browser tab.
To be fair, I don't do HTML/JS/CSS, so I bet VSCode or other GUI editors are great for that. But that's specifically because you want to see something rendered. Most of the time you can just see it in an actual browser next to your text editor though.
tatterdemalion
0 post score0 comment score
Probably best we just let them think they got one over on us.