HN user

tgirod

60 karma
Posts0
Comments22
View on HN
No posts found.

Nice project! Coming from computer science, I've been dabbling with electronics a bit. My path so far has been (sorry if I'm pointing the obvious):

0. computer science

1. arduino programming + very basic circuits

2. adding a few chips and talking to them through I2C/SPI: still in digital circuits territory, sending 1s and 0s

3. designing my frist PCBs with kiCAD: a huge learning step, and things start to get a bit messy (component tolerance, transmission delays ...)

4. looking at analog circuitry / alternative current / signal processing : a HUGE uncharted territory, full of promises and headaches.

This trajectory is probably quite common, and I'm sure atopile has a role to play there, when you start growing out of arduino. Making things a bit smoother, searchable, reusable, being able to learn from other people's design - what a wonderful tool it could be!

Can't find the source right now, but I think I've read a discussion on pijul's forum about its ability to change the tokenizer depending on the file type, for a more meaningful granularity level. I think someone was talking about plugging treesitter there to get an AST.

a few days ago I helped my neighbour install some light fixtures in her house. She was sold some smart lightbulbs with it because you can dim them and change the light color a bit from a remote control. There are 6 or 8 lightbulbs next to each others.

I'm impressed how unreliable this tech is. Standing 2 meters away from the lightbulbs, I had to press 3 or 4 times the off button to turn them all off. I just don't understand why you would knowingly install that kind of crap.

s/vais/suis/

I think the point you are making is grammatical: in pretty much any language, the most common verbs are irregular.

But isn't this poem more about orthography and pronunciation? Some languages are much more regular than english in that regard.

Well, first there is the common sense part - infinite growth with limited resources is likely to bump on a wall at some point. Someone (especially here) will probably argue that the resources are not really limited because technology and spaaaace, but that's precisely the kind of hubris I was reacting to in the first place.

I think the first extensive study on the subject is [the limits to growth](https://en.wikipedia.org/wiki/The_Limits_to_Growth).

A compelling thing I've seen (sorry can't find the exact source, I think it was from [the shift project](https://theshiftproject.org)) is the very strong correlation - almost linear relation - between GDP, energy consumption and co2 emission. So far we haven't been able to decorrelate those three.

IMO the problem here is the leap of faith you are making by believing an untested technology, operating on a planet scale, will help.

We only have one planet here, so instead of betting on a massive terraforming technology to suck the CO2 out of the air, I'd rather use a more conservative approach such as massive reforestation - something that is low-tech, can be done by anyone, anywhere, and improve the resilience of the ecosystem rather than kicking its balance again.

Hey, we are fucking up the environment by altering such a complex system way too fast for it to keep balance. Maybe if we alter it on a whole new scale with our limited understanding of the consequences, we can fix things up?

To be more constructive, this is exactly the kind of hubris that gets me very wary of technoscience.

Let's assume Project Vesta is run by well intentionned folks and has the potential to offer a net positive in a distant future. Even in those conditions, such a project serves the toxic political agenda of not facing the elephant in the room: our growth based economic model is not sustainable and we need to transition away from it.

Interesting read, but I think the first part would benefit from a detour toward interfaces, why they are not good enough to solve the sort problem, and how contracts can help.

IIRC it is along those lines :

You could define a `Lesser` interface with a method `Less(Lesser) bool`, and implement this interface on what you want to sort, but then you would have no way to assert at compile time that x and y are of the same type in `x.Less(y)`.

As I understand them, contracts allow you to assert things like this.

I agree with you. When I play, the "best" invaders tend to be the easy targets that have drifted to one side of the screen.

Here is a proposal for another fitness score: everytime a bullet is shot, raise the score of every survivor, weighted by the distance between the survivor and the bullet. The closer the bullet the better the fitness.

Intuitively, I think this would select for better dodgers.

Long time ago I used to make amateur remixes, and one tricky part was to isolate vocals from the remixed track. To do that I was using the noise removal tool: select a part of the track without vocals, run a spectral analysis on it and then substract the result to the whole track. Most of the time the result was terribly mangled, but sometimes I got something usable.

this demo got me thinking: if I want to remove something very specific from one track instead of learning a generalized filter, can I train this model with a smaller dataset, like a few seconds from that track?

I've been using this software quite extensively to design a small 25m2 house I'm building earlier this year. It can be a bit rough around the edges, but it's already quite usable and powerful!

IMO the main issue is that the constraint solver recomputes everything whenever you add/move something, even though past additions are already properly constrained. As a result, the software gets less and less responsive as your design gets more complicated. I don't know if the devs adressed that issue (it's a tough one), but I know it was already on the radar a few months ago.