I've been working on a web application for learning 倉頡輸法 https://demo.cangjieworkbook.com/ , no login required for the demo version (Cangjie Input method). It's a visual way of decomposing Chinese characters. It has a high initial learning curve so I've come up with a method based on the ways QWERTY is taught. I've added a few more texts and lessons in the last month. The most time consuming part is adding annotations to characters to show how they are composed, but it is worth doing. I already have a couple of users and they have given me helpful feedback. If you are interested, check it out and let me know how it goes.
> I suspect that Rust will start taking over as a dominant LLM output language.
I doubt it. I think most people will become more entrenched in their favored ecosystem.
> I also suspect that in short order we'll have entirely new languages that are engineered to be ideal languages for LLMs to generate.
This is already happening. A couple months ago I came across this language that is engineered for AI and human consumption https://www.moonbitlang.com/
I am fine with people having principles and doing things their way. Not everything has to be a race to be the best. There are still plenty of people that appreciate traditional crafts. Anyway, if Zig+AI can be the next, greatest thing, can't someone just fork it and make it happen?
Probably because it's a work around and not what most people want to do. Imagine someone telling you you have to type English in Cyrillic. I know if I could no longer type out Chinese characters and had to use pinyin it would feel very odd and like something was taken away.
My guess would be line height is a challenge and Naskh already exists. Then probably because these scripts are not used often in the places that are centers of software/OS development.
I would say some of us are welcoming and embracing it. Others are trying to fight the good fight, but it is hard to fight the momentum that is building.
It's very niche, but I have created a course for learning Cangjie 倉頡, which is a Chinese input system based on the visual appearance of characters (not necessarily etymologically correct). The advantage of this system is you can type most characters via unique output (there are a few collisions where you need to pick) and you do not need to pick the character from a list. This is particular useful if you work with specialized texts in Chinese.
You can find the tool at https://www.cangjieworkbook.com/ and there is a free demo linked inside. It should work on desktop and mobile web browsers.
What do you find about bringing it into production? Is it the actual language patterns or the tools? I've done Haskell in production for over a decade now so I am not sure what challenges newcomers face.
I don't agree with the repeated mantra that technology is neutral because the creation, maintenance and promotion of technology requires lots of resources and a lot of choices. A lot of conscious effort goes into creating things, and to change the thing after someone uses it. Make it better, make it safer, make it easier to use, etc. That doesn't feel neutral to me.
That sounds really nice. I have a couple of Haskell servers running on VMs, but the build requirements really slow down the process. I have to use dockers to help cache dependencies and avoid recompiling things that have not changed, but it is still slow and puts out large binaries.
The idea of having a language with most the batteries for a web server built-in is nice. I've never considered Golang, but it is compelling. I'll have to check it out. Though Rust keeps catching my eyes.
> For some reason the very concept of extended families and community engenders deep anger and hostility from some Americans
I think because excessive individualism plays into the hands of large companies. There is an individualist culture that has naturally grown over time in the US, but it has also been pushed by big corporations because if you can't depend on your neighbors and extended family, you need to spend money to fill the gaps.
That's fine for a library or locally run executable, but I've worked on distributed systems in Haskell and you really need logging in place to track what is going on.
Of course, you will have IO somewhere in a executable where you can handle logging so just separate pure and IO and make sure you have good tests for the pure functions. Also, linting to catch partial functions and dangerous lazy ones (or use an alternative prelude).
mchaver at gmail dot com