Live data from Hacker News

Brutal OS reached milestone 4

brutal.smnx.sh

41–50 of 75 posts

Re: Brutal OS reached milestone 4

#42
post #31

Very cool project, and i want that hardware badly... But... Please add some margin on your article before someone gets hurt

I believe that is a Soviet Project SPHINX system - a design for a smart home network that never actually got produced due to the fall of the Soviet Union. https://blog.adafruit.com/2021/12/13/project-sphinx-when-the...

Even if it only involves stuffing a raspberry pi into something, I want to yell at someone over the phone from my penthouse office in front of that thing while 80s power-montage music plays.

Re: Brutal OS reached milestone 4

#43
post #8
post #7

It’s not UNIX but it “is” UNIX? That’s kind of all I got out of the about. Glad to see new OS design in 2022!

The idea is to take all the concepts we like about UNIX and iterate on them. It's UNIX as if it was invented now. For example, let's have a C compiler but let's add lambda and a more complete type system. Or let's have a shell, but let's have full ide like autocomplete to it. Or instead of plain text, let's use JSON

What (if any) is the overlap with Plan9 (and its various forks and derivatives, including Inferno)?

Given KenC, I was amused to see that Brutal has its own C variant too!

Re: Brutal OS reached milestone 4

#44
post #36
post #25

Earlier quoted context omitted.

It looks cool but the keyboard is almost square, making it difficult to touch the keys in the top row while still resting your hands. A flat aspect ratio (like most keyboards have) would be better. It's easier to move your fingers over large distances horizontally than vertically; see also the piano keyboard.

Quoted post unavailable.

Ergonomics are important, and ignoring or powering through something that can injure you is a poor choice.

Re: Brutal OS reached milestone 4

#45
post #36

Earlier quoted context omitted.

Quoted post unavailable.

Ergonomics are important, and ignoring or powering through something that can injure you is a poor choice.

You know what you're doing right now. Stop it. We are not dainty wristed aliens yet. I love velcro shoes and elastic waistbands as much as the next guy, but this is bordering on comedy. How do you people lift a coffee cup with a straight face while saying this type of stuff?

Re: Brutal OS reached milestone 4

#46
post #45

Earlier quoted context omitted.

Ergonomics are important, and ignoring or powering through something that can injure you is a poor choice.

You know what you're doing right now. Stop it. We are not dainty wristed aliens yet. I love velcro shoes and elastic waistbands as much as the next guy, but this is bordering on comedy. How do you people lift a coffee cup with a straight face while saying this type of stuff?

You're right. Lifting a coffee cup with poor ergonomics isn't going to cause any injuries. Typing for hundreds of hours over many years in a poor position can lead to problems such as RSI.

Re: Brutal OS reached milestone 4

#47
post #40

Earlier quoted context omitted.

A language like C but with lambdas isn't really C, not that that's a bad thing. I was a little surprised that a compiler was in scope given the amount of other work that needed to be written and (hopefully) supported, though I guess that's a different issue.

> A language like C but with lambdas isn't really C, not that that's a bad thing. At that point, why not just use Rust?

Does rust have an equivalent to the classic KR book?

Re: Brutal OS reached milestone 4

#48
post #11
post #9

That kerning on that "hello world" vector font demo though

Yeah kerning is still WIP

Honestly the amount of crazy code involved in Linux font rendering[1], and then you get to CJKV support[2], it's mind-boggling. Even then, it's nowhere near as good as macOS :-/

[1] https://gitlab.gnome.org/GNOME/pango & https://github.com/harfbuzz/harfbuzz

[2] https://www.amazon.co.uk/CJKV-Information-Processing-Ken-Lun...

Re: Brutal OS reached milestone 4

#49
post #47
post #40

Earlier quoted context omitted.

> A language like C but with lambdas isn't really C, not that that's a bad thing. At that point, why not just use Rust?

Does rust have an equivalent to the classic KR book?

Did Unix? Does C with lambdas has its K&R?

I don't see why it's some sort of requirement.

Post reply on HN