metajack

18 ms·

121.
by metajack 11y ago
The current plan is to have Rust (in the form of rust-url replacing nsUrlParser) riding the trains later this quarter.
122.
by metajack 11y ago
I can't figure out what you mean here. WebRTC's implementation is totally open source. The only thing aside from accounts in Hello is the STUN/TURN servers, and I think OSS projects exist for running those. In other words, ev
123.
by metajack 12y ago
The Servo project[1] has a constantly maintained list of bugs and features appropriate for new contributors, and several people willing to mentor if needed. There is so much low hanging fruit building a new browser engine, that there is ple
124.
by metajack 12y ago
For anyone that wants to get started hacking on Daala, we keep a list of easy, good first bugs here on GitHub. https://github.com/xiph/daala/issues?q=is%3Aopen+is%3Aissue+... It's a really fun project to hack
125.
by metajack 12y ago
Which has been doing amazing things for Servo and Rust for years now!
126.
by metajack 12y ago
I can't understand this argument. There was not much extra stuff needed for mobile and most of the specs for it were written long ago. I suspect more people liked reinventing this easy-seeming wheel rather than XMPP was not ready.
127.
by metajack 12y ago
The demos there run Daala in JS already, but there is browser work to be done to make JS codecs more first class.
128.
by metajack 12y ago
> Interesting to see they're also applying Daala to still images. It's a very different set of constraints and optimizations than video. Video codecs have to encode keyframes, which is roughly the same problem as still images.
129.
by metajack 12y ago
You have the dependency graph wrong. Servo was not created to help test Rust. Rust was created to help build Servo.
130.
by metajack 12y ago
Mozilla Research - Video Codec Engineer - Remote or one of the global offices The Internet needs a royalty free video codec appropriate for universal deployment with no gatekeepers. Creating a better video codec is a difficult task, and cre
131.
by metajack 12y ago
There can be multiple script tasks even within a single page. For example, cross-domain or sandboxed iframes will have each DOM and script in its own task. Also, each of those will have their own layout and rendering tasks.
132.
by metajack 12y ago
Lots of bits of Servo use the FFI, but we've been replacing them as we go along with Rust versions. We did this so we could stand up a whole browser as fast as possible and then iterate on the important pieces first. As an example, we
133.
by metajack 12y ago
I updated the blog post with improved wording.
134.
by metajack 12y ago
This is certainly part of the intent, and it has already started to happen in some limited ways. For example, Bobby Holley noticed that certain document.domain changes could make implementing parallelism hard and worked to address this in t
135.
by metajack 12y ago
We try to support the newer things that are generalizations of the older things. One example of this doing all your list styling with a user agent stylesheet using generated content, instead of hardcoding how list bullets and things work. A
136.
by metajack 12y ago
We use Spidermonkey's GC for DOM objects.
137.
by metajack 12y ago
If the wording was "such as vulnerabilities similar to Heartbleed" would that make it better. The point I was trying to make is that you can't make that kind of mistake in the safe Rust language. You will fail a bounds check
138.
by metajack 13y ago
Great type system, memory safe, fast. It's like a wonderful mix of Haskell and Erlang to use when you'd otherwise reach for C++ or C. Of course, I'm quite biased :)
139.
by metajack 13y ago
Or buying their way out of the data contract Gnip has?
140.
by metajack 13y ago
One of our listed intern projects is exactly that. It's not a high priority project for the Daala team because we already have good royalty-free image codecs, but not video codecs. We have finite time, so we choose to attack what we se
141.
by metajack 13y ago
This is an amazing and challenging project to work on. If you'd like to join us, we hang out in #servo on irc.mozilla.org or just dive right into the code[1]. You don't need previous browser hacking experience, and we're happ
142.
by metajack 13y ago
We currently have GPU compositing and rendering[1]. Other browsers will get this eventually and some have it already. We plan to explore this space quite a bit. The other thing we're starting to think about is using SIMD ops for layout
143.
by metajack 13y ago
If we could just donate them back to the pool or opt out that would solve that problem.
144.
The Bridge of Khazad DRM(brendaneich.com)
16 points by metajack 13y ago|0 comments
145.
Studying Lossy Image Compression Efficiency(blog.mozilla.org)
13 points by metajack 13y ago|0 comments
146.
by metajack 13y ago
You make good points, and the Servo team is doing more or less as you described. Our primary target is 64bit and we plan to leave behind lots of legacy stuff. The extra parallelism we're after also enables new things too. For example,
147.
by metajack 13y ago
Release notes are here: https://github.com/mozilla/rust/wiki/Doc-detailed-release-no...
148.
Static Typing May Not Scale(pointersgonewild.wordpress.com)
1 points by metajack 13y ago|0 comments
149.
by metajack 13y ago
To be fair, I don't think the point of Acid1 was to show off form elements. Floats, percentage widths, and how the flows are constructed were the difficult bits. Note that we tried to support everything else even if the language allowe
150.
Next Generation Video: Introducing Daala(people.xiph.org)
215 points by metajack 13y ago|34 comments

More ›