Timot05

7 ms·

1.
by Timot05 4mo ago
agree with all of this. Though i'd say: since the language is mostly read by humans rather than written, in my opinion, it makes even more sense to have a language syntax that actually matches intent. In the case of Machine Learning, i
2.
by Timot05 4mo ago
I’m relatively new to programming but I wish they had used a functional language syntax rather than an object oriented one as the basis for mojo. From my experience, AI revolves a lot around building up function pipelines, computing their d
3.
Dekal – Design CAD kinematics with code(demo.dekal.sh)
1 points by Timot05 7mo ago|0 comments
4.
by Timot05 1y ago
Nice kickstand!
5.
Building CAD Assemblies with Functional Programming [video](youtube.com)
3 points by Timot05 1y ago|1 comments
6.
by Timot05 1y ago
Skip to 6:22 for the action. Feedback is welcome. Thanks!
7.
by Timot05 3y ago
Honored to be there!
8.
by Timot05 3y ago
Thanks! And glad you are making your way towards electronics. Yes, we hope for the packages.atopile.io to become a place where you can share your designs and explore what other people have built.
9.
by Timot05 3y ago
Pain might not have been the right word indeed. The aspect we wanted to point to was rather the fact that we had to do it over and over again. And so from that perspective it became a “pain”. Ultimately we do love electronics. This is one o
10.
by Timot05 3y ago
Thanks for sharing! We will have a look
11.
by Timot05 3y ago
Thanks for your detailed answer! Tons of information in there. To your point about how the work gets divided, I don't think that work will necessarily be distributed amongst many people for a given design but code gives you a couple of
12.
by Timot05 3y ago
Fully agree! We'd much rather be in a situation where criticism is consistently thrown at the project so we can further improve it rather than having positive feedback and the discussion just stopping there.
13.
by Timot05 3y ago
Thanks for sharing the docs! Our language is mostly declarative at the moment. There are some features we discussed that would be imperative and we might introduce them in future versions of the compiler.
14.
by Timot05 3y ago
Well designed schematics are great. Especially if you are sharing them with your team as documentation. The point we would like to move towards is one where atopile enables you to generate high quality documentation about your design in a s
15.
by Timot05 3y ago
Autorouting would for sure be a valuable tool to add to EEs toolchains. The reason we focused on the language first is because it is critical to provide high quality information to autorouter for them to do a good job. And achieving that wi
16.
by Timot05 3y ago
Thanks for sharing this blog post! Super cool to see how things were done early in the industry! Counterintuitively, I do agree with your points. We didn't end up designing the ato language because we actively wanted to end up there bu
17.
by Timot05 3y ago
Thanks!
18.
by Timot05 3y ago
I do think that is fair. The reason that we don't have a visualizer is not that we don't want one, but rather that the value to effort ratio is quite low (and really because the effort is high, not because of low value). I'm
19.
by Timot05 3y ago
Yeah, I think we only allow import x from y for the minute. And because we don't have a language server yet, it wasn't obvious that it was an issue. That'll change soon when the server is up though!
20.
by Timot05 3y ago
From a security perspective, it does help that ato is not executable!
21.
by Timot05 3y ago
Great point. We'll change that soon! Especially true for interfaces too since modules might have tons of accessible interfaces and the language server could list them out for you. Did you see the ESP32 in the package registry? https:&
22.
by Timot05 3y ago
Aspects of the python lexer and parser implementation were borrowed from python, which is partly why we ended up here. I do agree though.
23.
by Timot05 3y ago
Hey everyone, if you want to see a complete project, please check out the Spin Servo Drive that Narayan designed: https://github.com/atopile/spin-servo-drive It can be a good example of how to setup an ato project.
24.
by Timot05 3y ago
NetlistSVG is great yeah. We had a play with it. We had a visualizer in the compiler early on in the compiler implemented with JointJS. But it was a pain to maintain and difficult to get value out of. I'm sure we will have some flavor
25.
by Timot05 3y ago
Hadn't thought about the BOM line one but that definitely makes sense. The implementation I linked is definitely math heavy but might actually not be the best idea. As you say, the cost functions has steps. For less than a given amount
26.
by Timot05 3y ago
There are actually two steps to the design process: - First, requirements. In ato, you define how your circuit is connected and the requirements for the components that sit within it. From there, we generate a netlist and a BOM. - Second, t
27.
by Timot05 3y ago
Yeah the side by side thing makes sense. Especially for very low level or analog designs. But in some cases it wouldn't be desirable to show the whole circuit. Say you are dealing with a module that has been characterized and that you
28.
by Timot05 3y ago
Had a play here for equations: https://github.com/atopile/atopile/blob/tim/equations/sandbo...
29.
by Timot05 3y ago
We do agree. We built an early version of a viewer in the project but later moved away from it because it wasn't good enough to interact with. We might come back to it with something that is more targeted at inspecting only sections of
30.
by Timot05 3y ago
Oh yeah we did think about that. Would be cool to have an ato package for a keyboard! Or maybe a script that generates both the CAD (with OpenSCAD or similar) and the ato code would ne nice.

More ›