51–58 of 58 posts
Earlier quoted context omitted.
He was obviously obsessed by .net and circles. But what do you mean by "circles around Reddit" or "circles around something"? Like... g+ circles?
It's a figure of speech. See how people use it: http://news.gnod.com/search?f=run+circles+around
Where's the Vagrantfile?
Earlier quoted context omitted.
> In essence it's because there is a very large number of lazy programmers who live by cut and paste. I've had programmers copy and paste GPL'd code into proprietary projects I'm responsible for. It's not laziness it's ignorance. "What's a GPL?"
I've shipped hard product with GPL onboard and in use. Its great! I've also complied, 100%. Also great! Laziness, ignorance, irresponsibility. Or: usage.
The cards I'm dealt are "proprietary projects". I comply 100% too: we don't ship GPL'd code. We've gotten close, though (c/o what I mention above).
What causes people to need to sprinkle license boilerplate everywhere, including in files which are otherwise completely empty (like r2/r2/config/__init__.py), and then to have to update them every year? See this commit: https://github.com/reddit/reddit/commit/90cfcaaecc56cf35e758... It just seems to defy reason that we must make humans increment a number every year in every file in our projects, nevermind the fact t…
I do this too and so why do I do it? In essence it's because there is a very large number of lazy programmers who live by cut and paste. We're not just talking the "I've found a solution on Stack Overflow and will use that", but more "I've searched Github for keyword + language and this file does what I need". The files are copied into their projects in its entirety, sometimes whole libraries are, and those programme…
> If I use the suggestion you make, then by them copying files into their project they have changed the licence of a file (it now inherits whatever their project uses).
No, the only one who can actually change the license of a file is the rights holder, so the person who copied the code while ignoring the license misrepresents matters but does not change anything about how the work is licencsed.
Dear lord that JavaScript is painful to read. I want to submit a pull request and fix all their semicolons.
It's a pain that they are stuck with pylons, an unmaintained framework.
Why would that be a pain? Apparently it works for them, and is stable enough. Now, if pylons turns out to be a roadblock to an expansion they want to make, that'd be a reason to swap it out for something different.
Pylons most probably won't roadblock them but will definitely bring a lot more challenge.
Dear lord that JavaScript is painful to read. I want to submit a pull request and fix all their semicolons.
FWIW, there _is_ a proper styleguide now, it just hasn't been retroactively applied to older js. https://github.com/reddit/styleguide/tree/master/javascript