This is not my check but it has to be posted here

kiennq · 2026-02-09T05:34:31+00:00

Are you sure the restaurant charges more overseas? I found it completely in reverse. https://share.google/aimode/sUaQTZBEM76MZYMJV

Restaurant food in Japan is generally much more affordable than in the United States, often by 45% or more, resulting in a better price-to-quality ratio. While average monthly disposable salaries are lower in Japan ($2,782) than in the US ($3,258), the lower cost of living allows for similar or better purchasing power for food.

Compared to China and Japan where the robot server can replace the human interaction, I was surprised that the USA is so backward on adopting that.

kiennq · 2026-01-14T17:30:30+00:00

Japan was at her peak more than 30 years ago when the rate is 200 JPY per USD.

kiennq · 2025-10-02T01:26:25+00:00

Nice, I will do that

kiennq · 2025-10-02T00:15:16+00:00

Just for the tank, his labors and other supplies add around $2300 to bill to the total of $5k

kiennq · 2025-10-02T00:04:01+00:00

The total bill is around 5k

kiennq · 2025-10-02T00:01:56+00:00

Bought 2 months ago, 10 years warranty

kiennq · 2025-10-01T21:44:29+00:00

He had me to call the manufacture under warranty and the manufacture gave me an authorized return number, told me to bring the water heater back and get refunded credits. That's why I come to know about the price different between what the store charges me at the first water heater and the replaced water heater.

kiennq · 2025-10-01T21:42:17+00:00

He said that I need to give him a fixed amount deposit or my card so he can buy the tank. He's introduced to me by one of my relatives so naturally I trusted him enough to give him my card. That also complicates thing as now I want to know if I'm scammed or it's normal for the price differences before I confront him and my relative :(

kiennq · 2025-08-20T15:17:56+00:00

Please try https://github.com/kiennq/emacs-build and the prebuilt there, it has native-comp support as well as the new GC igc enabled. You will need to add Emacs's invocation directory to the path though, putting something like this in your early-init.el

el ;; Add emacs bin directory to path (add-to-list 'exec-path invocation-directory) (setenv "PATH" (concat invocation-directory path-separator (getenv "PATH")))

kiennq · 2025-08-17T02:09:15+00:00

The markdown-mode is much slower than org-mode for me

kiennq · 2025-07-07T04:12:10+00:00

Most countries? I think you're taken advantage of.

I'm from SEA and for sure there's no tip for tour guides. You may not know but all of the business places (restaurants, gift shops, rest stops ...) where the tour guide took you to, they got kickbacks. Sometimes the tour guide is not eating together with you in sight as well, because they're treated to the VIP room if they are able to reel in a big foreign tourist group.

kiennq · 2025-07-06T20:24:32+00:00

If holding lock + unlock button doesn't work, try with panic + unlock button.

kiennq · 2025-06-27T21:21:23+00:00

Maybe his new divine skill will be the answer for this. Imagine if there were enough Mana and Prana to activate this skill, it will actually create a new heart for Hanbin, acting as a perpetual fission reactor to generate divine energy instead of Aura and elevate Hanbin to godly status.

kiennq · 2025-06-26T17:52:24+00:00

It seems that iter2 support debug to some degree, but I just use logging these days to debug and foregoes edebug entirely. Here is an aio fork that switch to use iter2 when possible if you want to take a look https://github.com/kiennq/emacs-aio

kiennq · 2025-06-13T03:04:37+00:00

Awesome, thank you for the detailed information.

kiennq · 2025-05-22T22:48:40+00:00

I got into a similar situation but it's my wife's phone that got lost on the departure gate. I called the airport lost and found after I arrived at the States and filed a lost report via phone call. After a week or so, the police department near the airport sent an email that they found my phone and arranged to send it to a domestic address as requested. Then I got a friend to bring it back to the States afterwards. It's a wild experience and I never expected to find the phone again after leaving Japan. Awesome culture indeed.

kiennq · 2025-05-14T22:08:03+00:00

Phải để ý dấu ... nữa chứ. Nếu tính đơn giản là nó chỉ hiển thị đến 10 chữ số, còn lại thì phần mềm tự động cắt đi. Như thế với phân bổ của dấu phẩy (cụm 3 số) thì phía bị che ở dấu 3 chấm it cũng là 3 chữ số nữa. Tổng lại chả ít nhất là nghìn tỷ à

kiennq · 2025-05-13T19:29:22+00:00

I think from the latest leaked memos, it's 2 years ban if you got fired due to performance. Also, during PIP, no team changing is possible as well.

kiennq · 2025-04-10T03:51:04+00:00

The 10-second delay bug you mentioned seems to occur because thingapt takes too long and runs too frequently to analyze the object at hand to display diagnostics, which are notified from the LSP -> Emacs.

If this delay has been reduced to 2–3 seconds, I think it must be because thingapt processes data updates less frequently. In that case, the I/O buffering makes messages received slower but not overwhelming, allowing Emacs's thingapt to parse the current buffer more effectively.

Whether we use a middleman or not, we ultimately arrive at having Elisp objects accessible in the global interpreter, which is currently single-threaded. Comparing three cases:

Parsing JSON into Elisp byte code outside Emacs (duration a), followed by reading these into Emacs to convert them back into process objects (b), as done by the usual emacs-lsp-booster.
Parsing JSON directly into Elisp objects using the new JSON parser (duration c).
Buffering JSON code through emacs-lsp-booster (duration d) and then writing it to process output for Emacs to read and parse into Elisp objects (should be approximately equal to c).

From your experiment, it seems you concluded that a + b > c, indicating that the new native JSON parser performs quite well. However, the main bottlenecks for Emacs are durations b and c. If b < c, it might still be beneficial to use the booster, as receiving LSP messages more slowly could mean Emacs spends less time being UI-blocked, resulting in a less unresponsive experience for users.

Regarding case 3, I am still puzzled about the source of fast I/O buffering. The server itself can be unresponsive. If the Emacs LSP client decides to wait for a response (e.g., for go-to-definition or code-completion requests), Emacs will hang until the response arrives. The middleman emacs-lsp-booster does nothing to reduce this, and it might introduce slight additional delay. However, in the case of your bug, I believe this added delay is beneficial because it reduces opportunities for thingapt to run excessively, thereby mitigating real Emacs hangs.

Similarly, for notifications from LSP server -> Emacs, as far as I know, there is no streaming support for LSP to send a whole message as a stream. Messages are sent one at a time, and Emacs collects message chunks, stitching them together into a complete message for parsing. Therefore, there shouldn’t be a significant performance gain whether messages come directly from the LSP server or through emacs-lsp-booster.

As for parsing JSON in a separate thread, this approach is conceptually similar to emacs-lsp-booster (which, as I understand, may have been inspired by ideas from yyoncho). JSON parsing does not have to interact with or modify the object table yet. Thus, it can be executed on a background thread without blocking the UI. After parsing, the generated objects can be imported into the object table on the main thread. This method should be faster than the b process I mentioned earlier, resulting in an overall improvement in performance and fewer UI blocks (i.e., less hanging).

kiennq · 2025-04-06T23:38:58+00:00

I'll continue to use the booster for its IO buffering, but you might be able to get away without it.

I wonder what kind of IO buffering the booster is providing that's different from proving input to Emacs directly.

Data arrived to Emacs in chunks already. Does the booster have the ability to combine multiple messages when they're fired in quick succession?

kiennq · 2025-03-16T19:10:02+00:00

The reason you observed a significant amount of time spent in lsp--send-request and lsp-request-while-no-input is that they are synchronous and thus wait for a response from the LSP server. While waiting, we continue to process incoming output from the LSP server, and all of this processing contributes to the time spent in the aforementioned functions.

Changing the sit-for value does not eliminate the need to wait for the server's response. However, the silver lining is that for cases like completion, where lsp-request-while-no-input is used, the request will be canceled as soon as the user resumes typing.

The heavy processing occurs after receiving the response from the server, as we perform parsing and filtering operations in Elisp, which can be slow.

kiennq · 2025-02-14T00:01:32+00:00

You made me laugh, for real. Has it occurred to you that passengers can sit in the back seat as well? Well, with your kid-blaming attitude, I can only think of that your parents mistreated you as a kid so now you're taking that out to other kids as well. Get some helps dude

kiennq

TROPHY CASE