Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
mawildoer
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
13 ms
·
1.
▲
Malware Masquerading as MCP on PyPI
(inspector.pypi.io)
5 points
by
mawildoer
1y ago
|
1 comments
2.
▲
by
mawildoer
1y ago
I wanted to setup a slackbot to manager Doordash orders for our company. Starting with PyPi "Doordash Client": https://pypi.org/search/?q=doordash+client I was excited by 5 recently published packages. As I u
3.
▲
Show HN: Make the Most of Python's ExceptionGroups
(github.com)
3 points
by
mawildoer
1y ago
|
0 comments
4.
▲
Show HN: GitHub Actions OIDC for Python That Just Works(TM)
(github.com)
6 points
by
mawildoer
1y ago
|
0 comments
5.
▲
by
mawildoer
2y ago
I thought it was a big upgrade. Comparing Zerox w/ Unstructured on the first 5 pages of [this datasheet]( https://www.ti.com/lit/ds/symlink/lm5117.pdf); zerox gave me what I wanted, and Unstructured gave
6.
▲
by
mawildoer
2y ago
It's interesting how it ignores things like headers and footers. LLMs have an edge there in "deciding" whether to include something in the output or not. It'd be great if your hosted version would also accept a URL to a
7.
▲
by
mawildoer
3y ago
We have some plans and atopile already supports some configuration regarding those deviations. There's a component selector which can choose resistors, caps, inductors etc... from a database of known components. Currently it's a f
8.
▲
by
mawildoer
3y ago
Lot of good stuff! We're working on some updates to the package manager now that should make a lot of that super tenable to build out.
9.
▲
by
mawildoer
3y ago
Not at all! Thanks so much for engaging with us on this level. It's greatly appreciated!
10.
▲
by
mawildoer
3y ago
You're not the first person to ask for alternative syntax highlighting! Might be something we need to address soon. I think an LSP server is what we're really excited about, since it also means we can provide far richer autocomple
11.
▲
by
mawildoer
3y ago
You're right about "code" not being the right solution for everything. In the case of the layout we have indeed already already implemented an MVP of the "snippets" approach you described: https://atopile
12.
▲
by
mawildoer
3y ago
If we can build the equation solver our hearts are set on, you should be able to account for as many factors as your design requires - albeit with some performance limitations at some point. That is, assuming temperature can be factored int
13.
▲
by
mawildoer
3y ago
For sure! You've made two super important points; how can I trust it shuffling things under me and how can I justify trusting this thing if it's going in long-lead or production hardware (stuff that's hard to fix) The first o
14.
▲
by
mawildoer
3y ago
We hear you! We're most certainly planning on eating up the system's chain to describe, version control and validate up the system's chain. As one example in an earlier (and likely future) permutation of atopile we could comp
15.
▲
by
mawildoer
3y ago
Thanks mate!
16.
▲
by
mawildoer
3y ago
You're right. It definitely is currently. This is a hole we're planning to fill between linters and a language server. Picture a red-underline under an instance which is insufficiently configured, for example
17.
▲
by
mawildoer
3y ago
Thank you!! That's just about the workflow as where we lie today - albeit without the full suite of potency we're working towards. I haven't actually used Onshape, so I'm not intimately familiar with their constraints sy
18.
▲
by
mawildoer
3y ago
We're largely on board with the same problem's we're trying to tackle, and I most certainly understand why you're making these criticisms of these trivial examples and our current implementation. You're right to - t
19.
▲
by
mawildoer
3y ago
Sorry, not quite sure what you’re asking. Mind rephrasing?
20.
▲
by
mawildoer
3y ago
Super! So far that’s all we support for layout and we love that it’s also super-low-barrier to entry OSS.
21.
▲
by
mawildoer
3y ago
You're absolutely right! We've been thinking very similar ways about "dipole" components and how to best do this; and I think you've nailed it. What about using dunder __in__ and __out__ attributes? Easy enough to i
22.
▲
by
mawildoer
3y ago
Definitely agree this isn't taking away EEs - anytime soon or ideally ever! The goal is to make EEs far more potent, rather than bring SWEs to hardware (although letting them easily tweak existing board's filter constants, vdivs e
23.
▲
by
mawildoer
3y ago
We share similar thoughts about the core of the auto-routing/placement/simulation issues being UX! We're a bit more bullish on code being able to fix that as well. Noticing that these tools are infrequently even configured be
24.
▲
by
mawildoer
3y ago
Great question! We hope we have a few good reasons. This iteration of the project actually came after first working with and then modifying another awesome project called SKiDL ( https://github.com/devbisme/skidl ). It&#
25.
▲
by
mawildoer
3y ago
We're also super stoked about getting topology and equations together in the same file (and even code-base!) The equation solver is soon on our roadmap: https://atopile.io/roadmap/#language-features
26.
▲
by
mawildoer
3y ago
Not even quite synthesis yet! We're well aware there's quite a lot out there that's fairly analogous - but nothing that's quite translated to the space, despite a few efforts as pointed out above. There's a few part
27.
▲
by
mawildoer
3y ago
That's awesome! We're definitely thinking along the same lines in terms of a lot of those optimisations / cost-functions. Here's some of the basics Tim was playing with earlier: https://github.com/atopile
28.
▲
by
mawildoer
3y ago
Interesting! Haven't come across it before but those linked `~>` operators do indeed quite familiar. If you're familiar with GraphDSL do you have some elements we should look into?
29.
▲
by
mawildoer
3y ago
Absolutely love to hear that! 100% agreed about the ecosystem too. We've already created a perhaps-too-scrappy package manager, but it works! https://packages.atopile.io/ We're pretty convinced that the awesomenes
30.
▲
by
mawildoer
3y ago
Great question! Current HDLs tend to primarily be focussed on digital circuit design, while at the PCBA level, there's a lot more focus on the "fuzziness" of the physical world (eg. tolerances). We also noticed that most EEs
More ›