Notices by Fedor Indutny (indutny@mean.engineer)

@taiyo さすが傑作ですから！

Japanese to Japanese dictionary has a bit of Intel instruction set manual vibe.

There are multiple indices, several layers of indirection to get to the reading of the kanji you need.

I feel like a Turing machine doing all of that, but now I probably won’t forget that 庇 reads as ひさし😅🤣

Seriously, check this out.

First you find a radical by the number of strokes (presumably you know how to write it), this gives you a page and column number.

You open that page, locate radical, and under it look for the kanji you need. This gives you an 音読み reading… which is not what you need in many cases! (Unless you look up compound word)

Then search through the book to find the kanji by 音読み reading to identify the 訓読み reading!

Finally you find the word you need and a definition!

As a person learning the language and someone who tries to stare at the phone less throughout the day I won’t complain, though. This is exactly the experience I’ve been looking for!

(Someone please hide the phone away from me so that I stop posting here)

I wonder if people in Japan use a dictionary like this often. It must be too burdensome in the age where you can snap a picture of the word, select and copy, and lookup the word online.

オビタール・クラウドの下巻を読み終えたばかりです！

すごく面白かったですよ！特に（ネタバレをすみませんが）地球を動かすことが気に入りました。流石に @taiyo の作品は新鋭なアイデアと科学的の理論に溢れています。お薦めですよ!

@taiyo 聞いてよければ、度いう本ですか？

@jonasgeiler we still have a fight to do, but for now we are stable!

In a way I'm glad that we started discourse on LLM use in Node.js core because it revealed to me that there are a lot more people who are not in AI hype-cycle than I previously thought. I'm now much more optimistic about the future of software engineering!

Consider this:

- 87.3% upvote ratio with 298 upvotes on /r/node
- 76.6% upvote ratio with 50 upvotes on /r/javascript (and I just posted it)
- Incredibly supportive comments on HN (!!!)

Node.js TSC meeting ended slightly earlier today, and we had a very productive conversation on LLM use in Node.js core. I don’t think I covered all concerns that I heard or had, but I tired to summarize most of them!

The resolution is to hold a bigger discussion during the collaborator summit in London in 2 weeks.

For now the AI policy PR will remain blocked!

I'm so appreciative of @bengl right now. Their PR that proposes adding policy on LLM-generated contributions is receiving lots of feedback from other project maintainers and has helped me uncover additional concerns about LLM: https://github.com/nodejs/node/pull/62447

Like, I haven't thought until yesterday evening that LLM written code is completely antithetical to MIT-license under which Node.js is written. LLMs are designed to destroy attribution, but MIT license is built on top of it.

RE: https://mean.engineer/@indutny/116245283352156779

Over the night I got so many responses and boosts to my original Toot that I decided to start the petition to Node.js Technical Steering Committee (TSC) to make sure all our voices are heard.

If you don't want Node.js core to be diluted with AI slop - please sign it by opening a Pull Request here and boosting this Toot for reach:

https://github.com/indutny/no-slop-in-nodejs-core?tab=readme-ov-file#petition-to-nodejs-tsc-no-ai-code-in-nodejs-core

Thank you, you are the best!

#NoSlopInNodejsCore

@taiyo 馬鹿馬鹿しい政策の馬鹿馬鹿しい結果ですよね！

@zundan それでこの書き方もありますね

const a = () => ({ prop: 1 })

えー、これは何か？括弧でしよう？

@whitequark does he talk about monopoles?!

今日の新単語は

「生老病死」

#日本語

蓋然性と可能性の違いは何ですか？

One more book in Japanese read this year: Orbital Cloud by @taiyo

I wasn’t even remotely aware of the concept of space tether. Wrapping this in a spy story is such a great move 🥰

Thank you @taiyo for a very entertaining story! Can’t wait to read the part two in a bit!

#日本語