lad

Yeah, there are maybe a couple of reasonable ideas like using background and making comments stand out more, but that’s it. Especially weird is the idea about light theme not being used because of syntax highlight

I feel like GPU is massively parallel but still somewhat sync, but I’m not sure.

But what I think about the article is that it mixes a lot of wishful thinking into reality. There were other CPU architectures, including ones without synchronisation, and most of them never left research. In part because current architecture is abundant, but I think that also because making something complicated work async is quite hard.

Same as many long debunked concepts, sometimes even declared wrong by their own original author, it will continue to have followers and will never completely fade away. For this reason I don’t think that talking about it sometimes is a wrong thing

Just wanted to get back to tell that I tried graph1 to mess around with non-linear projection, it seemed like an interesting crate but it felt like it’s a bit too low level for doing a GUI with it.

Agree, setting up rustfmt and then battling other developers about it’s settings is not very fun. But having a standard tool with configurable settings that can be stored right in the repository is immensely better than not

“Why” comments are of course included in “we don’t need that” category

I think my manager is strongly Clean Code inclined. More than once they removed comments, because they will become outdated anyway (so there’s no use explaining what is going on at all, right? Right‽)

I thought it would be useful for filling and finding metadata, but I don’t think it can do that

Most of what I know comes from this educational video 🦇

I don’t know much about JS but I managed to get 10/28

More than once I just went with whatever seems unlikely, but not too unlikely to be logical answer. Using this in production seems fitting only for courageous and strong-willed

I think there’s just too many unfinished features and issues to also start working on GUI

I tried to build simple UI with floem, slint, and iced.

1. slint seems to allow to do the most, it’s GNU GPL, and it allows you to move boilerplate to separate *.slint files much like Qt, imo.
2. floem seemed the most flexible to me, but it requires attaching signals everywhere manually.
3. iced seemed the easiest to use, but not exactly too flexible. I think some looks of the already simple UI I wanted to create were not possible there.

You can check out my repo to see if it helps to answer your question. And yeah, I know the features shouldn’t be mutually exclusive 🌚

I created a file with backspace in name, it was hard to understand why filename doesn’t match

The first one is genuinely impressive

I thought it’s just a matter of colour count, but maybe you need more loops? Mine had more loops, I think, and after third colour it passed

I didn’t think it allows diagonal, because it wasn’t the case for me, that’s evil 🌚

I used the first diagram, but the second seems more helpful. 64th was around five lines down the second step from top, the only important thing is that it’s not split between several lines:

I mean, skill somewhat helps, but it definitely feels like the challenge cuts a little more slack. I don’t particularly believe in my skill growing this much 🤣

For me it says 85 is needed, and it seems to stop once I fall below 80%, so it always ends on 80% exactly

Edit: OK, I’m not sure if it becomes easier over time, like when chess pieces become queens, but I managed to beat it with 87%

There are three possible targets upon reset, I was only able to find a sign