{"action":"opened","issue":{"url":"https://api.github.com/repos/sudocurse/reading-list/issues/13136","repository_url":"https://api.github.com/repos/sudocurse/reading-list","labels_url":"https://api.github.com/repos/sudocurse/reading-list/issues/13136/labels{/name}","comments_url":"https://api.github.com/repos/sudocurse/reading-list/issues/13136/comments","events_url":"https://api.github.com/repos/sudocurse/reading-list/issues/13136/events","html_url":"https://github.com/sudocurse/reading-list/issues/13136","id":323963495,"number":13136,"title":"Mozilla: Rust Compiler Firefox Updates and Docker","user":{"login":"sudocurse","id":947518,"avatar_url":"https://avatars3.githubusercontent.com/u/947518?v=4","gravatar_id":"","url":"https://api.github.com/users/sudocurse","html_url":"https://github.com/sudocurse","followers_url":"https://api.github.com/users/sudocurse/followers","following_url":"https://api.github.com/users/sudocurse/following{/other_user}","gists_url":"https://api.github.com/users/sudocurse/gists{/gist_id}","starred_url":"https://api.github.com/users/sudocurse/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sudocurse/subscriptions","organizations_url":"https://api.github.com/users/sudocurse/orgs","repos_url":"https://api.github.com/users/sudocurse/repos","events_url":"https://api.github.com/users/sudocurse/events{/privacy}","received_events_url":"https://api.github.com/users/sudocurse/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-05-17T10:28:11Z","updated_at":"2018-05-17T10:28:11Z","closed_at":null,"author_association":"OWNER","body":"Mozilla: Rust Compiler, Firefox Updates and Docker<br>\nhttps://ift.tt/2Irs5eA<br>\n<ul>\n<li>\n<h5><a href=\"https://blog.mozilla.org/nnethercote/2018/05/17/the-rust-compiler-is-getting-faster/\" rel=\"nofollow\">The Rust compiler is getting faster</a></h5>\n<blockquote>\n<p>As changes are made to the Rust compiler, a suite of benchmarks measuring compile time is run regularly on the development version. The data is viewable at https://ift.tt/2cQMxot. The default view is graphical, showing data from the past month.</p>\n</blockquote>\n</li>\n<li>\n<h5><a href=\"https://blog.nightly.mozilla.org/2018/05/16/these-weeks-in-firefox-issue-38/\" rel=\"nofollow\">These Weeks in Firefox: Issue 38</a></h5>\n</li>\n<li>\n<h5><a href=\"https://gregoryszorc.com/blog/2018/05/16/scaling-firefox-development-workflows/\" rel=\"nofollow\">Scaling Firefox Development Workflows</a></h5>\n<blockquote>\n<p>One of the central themes of my time at Mozilla has been my pursuit of making it easier to contribute to and hack on Firefox.</p>\n<p>I vividly remember my first day at Mozilla in 2011 when I went to build Firefox for the first time. I thought the entire experience - from obtaining the source code, installing build dependencies, building, running tests, submitting patches for review, etc was quite... lacking. When I asked others if they thought this was an issue, many rightfully identified problems (like the build system being slow). But there was a significant population who seemed to be naive and/or apathetic to the breadth of the user experience shortcomings. This is totally understandable: the scope of the problem is immense and various people don't have the perspective, are blinded/biased by personal experience, and/or don't have the product design or UX experience necessary to comprehend the problem.</p>\n</blockquote>\n</li>\n<li>\n<h5><a href=\"https://gregoryszorc.com/blog/2018/04/09/release-of-python-zstandard-0.9/\" rel=\"nofollow\">Release of python-zstandard 0.9</a></h5>\n<blockquote>\n<p>Zstandard is a highly tunable and therefore flexible compression algorithm with support for modern features such as multi-threaded compression and dictionaries. Its performance is remarkable and if you use it as a drop-in replacement for zlib, bzip2, or other common algorithms, you'll frequently see more than a doubling in performance.</p>\n</blockquote>\n</li>\n<li>\n<h5><a href=\"https://gregoryszorc.com/blog/2018/05/16/revisiting-using-docker/\" rel=\"nofollow\">Revisiting Using Docker</a></h5>\n<blockquote>\n<p>When Docker was taking off like wildfire in 2013, I was caught up in the excitement like everyone else. I remember knowing of the existence of LXC and container technologies in Linux at the time. But Docker seemed to be the first open source tool to actually make that technology usable (a terrific example of how user experience matters).</p>\n<p>At Mozilla, Docker was adopted all around me and by me for various utilities. Taskcluster - Mozilla's task execution framework geared for running complex CI systems - adopted Docker as a mechanism to run processes in self-contained images. Various groups in Mozilla adopted Docker for running services in production. I adopted Docker for integration testing of complex systems.</p>\n</blockquote>\n</li>\n</ul>\n<p><a href=\"http://www.tuxmachines.org/node/111773\" target=\"_blank\">read more</a></p>\n<br>\n<br>\nvia Tux Machines https://ift.tt/VTl7oF<br>\nMay 17, 2018 at 06:25AM"}}
{"actor":{"display_login":"sudocurse"}}