I did Waterloo engineering co-op as well and yes, it is a bit hectic, but at that age you can handle it. I wouldn't have traded it for anything. I had interesting jobs in a number of different countries. I invested my interest-free student loan in energy mutual funds which turned into a goldmine at that time and combined with my salary I finished university with lots of experience, no debt and a ton of money in my bank account. If that is a "curse" then please curse me some more.
It seems like the use of the word "curse" is a bit suboptimal. As a UWaterloo co-op student myself, I agree with everything in the article. I just refer to the negative points of co-op as a "cost".
As a UofT grad, I am envious of the co-op experience that you guys have. I had to carve out my own opportunities, which in itself taught me about paving my own path. Nonetheless, definitely a great university and a great program to help students build a solid foundation.
It was similarly hectic trying to arrange for my own co-op opportunities but correct me if I'm wrong, I felt it was only hectic because I had never gone through something like that before. Once we've all been through it, looking back, it doesn't seem so bad after all. What do you think?
The async support you linked, while useful, isn't really the same thing. It requires explicit, manual coordination between different parts of the code that want to fetch data. You're responsible yourself for batching fetches, polling, and running other code until the results are returned.
With Hack's async support, the runtime manages all of this for you. You call "await $query", and then your function is suspended until the data is available. Other code automatically runs until it too hits an await statement -- which might block it on MySQL, memcache, curl, or anything else, with no extra manual coordination needed. The runtime manages it all for you.
http://hhvm.com/blog/7091/async-cooperative-multitasking-for... has some examples for what this looks like with curl -- in the final example, notice how you can just "await" on a bunch of different things and let the runtime worry about coordinating all of them.
The async stuff in HHVM is far more powerful than the meagre-at-best support for asynchronous operations in the original PHP runtime. In usage, HHVM's will be much more powerful.
Such odd language in those release notes. Git is being "taught" things or the various features are "learning". It's like they really do think of it as an actual git.
I still like StartSSL better than the other options. Yes, obviously opt out of having them generate your private key and CSR and upload your own. There is a big obvious "skip this" button there for that. To me the killer feature is that with class 2 validation ($60/year) you can generate as many 2-year certs, including wildcard as you want.
That's not a Yahoo hack though. When that happens it is almost always your local machine that has been breached by a virus which simply reads the locally stored contact list. And to answer your question, no, it is not a regular occurrence for Yahoo, or any of the major players, to have their servers hacked.
A number of times in recent memory Yahoo has been subject to attacks using XSS and similar. One example of one that was exploited (there was a disclosure back in May, but that didn't have reports of active exploits): http://thenextweb.com/insider/2013/01/31/yahoo-mail-users-st...
To my knowledge, my machine is secure. It wasn't Windows and I had both anti-virus and a firewall active. For one thing, what made this strange was that I haven't even logged into Yahoo for months (probably close to a year) when this happened, repeatedly.
If I remember correctly it was a random alpha-numeric password with both different cases and a special character or two, and I've never used the same password on a different service.
All I know is that I've never had this problem on competing services.
I've found XSS bugs that allow full account takeover being actively exploited on Yahoo! a couple of times. They have a lot of legacy crap that was written 15-20 years ago.
Consumer Reports is targeted at people in the US too.
Taxes in other countries means that cars get different engine, so for example in the past we used to get Audi with the power tweaked down in Belgium.
Also Tesla is a lot more practical in Belgium (small dense country) than in Spain (where energy is expensive, there is no supercharger and your regular electricity contract is 15A (220V), so not enough to charge a Tesla properly in the average dwelling)
There are so many factors, it is better for consumer magazine to focus on a single country.
I was at Yahoo during the years in question and must have been approached 50+ times by Google recruiters. I wonder if Yahoo refused to play along or perhaps they were never invited.
