I've only used them while using certain frameworks to dynamically generate queries referencing multiple tables. They end up getting turned into an implicit inner join though. The following queries are equivalent.
SELECT a.*, b.*
FROM a CROSS JOIN b
WHERE a.id = b.a_id
SELECT a.*, b.*
FROM a, b
WHERE a.id = b.a_id
SELECT a.*, b.*
FROM a INNER JOIN b ON a.id = b.a_id
IIRC .NET's Entity Framework will (or at least used to) generate queries similar to this as well.
I mean yes, but also no. I was skeptical that I could get into the game after reading about it, but I played the free demo [1] and got hooked. After "beating" it about 80 hours in I've lost a bit of interest because it seemed a bit more like work than play to really scale things, but the 80 hours of enjoyment was worth it. Might come back to it at some point and try to make a megabase or try some mods.
JetBrains does a pretty good job making this a bit less painful. They have a license server you install that dishes out floating licenses to IDEs. Floating licenses are released after 2-3 days, so if someone isn't using the product it doesn't consume a license.
We help organizations succeed with Apple! We're looking for software engineers with Java and/or iOS experience to help build the Casper Suite, a leading Mac OS and iOS management solution.
At JAMF Software we work hard to turn great ideas into great products and services for our customers. And we have always been devoted to providing the best customer experience. Our team brings passion and dedication to this mission, and we seek out these characteristics in people looking to join us. Together, there's no telling what we can accomplish as we continue to provide our customers with best-of-breed OS X and iOS management software–software that has become the foundation for transforming education and business.
We help organizations succeed with Apple! We're looking for software engineers with Java and/or iOS experience to help build the Casper Suite, a leading Mac OS and iOS management solution.
At JAMF Software we work hard to turn great ideas into great products and services for our customers. And we have always been devoted to providing the best customer experience. Our team brings passion and dedication to this mission, and we seek out these characteristics in people looking to join us. Together, there's no telling what we can accomplish as we continue to provide our customers with best-of-breed OS X and iOS management software–software that has become the foundation for transforming education and business.
Some of the previous work on this involving timing attacks against SSH [1] is particularly interesting because it's so obvious in retrospect, but no one saw it when SSH was being designed.
If you look at the difference in surface area between traditional men's/women's models of the same watch [1] there's a pretty massive difference in what you'd be able to do with the space. However, you do see more women wearing men's watches now, so I could see it catching on.
I think they will need to hit a pretty big number for battery life. A "40-hour power reserve" (what most mechanical automatics have) would be a big step towards being taken seriously as a watch instead of a gadget.
"Security research is the continual process of discovering your spaceship is a deathtrap" has to be one of the most apt descriptions of security research I've ever heard. What a great read!
No query optimizer would look at this and say "1M rows? Let's group and aggregate before filtering." Not to mention, the question specifically states that a=? would return 100 rows and a=? and b=? would return 10.
Regarding O(1), the first query would be some form of O(n log n) or O(log n) depending on the table/index data structures.
Regarding #5:
>That caught me by surprise. Both options “roughly the same” and “depends on the data” got about 25% — the guessing probably.
I don't think it was guessing so much as reasoning that fetching 100 rows (and filtering by value) instead of 10 rows doesn't have significant real-world impact unless the row data is particularly large. I'll admit I didn't think of the out-of-index lookup, but my main thought was 100/1000000 vs 10/1000000 isn't a big deal unless the DB is running on an abacus.
Unless I'm misreading this decision it merely upholds the FCC's right to classify ISPs as "information services" instead of "telecommunication services" because the Telecommunications Act is a bit fuzzy and leaves a lot up to the FCC. The FCC could decide to reclassify them as telecommunications services due to industry changes and I believe that this case would serve as precedent for them to legally do so.
Generally AMEX is known for better customer service, but YMMV. AMEX is often seen as a good choice for people looking to build credit because they're often willing to give out a 3x credit limit increase (without a hard credit pull) first 90 days after getting a card, and then every 6 months after that (up to a point and assuming you're using the account and in good standing).
IIRC .NET's Entity Framework will (or at least used to) generate queries similar to this as well.