The engineering blog of Bocoup, a web consultancy that works on JavaScript, browser standards, and front-end tooling.
HN commenters link it for documentation advice, a clear flexbox explainer, and background on Web Platform Tests and contributing to the web platform.
I empathize. I feel like my work in implementing insurance programs & payday loan portals is of low value to society, yet it pays the bills. Meanwhile I'd much rather focus fully on my project to implement a WASM jit for Lua. That has future potential alone due to WASM unicorns wanting to open up to being useful as a JIT target
Sort of flies in the face of people thinking basic income will result in a bunch of stay at home drunks
SVG is cool. Was really wanting SVG2 as in order to get wordwrap I'm embedding HTML into the SVG which I'm embedding in HTML. openEtG uses SVG as an alternate backend to cards/deck rendering (as opposed to <canvas>)
Deck SVG: http://etg.dek.im/deck/047130c6qq016u1036u30177o0177g027aq027dm017h7017k2057n8017q5017th0380g018pr.svg
Card SVG: http://etg.dek.im/card/56f.svg
There's some issues in rendering interacting with the page's CSS. The card back is rendered off a spritesheet, in the SVG I just offset it so that the rest of the image is clipped away
Code: https://github.com/serprex/openEtG/blob/master/svg.js
If this seems off topic.. well I'm bad at being personal, & in response to a personal blogpost, this is how I make a personal response
I was hoping to try get remote work with https://bocoup.com but unfortunately I'm also Canadian & they're not open to being that remote. But I'm just some guy who made an open source HTML5 CCG. Maybe they'd take closer consideration of you. Granted I open with a salary of 25k CAD, don't know what you…
I'm the guy who ported this to processing.js, and no, it isn't that simple. I tried just adding that one line and it didn't actually work at the time. It turns out it's slightly more involved, and as I was just trying to make this a quick proof-of-concept hack, I didn't spend the time to rewrite the loading mechanism to make it IE-compatible.
You can read more about the interactions between processing.js and excanvas at http://bocoup.com/processing-js/docs/index.php?page=Using%20exCanvas.js%20with%20Processing.js if you're so inclined, but please don't think that it's just because I was too lazy to add a single line of HTML.
The niche situations aren't going to use the built-in rand() anyway because they can write their own or use someone else's that's faster. Even if they end up using the same algorithm (e.g. a Mersenne Twister) they can still often go faster.
Interestingly according to https://bocoup.com/weblog/random-numbers Firefox is just going to use its CSPRNG once the crypto api is ready. (Bug 322529 is still in NEW state, though.)
There are literally no other metrics.
Web Platform Tests were literally a project to align browsers on compatible implementations of a bunch of web APIs. Started by Opera and w3c and maintained by w3c https://www.bocoup.com/blog/wpt-an-overview-and-history
Good documentation is a key part
- Good summary of best practices for documentation: https://bocoup.com/weblog/documenting-your-api
- Tips for good api doc design: http://blog.parse.com/learn/engineering/designing-great-api-docs/
Actually I just read "Dive into Flexbox" and in 5-10 min read now have a clear understanding of how flexbox is designed to work. Best explaination I've read.
http://bocoup.com/weblog/dive-into-flexbox/