I was really hoping this article was going to discuss how Rome was somehow more open or prone to invasions due to their water networks. Instead, I was treated to the fairly unexciting conclusion of Rome traded a lot, causing its various regions to be interdependent, therefore possibly vulnerable because of additional risks inherent in relying on a trade network to supply your city with food.
HN user
toastedzergling
Fair enough, but implied anchors are not part of the regex standard
Yes, that's exactly my point. By occuring zero times, it means the preceeding token is irrelevant, and will match any arbitrary string.
I have no idea what you're talking about. My point is more pragmatic the regex /A/ will match the string "QQQQ" and this tool doesn't take that into account. E.g., I type this into my javascript console:
/A*/.test('QQQQ');
> true
Showing that yes, /A/ does match 'QQQQ'I really dislike that patterns using * wildcard required using the letters beforehand. The game requires A* to match a row with zero or more A's, but this is absolutely incorrect, as A* will gladly match ANY string, like QQQQ.
I wonder how many more months I have until I'm required to use a Google+ login to chat on twitch.
It should be noted that this isn't an option if you're aleady late stage and have cirrhosis of the liver. Hep C isn't really curable past the point where they can longer administer to you the interferon it is mixed it, which requires a relatively healthy liver to handle.
Sure, I suppose I am qualified to chime in here, after all, I'm a developer for an A/B testing company (but not the one posted here-apptimize).
A/B Testing is a bit of a catch-all phrase for "testing the effectiveness of website changes." Strictly Speaking, A/B only refers to the testing specifically is testing of one change "A" against another "B". You can have multi-variate testing as well where you add in a third group "A,B, or C", or mixtures "ABC vs AB vs AC vs BC vs CONTROL"... it's up to the test design.
But basically it's a tool to help you see if the changes you make to your website will work, while the website is up running, using real users. So, for example:
* If your goal is to get more downloads, maybe you'll tset some page layouts or images and see which test group clicks the download button more
* Or, See which splash page results in the most "Sign up for Newsletter" clicks
This is great information for marketers, or really testing out any old thing you want that is trackable through browser-events.
Really though, this is just the tip of the Iceberg of what is possible... but I'll leave it at that. If you really want to know more let me know.
I find pair programming to be an excellent when you are debugging a problem and need two sets of eyes. It's also great for teaching/learning when a junior developer has banged his/her head against the problem before coming over to a more senior person for help. For research projects or deep thinking exercises, it's pretty counter-productive.
As a renter with a good job and excellent this article really makes its point clear: invest in some apartment ETFs
Youtube wasn't the breaking point for me, twitch.tv was. Granted, the streamers themselves do have control over this, I found it utterly annoying to see the same 1 or 2 ads played over and over in my face. Once I had ABP installed, the whole internet suddenly became faster to load too. The only annoying thing is, some websites that have those annoying ads that scroll across the webpage will now result in a dead-iframe blocking its content. Fortunately, I know how to right click, inspect element, navigate to the iframe container, and delete it, which, takes about 5 seconds.
I feel HTML5 today's "Web 2.0" of a few years ago. It's an overblown term that doesn't really capture what it is. CSS3 is cool. Canvas is cool. More native video is cool, I guess. The other new html elements are... ok... but quite frankily I'm fine with <div>s and changing them to <sections> seems annoying more so than helpful. HTML5 doesn't seem to bring anything radically new; most of what it allows could be done before, just with more workarounds and quirks. It's being hyped up as some next great thing, and not really a radical new development, it's much more incremental really.
And plenty of people are still using IE8 and Windows XP, and will for the next few years, so I don't think it's really more critical to learn HTML5 than over HTML4. Actually, it's hardly even possible to learn one without the other.
Please see elaborated reply in the comment here: https://news.ycombinator.com/item?id=5935039
I didn't express myself well enough, but your comment helped coax the idea from my heart to my brain:
I have no problems with explicit fees, nothing about that feels wrong to me. They are black and white. I want food, I pay for it. The non-negotiable, you pay the price on the menu aspect means both parties know fully-well in advance and can agree to what's being exchanged.
It's the ambiguous / "implicit" fees that cause me anguish. The waitress, in knowing that after the meal I'll be forced to make a judgment call, evaluating their service allows the possibility that every interaction leading up until I've paid them has been constructed to manipulate me. And outside an egregious there's little I can do to prove/disprove that. Whereas if its spelled out that upon entering the restaurant you will "pay XX rate for the service to do YY for you" you have the peace of mind that all parties involved know exactly what's going on. And anything they do above and beyond that is authentically who they are. If they tell me a joke, I know it's because they wanted to, not because they thought it might coax more money out of me.
As an American who eats out a lot, I have to admit I loved going to Iceland where tipping is not expected whatsoever. Tipping feels like prostitution; when cash is exchanged it's hard to believe you're getting authentic service.
Does anyone have the time to do a similar writeup for the tech scene in and around LA? I'm probably going to be doing the move from Boston-LA myself in just a few months.