Hacker Newsnew | past | comments | ask | show | jobs | submit | abjorn's commentslogin

Drivers around San Antonio can be insane, from my experience


I don't know, I've lived in Austin my whole life and I've always loved it. But I've also never lived anywhere else for any kind of comparison. But the traffic I've experienced visiting other cities really makes the traffic here seem not so bad, especially now that the Mopac construction has wound down.

But yes, it's frickin' hot. But I'm a homebody anyways :)


Nothing is forcing you to put everything in Redux. If state only has relevance to a single component then keep it in that components state, Redux works perfectly fine with this approach.


And when the state has relevance to two components? Now it's okay to make it a global, because we can't be bothered to type "prop = value"?

I'm just not buying this argument. People add Redux to projects because they intend to use it, and there's almost never a case where a piece of data is actually needed in enough places that it should be global. It's certainly not common enough to justify importing a whole framework for managing global state.


It's hard to shop around when you're having a heart attack.


You're supposed to do that _before_ you have a heart attack.


Correct me if I'm wrong, but I'm pretty sure the 911 operator doesn't ask your preferred doctor before sending an ambulance.


Congrats. You managed make it like telco market, in that everyone will subcsribe to a group of doctor for a long-term contract.


This is how a HMO works in the US and they are very popular due to lower costs than health insurance plans that allows you to go to any doctor/hospital of your choice. My experience with Kaiser in California is that they also provide better service in general, but sometimes don't have the specialty services you might need in their system.


I never even considered this option, a whole new world awaits me


Professionals tried different settings, that's the key difference.


I'm wondering how this compares to the frequency of any comments by day. It could be that more comments are posted on Sunday in general, and the least on Wednesday.


The negativeness is a percent (number of negative comments divided by number of total comments). I don't think the data is too significant though, because they are all + or - 5 percent of each other


Customary, but unless the name is trademarked, not required.


Some licences require a change of name for substantial modifications, e.g. the Artistic Licence and Apache Licence v1. But those kinds of clauses are pretty rare nowadays.


Is that such a bad thing? Slightly redundant, but that seems more aesthetic than anything.


This doesn't quite look like the same bug described in the article. Maybe the inconsistency with the comma separator is a separate bug?


After many repeated tests with multiple LIMIT sections in .htaccess (and without restarting apache2) i've managed to get a leak of part of config file:

  Allow: �E2�~,HEAD,,ex.html/,OPTIONS,POST,,HEAD,,HEAD,Pek�~,HEAD,,,ex.html/,GET,HEAD


Most certainly something is leaking:

  l-lbiegaj ~ -> curl -sI -X OPTIONS http://mysite/ | grep ^Allow
  Allow: allow,HEAD,GET,HEAD,POST,OPTIONS
Value returned in 'Allow' changes with every apache2 restart, but I haven't yet seen any parts of the config or something other than extraneous commans or 'allow' string.


Interesting. Maybe see if it still leaks with the patch jimjag points out below?

http://svn.apache.org/viewvc?view=revision&revision=1807754


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: