Hacker News new | past | comments | ask | show | jobs | submit | mmstick's comments login

They sell high end Linux systems, and maintain the Ubuntu-based Pop!_OS Linux distribution. The Lemur Pro — and other Intel-only laptops — are running open source firmware developed by System76 in collaboration with Intel.

Who buys computers from System76? People that care about buying hardware that's guaranteed to work with Linux, from a company that supports Linux. That ranges from web developers to NASA.



You can purchase a USB3 to 1G ethernet adapter for $10.


A right pain, but more importantly you lose your only usb3 port


Not if the gigabit ethernet adapter is also a USB3 hub, like so: https://www.amazon.com/USB-Ethernet-Splitter-HUB-Network/dp/...


Do you support the 19.10 release? The inability to compile or package every version and variant of TF, and GCC9 conflicts with both the CUDA SDK and Tensorflow, is precisely why we created Tensorman.


Lambda Stack supports 16.04 and 18.04 at the moment.

It's value prop is to enable people to easily install TensorFlow / PyTorch and their dependencies in a container-less fashion. Though it doesn't provide the isolation of containers.

What I've learned from talking to customers is that many people don't care that much about handling multiple versions of the same framework. I wouldn't be surprised if you find that, like Lambda Stack, people are mainly using this product to easily get started with TensorFlow/Pytorch.

Now that TensorFlow 2.0 is out, we will see a much more stable API. People won't have to change their code if TensorFlow bumps up a dependency version. For many, this will reduce the impetus for moving to containers.


Install of PyTorch and CUDA is literally one line in anaconda. I don't remember what I did for tensorflow, but I have it up and running and I am quite the computer phillistine so it could not have been much harder.

Maybe the second part is more of a value prop or good point of focus?


It did not have serious memory bugs. All of the unsafe code in Redox, of which only a small fraction is unsafe, is neatly compartmentalized so that it's easy to audit.


It was a year ago: https://gitlab.redox-os.org/redox-os/redox/issues/1136 https://gitlab.redox-os.org/redox-os/redox/issues/681

And we're talking about a bunch of people randomly clicking / trying things, so imagine what's really inside Redox.


Having written Rust code for 4 years, I'd say it's not the biggest feature of Rust. It's just one of many good points. Among my favorite are the explicit & rich APIs, high level concepts (ADTs, pattern-matching, trait-based generics), and Cargo. The safety does play a big role in shaping some of the features though, and enabling some powerful APIs and optimizations.


He was given a notification by System76 back in January that we were busy with moving into the new warehouse, hardware testing, and developing our 18.04 release. Getting our firmware to work with his tool is not a high priority.


Rust doesn't have a runtime, so there's no runtime code to ship in the first place. It's as low level as C, but with a modern syntax and accompanying core and standard libraries. Thread support is done by using existing OS primitives for threading.


We've already thrown away POSIX compatibility. Linux isn't POSIX. Mac OS X isn't POSIX. Windows isn't POSIX. POSIX only continues to exist in varying degrees at different times.


Although, a lot of us are working towards replacement of C in a lot of areas. Being able to say you've written something in Rust is one thing, but having the whole stack Rust all the way down is something else. Not to mention, it's fairly simple to create C bindings from Rust libraries using Cargo workspaces and cbindgen.


Consider applying for YC's first-ever Fall batch! Applications are open till Aug 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: