369 karma · joined April 15, 2012
...Or at least, that used to be the case. Looking at the most recent version of rebass, it looks as if it uses the same dynamic classname/stylesheet generation strategy. Now I'm not so sure what the difference between rebass and axs are, except that the former seems to be a comprehensive set of UI components, and the latter a tool for generating your own component library.
In any case, I'm glad jxnblk keeps experimenting with these libraries, even if it's hard to keep up with the changes. Their surface area is so small that it's easy to pick up the API and it doesn't feel like a risk or burden to stay on older versions.
PeriodO (Periods, Organized) is a two-year grant-funded project to help scholars, students, librarians, archivists, and museum curators understand and manage differences in how time periods are defined. For example, many archaeologists may use the term “Bronze Age,” yet each may define the spatial and temporal extent of that period differently. During the first phase of the project (funded by the National Endowment for the Humanities) we collected over 3500 of these time period definitions and developed a tool for curating them. The Institute of Museum and Library Services is now funding the next phase, which will focus on tools for visualizing differences and patterns among period definitions.
We are hiring one part-time JavaScript developer who will help our two programmers (a PhD student and professor at the University of North Carolina) build interfaces that will allow our users to visualize, find, and curate relevant time periods for their work. This developer should have experience with React, d3, and modular JavaScript design. Familiarity with RDF would be beneficial. The time commitment is negotiable, although all work must be completed by May 2018 at the latest. All work will be remote. Email ryanshaw@unc.edu with a resume and short introduction if interested.
var a = (prop => prop > 5 ? prop : whatever)(objImUsing.prop.someLongName)
rather than var a = (function (prop) { return prop > 5 ? prop : whatever })(objImUsing.prop.someLongName)I don't think there's a simple way to get to that point anywhere in America. His hunch, one I agree with, is that people in this country have to make things The Biggest and The Fastest and The Best, which is why we are at the forefront of bike technology & craftsmanship but are so pisspoor when it comes to cycling as a safe, simple means of transportation.
[1] http://www.chroniclebooks.com/titles/a-bike-snob-abroad.html
That site helped a lot when I was first getting the gist of CBVs. Browsing Django's source for the views was surprisingly unpainful, and doing that was aided by iPython's introspection capabilities (typing ?? after an object will show you the source of the class).
FF:
>>> document.getElementsByTagName('div')
(pocs:({}), pocs0:({}), pocs1:({}), pocs2:({}), cst:({}), mngb:({}), ... )
Firebug: >>> document.getElementsByTagName('div')
HTMLCollection[div#pocs, div#pocs0, div#pocs1, div#pocs2, div#cst, div#mngb, ... ]
Chromium: >>> document.getElementsByTagName('div')
[<div id="pocs" style="display: none; position: absolute;">…</div>,
<div id="pocs0">…</div>,
<div id="pocs1">…</div>,
<div id="pocs2">Press Enter to search.</div>,
<div id="cst" style="display:none"></div>,
<div id="mngb">…</div>, ... ]
(edit: formatting)Currently I hack some limited readline functionality with Pentadactyl, which is probably appropriate given the potential invasiveness of that change. But if we're talking about dream FF dev features-- there you go.
http://arstechnica.com/business/2010/10/libya-beginning-to-p...
For more, see: http://www.merlyn.demon.co.uk/js-datex.htm#RoND