>> Even if it only catches one small, it could save thousand of dollars down the line.
Or it could send a design team down thousands of dollars in false positives/false negatives. With zero benchmarks provided, it is very fair to question a product that could have material negative impacts on a hardware team.
The tool would ideally classify the output into levels. Just like a compiler or DRC checker. If you submit a clean design, the tool should not be throwing major flags. 99% of the time you should be getting advisory outputs, which should not be tricking any designer. The 1% red flags should easily be understood and if you, as the designer, can't discern them, perhaps you don't understand the fundamentals of your own design.
This is really great, both from a specific application perspective, but also the approach. Really enjoyed looking through the repo and was inspired by your work.
C#/dotNet has Ahead of Time compilation that works very well with containerization. Obviously there are still overheads for the AoT runtime, but it is pruned.
AOT would solve a lot of these problems if it didn't have show-stopping restrictions like "you can't use reflection" and "you can't use native sessions".
Reflection doesn't work with AOT because there is nothing left to reflect on... it's compiled away. You can't use reflection with C, C++ or Rust either, doesn't mean you can't use them for useful things.
I had an Abloy Protec2 malfunction while locked (PSA don't use them for key-only sashlocks) and the locksmith drilled it out in ~10 seconds. That is the last time I spend that kind of money on a lock!
My assumption is that there could be higher dimensional 'token' representations that can be used instead of vision tokens (though obviously not human interpretable). I wonder if there is an optimisation for compression that takes the vector space at a specific level in the network to provide the most context for minimal memory space.
Naturally, moral is a relative term when it comes to companies in a society like ours. However I would say Purism, Pine64, Raspberry Pi, or Framework would be acceptable.
If you close your eyes on cozying up to authoritarian regimes. Apple operates in China at Beijing's pleasure. Much of it is behind the scenes because that's how Chinese like to do. Compare that to US, where everything is a show. Look no further than the gold plated plaque that Apple gave to Trump. That was shameful.
Funny thing is, we can assume that all the nasty stuff happens in China... but Apple is still a US company.
However Tim Cook kisses up to Trump in public is corollary to how he kisses ass in private. If Chinese iCloud servers had backdoored HSMs installed without anyone throwing a hissy-fit, imagine what kind of control the US Government has had for the past decade...
and of course you can do that if you wish, as many CSV libraries allow arbitrary separators and escapes (though they usually default to the "excel compatible" format)
but at least in my case, I would not like to use those characters because they are cumbersome to work with in a text editor. I like very much to be able to type out CSV columns and rows quickly, when I need to.
It’s all a pros and cons.. the benefit of those characters are they are not used anywhere else, hence you never have to worry about escaping/quoting strings. But obviously most of my csv usage is automated in/out.
Or it could send a design team down thousands of dollars in false positives/false negatives. With zero benchmarks provided, it is very fair to question a product that could have material negative impacts on a hardware team.