Except those are generally requirements if you want to run a taxi service that can be hailed on the street. Services where you have to call have existed since FOREVER, legally, without any issues (ie: In NYC they have been very common). Those laws didn't apply to them because you couldn't just hail one.
Second, taxi services have historically been one of the most corrupt thing ever, both on the companies side and the drivers. So basically all of those rules are broken on a daily basis, and getting them enforced is hard.
So in many cases, Uber was totally legal (as the former), but taxi lobbies just interpreted the rules very creatively to try and get the taxi rules (which should not apply) to Uber, while they themselves do not follow them.
Some problems in IE were from implementing things before the standard was complete. Other browsers did this as well, but the other browsers would usually change their browser to match the standard when it was complete. Microsoft would not change to the standard to keep backwards compatibility with pages made specifically for their non-standard implementation.
More recently it got to the point where whatever Firefox, and then later Chrome did WAS the standard, like IE once did.
That being, if Firefox broke the standard, the standard changed to match Firefox. Or if IE matched the standard but other browsers didn't, IE took flack for "implementing a stupid part of the standard".
Its just silly now. All hails the W3...Webkit/Blink.
That's fairly similar to the point system in the west, give or take. Have X amount of points, speeding makes you lose points, when you're at zero you're screwed.
There hasn't been much value in writing code in a LONG time. You still need someone to do it, and it is somewhat time consuming (enough that people that do it aren't competing with bugger flippers...), but really, 95% of the value is between the time someone thinks up of a problem with a solution and its implementation design, until they open the text editor and start typing. After that point, a monkey could do it with a bit of support.
Oh, that strategy does work to some extent for sure. Though Apple's success has a lot more to do with their godly beyond comprehension marketing department than anything about the actual product. SOME of their product decisions don't hurt either, but its far from the main reason they're so popular.
You are not only confused, but also being duped. The only kind that would be considered homeopathic are the "highly diluted" ones. And by highly diluted, it means potentially thousands of times (ie: there is virtually no trace amount of the original ingredient in). That is the definition of homeopathy.
Homeopathy is when you take an active ingredient, put it in water, then dilute hundreds or even thousands of times until all the active ingredient is gone. Then by using a concept often referred to as the "memory of water", the nearly distilled water left is supposed to be more powerful than the original compound that contained the active ingredient.
If you have a non-trivial amount of active ingredient, then its naturopathy or even just "medicine". Those are often mislabeled on purpose, so that the real homeopathic treatments (which, being water, are impossibly cheap to produce), get traction.
As people mentioned already, that's not homeopathic. There's actually an active ingredient in there. Anything that isn't virtually distilled water is NOT homeopathy, and is generally naturopahy. If I can take your homeopathic remedy, analyze it, and easily find something that isn't pure H2O, then its simply not homeopathy at all. BY _DEFINITION_
No, that's not homeopathy. At all. You're describing naturopathy.
Homeopathy only has 1 compound. Water that once upon a time had something else in it and was diluted until there was nothing left of the original. Generally speaking, if there's anything but trace amount (if that) of the original compound, you're not done diluting yet. An homeopathic compound, scientifically, is pretty much always pure water.
Seems like several people are confusing the two in this thread. Homeopathy is not "natural products". It is something very specific (the above compound diluted so much there's only water left, along with some patient/practitioner relationship and near-rituals).
Except there's nothing to analyze in homeopathy. Its a mix of "relationship with the practitioner" and distilled water. that once upon a time (before it was more or less distilled) had something in it. It no longer does, so you won't find anything.
The tree bark and goat liver concoction and all that crap can potentially work, because there's SOMETHING in it, but that's naturopathy, not homeopathy, and its COMPLETELY different.
Chinese push it to the extreme though (disclaimer, my wife is chinese, and her family fit exactly the description above, and they freely admit it...my wife was born here and was kind of a rebel, thus why she broke the line and ended up with a white guy).
The length they'll go to avoid all "foreigners", even when they're in the middle of big cities, big schools, etc...All big companies have a "Chinese" mailing list that a ton of them subscribe to, eat together, go out together, only deal with doctors/contractors/etc who are chinese, etc. Its crazy.
Our brains are basically designed to spot differences and handle them as special case scenarios (thus why if I have a wall full of green dots and one is red, you'll probably notice the red dot before you realize there's a wall behind it).
We're also (understandably so) relate better to things that remind us of ourselves/our families/etc.
The two put together means someone who physically looks different than what you're used to, will automatically take a pretty big hit. Black people take the brunt of it, being a lot more different visually than, let say, a white westerner and an asian.
That's not enough in itself though. Black people in countries that don't have historical background relating to them will have a lot less racism issues.
Then tack on statistical differences in certain areas (ie: a city where there's a big economic divide with a high racial correlation, usually again because of historical reasons), and you hit a society perfect storm that will take a miracle (or just a lot of time....) to overcome.
That will heavily depend on how you do it. If you have a 1 to N, and insert the object trees one by one, you're going to get a crazy amount of back and forth. The amount of queries will be the same, and similar to the ones you do manually, so there won't be any meaningful differences there.
The main difference is that you're likely to do "Insert 1 in master, 5 in detail, 1 in master, 5 in detail", batching them in groups of 1 and N, when the correct way is to insert all the rows in master, then all the rows in details (batching in smaller groups if transaction size is a problem).
EF can handle that scenario just fine. Its just not that clean.
That's just understanding how an ORM work, and all ORMs have these issues. You get used to working around them. (You'd have a seizure seeing what Rails Active Record does, yet people use it in petabyte scenarios.)
What's readable or not is relative to the context of the reader.
A lot of the features that were added, were only added once they were pretty much standard everywhere else.
I remember the first time I saw a lambda in a language... var foo = (x, y) => x * y
What...the...fuck...is going on there.
Of course, now that syntax or slight variations of it are everywhere, so most people will be able to read the above just fine, even if their language is choice doesn't use that exact syntax (ie: ruby). The C++ version is a little messy, but it sure as hell was needed.
Entity Framework being slow isn't the problem with it. The performance of an ORM only really depend on 2 things. The time it takes to do the mapping, which is trivialized by the actual queries and is really a micro-optimization, and the SQL generated.
The later is fine in almost all of the mainstream ORMs, and the only real issues come from N+1 queries, and not aggregating queries that can be by using the context and futures. ActiveRecord based ORMs have issues because of the way context vs model objects is managed but they can still handle it fine, the N+1 problem is almost always a developer thing.
The reason Entity Framework sucks is that its API is poorly documented, so short of reading the code, no one knows how to do things correctly, a lot of its features are not exposed through the tools, thus encouraging using the RAD/shitty ways of doing things, and they pulled it in all directions trying to make everyone happy, ending up with a lowest common denominator.
You can get perfectly good performance out of EF, it has all the features an ORM needs to achieve it. Its just hidden/awkward/changes all the time/forces you into writing shitty code.
Development cost for these things is still pretty close to half the whole cost. If you think making an engine from scratch is gonna cost you less than 5% (though do take in consideration the cost of learning/using the engine is, as that's not zero), go for it. Some companies still do it. Fewer and fewer though.
Generally when people say compiled language, and they refer to things like Objective C and C++, they usually mean compile to as close to native code as possible. I love C#, but its fairly obvious that bytecode languages were not options this time around.
Looked at the site, can't wait to be able to try it (signed up on the site to hopefully get in the beta eventually).
We're also in Boston and starting to have remote teams/offices, but full digital whiteboards are a little too much for us. This looks like a sweet spot.
Its people's reaction to seeing naked pictures of you that are the problem. You can get fired, disqualified from jobs, shunned, and all around your life can become a living hell.
If you get beat up in a alley, the damage (aside for the psychological damage from the event itself) might go away once the wounds heal. If you're a teacher and students find pictures of you? You potentially can kiss your career (or at least your next promotion) good bye.
And its one thing if the person allowed the picture to be taken (though even then, but whatever), but a lot of people abuse of positions of trust, and a lot of those pictures are taken without consent. There's a LOT of assholes out there.
Slashdot Mirror
Except those are generally requirements if you want to run a taxi service that can be hailed on the street. Services where you have to call have existed since FOREVER, legally, without any issues (ie: In NYC they have been very common). Those laws didn't apply to them because you couldn't just hail one.
Second, taxi services have historically been one of the most corrupt thing ever, both on the companies side and the drivers. So basically all of those rules are broken on a daily basis, and getting them enforced is hard.
So in many cases, Uber was totally legal (as the former), but taxi lobbies just interpreted the rules very creatively to try and get the taxi rules (which should not apply) to Uber, while they themselves do not follow them.
Thats a big problem.
More recently it got to the point where whatever Firefox, and then later Chrome did WAS the standard, like IE once did.
That being, if Firefox broke the standard, the standard changed to match Firefox. Or if IE matched the standard but other browsers didn't, IE took flack for "implementing a stupid part of the standard".
Its just silly now. All hails the W3...Webkit/Blink.
Everyone knows that rich people don't deserve anything because of how priviledged they are. DUH.
That's fairly similar to the point system in the west, give or take. Have X amount of points, speeding makes you lose points, when you're at zero you're screwed.
Markup fail. I meant "Less than $100"
You're reading it wrong. Its not 50% of their daily income. Its 50% of their calculated disposable income.
So you take their yearly salary, minus some estimate of their cost of living, then divide the result by 2.
Using the same math as the rich people example above, the fine here would be $100
There hasn't been much value in writing code in a LONG time. You still need someone to do it, and it is somewhat time consuming (enough that people that do it aren't competing with bugger flippers...), but really, 95% of the value is between the time someone thinks up of a problem with a solution and its implementation design, until they open the text editor and start typing. After that point, a monkey could do it with a bit of support.
Oh, that strategy does work to some extent for sure. Though Apple's success has a lot more to do with their godly beyond comprehension marketing department than anything about the actual product. SOME of their product decisions don't hurt either, but its far from the main reason they're so popular.
No. If you're using the extract, then its not homeopathy. Time to read up.
You are not only confused, but also being duped. The only kind that would be considered homeopathic are the "highly diluted" ones. And by highly diluted, it means potentially thousands of times (ie: there is virtually no trace amount of the original ingredient in). That is the definition of homeopathy.
Homeopathy is when you take an active ingredient, put it in water, then dilute hundreds or even thousands of times until all the active ingredient is gone. Then by using a concept often referred to as the "memory of water", the nearly distilled water left is supposed to be more powerful than the original compound that contained the active ingredient.
If you have a non-trivial amount of active ingredient, then its naturopathy or even just "medicine". Those are often mislabeled on purpose, so that the real homeopathic treatments (which, being water, are impossibly cheap to produce), get traction.
As people mentioned already, that's not homeopathic. There's actually an active ingredient in there. Anything that isn't virtually distilled water is NOT homeopathy, and is generally naturopahy. If I can take your homeopathic remedy, analyze it, and easily find something that isn't pure H2O, then its simply not homeopathy at all. BY _DEFINITION_
No, that's not homeopathy. At all. You're describing naturopathy.
Homeopathy only has 1 compound. Water that once upon a time had something else in it and was diluted until there was nothing left of the original. Generally speaking, if there's anything but trace amount (if that) of the original compound, you're not done diluting yet. An homeopathic compound, scientifically, is pretty much always pure water.
Seems like several people are confusing the two in this thread. Homeopathy is not "natural products". It is something very specific (the above compound diluted so much there's only water left, along with some patient/practitioner relationship and near-rituals).
Except there's nothing to analyze in homeopathy. Its a mix of "relationship with the practitioner" and distilled water. that once upon a time (before it was more or less distilled) had something in it. It no longer does, so you won't find anything.
The tree bark and goat liver concoction and all that crap can potentially work, because there's SOMETHING in it, but that's naturopathy, not homeopathy, and its COMPLETELY different.
What makes things difficult, is that the people who are wrong don't know they're wrong.
So you have 2 people who think differently and thinking the other is wrong. Which one is? Who knows! Its easy in hindsight of course.
Chinese push it to the extreme though (disclaimer, my wife is chinese, and her family fit exactly the description above, and they freely admit it...my wife was born here and was kind of a rebel, thus why she broke the line and ended up with a white guy).
The length they'll go to avoid all "foreigners", even when they're in the middle of big cities, big schools, etc...All big companies have a "Chinese" mailing list that a ton of them subscribe to, eat together, go out together, only deal with doctors/contractors/etc who are chinese, etc. Its crazy.
Our brains are basically designed to spot differences and handle them as special case scenarios (thus why if I have a wall full of green dots and one is red, you'll probably notice the red dot before you realize there's a wall behind it).
We're also (understandably so) relate better to things that remind us of ourselves/our families/etc.
The two put together means someone who physically looks different than what you're used to, will automatically take a pretty big hit. Black people take the brunt of it, being a lot more different visually than, let say, a white westerner and an asian.
That's not enough in itself though. Black people in countries that don't have historical background relating to them will have a lot less racism issues.
Then tack on statistical differences in certain areas (ie: a city where there's a big economic divide with a high racial correlation, usually again because of historical reasons), and you hit a society perfect storm that will take a miracle (or just a lot of time....) to overcome.
That will heavily depend on how you do it. If you have a 1 to N, and insert the object trees one by one, you're going to get a crazy amount of back and forth. The amount of queries will be the same, and similar to the ones you do manually, so there won't be any meaningful differences there.
The main difference is that you're likely to do "Insert 1 in master, 5 in detail, 1 in master, 5 in detail", batching them in groups of 1 and N, when the correct way is to insert all the rows in master, then all the rows in details (batching in smaller groups if transaction size is a problem).
EF can handle that scenario just fine. Its just not that clean.
That's just understanding how an ORM work, and all ORMs have these issues. You get used to working around them. (You'd have a seizure seeing what Rails Active Record does, yet people use it in petabyte scenarios.)
What's readable or not is relative to the context of the reader.
A lot of the features that were added, were only added once they were pretty much standard everywhere else.
I remember the first time I saw a lambda in a language... var foo = (x, y) => x * y
What...the...fuck...is going on there.
Of course, now that syntax or slight variations of it are everywhere, so most people will be able to read the above just fine, even if their language is choice doesn't use that exact syntax (ie: ruby). The C++ version is a little messy, but it sure as hell was needed.
Same thing can be said of most of the additions.
Entity Framework being slow isn't the problem with it. The performance of an ORM only really depend on 2 things. The time it takes to do the mapping, which is trivialized by the actual queries and is really a micro-optimization, and the SQL generated.
The later is fine in almost all of the mainstream ORMs, and the only real issues come from N+1 queries, and not aggregating queries that can be by using the context and futures. ActiveRecord based ORMs have issues because of the way context vs model objects is managed but they can still handle it fine, the N+1 problem is almost always a developer thing.
The reason Entity Framework sucks is that its API is poorly documented, so short of reading the code, no one knows how to do things correctly, a lot of its features are not exposed through the tools, thus encouraging using the RAD/shitty ways of doing things, and they pulled it in all directions trying to make everyone happy, ending up with a lowest common denominator.
You can get perfectly good performance out of EF, it has all the features an ORM needs to achieve it. Its just hidden/awkward/changes all the time/forces you into writing shitty code.
Development cost for these things is still pretty close to half the whole cost. If you think making an engine from scratch is gonna cost you less than 5% (though do take in consideration the cost of learning/using the engine is, as that's not zero), go for it. Some companies still do it. Fewer and fewer though.
Generally when people say compiled language, and they refer to things like Objective C and C++, they usually mean compile to as close to native code as possible. I love C#, but its fairly obvious that bytecode languages were not options this time around.
C++/Boost is their best bet.
QI chargers, already used across the Nexus line, and I _think_ some Samsung phones?
Im personally happy, since all my phones/tablet support Qi.
Looked at the site, can't wait to be able to try it (signed up on the site to hopefully get in the beta eventually).
We're also in Boston and starting to have remote teams/offices, but full digital whiteboards are a little too much for us. This looks like a sweet spot.
Except it happens all the time. In many profession. Even in Europe. Just google a little.
Its people's reaction to seeing naked pictures of you that are the problem. You can get fired, disqualified from jobs, shunned, and all around your life can become a living hell.
If you get beat up in a alley, the damage (aside for the psychological damage from the event itself) might go away once the wounds heal. If you're a teacher and students find pictures of you? You potentially can kiss your career (or at least your next promotion) good bye.
And its one thing if the person allowed the picture to be taken (though even then, but whatever), but a lot of people abuse of positions of trust, and a lot of those pictures are taken without consent. There's a LOT of assholes out there.