CircuitHub founder here. Most fab by order volume is in the US, but for now, at least, we do have to source some fab from overseas for various reasons.
This would be super interesting as an open-core company. In particular, we would want direct access to the underlying SQL database and the ability to customize the code directly.
hey - we'll think about this. In the meanwhile it is still powered by the same high-performance customizable ledger from our earlier ledger api pivots - it is 100% accessible via API.
Interesting to see exponential growth in NixOS github stars https://star-history.com/#NixOS/nixpkgs&Date . Perhaps the user base is reaching a tipping point where there will be the resources to address some of these problems.
Currently running our corporate VPN on Wireguard, would highly recommend. Wiretrustee looks like a very useful featurset on top of Wireguard, nice work.
I'd be interested to hear more about how you're using NixOS if it isn't something you've already written about. My guess is that you're mostly leveraging the declarative configuration and immutability for internal infrastructure use. What I'd love to see would be consumer devices using NixOS, allowing updates (especially security patches) to be deployed to endpoints without too much fear that it will brick something. I think that would allow companies to more inexpensively maintain their IoT devices throughout their lifetime. I imagine a device where it could automatically revert to the last working generation if a new config fails for some reason.
NixOS probably helps with this, but it isn't a requirement - some devices already have a dual-root-type setup where they update the inactive root, boot into it, and the boot sequence doesn't mark it permanently active until it boots properly, reverting to the original root if something goes wrong.
I think if more devices aren't doing this kind of thing then the cost might not make sense to them at all. Perhaps they aren't bricking devices often, or perhaps their support load is low.
But I'm only speculating. I'm all for more NixOS if it helps people.
>dual-root-type setup where they update the inactive root, boot into it,
Fedora-IoT effectively does this with rpm-ostree + greenboot.
Greenboot specifies a series of directories under /etc that organizes your custom scripts (scripts that must not fail, scripts that may fail, scripts to run on success, scripts to run after previous failed, etc) then it marks your current ostree as either being active or auto-rollsback into previous.
Deepmind is owned by a US company (Alphabet) and located in the UK.
Universal Robots is owned by Teradyne, also in the US.
ABB I don't know. How are they market leaders?
Also, looking at ABB it seems this are those old industrial robots with few degrees of freedom. The future will be less specialized robots with more degrees of freedom. Powered by AI, not by explicitly coded motions.
DeepMind was never a business (and never will be), it's an AI R&D toy for a trillion dollar tech company. It was always going to end up in the belly of a larger tech company, and the US has all the dominant tech companies outside of China.
Besides, it's fair game. The US had one of the two global leaders in AgTech in Monsanto, which was captured by the Germans. That repeatedly happens in biotech as a prominent example, most of the European biotech industry was built up on the back of acquiring US biotech companies.
Even ARM Holdings was originated heavily by US companies. There is hardly a piece of the global tech market that wasn't directly financed or made possible by the US tech industry and its mountain of profits and VC money, from SoftBank to China's tech companies to Shopify or Atlassian.
Captured? Enabled. DeepMind runs at big losses, only a company with enough firepower and vision such as the GAFAMs could (and luckily did) save DeepMind.
Our startup runs on Haskell. I was worried about this initially but in practice finding great Haskell developers has been no more or less difficult than finding great developers in general.
Yeah, finding a decent Javascript or C++ developer is actually very difficult - everyone thinks they know C++ and Javascript when in fact only a small minority actually do.
Thanks! I'm at omri@routable.com if you want a walk-through
We built support for custom fields on NetSuite - we did the research and 99% of our competitors decided not to support it because it's a lot of work and hard to maintain.
I'm a longtime Ubuntu user and recently gave NixOS a try as most of our team use it. I have to admit I was highly skeptical as it all looks very complicated. The learning curve was a bit steep due to the documentation and odd terminology. But after you get going it solves so many problems. The fact you can declare you're entire desired set up in a single configuration.nix then "nixos-rebuild switch" and you're done saves so much time.
I tried to fully switch my work environment to NixOS 2 or 3 years ago. I really like the concept and I think it's a very good approach to reproducible build environments, in theory it's much cleaner than the massive data replication you get with e.g. Docker.
I only lasted for a month or two though, for a couple of reasons. The main one was that I had a lot of trouble with Python packages - Nix suggests a certain approach for dealing with them which didn't work very well for me and I didn't manage to set up an alternative that I liked. (For Haskell I loved working with Nix though!) A lot of software I use also wasn't available in the repositories and I tried to build some packages but found the Nix language a bit obtuse. The basic syntax and logic are not too hard but I still found many of the packages I used as examples very confusing.
In the end I'm back to Ubuntu using Docker whenever I need reproducible environments.
