1,065 karma · joined March 27, 2011
Guessing by how frail software on these types of devices (routers, access points, home automation stuff, DSL modems, cable boxes, consumer NAS enclosures, etc etc) often feels, I fear it's the latter.
A good example would be MySQL. The case sensitivity of table names is determined by the file system on which MySQL is running.
It's terrible, I know, but if you're developing a webapp which is going to run on a Linux-server you might want to have a case sensitive database locally as well or you could end up with queries that run without a hitch on your dev machine but give a "No such table" error in production. That sucks.
Of course, nowadays, you could just use a Vagrant VM or something similar, but still.
For stuff like in-depth analysis and backgrounds, imo the only area in which newspapers still add value nowadays, I think $0.10 is perfectly reasonable.
E.g. in phrasing my question, specifically having to mention a whole bunch of things that obviously aren't the problem but people are going to insist on anyway unless I've already mentioned them myself.
Or the whole "Well, you shouldn't be doing this in the first place so I'm not going to help you with your actual problem".
It can be incredibly helpful to point this out. But often I'm doing things in a certain way for a reason (constraints that aren't relevant for the question, like "yeah but our entire codebase").
So when I say I'm doing it this way for a reason and looking for a way to make it work, either trust my judgment or decide I don't deserve to be helped and stop commenting. But it often ends up being a massive distracting derail preventing others from trying to answer the question I was actually asking in the first place. Most annoyingly, this behaviour is often rewarded with upvotes.
For example:
> "I can't connect to my database due to error 110, I have no idea what that means"
"Why aren't you using an ORM?"
> "I have good reason not to, besides, I'm just looking to fix error 110 now"
"But a good ORM handles these types of errors for you, it'd be stupid not to use it"
> "You're probably right, but that'd require a lot of rewriting and refactoring and that's simply not an option right now"
"Ok, get back to me when you're actually using an ORM and still having trouble with your database"
when all I'm looking for is "That's a connection timeout, tried checking your firewall configuration?"
I can imagine tunnelling your traffic through DNS to avoid a captive portal (i.e. actually paying for it) counts as circumventing a security measure, which is illegal in a lot of places including the country where I live in.
So basically, yellow would mean "You could, but unless you really need to, you probably don't want to" ;)
Some of the things have links to rants explaining why they apparently suck, but that's just more adolescent ranting mixed with quotes.
I like a good rant occasionally, but those are well-written, make a point worth making and actually show some effort to convince the reader. This is just not it.
Ask for a small percentage of profits or something. The author can't lose more than he already is by completely abandoning it and letting the domain expire. If only because when someone else is keeping it running, he could still use it himself.
It reminds me of when Wordpress gave one of their milestone releases the code-name Django. They actually changed it to "Rheinhardt" after the initial release because of the confusion it was causing.
In this case it's even worse. Giving a component of a web framework the same name as a different, in a sense competing, framework is just plain silly.
Until, of course, you hit a merge commit. Which most projects have a lot of regardless of whether that's a good thing. I suppose you could always pick the parent which is on the same branch, but still.
Of course, that graph could easily be flattened (e.g. simply sort by date) but that'd cause you to jump all over the graph. It would make for a terrible and confusing user experience as the next commit is suddenly based on a state of the code you saw 20 steps ago.
As it would only work properly for projects with a completely linear history (which most projects don't have) I can understand Github not adding this feature. I'd say this is something a third party app using the Github API could do very well for projects specifically set up for learning through their history (like this one).
As they're messing with DNS, you'll still be connecting to their evil version of YouTube through your SSH tunnel. In Firefox this behaviour can be changed by toggling network.proxy.socks_remote_dns in about:config.
Of course, setting up an actual tunnel (i.e. on a lower network layer) would be better but that's a bit more complicated to do.
A friend works in an office where headphones are even banned because they create too much of a barrier to talk to a co-worker. I'd go absolutely crazy there in less than a week.
With "No, unless ...", it's a different story. Then success is dependant on the conditions mentioned and they're much more likely to do their part in making sure those conditions are met. If you said "Yes, if" they'll often just remember you promised you could do it and leave it at that.
What RapGenius (also a legitimate site in the sense that they're not scammers and providing an useful service) did wasn't just unwanted behaviour but specifically forbidden. And yes, they're far from alone in what they did. Which is exactly why Google is making an example out of them.
I know, it sucks, all your competitors doing similar things forces you to choose between taking this risk and never making it in the first place. But that's exactly why it's a good thing Google is making a stand and setting an example.
It's a move towards a level playing field where nobody is making the internet a worse place by engaging in tricks like link farming rather than a level playing field where everyone is doing it and the end user suffers the consequences.