6 ms·
What is opensource and why do I feel so guilty? (2012) [video]
- notwedtm 11y agoThis sounds like a good article (from the title), however my company seems to have bulk-blocked the .xxx TLD. Out of curiosity, why did you put your blog on the .xxx domain? Unless you are talking about open-source boobs, or something. Then I understand completely.
- deleted 11y ago[deleted]
- Joky 11y agoAnd the slides: http://fat.github.io/slides-os-guilt/ http://fat.github.io/slides-os-guilt/
- 49531 11y agoBecause it's @fat, and that's how he do. No boobs here though all fairly SFW.
- jMyles 11y agoAnd, FWIW, boobs are SFW as well. At least in the USA.
- stephengillie 11y agoWhile you are technically correct, the term has an exact meaning in internet culture. The term "safe for work" refers specifically to a lack of sexual and...medical... content. Looking at cat pictures might get you fired, but it's still "safe for work".
- deleted 11y ago[deleted]
- jMyles 11y agoI didn't mean boob pictures, but actual boobs. As in breastfeeding.
- fat 11y agohaha <3
- nfoz 11y ago> Out of curiosity, why did you put your blog on the .xxx domain? Maybe it helps to point out how silly it is to filter based on the TLD.
- knieveltech 11y agoOr underlines how silly it is to use a TLD ostensibly intended for porn sites for a blog.
- herge 11y agoWould you prefer .com? Or .org?
- knieveltech 11y ago30 years ago .com may have been intended specifically for commercial purposes but that is buried underneath three decades of use as a generic catch-all TLD and as such using it communicates almost nothing about the site in question. .org is by convention and usage largely reserved for nonprofit organizations. As such use of .org (intentionally or otherwise) communicates that the website in question is for a nonprofit. xxx is, at merely 4 years old, brand spanking new. There hasn't been time for intent and practice to diverge meaningfully, ergo it's perfectly reasonable to assume a site that uses the .xxx tld is in fact a porn site.
- s1lver 11y agoIn much the same was as io meaning input output and not an island!
- deleted 11y ago[deleted]
- phpnode 11y agopretty sure the only point of the .xxx TLD (aside from it being yet another source of income for ICANN of course), is that it clearly signals that the content is NSFW. It is totally reasonable for certain organisations to block it.
- ryanSrich 11y agoYou wouldn't understand...
- X-Istence 11y agoLink to the YouTube video: https://www.youtube.com/watch?v=UIDb6VBO9os https://www.youtube.com/watch?v=UIDb6VBO9os
- brianzelip 11y agoit's a hack.
- nickpsecurity 11y agoThis is one of those situations where it would be great to have slides detailing points of the video. His are just drawings of some people's names and time points. I love the retro, sketch-style art but it doesn't tell me a thing. Several minutes in of rambling and I still don't know what it's about. Click the little X... So, out of thousands of vids on the net on OSS or programming... each 20+ min long... why watch this unless I'm already a fan of the authors work? Not even critiquing the presentation as much as saying: give us a matching article or slides that lets us determine if we really want to watch the video. If it strikes a chord, people watch the presentation. Otherwise, most will just skip it and miss out on any gems it might have had. And that's a rational decision given the flood of info on the web. This applies to a ton of videos rather than just @fat's. Anyone having to do a lot of research or want to get most out of their time relies on summaries. People not doing them are reducing impact of their own work.
- AndyKelley 11y agoI completely agree. I came to the comment section in attempt to get such an overview to determine whether the video was worth watching.
- ZenoArrow 11y agoScroll through until you see a slide about cute puppy syndrome (I think that was what it was called). You'll miss the buildup and the fun presentation of open source history but that's the key part of the talk. To spoil it slightly, it's about the lifecycle of open source projects.
- nickpsecurity 11y agoDidn't see this one when I posted my other two comments. So, that's three comments that do a bit of what author didn't. Merging them together mentally gives me an idea of what to expect. Even an abstract saying about the same as you did would've been nice.
- daveidol 11y ago
- mizzao 11y agoUgh. This post and https://news.ycombinator.com/item?id=8712035 https://news.ycombinator.com/item?id=8712035 just gave me some incentives to do the following to these types of GitHub issues on my OSS projects: https://github.com/mizzao/meteor-autocomplete/issues/98 https://github.com/mizzao/meteor-autocomplete/issues/98
- nanny 11y agoGood on you. Don't be rude, but don't beat around the bush, and maybe someone will understand eventually.
- anthonycr 11y agoSometimes I feel guilty closing even low quality issues like those :(
- Demiurge 11y agoThere should be no guilt on either side. Sometimes putting time into investigating the stack trace isn't worth it for the user. However, reporting it still a good idea because the developer might recognize a regression or another angle at a bug being already experienced. If not, it's not a big deal to dismiss.
- enraged_camel 11y agoI don't agree. The reporting party should feel guilty about not putting effort into providing system information and troubleshooting further and reporting their findings. This is exactly why Stack Overflow works so well: low quality questions are downvoted mercilessly, and closed if they aren't improved within a short time period. It is also why automated reporting tools provide a good amount of contextual information along with the error and stack trace. Furthermore, not including a description of the issue along with the stack trace makes it impossible for other users to determine if they are experiencing the same issue or something else (since it is possible for two different bugs to produce the same stack trace, or even the same error message).
- unimpressive 11y agoSkip to 19 minutes in for the content.
- grhmc 11y agoOr you can not maintain your projects and it doesn't matter.
- beloch 11y agoAnswer to clickbait title found 20 minutes in: Opensourcing a project that becomes popular induces guilt, because it needs your time and attention to thrive, but you can't afford to give it, especially if you're interested in creating other things.
- enraged_camel 11y agoWhich is a strange concern because the solution is obvious: if the project is popular, it should be easy to find someone else to pass on the leadership position to and move on to other things. The only guilt should come from just straight up abandoning the project. Unfortunately the open-source world is chock full of those.
- akerl_ 11y agoWhy should someone feel guilty because they made something, shared it to the world, but one day realized they didn't want to or couldn't continue to maintain it? To suggest I should feel guilt for admitting I can't maintain all the personal code I've opensourced for other users suggests I ought to have kept it closed source, which seems like a net loss all around.
- enraged_camel 11y agoI'm not asking people to never abandon their projects. All you have to do is find someone else to lead (or at least maintain) the project before moving onto something else.
- unknownknowns 11y agoIndeed. I made a project a few years ago and maintained it for several years. At one point I just didn't have the time (or motivation, I suppose) to continue updates and essentially abandoned it without much official word, while putting in a good amount of work every few months. The guilt was pretty crushing, so I can understand where the author comes from. Fortunately, someone offered to take it up recently so I feel much better now.
- 11y ago
- tomphoolery 11y agoRegardless of how you might feel about this talk, I feel like it's awesome because it's so entertaining :)
- deleted 11y ago[deleted]