For about first 5-10 years of its existence DuckDuckGo also promoted their use of Perl, and afaik they contributed to Perl development.
For about first 5-10 years of its existence DuckDuckGo also promoted their use of Perl, and afaik they contributed to Perl development.
- https://en.wikipedia.org/wiki/Honda_Motocompo in 1980s and
- https://motocompacto.honda.com just a few years ago. This one is electric.
* They came with a mail and chat (IRC) clients, a download manager, a set of browser dev tools, and in the age of limited internet traffic all of that was smaller than a single download of Firefox.
* Their dev tools were the first that allowed remote debugging. You could run Opera on your phone (Symbian, Windows Mobile, early Android) and debug your website from a computer.
* They were the first browser to sync your bookmarks, settings, history, extensions across devices.
* They were the first to add process isolation, albeit initially on Linux only. If an extension crashed your page it didn't take the whole browser down with it. This was later added first by Microsoft in IE8 and then by Google in Chrome.
Their browser was a brilliant piece of tech and a brilliant product. Too bad that the product couldn't survive under pressure.
I’ve seems like a great tool, but I remember thinking the same about piping, too.
uv seems like a great tool, but I remember thinking the same about pipenv, too.
I’ve seems like a great tool, but I remember thinking the same about piping, too.
Very direct, very plain and detailed. They cover all the bases about the why, the how, and what to expect. I really appreciate it.
Best of luck to the team and hopefully the new home will support them well.
For the past 8 months, or so, I've been working on a project to create a Linux-compatible kernel in nothing but Rust and assembly. I finally feel as though I have enough written that I'd like to share it with the community!
I'm currently targeting the ARM64 arch, as that's what I know best. It runs on qemu as well as various dev boards that I've got lying around (pi4, jetson nano, AMD Kria, imx8, etc). It has enough implemented to run most BusyBox commands on the console.
Major things that are missing at the moment: decent FS driver (only fat32 RO at the moment), and no networking support.
More info is on the github readme.
https://github.com/hexagonal-sun/moss
Comments & contributions welcome!
Would something like Smoltcp be of help here? https://github.com/smoltcp-rs/smoltcp
Great project either way!
How do you decide which sys calls to work on? Is is based on what the user space binaries demand?
Historically, these candidates have been the hiring sweet spot: less risky than brand new engineers, still small enough experience to efficiently mold them into your bespoke tools and processes and turn them into long-term employees, and still very cheap.