brson

26 ms·

91.
by brson 10y ago
Honestly, it's extremely taxing to maintain this pace without everything falling apart. The size of the team employed by Mozilla is quite modest. Firefox, which has a similar release schedule, has an entire team dedicated to just getti
92.
by brson 10y ago
I think it is unlikely we will make FreeBSD tier 1 any time soon. The project is stretched beyond its limits with its platform support commitments, and FreeBSD is historically difficult for us to support. The next tier 1 is going to be ARM,
93.
by brson 10y ago
rustbuild can optionally build from vendored (in-tree) source of all cargo dependencies, where it does not touch the network, and that's how we expect packagers to build Rust. I believe Debian has their own bootstrap lineage where they
94.
by brson 10y ago
Yes, the Makefiles were an abomination. Nobody could understand them. The reason the makefiles are so heavily macroized like they are is because of cross-compile bootstrapping, where the build rules are the same in many configurations, with
95.
by brson 10y ago
rustbuild is actually pure-Rust. The entire Rust build is written in Rust (Rust is bootstrapped all the way down!). The python scripts are a slim wrapper that downloads the bootstrap compiler to get into the Rust world.
96.
by brson 10y ago
Graydon has been on Swift for a while, and there are a few other prominent Rust contributors there as well. I hope they are enjoying themselves and make good things.
97.
by brson 10y ago
If anybody is looking for a Rust job, they in fact do exist, and are growing. This Week in Rust lists 5 this week [1], and 5 is more than zero! [1]: https://this-week-in-rust.org/blog/2017/01/17/this-week
98.
by brson 10y ago
And stack probes are one corner case of stack overflow. Rust protects against stack overflow in most cases, on all platforms, in every case on Windows, and is intended and designed to protect against all stack overflow, but it has a bug due
99.
by brson 10y ago
There's little evidence for a "dark cloud" on the horizon because of Rust nightlies, besides people complaining of dark clouds. I'd suggest providing evidence of problems with nightlies and filing bugs about things that
100.
by brson 10y ago
Dependence on the nightly channel has been one of the biggest risks in Rust. The problem is not solved yet, but it will be. The Rust stable / nightly split is disimilar to the Python 2 / 3 transition in important ways. The notion
101.
by brson 10y ago
As I member of the Rust team, I personally would like Rust to be a suitable replacement for fortran, and I suspect most Rust core contributors would feel the same. Rust already has competitive performance so it feels like a small step to be
102.
Imix: A Board for Tock OS Development and IoT Prototyping(crowdsupply.com)
3 points by brson 10y ago|0 comments
103.
by brson 10y ago
We want rust to be successful and that means being adopted and used. It has nothing to do with management and justifying investing in rust. We are fortunate that Mozilla invests in rust to use rust and is currently very happy doing so.
104.
by brson 10y ago
They are not.
105.
Tock: A secure embedded operating system for Cortex-M microcontrollers(github.com)
2 points by brson 10y ago|0 comments
106.
by brson 10y ago
Yes, metapackages are intended to be a general cargo feature, available to all. I suspect the design has not progressed far enough to definitively answer your question about conflict resolution, but I'd imagine you have to override tha
107.
by brson 10y ago
Congratulations, servo team. This is an exciting milestone. Getting all these eyes on servo is going to accelerate development even more.
108.
by brson 10y ago
Eventually, yes.
109.
by brson 10y ago
Try `rustup target add aarch64-apple-ios` and see how far you get. It's a tier 2 platform so it usually has builds available. But the iOS targets are some of the least tested for Rust. I have no idea if they work! The process for addin
110.
by brson 10y ago
This question comes up a lot, and we've debated it a fair bit. There are a few key arguments for keeping them separate from my perspective: First, they have distinct audiences. Cargo is a tool for building Rust programs no matter how y
111.
by brson 10y ago
I do recommend using rustup to all Rust developers now, despite still having reservations about its done-ness, and not being ready to commit to putting it on the main website (I guess that's something of a contradiction). This blog pos
112.
by brson 10y ago
https://github.com/rust-lang-nursery/rustup.rs is the repo. The setup tool and the tool itself are the same binary. The rustup install is basically copying rustup-init.exe to `~/.cargo/bin/rustup.exe`.
113.
by brson 10y ago
Both Rust and emscripten do produce notably large output. On the Rust side it's true that the emscripten port won't use jemalloc, but instead the emscripten malloc (which presumably is better tuned for its environment). Also the w
114.
by brson 10y ago
I've been told that the LLVM branch I linked to is 'the most wrong branch you possibly could have linked to'. This is the right one: https://github.com/rust-lang/llvm/tree/rust-llvm-2016-03-13
115.
by brson 10y ago
Today Rust only has a [few patches to LLVM]( https://github.com/rust-lang/llvm/tree/rust ). One is for Android stack overflow detection using a mechanism that upstream isn't fond of (split stacks), the oth
116.
Ncollide – 2D and 3D collision detection library(ncollide.org)
94 points by brson 10y ago|42 comments
117.
by brson 11y ago
This is actually unlikely to be Rust's solution (at least in the long term), because it requires running LLVM IR through emscripten to generate asm.js to generate wasm. Making Rust and emscripten use the same LLVM IR is difficult becau
118.
by brson 11y ago
Ridiculously easy. It's all but done already via the emscripten port [1]. The emscripten port though is hampered by needing a large out-of-tree patch to LLVM. Once the LLVM wasm backend is ready upstream there will be little left but t
119.
by brson 11y ago
'lang item' does roughly mean symbol, but they have their own Rust syntax to communicate their existence to the compiler. Lang items are special functions / types that can only be defined once globally, must be defined for ce
120.
LALRPOP, an LR(1) parser generator for Rust(smallcultfollowing.com)
130 points by brson 11y ago|26 comments

More ›