I looked into switching to zstd recently however at least crane the utility that rules_oci uses to upload containers does not yet support uploading zstd layers.
Issue is over two years old. Man it is so sad how hard it can be to upstream work to big open source projects. I have a number of PRs open on both the kubernetes and etcd projects and it is almost impossible to get anyone to review them, and since nobody will review my PRs I cannot get enough work under my belt to be a committer. Sometimes I feel like if you don’t have an @redhat or @google account people just ignore you.
Brain Corporation | Many Software Engineering roles | Hybrid and Remote | full time | San Diego CA
Brain Corporation is looking for software engineers to help us build our autonomous mobile robot (AMR) platform. We have open roles within our Cloud and Robot platform teams as we start to ship our next generation AMRs.
I've worked with this poster before for a few years before moving on to break into a different industry. Fantastic engineer, great person to work for. I highly recommend sending your resume their way.
A big issue with botnets running on device owner equipment is the amount of bandwidth they "steal" from the device owner. Especially for device owners who are on constrained networks (such as a mobile/satellite network) this can be a really expensive issue for the device owner.
So while the device owner may not be the primary victim, they can definitely still be heavily affected.
Brain Corporation | Multiple Roles | Full Time | Hybrid (Onsite as needed) | San Diego
Brain Corp is a team of innovators, surfers and, well, brainiacs, that love bringing robots to life through pioneering AI software technology. We take great pride in helping our customers build smarter operations around autonomous robots that are safe, intelligent, and easy to use so they can help people in everyday jobs within environments such as retail stores, malls, airports, hospitals, and more.
We are hiring for multiple roles including a Senior Data Engineer and a Cloud Software Engineer.
Brain Corporation | Multiple Openings |San Diego, CA |
Brain Corp is a San Diego-based AI company that specializes in the development of self-driving technology. We are taking our proprietary BrainOS (robot operating system) and putting it on machines to turn them into self-driving, autonomous robots. We have raised $110m from SoftBank and Qualcomm Ventures.
We have announced partnerships with Walmart in the US and Softbank Robotics in Japan and have over 10,000 mobile, autonomous robots in commercial environments.
We are hiring across all engineering functions (Research, Software, Electrical, Mechanical). Our full job board can be found here: https://www.braincorp.com/careers
Highlighted openings:
* C++, Rust, Python Developers (Linux)
* Go, Typescript Cloud Software Engineers (Jr & Sr levels)
* Software Test Automation Engineers/ SDETs
All positions are posted on the website link above. We have great benefits including lunch catered daily, unlimited snacks & drinks, unlimited vacation for exempt positions, and 4% 401k matching. Typical Interview Process: recruiter phone screen, take home test, technical phone/video screen, onsite, offer.
Contact us at careers@braincorporation.com if you don't see a role that matches; feel free to send your resume over to us and let us know what you would be interested in.
Intermediate packages permit you to choose different deployment situations later, with minimal additional cost now. Tying everything to Docker images ties you to Docker and removes your ability to transition to other systems. It may not be worth the cost now, but as soon as you want to deploy on more than one platform it can become critical to maintaining momentum (vice having to hand tailor deployment for each new environment).
We've been going that direction. Packages integrate better into multiple use cases (e.g. VM images, containers). Running a properly signed apt repo is easy these days, so why not?
For people that disagree with this model: where do you think the the software comes from when you apt/apk install things inside your Dockerfile?
Most people don't need to do that. You can build things you need as part of the image build. No need to setup a deb or rpm package unless you're also installing it that way somewhere else.
We use jfrog. One jenkins job builds our code into a .deb and pushes it there. Another job builds the VM image which is then deployed once testing passes.
Data scientists at my previous company switched to https://github.com/has2k1/plotnine when we made a big push to python. Bit closer api to ggplot than Altair.
Its really great to see more AMD options for cloud instances. Now I'm just waiting for more ARM architecture options. Not having to cross compile code (a1/m6g AWS instance types) has been very useful in my day to day job.
I wonder if this will be useful for electron based editors like vscode's vim plugin. I know the plugin is "good" but I always find something that works in vim and doesn't in the plugin and end up going back to my terminal.
I recently found Oni, which aims to be a web-tech UI for neovim. (The new version should even support the full VSCode extension API / ecosystem) https://github.com/onivim/oni2
The office 365 support could be implemented using the jupyter kernel protocols rather than transpiling to javascript. That would give them a consistent behavior across desktop and web and even open the door to support more languages in the future if they really wanted to.
https://github.com/google/go-containerregistry/pull/1827