That depends on why the new round exists. It may simply be that the initial investment was traunched, and that it was always expected that no profit could be made by this point, but the investors still wanted a check point to make sure things were developing on track.
Swift can guarantee data-race freedom, in exactly the same way that C and C++ can - by using the normal threading and locking primitives you get from the OS's libraries. It even ships with a more user friendly library for doing this (GCD) than most OSes provide.
And swift absolutely does not require thread safe ref counting. Swift has both value types and reference types. Value types are passed by value (what a surprise), and include non-ref-counted pointer types. All you need do to avoid ref counting is to not use the word "class" in your program, and instead stick to "struct".
Neither of these are impediments to system programming.
Usually it's a case of needing to understand the actual use case in order to be able to provide alternate options.
Usually it means "The thing you're trying to do is dumb for a number of reasons, but since you haven't described what the *actual* goal is, but instead only what a possible implementation might look like, it's impossible to tell you why it's dumb and what a better choice is."
Concurrency/parallelism primitives was available through extensions (like posix threads, locks etc.). Those were available because, as native languages, C and C++ can make use of (inline) assembly and anything supported by ISA. Try that on interpreted/JIT-ed language.
Yes - the point I'm making is that these are all equally available in Swift. All C APIs are available without any modification in Swift.
No other modern language is capable of safety and is low level enough. I saw one comment here asking why no swift, well for starters it has no concurrency or parallelism primitives which are a necessity for a systems language. Certainly for whatever language you want to write a browser in...
That seems like a strange assertion to make given that C has, and C++ until recently had no concurrency or parallelism primitives, and are the de-facto systems programming languages at the moment.
It also seems like a strange assertion when Swift by default ships with Grand Central Dispatch, which gives it strong concurrency and parallelism support.
The issue with swift as a systems programming language is that its compiler output is too magical. Several of its features can cause weird and unexpected perf implications when used in subtly different ways. For example, it's generics implementation can end up compiling down to either fully dynamic dispatch, or just normal C function calls depending on whether the compiler analysis could figure out which types you were using, when, and how often.
Knowing how much companies like Microsoft, Apple and Google etc pay H1Bs, I would bet reasonably heavily that all of these people already earn over $150k.
Microsoft, Apple and Google (and all the other big tech companies) are not the ones you care about re problem 1 - that's infosys and tata. They're dealing with problem 2, and already applying your solution.
What Microsoft is saying is "uhhh, we have guys that do awesome work who are from Iran/Syria/Somalia/..., we need them to carry on doing that awesome work".
The most significant "geographic barrier" to this story is San Jose. All the tech industry's families are being raised in the urban sprawl that is categorised as part of it, rather than part of SF.
Yeh, both the RPI and CPI are showing marked increases after brexit, so yes, the price of a loaf of bread is not only going up, but going up faster than before.
This is a pretty common requirement in the western world. The US is the only western country I'm aware of in which there's not a law against advertising an item as on sale when it's never actually been sold at a higher price.
In the UK (and most of Europe) for example, all price cuts must be advertised as being cut from a different price that you have sold the item at for a continuous 30 day period.
With today's cars it's not out of scope, but it's annoying - you'd need to charge even in the highest range of them (315 miles in a P100D, make that 270 in the winter). With a supercharger the time to charge than missing 120 miles is going to be about half an hour.
The good news is that with this samsung battery, you wouldn't need to charge, but even if you did, with charge point's new 400kW chargers you'd be able to charge enough for your *whole* trip in 15 minutes. In the summer, make that 10 minutes.
If you actually read, you'll see that the study isn't about the fact that alcohol triggers you to eat more, it's about how it does it, which parts of your brain are affected, and why. That's important information if you say.... wanted to make drugs that suppressed your starvation response to help you lose weight.
That depends entirely on what benchmark you're looking at.
If you're goal is to play GooSplatter 2017 at 3840x2160@144Hz, then staring at a benchmark that reports the frame rate of GooSplatter 2017's rendering engine, with representative scenes from the game is an entirely reasonable thing to do.
Don't assume that all people staring at benchmarks don't understand what each test is actually measuring.
I have no details about this battery in particular, but my experience with owning an EV, and knowing others who own them is that range drops around 15% at 0-5C compared to 20-30C.
Come on, the lightsaber battle in 1 was really good, and pretty dark all by itself. Also the initial scene on the droid ship was pretty good if you think of it standalone and ignore the absurd droid army stuff that comes later.
And if you ignore the fact that they hired 12 year old actors for it, and cheesed up the ambassadors being bumbling fools.
The point is that the goal of google is to write the popularity formula in such a way that better quality, more reliable results get ranked more highly. Their formula is breaking down in this instance (probably due to gaming), and it needs to be investigated why, and fixed.
The issue isn't with showing the result, it's with the ordering of the results. You would hope that more trustworthy results are ordered above less trustworthy ones.
The key is that the informal drop in meetings that take 15 minutes should be replacing the 2 hour long meetings with project managers, 2 layers of management and 8 engineers.
By making sure you understand all of the problems, and all the relevant co-workers do too, you can head off those meetings by convincing the PMs that everything is on track, and explaining what's going on in emails.
Hah, no. "Unlimited time off" is code for "you have no contracted amount of time off that you're allowed to take off, so we can make you feel guilty about taking any amount of time off at all, while making it much harder to track how much time you really are taking".
Slashdot Mirror
That depends on why the new round exists. It may simply be that the initial investment was traunched, and that it was always expected that no profit could be made by this point, but the investors still wanted a check point to make sure things were developing on track.
Swift can guarantee data-race freedom, in exactly the same way that C and C++ can - by using the normal threading and locking primitives you get from the OS's libraries. It even ships with a more user friendly library for doing this (GCD) than most OSes provide.
And swift absolutely does not require thread safe ref counting. Swift has both value types and reference types. Value types are passed by value (what a surprise), and include non-ref-counted pointer types. All you need do to avoid ref counting is to not use the word "class" in your program, and instead stick to "struct".
Neither of these are impediments to system programming.
Usually it's a case of needing to understand the actual use case in order to be able to provide alternate options.
Usually it means "The thing you're trying to do is dumb for a number of reasons, but since you haven't described what the *actual* goal is, but instead only what a possible implementation might look like, it's impossible to tell you why it's dumb and what a better choice is."
Concurrency/parallelism primitives was available through extensions (like posix threads, locks etc.). Those were available because, as native languages, C and C++ can make use of (inline) assembly and anything supported by ISA. Try that on interpreted/JIT-ed language.
Yes - the point I'm making is that these are all equally available in Swift. All C APIs are available without any modification in Swift.
No other modern language is capable of safety and is low level enough. I saw one comment here asking why no swift, well for starters it has no concurrency or parallelism primitives which are a necessity for a systems language. Certainly for whatever language you want to write a browser in...
That seems like a strange assertion to make given that C has, and C++ until recently had no concurrency or parallelism primitives, and are the de-facto systems programming languages at the moment.
It also seems like a strange assertion when Swift by default ships with Grand Central Dispatch, which gives it strong concurrency and parallelism support.
The issue with swift as a systems programming language is that its compiler output is too magical. Several of its features can cause weird and unexpected perf implications when used in subtly different ways. For example, it's generics implementation can end up compiling down to either fully dynamic dispatch, or just normal C function calls depending on whether the compiler analysis could figure out which types you were using, when, and how often.
Knowing how much companies like Microsoft, Apple and Google etc pay H1Bs, I would bet reasonably heavily that all of these people already earn over $150k.
Microsoft, Apple and Google (and all the other big tech companies) are not the ones you care about re problem 1 - that's infosys and tata. They're dealing with problem 2, and already applying your solution.
What Microsoft is saying is "uhhh, we have guys that do awesome work who are from Iran/Syria/Somalia/..., we need them to carry on doing that awesome work".
The most significant "geographic barrier" to this story is San Jose. All the tech industry's families are being raised in the urban sprawl that is categorised as part of it, rather than part of SF.
Yeh, both the RPI and CPI are showing marked increases after brexit, so yes, the price of a loaf of bread is not only going up, but going up faster than before.
Sure it is as long as your average priced EV is a Chevy Bolt.
The other common thing they do is alternate two sales -
Oranges, £0.49 –SALE, 3 for 2!
Oranges, SALE £0.33 was £0.49
Each for 30 days.
This is a pretty common requirement in the western world. The US is the only western country I'm aware of in which there's not a law against advertising an item as on sale when it's never actually been sold at a higher price.
In the UK (and most of Europe) for example, all price cuts must be advertised as being cut from a different price that you have sold the item at for a continuous 30 day period.
With today's cars it's not out of scope, but it's annoying - you'd need to charge even in the highest range of them (315 miles in a P100D, make that 270 in the winter). With a supercharger the time to charge than missing 120 miles is going to be about half an hour.
The good news is that with this samsung battery, you wouldn't need to charge, but even if you did, with charge point's new 400kW chargers you'd be able to charge enough for your *whole* trip in 15 minutes. In the summer, make that 10 minutes.
Oligarchy *is* better than Democracy, if your goal is to do something that fits the needs of a small number of people (specifically, the oligarchs).
Uhhh... Yes.
If you actually read, you'll see that the study isn't about the fact that alcohol triggers you to eat more, it's about how it does it, which parts of your brain are affected, and why. That's important information if you say.... wanted to make drugs that suppressed your starvation response to help you lose weight.
That depends entirely on what benchmark you're looking at.
If you're goal is to play GooSplatter 2017 at 3840x2160@144Hz, then staring at a benchmark that reports the frame rate of GooSplatter 2017's rendering engine, with representative scenes from the game is an entirely reasonable thing to do.
Don't assume that all people staring at benchmarks don't understand what each test is actually measuring.
I have no details about this battery in particular, but my experience with owning an EV, and knowing others who own them is that range drops around 15% at 0-5C compared to 20-30C.
known by your enemies, and are not being fixed
ftfy
Come on, the lightsaber battle in 1 was really good, and pretty dark all by itself. Also the initial scene on the droid ship was pretty good if you think of it standalone and ignore the absurd droid army stuff that comes later.
And if you ignore the fact that they hired 12 year old actors for it, and cheesed up the ambassadors being bumbling fools.
http://imgur.com/gallery/Putq2
Nor does the USA.
He's not - he's entitled to the cheapest he can get hold of for the required skill level.
The point is that the goal of google is to write the popularity formula in such a way that better quality, more reliable results get ranked more highly. Their formula is breaking down in this instance (probably due to gaming), and it needs to be investigated why, and fixed.
The issue isn't with showing the result, it's with the ordering of the results. You would hope that more trustworthy results are ordered above less trustworthy ones.
The key is that the informal drop in meetings that take 15 minutes should be replacing the 2 hour long meetings with project managers, 2 layers of management and 8 engineers.
By making sure you understand all of the problems, and all the relevant co-workers do too, you can head off those meetings by convincing the PMs that everything is on track, and explaining what's going on in emails.
Hah, no. "Unlimited time off" is code for "you have no contracted amount of time off that you're allowed to take off, so we can make you feel guilty about taking any amount of time off at all, while making it much harder to track how much time you really are taking".