202 karma · joined August 6, 2015
This is a good place to get that kind of information
remote: Resolving deltas: 100% (3/3), completed with 3 local objects.
remote: fatal error in commit_refs
To github.com:acme/foo.git
! [remote rejected] HEAD -> acme/foo (failure)
error: failed to push some refs to 'github.com:acme/foo.git'1. "We are a company that promotes openness and transparency"
2. "Let's commit to maintaining complete confidentiality about the company—no exceptions"
Call me old fashioned, but if you really want to see what something looks like on you just go to the store. Personally, I think buying clothes is not just about how they look on you but also how you feel in them. You can't replicate this with a digital solution (yet?).
Excuse the dramatic title of the post
I am not against gender inclusivity but to call out what is essentially innocent language as inherently “bad” is not a good path to go down.
The value of this cannot be underestimated, in my experience, as using things like “git bisect” mean you always have a working build.
I believe it's still in the roadmap for Go 2.0
Wake me up with some news.
Having someone remove a package and breaking a ton of other packages is nonsensical.
This really makes me uncomfortable, standards are there for a reason, you don't just ignore them because you don't agree with them.
This is just another example of Facebook doing whatever they please just because they can. I wonder how long that will last until people start moving away from the platform.
The sha1 hash has been known to be cryptographically insecure since as early as 2007 (https://www.schneier.com/blog/archives/2005/02/cryptanalysis...).
The very fact that LinkedIn reset everyone's passwords backs this up.
After this data leak I deleted my account, not only is LinkedIn destroyed the art of recruitment it has been completely irresponsible with user's data.
The only sensible solution here is to bring on regular contributors as repository owners and spread the responsibility.
iPads are far from a replacement for your MacBook or iMac - for one you can't properly multitask, and you as a developer you couldn't properly debug and write code on an iPad.
OSX will be around for years to come.
I've worked a lot with Ooyala's live streams and was just looking at moving a client over to their HTML5 offering. They claim to offer it in all browsers but that is probably with a flash fallback, they haven't open sourced their JS (or at least I can't see it on their GitHub page).
We also use StreamUK on a lot of sites (but I've never used it directly) and from what I have heard they have great support for HLS. They have no GitHub presence so not quite sure if they're using the same libs the article mentioned or something proprietary.
Obviously DRM would still be an issue unless the browser natively supports EME.