Partly because people replace phones more often than computers, (to upgrade, or because the screen breaks, etc) so they stop using the device before the RAM fails. But also the RAM they use in portable devices was made specifically for the device and integrated directly into the mainboard. There’s less points of failure and compatibility is never an issue. Since desktop RAM can be replaced and upgraded, it’s not as big of a deal if it fails, you can just swap it out with a new stick. Whereas it would brick the whole device if mobile ram fails, so quality standards are much higher.
Not to mention the differences between a soldered interface with the chip directly on the main board designed to basically be permanent, versus a simple contact interface and daughter board designed to be removable, thus adding additional points of failure.
Which I had to do to fix a mystery hard-reboot-without-warning issue I had just a couple of months ago. Connectors, especially dinky edge connectors on sensitive high-frequency components, are the weak point of most PC hardware.
If your RAM fails then it generally does so quickly, and also if your RAM fails you probably bought some bargain-bin stuff. As a rule of thumb don’t buy DIMMs from companies which don’t produce their own chips, or are extremely reputable. And with that I don’t mean “you have heard of them”.
I tried it twice. it require enabling affinity support, which causes vscodium to freezes after an hour of use. might be an issue just on my machine, but it made be use just nvim :)
bram was a chad, mate. I once opened vim without any file(just plain vi) and saw help poor children in Uganda. read whole uganda.txt file and then saw how his organisation is fully involved in getting material benefits to the ground. further went down the rabbithole and saw his org’s photos in uganda.
made me really appreciate the man.
Now that you know about ci(, I highly recommend taking a look at tpope’s plugins. Especially the surround plugin. It can change the surrounding parentheses and tags (if you’re editing an HTML or XML document). Quite cool. Also, there’s much more in tpope’s library of pugins.
PS, did you know that zsh has a vi mode, where you can use typical vi commands to edit the command prompt instead after the default ones? Quite useful as well.
I watched him for a while and even kinda liked some of his “old man yells art cloud” videos, but he lost me around the time of his “explaining Linux to newbies” video.
vim’s shortcuts like these are giving me 'gasms and regret(that I wasted so many collective hours using Ctrl + arrow/mouse over this). it’s a weird feeling.
and yeah, you never learn vim. you just learn it enough.
Funny I had to Google ci" to remember what it does even though I use that sometimes.
I’ve committed to learning vim years ago and in most situations im faster in vim than in nano etc. (especially because of muscle memory) I still feel like I’m not properly using vim to it’s full extend (like whenever I remember using registers it feels like magick and I’m sure there’s more like that)
explanation for the command ci": c: change. analogous to delete(d) followed by insert(i) i: inside ": the double quote
so, it’s basically change inside double quote(easier to remember as it sounds exactly what it does).
you can similarly do di((delete inside parenthesis).
an inferior alternative on vscodium would be shift + alt + right/left arrow
discuss.tchncs.de
Newest