arderary

3 ms·

1. 1.▲
   Cloudflare Workers Introduces WebSockets(blog.cloudflare.com)

   10 points by arderary 5y ago|0 comments
2. 2.▲
   by arderary 6y ago

   1 to suggest replacing the lightbulb with systemd-lightd
3. 3.▲
   by arderary 6y ago

   How are you handling analytics? Will distribution be through a customer's Spotify/Apple account (so analytics are visible), or will you be building a portal to combine the two sources (plus server-side download logs, maybe?) of an
4. 4.▲
   by arderary 6y ago

   I really don't understand the glorification of no-js websites on HN. Like, I'd get it if it was Flash or something ('cause that definitely has some real accessibility issues, and required a plugin to be installed), but the we
5. 5.▲
   by arderary 6y ago

   In a lot of cases it's worth considering whether orchestration is necessary at all — pure docker can take you quite far, with just a couple shell scripts called from the last stage of your CI (or manually)
6. 6.▲
   by arderary 6y ago

   It seems like your specific use case could be solved (as you mentioned) by passing down a `className` prop, exactly like React. It's described as a workaround in the RFC because the approach there relies on internal class names (and
7. 7.▲
   by arderary 6y ago

   This seems in fairly bad faith. As best I can tell, it suggests that the argument that billionaires exploit people is unfounded, because they delight _users_? I mean, sure, but that says _nothing_ about exploitation. A company that exploits