As you note correctly, the ISA is open, not this CPU (or board).

The important point is that using an open ISA allows you to create your own CPU that implements it. This CPU can then be open (i.e. you providing the RTL, etc.), if you so desire

I assume it will be much more difficult (or impossible?) to provide the RTL for a CPU with an AMD64 ISA, since that one has to be licensed. I wonder if you paying for the license allows you to share your implementation with the world. Even if it does, it's less likely that you will do so, given that you will have to pay for the licensing fee and make your money back

Since there is no license to pay for in case of RISC-V, it allows you to open up the design of your CPU without you having to pay for that privilege

Comments URL: https://news.ycombinator.com/item?id=46590473

Points: 11

# Comments: 2

> What if you don’t care about efficiency or causality?

"Yeah, what about if you don't care about money/time and are happy with finding a correlation only?!!?"

My main issue with the protocol is that it is requiring creating a new TLS connection for every request. That is indeed a simple approach but I argue that the extra round trip times added due to this are not worth the trade-off for the simplicity gained in this case

Coming up with a simple way to reuse a connection would reduce the round trips needed drastically. If we put our heads together, I feel like we could come up with a way to do that, that doesn't overly complicate the protocol ...

It's just unlikely that it will get as big of a following as Linux has.

That grants people an easy way to discuss content and to check any prior discussion, if any.

Something like https://lists.sr.ht/~shugyousha/public-inbox for example.

It is well suited for me because

- I like wood

- I like knives

- I'm into typography

- it doesn't require that much work space

I have only just started out but it feels nice indeed! A hindrance is that I am not very artistically gifted, but as long as I make it mostly for myself, I don't mind too much.

Comments URL: https://news.ycombinator.com/item?id=42747005

Points: 2

# Comments: 0

The reason is that in a monospaced font all the glyphs are supposed to the same advance value. This forces the ligatures to always take up the same space as two (or however many glyphs) are involved, which may stretch the ligature glyph in a non-intended way (if it is even possible to rasterise it that way).

Monospace fonts are also often used for programming (because they make sure that the columns line up consistently, regardless of the font being used). I personally don't see the point in showing ligature glyphs that do not correspond to the actual Unicode code points encoded to bytes in the source code.

Just my 2 cents.

There are one or two advantages over regular GUIs, but that's it.

The biggest is probably that they are lightweight since there are no GUI library dependencies (and if there are TUI ones, they are usually much lighter than their GUI sisters). This also means there are fewer (if any) dependencies to distribute compared to a GUI.

The only other advantage I can come up with is that a TUI will have to be usable by keyboard only (in almost all cases). This is not a given for regular GUI libraries.

I'm not a fan of TUIs either. I think the only one I am using regularly is `tig` (https://jonas.github.io/tig/). I guess the reason is that I don't have to remember the git revision list syntax that way and that `tig` allows for easy commit searching with `/` ...

Comments URL: https://news.ycombinator.com/item?id=41389157

Points: 11

# Comments: 5

Even 80ms seems unnecessarily slow to me. 300ms would drive me nuts ...

I'm using a tiling window manager (dwm) and interestingly the spawning time varies depending on the position that the terminal window has to be rendered to.

The fastest startup time I get on the fullscreen tiling mode.

   hyperfine 'st -e true'
   Benchmark 1: st -e true
     Time (mean ± σ):      35.7 ms ±  10.0 ms    [User: 15.4 ms, System: 4.8 ms]
     Range (min … max):    17.2 ms …  78.7 ms    123 runs

Comments URL: https://news.ycombinator.com/item?id=41047110

Points: 270

# Comments: 41

and the code (at least a large part of it in the form of Chromium) is Open Source. I don't think it's as bleak as people make it out to be.

The link is interesting because these emulators seem to be part of the standard distribution of 9Front. Most likely those are written from scratch, given that Plan 9 is not a POSIX system (unless they are using http://doc.cat-v.org/plan_9/4th_edition/papers/ape).

Comments URL: https://news.ycombinator.com/item?id=40104064

Points: 4

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=39446282

Points: 13

# Comments: 5