Sleef is a SIMD library that is often used (transitively) when working with LLMs.

Its maintainer now requests $1000 for approval of PRs.

Here is an example where they reject a small PR to add loongarch64 support from individual contributor: https://github.com/shibatch/sleef/pull/672

First, where does it say it costs $1000 for PR approval?

Second, what's the problem? The person who opened the PR is adding code support for the feature; the repo maintainer says they need a dedicated CI environment for that new feature; the person who opened the PR is unwilling to meet that condition.

If they can get the data without a user's consent, then it's independent of this new feature and thus unrelated. If you believe that the government has unlimited access, then it was most likely already possible before this feature. Now, there is at least a "proper" way to give law enforcement access.

In that case they don't need consent anyway and it's not about this new feature.

A similar project: https://toitlang.org (or https://toit.io).

Currently it's only targeting the ESP32 family, but the code is pretty portable. By default, it probably also needs more resources due to OS-like abstractions, allowing for multiple containers to run on parallel, etc. Obviously that also brings some nice advantages. For example, installing or updating, a new container is just a few lines of code.

We have been working on it for more than 5 years now, and it's definitely at a stage where lots of projects would benefit from it.

Let me say that Florian and co are super helpful and responsive with code examples, fixing bugs, and have built a very dependable language in Toit.

What's the advantage over MicroPython?

Speed and reliability.

We found that Python isn't really designed for constrained environments. The object model, in particular, makes it hard to have fast method calls. The memory layout is also affected by the language, leading to bigger objects and a worse GC.

If you are just running a small hello world, or a number crunching loop, then both languages behave similarly. However, if you actually want to run something more consequential in production you will have an easier time with Toit.

Speed: maybe, sometimes. Of course, MicroPython makes it very easy to create modules written in C, accessible from MicroPython. So if you need extra perf you can always write a smattering of C.

Reliability: I don't see why Toit would be any better? FWIW we make medical devices using MicroPython and have tests that have run for many months with no failures. MicroPython, the language, is extremely reliable and thoroughly tested [1], though admittedly the port-specific code can be less so.

We've evaluated Toit and it has some nice features (the containerization is novel and powerful!)...but it's a quirky language with sparse peripheral support. Ultimately it's trivial for Python-familiar developers to switch across to MicroPython - a big benefit. Being constrained to the ESP32 is a limitation that many of our customers would not allow.

[1] See the py folder: https://micropython.org/resources/code-coverage/

You will improve your language skills this way, but if your skill level isn't high enough it's going to be exhausting to the native speaker as well.

I have been living in Denmark for 15 years now, and it's still easier to do conversations in English. When I speak Danish it requires more mental capacity from the other side.

I am speaking Danish from time to time, but it's only to get better at it. The English proficiency in Denmark (and probably the Netherlands) is so high that you need to be really good at the native tongue before it is easier than English in conversations.

This is my point. especially in a country where everybody speaks English anyway. you will never be better at Dutch than English so by that logic. it will always (or at least for many years) be more difficult to talk to you in Dutch. so, ask the hard question:

Are you learning it to actually talk to other people?

If yes, just do it. to many people it is endearing if you are struggling with a language. And if they don't like it they probably just don't like talking to you in general so learned or not doesn't matter.

I think many people are scared of talking and use language learning as an excuse for fear. You can start talking to real people or you can keep learning and never talk to real people and then what's the point.

Balcony solar requires the 50Hz of the energy grid. If you turn off the main power they will stop feeding into the system.

Technically probably yes, provided you had millions of neighbors, the sun never sets and all big users like kettles and heat pumps kindly switch off as well. If either of those conditions stops being true, then either the frequency or the voltage will drop too much and the panels turn themselves off. In practice these balcony panels are not sufficient in the slightest to power a house, let alone an entire apartment building, and they will turn off almost instantly.

I implemented `DateTime` in Dart and Toit and wrote a blog post about the things I noticed: https://medium.com/@florian_32814/date-time-526a4f86badb

Timezones are fun...

I have aphantasia, and I don't feel handicapped at all. The only thing where I really notice differences is when trying to describe people. Since I can't visualize them in my head, I can only describe "known facts", like "they have brown hair". I would make a lousy crime witness...

This was my biggest puzzle as a child: how do all those people in crime shows describe suspects? And was it just made up?

The other ones for me:

- "go to your happy place", or "imagine you are on an island..."

- counting sheep to fall asleep. I just couldn't visualize them.

I still counted them, it just didn’t make sense. It was more a spreadsheet - spreadsheep? - than visualizing real sheep.

And it didn’t help me fall asleep at all.

I had to laugh so much because of spreadsheep. Thank you.

When I tried counting sheep it was very hard work: like stop motion animation. First picture a sheep, move it one frame, then re-draw everything including the fence that vanished every frame. It could easily take many minutes to move on sheep over a fence and exhaust me.

Same here. The scene where the witness describes the criminal's face in detail while the sketch artist can render a perfect drawing - I assumed that was pure Hollywood fantasy. Then I met people who could effortlessly recall/draw to that level and realized that wow it's real, but not for me.

I thought it was all metaphorical or for dramatic effect.

If I think of basically anything technical I get an image in my head. Any algorithm I write first exists in my head as a visualization of what I want to do. If I can't visualize what is going on I can't understand it and am in a state of confusion.

I might not have complete aphantasia, when trying to imagine an apple I struggle to imagine it beyond a circular form with a rod pertruding from an indent at the top. No color, no texture. As soon as I try to add more detail the previously imagined details dissapear and I have to circle back and reimagine them. Like having a very limited amount of draw calls every frame.

But I don't feel like I am impacted in imagining simple algorithms. I also construct them of very simple forms and rearrange them in my mind. I also feel like it is a lot easier for me to imagine things „automatically“ due to it being memories or being a byproduct of thinking about something. But my mind struggles constructing these images at will.

Also taking a pen and drawing these things up can replace some of the missing imaginary power :)

> As soon as I try to add more detail the previously imagined details dissapear and I have to circle back and reimagine them. Like having a very limited amount of draw calls every frame.

This matches my experience - I think of it a bit like a really slow CRT, the phosphorescence fading before the image can be composed.

I used this technique to send data from the cell-phone to an ESP32 using the phone's flashlight: https://www.reddit.com/r/esp32/comments/wfea4r/send_data_wit...

In vscode: ctrl-d selects the word at the cursor, or the next occurrence of the current selection. Use it all the time.

In bash: alt-. copies the last argument of the previous command (history).

I can't get ctrl-. to work as you say, but esc-. calls up the last argument of the previous command. It's nice for when it's a long file path because you don't have to type it again.

My mistake. It's, alt+., not ctrl.