Hacker Newsnew | past | comments | ask | show | jobs | submit | sschmitt's commentslogin

Pretty good! Translation by AI? First lessons quite well, but first quiz in German "Welche dieser Noten ist... ganze Tonoberhalb?" makes no sense.


All but english and french (my native language) are machine generated yes sorry about that but there is quite a bit of text with all the lessons so I can't afford man made translations at my scale.

Maybe I will find a middle ground and get translators just for the critical parts such as the challenges, or at least find a better way to translate parameterized strings like the one you are referring to.

EDIT: there is indeed an issue with some localized entries where the parameters are not placed properly, I will fix this for the next version


I came here just to ask this question. I was really struggling to understand what that could mean. I’ll use the English version then. :)


Can it document modular synthesizer patch configurations?


Interesting application - not sure the visualization currently lends itself well to that. My first approach would be to make the modules components and then arrange them to mimic the actual appearance. We don't currently have text on the component creator so labeling may be tough.

I'll put something together with the current features and share here.


How is this different from https://github.com/nextjournal/clerk?


Think of Civitas as a "static site generator" that uses the GH pages for the project as the public hosting for all the content -- a centralized, Clojure-specific blog if you like.



What's the best strategy for a full backup and recovery if updating to LTSC goes wrong?


I suggest making a disk-to-image backup of your whole boot drive using clonezilla, to a second external disk.

To test recovery, take a third spare drive, restore to it from the backup image using clonezilla, and replace your boot drive with it. If this boots up well, you could even do your upgrade tests using this spare disk, restoring from the backup file as necessary. Then once you're confident, put your boot drive back in and proceed to upgrade it.


Maybe create a full disk system image? But also upgrade adds a way to restore itself


The thing is that with the LTSC branch, you never get full-version upgrades. That is why it exists.


The full-version upgrade here is LTSC


Ah, OK, I see what you mean. All right then, my mistake.


How has this changed with the successful implementation of LLMs in the recent past?


Cool! Will be interesting to compare to https://github.com/mit-pdos/xv6-riscv!

Shameless plug for my html version of the xv6 book: https://xv6-guide.github.io/xv6-riscv-book/


xv6-riscv is 7000+ LoC. Half of that is userland utilities though.


HTML conversion

https://xv6-guide.github.io/xv6-riscv-book/

and cmake build

https://github.com/xv6-guide/xv6-riscv/blob/cmake/CMakeLists...

for xv6: a simple, Unix-like teaching operating system.


There's also the BrainScaleS neuromorphic system that features wafer scale integration:

https://arxiv.org/abs/2303.12359


Jeffrey Snover, inventor of PowerShell, wrote in 2007:

"It was a mistake to think that GUIs ever would, could, or even should, eliminate CLIs."

16 years later. Has the situation changed? Will it ever change?


We should obviously have both.

CLI is for automation. GUI is for exploration and certain limited contexts like mobile devices.

But CLI should be preferred when in doubt, or you lack resources. PowerShell type of CLI at that.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: