erickt

12 ms·

61.
by erickt 10y ago
That's a reasonable question! I put that on our list for the next survey: https://github.com/rust-community/team/issues/28#issuecommen...
62.
by erickt 10y ago
Yeah, we iterated a bunch on this question, and I still don't think we have it quite right. On the REPL side, we've had a few prototyped out [1] out over the years. We'd love something someday. What do you use for your scient
63.
by erickt 10y ago
Rust Community Team lead here. It is fine if people don't consider themselves underrepresented, we just want to be proactive about discovering if people end up self selecting themselves out of our community because they don't feel
64.
by erickt 10y ago
Rust Community Team here. Yeah that was a mistake. We were trying to cut out redundant questions, but it would have been so easy just to split this into three answers. We might be able to split this out based on secondary information, but w
65.
by erickt 10y ago
As I mentioned in my prior post, consider the percentages against the total number of responders, rather than across each demographic.
66.
by erickt 10y ago
Rust Community Team member here. This survey question allowed for people to describe themselves as they decided, and so people could select multiple choices if they wanted, as well as enter in free text. The percentages John used in this wr
67.
by erickt 11y ago
We have our meetups at Mozilla's San Francisco office, so we piggy back on their AV equipment. Unfortunately I don't know what that they use. However, there is an IRC channel irc://irc.mozilla.org/#airmozilla that I
68.
by erickt 11y ago
Cool! I run this meetup. This video was taken at the Bay Area Rust meetup [1] last week. We also had two other speakers that also gave great talks: Sean Griffin, on Diesel, a safe and extensible ORM [2] Alan Jeffery, on Parsell, a streaming
69.
by erickt 11y ago
But only if you use the `slice.unchecked_get`[1] method, otherwise you still get bounds checking in an unsafe block. [1]: http://doc.rust-lang.org/std/primitive.slice.html#method.get...
70.
by erickt 11y ago
If anyone is interested in hearing from the creator, Sean Griffin will be talking about Diesel at the next Bay Area Rust Meetup on February 18th [1], which will be live streamed and eventually archived on Air Mozilla [2]: [1]: http:/&
71.
by erickt 11y ago
Wonderful! Are you able to say which company you deployed this in, and if you've run into any trouble? And by DLL, was this in Windows? I can't recall if we've heard of any Windows users putting rust into production yet. We&#
72.
by erickt 11y ago
Yes there is. That's the wasm2asm project Alon mentioned in the post.
73.
by erickt 11y ago
Last I worked on llvm-c, it was supposed to stay backwards compatible. They do add new functionality but the old API should still work until llvm 4. For rust, while we have been broken by bad code we generated and llvm bugs, I can't re
74.
by erickt 11y ago
Don't forget we kinda sorta have byte characters and strings a la `b'x'` and `b"foo"`, which are really just simpler ways of expressing byte slices. Unfortunately they lack string specific methods until we get speci
75.
by erickt 11y ago
Longtime Rust developer here. You definitely made the right choice, it would have been a pretty big risk to bet a startup on rust back in 2014 if you didn't have the freedom to keep up to date with the breaking changes. Crazy people li
76.
by erickt 11y ago
It doesn't quite yet. By default it errors on unknown fields, and my plan is to add an annotation to ignore it instead. Not quite sure if I got the default behavior correct though. I'm considering flipping it.
77.
by erickt 11y ago
Thanks! I need to get back into writing on it. I just pushed up a rust pull parser version here: https://github.com/kostya/benchmarks/pull/54 . Is that what you were thinking of?
78.
by erickt 11y ago
I wrote serde_json, and wrote the rust benchmark here a few months ago. Interestingly when I wrote this benchmark, I had my implementation as equivalent to RapidJSON on my Mac, but for some reason Kostya couldn't replicate it: O https:
79.
by erickt 11y ago
I love these articles, thanks! I can't wait for rust to get more involved in this space. How do you plan on doing error handling in timely? Do you expect it to be more along the lines of MPI, where you restart from the last snapshot, o
80.
You're doing it wrong (2010) – Optimizing Varnish(queue.acm.org)
3 points by erickt 11y ago|0 comments
81.
by erickt 11y ago
You're not accounting for fractional reserve banking, where the banks only need to keep a certain amount of deposits on hand, and can loan the rest out to other people. For example, you deposit $100 into a bank. They keep, say, $20, an
82.
by erickt 11y ago
There's a fierce battle between the honorable Vim-ers ( https://github.com/rust-lang/rust.vim ), and those scoundrel Emac-ians ( https://github.com/rust-lang/rust-mode ). Work is ongoing to have
83.
by erickt 11y ago
We're still pretty confident that Rust will be able to support a high quality green threading library and other M:N concurrency libraries without needing to be integrated into the language itself. All the type magic that we do to pass
84.
by erickt 11y ago
Serde ( https://github.com/serde-rs/serde ) is my baby, so let me know if you need any help with it. In a sense serde is a compile time reflection library. It's designed to recursively walk through a structure whil
85.
by erickt 11y ago
No it's not a stupid question. libc (or CRT on windows) really is the library that exposes all the user space system libraries. It contains the functions to do IO, sockets, threads, and etc. So we use it to expose that functionality to
86.
by erickt 12y ago
Zappos built their brand on high quality customer service: http://www.businessinsider.com/zappos-customer-service-crm-2...
87.
by erickt 12y ago
Years ago we had pure functions that have since been replaced with our current function model. I'm betting that we are still reserving "pure" from that time. I haven't heard of anyone proposing to use it for something, s
88.
by erickt 12y ago
We are not quite ready to support users of libsyntax and librustc as we are very serious about keeping our stable api stable, and freezing those apis would really impact the future development of the compiler, so it will not be exposed in r
89.
by erickt 12y ago
It is very probable that a sufficiently smart optimizer could see the assertion was always true and delete it. Then see no one reads "a" and delete it as well. In certain circumstances this can cause a secret to be leaked in, say
90.
by erickt 12y ago
We had a Bay Area Rust meetup [0] all about cryptography back in December (here[1] is a video if you want to watch the event). One of the subjects of that talk was about a project tars[2] that tries to provide for a secure buffer for keys t

More ›