Report from Vietnam: I received scam calls pretty often before. It Vietnam trash SIMs were fairly common, and it bothered people so much that the goverment has to force every mobile company to "standardize" their consumer's data (i.e. fixing the incorrect data in trash SIMs). I have not received any scam calls since doing it.
Basically SIMs owned by previous owners that are brimmed with scam messages and calls. They are much cheaper than new legitimate SIMs so many people choose them. Sometimes people buy trash SIMs that has "good" or "lucky" numbers (something like 999 999 9999)
I was interested in CSGO for a while because of the eSport history videos but never got the chance to try it out because my main computer is a Linux and my brother's Windows computer is absolute garbage at running everything honestly. Thanks for this OP!
I used Thonny from when I was just starting to learn how to code. It was a great experience. Neat, much lighter than the PyCharm, easy-to-use, simple UI, adding packages is just about 2 clicks. Not much to complain, although sometimes the package installation dowsn't work.
Thanks for that. I spent part of the day fighting with my kid's Windows 11 PC to properly install the requests module in the Python IDLE, without success. He had Thonny already installed and installing requests was a snap.
I'm also a Youtube addict whose only active social medias are Youtube and HN. I do use Discord and Twitter but quite lightly.
I can't imagine the amount of time I have spent on Youtube. On my screen time tracking app, I have already spent 20+ hours on Youtube only. That's almost one goddamn day! Now imagine that plus my two years since I bought this phone.
On Youtube, I get pulled in for things I don't really cared or have never heard about. Last week it was Bluey (which seems pretty good), now it was about Nardwuar. Last time it was Radiohead, now it is CS:GO histories.
Youtube is so good at pulling me in and find the things I could be interested that sometimes I just wish Youtube's surveilliance tool will automagically knows exactly what I wanted and just served it up to my Recommendation, since for whatever reasion I refused to use the search bar.
In my journey of beating my social media addiction, Youtube is the true final boss (HN is also a big boss but not on the same level). I have been aggressively and gradually reduced my Youtube time. Refused to use it until it's 10 AM. Only used it as a break between my pomodoro sessions. I have not fully remove Youtube addiction in my life yet, but I'm on the way.
In my career of building programming languages, two of them arr Forth-based (stack-based)[0][1] and one is a Lisp[2].
I sometimes can't grasped how my Forth-based languages work when processing larger code, but it could have been easily because I never invested thst much into learning Forth anyways, which is why my third one is a Lisp.
Still, Forth is a very simple and incredible language. It is simple to understand, but harder to process on larger code. It is incredibly easy to implement, and easily extendable. It is also very predictable with only a few exceptions, which makes it a favorite for first-time esolangers.
The only shortcomings from Forth's design is getting used to stack-based operators, but I feel like it's something that can be adapted over time.
I tried Alpine.js a very long time ago. Managed to build some small web apps with Haml[0], but never everything big. It's generally very easy to use but when it comes to scaling it doesn't scale very well. Building a todo app with it requies many lines of JS objects, combined with that every object is defined in a string makes the code look a bit ugly. Useful for prototyping and small web apps if you dont want to use complex stuff.
I think this is the answer. I started using vi 33 years ago and initially learned just what I needed to know. As time went on I learned more commands.
If I wanted to erase a word in a sentence, which had seven letters, initially I might type x eight times (erase the word and a space). Then as I learned more vi I might type 7x. As I learned more vi I might type dw.
You can get a lot of navigation and editing done just knowing a few commands in vi. If you use it a lot, you can learn more commands and have an easier time.
About 7-8 years ago the standard IDE for my programming niche changed, and I had to learn a new IDE and what I knew of the old IDE I have almost never used since. The vi stuff I learned 30 years ago I am still using.
> For hjkl I just used arrow keys since they are nicer and I dont find much difference between them.
The point of hjkl is to keep your fingers in the home row of your keyboard. This is generally accepted to be good typing practice as it improves speed.
>> The point of hjkl is to keep your fingers in the home row of your keyboard. This is generally accepted to be good typing practice as it improves speed.
You might get some benefit to speed if you keep your hands on the home row, or you might not. This is mostly something people have been repeating as gospel, but I'm not aware of anyone testing it.
Intuitively, using the arrow keys to move the cursor without inserting a character should be faster. Assuming one is moving around the text while editing, it takes at least three keypresses to use hjkl to move the cursor without inserting a character: one to switch to command mode, one to move the cursor, and one to switch back to insert mode. That's because hjkl in insert mode simply insert their respective letters. By contrast, using the arrow keys to move the cursor without inserting a character needs one keypress: to press an arrow key.
Even if you count moving your hand to the arrow keys and back as two distinct "operations", and each keypress as a single operation, it takes at least three operations to use the arrow keys (i.e. as many as using hjkl): one to move a hand to the arrow keys, one to press a key, and one to move the hand back. Assuming that each operation takes constant time, that means that, at best, there is no advantage over keeping your hands at the home row and moving the cursor with hjkl, than using the arrow keys.
So that idea, that it's faster to keep one's hands in the home row, must be a superstition.
Incidentally, I've been using vim continuously since 2011. These days at work I use a Spanish QWERTY keyboard, but with an English Euro layout. I got the Spanish keyboard by mistake and it was simpler to keep using it with the layout I know, and benefit from more than a decade of muscle memory, than to try and learn the new key positions (and combinations). This is another reason why I am skeptical of the claim about the home row: muscle memory is faster than any spatial optimisation you may think of, or, rather, if you've already learned to move your hands one way and can do it fast, changing to a new way will slow you down, first. And then we're talking about long-term gains of maybe a few milliseconds in the long term in this case. That sounds pointless.
Not only that, it is more ergonomic -- if you can get the same thing done without moving your arm so much, it reduces the strain.
It is for this exact reason I am using vim in VSCode. I get some speed up in vim vs mastering VSCode shortcuts, but not enough that would make me switch. However, with vim I hardly need to move my arm over to use arrow keys or mouse, which makes it much easier on my hands and my arm.
