If James Golick considers this to be important enough to criticize other people and even write a blog post about it, why does he write a fix?
Reminder: "Broken gets fixed, but shitty lasts forever"
31–38 of 38 posts
Re: Reminder: "Broken gets fixed, but shitty lasts forever"
#32Here's a reference/cheat sheet to using SSL with verification with Net::HTTP: https://github.com/augustl/net-http-cheat-sheet/blob/master/... It shows different ways of providing Net::HTTP with verification certificates.
Thank you. This is the best example I've seen of how to make Net::HTTP do the right thing with SSL certificates.
The reason the VERIFY_NONE fix got so popular is that, by default, if you turn on SSL support in Net::HTTP in an otherwise working codebase, your calls fail with certificate errors. The docs (http://www.ruby-doc.org/stdlib/libdoc/net/http/rdoc/index.ht...) have absolutely no helpful information except for mentioning the default of VERIFY_PEER. If you're noodling around on your own you'll discover VERIFY_NONE works well before you discover how certificate stores work.
Re: Reminder: "Broken gets fixed, but shitty lasts forever"
#33Re: Reminder: "Broken gets fixed, but shitty lasts forever"
#34Earlier quoted context omitted.
Does recreating UITableViewController to be slightly more flexible really constitute a new approach?
It's not slightly more flexible, it's hugely more flexible. As someone who has apps that consist of a complicated web of tableviews, Matt Gallagher's work is amazing and helped me immensely. Although, I think this link is better: http://cocoawithlove.com/2010/12/uitableview-construction-dr...
If you remove "to be slightly more flexible" from my previous post, you'll find the real point I was trying to make.
Re: Reminder: "Broken gets fixed, but shitty lasts forever"
#35I find it repulsive that poor diligence on the part of a programmer can be blamed on some ‘community leader’ setting a bad example. As a programmer, all code that goes into your project is your responsibility. When things go well you’re the only one who gets paid, therefore when they go wrong you’re the only one who should get the blame. See also: http://enfranchisedmind.com/blog/posts/fyi-my-open-source-us...
Your approach is unpractical and I doubt you follow it yourself. Almost nobody that uses opensource libraries reads all of the code. As with journalism, science and many other things in life, you have to trust upon others to deliver work that conforms to certain standards. Even though every newspaper article and scientific paper that you accept is 'your responsibility', you would be pretty miffed if an article in the free local paper was completely false.
If you give away toilets for free, it's your responsibility to make sure they aren't lined with sodium and will blow up after the first flush. If you give away a toilet for free, you are an asshole if you know it has a huge hidden hole and you don't warn takers about it. If you write a piece of software that claims to be doing something, but it actually contains malware, then you are violating the law (as much as when you give me a nice statue that contains a spy camera).
It has never been possible or allowed to give just anything you want away for free, without you being liable in any way. That hasn't changed with software and no license in the world can exempt you from certain basic responsibilities concerning your 'gift'.
Re: Reminder: "Broken gets fixed, but shitty lasts forever"
#36Earlier quoted context omitted.
Oh yeah I agree that Three20 is a cluttered, monolithic mess. What I should have said was that Three20 was the first major attempt (that I know of) to break away from the strict nested-controller way of making data-driven apps by implementing a pretty nice URL-based application model. Matt Gallagher has also done a good job of deconstructing the Apple Way and try new approaches: http://cocoawithlove.com/2009/03/recre…
Does recreating UITableViewController to be slightly more flexible really constitute a new approach?
I think he's referring to TTNavigator, which is a really cool idea (and an idea I stole for my use in Cydia.mm, fwiw).
Re: Reminder: "Broken gets fixed, but shitty lasts forever"
#37I find it repulsive that poor diligence on the part of a programmer can be blamed on some ‘community leader’ setting a bad example. As a programmer, all code that goes into your project is your responsibility. When things go well you’re the only one who gets paid, therefore when they go wrong you’re the only one who should get the blame. See also: http://enfranchisedmind.com/blog/posts/fyi-my-open-source-us...
Your approach is unpractical and I doubt you follow it yourself. Almost nobody that uses opensource libraries reads all of the code. As with journalism, science and many other things in life, you have to trust upon others to deliver work that conforms to certain standards. Even though every newspaper article and scientific paper that you accept is 'your responsibility', you would be pretty miffed if an article in the…
Are you speaking morally? From my understanding the warranty disclaimer in many licenses (GPL, BSD, MIT) does exempt you from responsibility...
Re: Reminder: "Broken gets fixed, but shitty lasts forever"
#38Earlier quoted context omitted.
Your approach is unpractical and I doubt you follow it yourself. Almost nobody that uses opensource libraries reads all of the code. As with journalism, science and many other things in life, you have to trust upon others to deliver work that conforms to certain standards. Even though every newspaper article and scientific paper that you accept is 'your responsibility', you would be pretty miffed if an article in the…
Are you speaking morally? From my understanding the warranty disclaimer in many licenses (GPL, BSD, MIT) does exempt you from responsibility...
Claiming you are exempt from any responsibility does not actually legally exempt you from any responsibility. You can't legally bring a spy camera into my home by presenting me with a free gift that contains a hidden camera. You can't legally blow up my home, even if I accept a free device from you and press the buttons you told me to press, unless you were very clear about what the device would do (and no, claiming in the license that it is not meant for anything does not nullify the website and the examples of what the code is obviously supposed to do). Going from the realm of the obvious to the realm of the somewhat less obvious: if you give me a free bicycle, knowing it's fron fork is starting to give way, you are responsible for my skull fracture if you don't tell me about it. The practical problem, usually insurmountable, is proving you knew about it. More broadly: the consequences of known defects that obviously have disastrous consequences are the responsibility of the provider. This also holds for software and doesn't depend on the license.
Now my point is not that this is the case here or that such cases are common or even important. The point is that the blanket statement of my parent is plainly false.
Of course, IANAL, but you don't need to be a lawyer to understand jurisprudence. There are plenty of known cases where people intentionally harmed others and tried to plead guilty based on not actually performing the action that lead to the damage. It doesn't fly.