In Go, if runtime.GOMAXPROCS() returns 1 or is set to 1 (meaning, Go only has access to a single system thread), the 'for' loop canabalizes the scheduler and the goroutine is rarely or never scheduled.
That fact doesn't make the OP's statement true, or have anything to do with the optimization bug, but it is worth pointing out that there are situations where Go correctly cannot guarantee that goroutine is executed.
Investors pull the strings. The behavior isn't the result of an investment, but failing to implement procedures after the fact to stop future incidents definitely can be. Not through action, but through inaction.
Meaning, more ethical investors (also known as: Board Members) might say "We need to do something about this."
Looks great. My main complaint is that the templates feature appears to be reinventing Terraform. Would have been cool if we could use the Terraform templates we already have, or even provide support for CloudFormation (given this is an AWS-only tool).
I can't generalize for every school, or everyone at every school. I attended an engineering program at one of the top 5 schools by total international student population.
Honestly, international students are cliquey. Many of them that I talk to openly admit to cheating on their english proficiency exams universities require you to take before you can attend. Meshing with local students is nearly impossible if you don't understand the language proficiently.
I'd expect you'd see roughly the same numbers if you looked at American students in Chinese universities, or elsewhere. But we have to make this anti-American because its Quartz, and Trump is bad, right?
When I say MacBooks... I mean the MacBook Pros. As in, what this article is talking about. Apple never reduced the size of the MB battery by 30%. Or added a second screen. Or kept performance they same (they improved performance gen-over-gen with the MB). Use your head. Apply some context.
Everyone talks about the downsides of the new MacBooks. No one talks about about how they reduced the size of the internal battery by 30%, effectively added a second screen, improved overall performance, and still kept the same battery life.
Most people (think: GNU wizards) who do projects like this don't want to monetize; not for capability reasons, but for philosophical and social reasons. They think monetization is against some principal of free software, or their morals, or that people will stop using their software if they do, or, simply: they're lazy and just want to code, without worrying about menial things like income.
And then, when they can't afford to work on their project anymore, they want our pity. They don't have mine.
It is his responsibility to capture the value of his work. The world does not owe him this. The world doesn't owe him anything unless he demands it.
You're asking to have your cake and eat it to: Give software away (altruism) but also feel guilty when he complains that he doesn't have any money. You can't have both.
Honestly, I'm 100% more fine with Apple spying on me than pretty much anyone else. I'm less perturbed with the entire concept of spying than I am with who is doing it.
It is so concerning to me that the company has committed to spending an average of $400M per year on cloud infra when their revenue is only $200M, and they've revealed that user growth slowed from 17% to 3% in the quarter Insta released Stories.
It'd be one thing if they were going to use some of the IPO money to cost-optimize revenue, but I get the feeling that they need to focus on growing revenue due to how Insta Stories gutted them in 2016. That means hiring more people and writing bigger checks to Google.
And they're branding themselves as a "camera company." Their hardware division does not contribute materially to revenue (not profit: Revenue), and practically every other consumer camera company, from Kodak to GoPro, is dying.
I get that things can be fluid, but its such a meat machine.