Kivutar

I've been reading, writing, and translating text in Toki Pona for a year.

My main criticism of the language is that the word are so abstract that understanding spoken Toki Pona at real speed is practically impossible. Too many possible translations. Too many ways of combining these words, and no mechanism to identify which words form a compound.

I'm using love2d, which is good if you want to see only code, no graphical interface.

We never implied that smart contracts were legally binding. They are just code, code can by buggy.

It's the first time I read something this ridiculous on HN.

Am I the only one thinking that it looks easier to interpret Ruby in Go with cgo than doing the opposite like they did in this article?

Also the good part of Go are the goroutines, the channels, the types, the safety...

The article was fun but they will find the limit as soon as they will try to support the important parts of Go.

Trying to go further will just demonstrate the opposite of their point.

No.

Isn't Cyclone 68000 already doing the same thing? The core used in Picodrive.

Yes, I haven't been to engineering school, so in almost every company or open source community I've been part of, colleagues have been mentoring me.

The mentors I had were very passionate about their field and happy to share their knowledge.

The mentoring was not really about small details. More about seeing what technologies and concepts I was comfortable with, and telling me what things I should explore next. It was most of the time very opinionated, but this was OK, as I had more than one mentor.

We have this where I come from (Corsica) and it's not so bad. You have to drink wine when eating this, like stroooong red wine.

Note that even if it's a traditional dish here, only a minority of people are OK to give it a try. Often to impress other people around the table.

My grandmother used to prepare it. It's quite simple to make. Put the right kind of cheese in a pot, cover it with a green cabage leaf, cover and wait for a week.

Exactly.

"Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away."

By simplicity, we mean frugality.

If you can implement something without adding a ton of dependencies, abstraction layers, and design patterns, it will be easier to understand and debug.

YAGNI is everything but abused.

Some years ago, I was developing a Linux distro for embedded systems. Some of these embedded systems come with old kernels, and you will never get a recent kernel for them.

Systemd is written in C and relies on kernel headers. Which means that they need to have a layer that deals with different versions of the kernel headers. I remember it was headers about network.

At the time I was working on this, I had to contribute to systemd to add support for my kernel version. Got a few patches accepted in their master. And things were working fine for a while.

Until they suddenly decided to drop <= 3.10 kernel support. Yep. Afterwhat I had to maintain patch sets for systemd, which is a great amount of job, given that my upstream was updating systemd quite often.

Now my good people, explain me how such a mess could have happen with a previous init based on shell?

There is a libretro version of the DOSBox emulator. If that's what you want. It's not yet in the default installation but can be added using the core updater.

No. We don't ship KODI. We do ship ffmpeg as a libretro core, but it's not accelerated.