Too socially prevalent. Most people know about this change, but they still use the old one. Anything official are now using the standard age, though.
Anyone born on Jan 1st stays one year old for the whole year since people gain age every time the year changes. This does mean that a person can be born on Dec 31st, and be two year old next day.
Not money, but fucking vouchers.
It’s just <Number>살 for us. The way the age is counted is a bit different. If you were using the standard way of calculating the age, you add 만 in front of it.
Finally moving onto N4 and thank god my book now fully uses kanji instead of writing them in hiragana. N5 took me way too long. I tried to learn all the words in kanji even if they aren’t written in one because I figured it’s just delaying the inevitable, but it slowed things to a crawl.
Yeah, it stops at first page on Boost for me, even though browsing via website works just fine.
People are seriously downvoting a silly but innocent question posted here? 😭
There’s a reason why usable security, project management, HCI are a thing
Unless you count the dorm, yeah I do. It’s pretty normal to live with your parents.
My guess is that they hope this somehow stops the scam calls.
No fucking way they actually wrote an article based on a post on r/AITA 😭😭
lmao that thumbnail choice
🗣️🗣️ “The war is at its height – wear my armor and beat my war drums. Do not announce my death.” 🗣️🗣️🔥🔥🔥🔥
Miku is controlled by the big miku
() creates a subshell, and & runs the command in background. The $@ means everything after the first argument, so the <command> is executed like a normal command. I am not sure why this works, but it has worked more consistently than nohup, disown, and it’s a lot shorter than most other solutions.
IIRC disown is a shell built-in command, so its use is a bit limited. Not sure if & is also a built-in, but I found disown to not work in some situations. Besides, it’s shorter.
I have a script named d in my PATH and it contains this:
("$@" > /dev/null 2>&1 &)
It allows me to run any program in a fully detached state in a way that works even if the terminal that started the program closes, and it’s as simple as d <command>.
I just write everything down. If I forget it in the next session, I repeat it again. The idea is that you eventually end up remembering them.
reproducible
You tried writing bash scripts that set things up for you, haven’t you? It’s NixOS for you.
Encrypt it locally, and upload it anywhere. If you are at a level where you cannot trust anyone, it’s best to do it yourself. The provider will just get gibberish alongside general file size, last modified/access time, and your general login habit.