chadly

8 ms·

31.
About pull request reviews(help.github.com)
1 points by chadly 10y ago|0 comments
32.
by chadly 11y ago
If you publish sensitive information (even if you immediately remove it), that sensitive info is compromised. All the "unpublish" feature does is lull users who don't know any better into a false sense of security (I don&#x27
33.
by chadly 11y ago
Yes, you would need to publish a new version of the package with a different name. But the history of what happened (and consequently anyone depending on the old name) would be preserved.
34.
by chadly 11y ago
Your "control" of your code is an illusion if you publish it as open source. This policy now makes clear the way it already works (or should have in the case of last week).
35.
by chadly 11y ago
These seem to be relatively good changes. I still think the reasons they outline for "unpublishing" (still not a word) are not compelling. I would like to see an immutable package feed.
36.
Unpublish Isn't a Word(chadly.net)
2 points by chadly 11y ago|0 comments
37.
by chadly 11y ago
It is not insanity. It is actually what many sane package managers do. Allowing someone to "unpublish" something that many depend on - that is insanity.
38.
Strange star that has serious scientists talking about an alien megastructure(washingtonpost.com)
2 points by chadly 11y ago|0 comments
39.
by chadly 11y ago
It's not a decimal number. It's a version number. If you add the implicit .0 back to the end of 0.14, it is easier to see. 0.14.0 is obviously not a decimal number. 14 > 13 > 9
40.
Git for Windows 2.5.0(github.com)
50 points by chadly 11y ago|13 comments
41.
by chadly 11y ago
How does this compare with Flux? Is it intended to be used with Flux or instead of Flux?
42.
Publishing an ASP.NET 5 App to Docker on Linux with Visual Studio(hanselman.com)
2 points by chadly 11y ago|0 comments
43.
NASA Announces Journey to Mars Challenge(nasa.gov)
3 points by chadly 11y ago|0 comments
44.
Evaluating NASA’s Futuristic EM Drive(nasaspaceflight.com)
19 points by chadly 11y ago|3 comments
45.
Publishing a React Component to npm(chadly.net)
1 points by chadly 11y ago|0 comments
46.
by chadly 12y ago
The current relational database is too limiting. We're dropping all sorts of interesting data on the ground because we don't have suitable pigeonholes to put it into. That is the best description of the problem event sourcing tr
47.
by chadly 12y ago
His last point about windows that it seems like he just glosses over is the main reason I prefer tools like grunt/gulp. It is very easy to get a cross-OS JS build working with grunt/gulp - not so sure using the `npm run` method.
48.
A Good Developer is a Healthy Developer(chadly.net)
2 points by chadly 13y ago|0 comments
49.
by chadly 13y ago
Is bitrot something the average hard drive user even needs to worry about? I know the hard drives themselves at the hardware level implement checksums. Is it really necessary to also have it at the filesystem level? I am legitimately asking
50.
by chadly 13y ago
I find having a "standard" way to run tasks enormously beneficial especially when working with developers cross-platform. Whatever OS you are running, just grunt and all is well. :)
51.
by chadly 13y ago
This seems like a really cool idea. Would it work with multiple users? e.g. if I wanted to share one device with my spouse - would it be able to keep track of multiple people?