As a buyer, eBay accounts are throwaway. For things like Steam, where one chargeback could nuke / limit your whole account and the operators ignore all of your rights because "LOL VIDEOGAMES", create individual accounts for individual titles you're unsure about. Alternatively, don't buy from stores with shitty fucking policies.
If you're using a term like "Big Data", you don't belong in the fucking building. Relational databases are perfectly suited to extremely large and complex datasets. You just have to intelligently design your database. You can't just throw noise into a pot and expect useful results. Hadoop (map reduce) tries to do exactly this. If you care about correctness, completeness, and synchronization of data, it's trash.
SQL server is based around the idea of small amounts of changes with data retention being long.
Assume a system throwing off 3mbs of data which many companies can have if they are aggregating simple stuff like all customers on the websites and sequencing page by page access to look for correlations. There are 28,500 seconds in a workday (more if you have multiple locations). That's 85.5 petabytes of data per day. You need to aggregate this data fast. SQL Server's engine isn't designed for that.
Or for example SQL Server doesn't handle queries against unstructured information. Imagine that each record has a field of text and you want to do joins based on fuzzy matching between these text fields. Even with a few gigs of data SQL Server will die.
Check your math on that, please. 8*3600*3 = 84.375 GB, not 85.5 PB.
Further, 85.5 PB per day is no problem if you can manage to write all of that out to disk (1037 GB per second non stop lol). SQL Server 2014 handles.5 EB per database, so it's not a problem. And if your tracking 3 MB per second per user, you're tracking bots, not users - it would actually be cheaper to just log all packets at that point.
As for making sense of the data, SQL can handle all of it if you design your database sanely. Even if you don't, you can slap a full-text index on it (including "natural language" style indexes). You pay a penalty for your poor design, sure, but everything works.
Something as simple as manufacturing data far eclipses this number every day. Think of every screw from every supplier in every product. Then tracking the reliability of this product through the entire lifecycle with self diagnostic tests. No, this is not for your toy made in china, but when it comes to real top end products that HAVE to work, then you need this kind of data to figure out what went wrong and fix it fast. That could save your company millions.
No, making your latest dot bomb app does not need this, but there are many places that do. Also check out financial apps like credit fraud, insurance, etc.
Every screw from every supplier in every product? No one dealing in volume tracks that because it's fucking pointless. People dealing with really-expensive shit that requires that tracking don't deal in volumes where it would be a problem.
But lets pretend we live in a fantasy world where that's true.
SUPPLIERS ID - INT PrimaryKey, Identity Name nvarchar(whatever)...
PARTTYPES ID - INT PrimaryKey, Identity SupplierID INT ForeignKey (SUPPLIERS.ID) Name nvarchar(whatever)...
PARTS ID - BIGINT PrimaryKey, Identity PartTypeID INT ForeignKey (PARTTYPES.ID)...
PARTTRACKING ID - BIGINT PrimaryKey, Identity PartsID BIGINT ForeignKey (PARTS.ID)...
Add location/action/QC, result, timestamp, and employee id columns to the PARTTRACKING table and you get maybe 40 bytes per row total.
Pretend there are 100 tracking entries per part (LOL), 10,000 tracked parts per product (LOLOL), and 1,000,000 of these presidential spacecraft level products per day (LOOOOL). You're only looking at 36 TB per day for PARTTRACKING, the most expensive (by far) table. Bump it up to 50 TB for all other shit in the DB.
Your claim was that one day of manufacturing tracking would far eclipse.5 PB. Not only is this not true, SQL Server 2014 has a limit of.5 EB, not.5 PB.
Further,.5 PB per day, even assuming non-stop operations, would be 6 GB per second of writing. And your claim is that that would be "far eclipsed".
Hadoop was created in 2005 and named after a toy elephant. It was an open source implementation of some shit Google wrote some papers on. The "Apache Hadoop" branded package hit RTM in 2011. Apache only got involved because of all the retards mindlessly jumping onto it. Those retards jumped onto it because they were told it was based on Google's work.
As for datasets being too big for RDBMS engines to handle, WTF are you talking about? MS SQL can handle all the data you throw at it and has complete clustering capabilities. If your database is designed properly there's no problem. Oracle is the same.
For SQL Server 2014, individual files are limited to a mere 16 TB, and you can have only 32,767 filegroups per database. The maximum size of a single database is 524,272 TB, and you can have 32,767 databases per instance, and you can have 50 instances per server. The number of rows per table is limited only by available storage. The max size of any in-page row is 8,060 bytes, with anything larger being moved off-row and the row maintaining a pointer.
Please tell me what sort of dataset exceeds the 800 YB maximum you get from SQL Server 2014.
Did I trip into a time warp and come out a decade in the past? Who the fuck is actually talking about hadoop or map reduce in 2015? The same retards that were creaming their little cunts about it in 2005?
Even when you ignore the joke that is Java, hadoop is unwieldy, unreliable shit if you actually care about storing and retrieving correct, synchronized data. If you're fine with throwing all of your data in a pot and getting some sort of result that looks mostly correct, then knock yourself out and use hadoop.
If your data needs to be correct, define it and its relationships then use SQL. You will have to pay someone decent money to do this correctly.
twenty automated levels before you can speak to a person , hit the wrong option oops have to redial and start again. Then you to valdiate with a person before they will transfer you through to the appeals dept. Where you have to validate again. After 25 attempts the appeals department wont tell you how you appeal.
All for an item the that never arrived because the courrier company delievered it to the wrong house number , wrong street , wrong postcode - but as it was signed for according to ebay it was successfully delivered.
Which is why you pay with a credit card and issue a chargeback at the first sign of bullshit.
everyone has a price, and if you have the dollars, you can use the dollars from your monopoly to poach anyone. This isn't an anti-collusion suit; this is a civil suit about monopoly abuses.
The teachers of the law and the Pharisees brought in a woman caught in adultery. They made her stand before the group and said to Jesus, "Teacher, this woman was caught in the act of adultery. In the Law Moses commanded us to stone such women. Now what do you say?"
They were using this question as a trap,in order to have a basis for accusing him. But Jesus bent down and started to write on the ground with his finger. When they kept on questioning him, he straightened up and said to them, "Let any one of you who is without sin be the first to throw a stone at her."
Again he stooped down and wrote on the ground. At this, those who heard began to go away one at a time, the older ones first, until only Jesus was left, with the woman still standing there. Jesus straightened up and asked her, "Woman, where are they? Has no one condemned you?"
"No one, sir," she said. "Then neither do I condemn you," Jesus declared. "Go now and leave your life of sin."
Kinda like the one that says divorced women should be killed, and stuff?
Not everything in the bible is a prescription of what should be. Much of it is accounts of the various ways people, governments, and society were horrible. If you're having trouble distinguishing between what is a religious tenet and what is an account, you may want to try thinking, or you may want to give up.
Sure if you cherry pick your applications to suit your case then you could argue that. To me I see open source vulnerabilities which are called CVE-215-3456 which someone happens to have an alternate name for. I see programs called StarOffice, and Libre Office. I see MySQL, openLDAP, and systemd. All very descriptive of what they do.
Let's not over generalise.
What does "Star Office" do? How is it different from "Libre Office" or "Open Office"? Wait, "Open Office" IS "Star Office"? Oh, it's NOT? Then why does installing "Open Office" give me and "soffice" executable?!
What's "MySQL"? Is it mine? Whose is it? Is it a server? Can I only use it for personal use?
What's an "LDAP"? Do I want an open one or a closed one? I need it to be secure, so I probably don't want an open one.
Oh, you included systemd. Your entire post is a troll.
Yet everyone's champing at the bit to get browsers to implement shit that used to be handled by optional plugins and calling it more secure.
I can choose not to install a plugin, but I can't remove the analogous code in the browser - at best I can turn the feature off in the hidden settings page and hope it's actually disabled, never loaded into memory, and a bug can't be used to reenable/jump to the code and leverage it in an attack.
Anything that just runs current through a stick of metal to achieve the desired effect. Heaters, electric stoves, electric blankets, light bulbs, etc.
Light bulbs are easily broken, but the other three can take a beating and have enough metal in them to stand the test of time. The blanket has less, but it's insulated heavily to protect it from corrosion. For all of these devices, you can bypass any temperature controls, safety mechanisms, etc. and get the device to work by simply applying your voltage directly to the heating element.
Yeah! Learn to throw out studies you don't like and include the ones you do like to suit your agenda! And then champion the fact that the best study you can come up with is the one that says "Uh, I dunno."!
Shit traveling near the speed of light experiences much less time than shit at non-relativistic speeds.
I don't think relativity enters into this. In space, light travels at the speed of light. And to a photon, time means nothing.
Light travels at the speed of light, but time is relative. And you don't know that time means nothing to a photon. They could be sentient spacefarers for all you know.
If investors have been dumb enough to prop up the company for this long without seeing any sort of profit (and instead, big fat losses) why should I be worried about whether or not it can turn the tables? The worst that can happen is the service gradually winding down before the name is sold off to some other schlubs who will either:
A - repeat the mistake and run their own version of it at a loss B - change some shit and run their own, slightly worse (for users) version of it at a mild profit C - change a lot of shit and kill it in the same way Napster was killed D - sit on it and do nothing
In A and B, users win. In C and D, users lose until a new copycat (or 5) come along and get the same idiot investors to buy in and keep it running for free (to users) and at a loss (to investors) for years to come.
TFA says it was 11,000 light years away, so it took 11,000 years for the light to get to Earth. We should have seen it 300 years ago, but the explosion was a long time before that. So the summary's opening line of "A little over 300 years ago, a supernova... exploded" is incorrect.
To a relatively stationary you 11000 ly from the source, it was about 11000 years ago. To the light emanating from that explosion that reached us (unnoticed), it was 300 years ago. The the light emanating from that explosion that reached us via reflection, it was however long ago we detected those reflections. Time is relative. Shit traveling near the speed of light experiences much less time than shit at non-relativistic speeds. HEY! Maybe that's why it's called relativity!
White House Press Goons: "Ed joins a growing number of techies at the White House working to further President Obama’s vision to ensure policy decisions are informed by our best understanding of state-of-the-art technology and innovation, to quickly and efficiently deliver great services for the American people, and to broaden and deepen the American people’s engagement with their government."
Slashdot Mirror
If you're not eating raw, fair-trade, organic beans, you don't know what coffee is.
But corporations are people, so...
I don't think the state will actually kill anyone over the matter
LOL!
The state will kill for any reason or no reason.
As a buyer, eBay accounts are throwaway.
For things like Steam, where one chargeback could nuke / limit your whole account and the operators ignore all of your rights because "LOL VIDEOGAMES", create individual accounts for individual titles you're unsure about. Alternatively, don't buy from stores with shitty fucking policies.
If you're using a term like "Big Data", you don't belong in the fucking building.
Relational databases are perfectly suited to extremely large and complex datasets. You just have to intelligently design your database. You can't just throw noise into a pot and expect useful results. Hadoop (map reduce) tries to do exactly this. If you care about correctness, completeness, and synchronization of data, it's trash.
Tell that to the people who use it as a database and say it heralds the end of SQL and other relational databases.
SQL server is based around the idea of small amounts of changes with data retention being long.
Assume a system throwing off 3mbs of data which many companies can have if they are aggregating simple stuff like all customers on the websites and sequencing page by page access to look for correlations. There are 28,500 seconds in a workday (more if you have multiple locations). That's 85.5 petabytes of data per day. You need to aggregate this data fast. SQL Server's engine isn't designed for that.
Or for example SQL Server doesn't handle queries against unstructured information. Imagine that each record has a field of text and you want to do joins based on fuzzy matching between these text fields. Even with a few gigs of data SQL Server will die.
Check your math on that, please. 8*3600*3 = 84.375 GB, not 85.5 PB.
Further, 85.5 PB per day is no problem if you can manage to write all of that out to disk (1037 GB per second non stop lol). .5 EB per database, so it's not a problem. And if your tracking 3 MB per second per user, you're tracking bots, not users - it would actually be cheaper to just log all packets at that point.
SQL Server 2014 handles
As for making sense of the data, SQL can handle all of it if you design your database sanely. Even if you don't, you can slap a full-text index on it (including "natural language" style indexes). You pay a penalty for your poor design, sure, but everything works.
Something as simple as manufacturing data far eclipses this number every day. Think of every screw from every supplier in every product. Then tracking the reliability of this product through the entire lifecycle with self diagnostic tests. No, this is not for your toy made in china, but when it comes to real top end products that HAVE to work, then you need this kind of data to figure out what went wrong and fix it fast. That could save your company millions.
No, making your latest dot bomb app does not need this, but there are many places that do. Also check out financial apps like credit fraud, insurance, etc.
Every screw from every supplier in every product? No one dealing in volume tracks that because it's fucking pointless. People dealing with really-expensive shit that requires that tracking don't deal in volumes where it would be a problem.
But lets pretend we live in a fantasy world where that's true.
SUPPLIERS ...
ID - INT PrimaryKey, Identity
Name nvarchar(whatever)
PARTTYPES ...
ID - INT PrimaryKey, Identity
SupplierID INT ForeignKey (SUPPLIERS.ID)
Name nvarchar(whatever)
PARTS ...
ID - BIGINT PrimaryKey, Identity
PartTypeID INT ForeignKey (PARTTYPES.ID)
PARTTRACKING ...
ID - BIGINT PrimaryKey, Identity
PartsID BIGINT ForeignKey (PARTS.ID)
Add location/action/QC, result, timestamp, and employee id columns to the PARTTRACKING table and you get maybe 40 bytes per row total.
Pretend there are 100 tracking entries per part (LOL), 10,000 tracked parts per product (LOLOL), and 1,000,000 of these presidential spacecraft level products per day (LOOOOL).
You're only looking at 36 TB per day for PARTTRACKING, the most expensive (by far) table. Bump it up to 50 TB for all other shit in the DB.
Your claim was that one day of manufacturing tracking would far eclipse .5 PB. Not only is this not true, SQL Server 2014 has a limit of .5 EB, not .5 PB.
Further, .5 PB per day, even assuming non-stop operations, would be 6 GB per second of writing. And your claim is that that would be "far eclipsed".
Stop talking out of your ass.
Hadoop was created in 2005 and named after a toy elephant. It was an open source implementation of some shit Google wrote some papers on.
The "Apache Hadoop" branded package hit RTM in 2011. Apache only got involved because of all the retards mindlessly jumping onto it. Those retards jumped onto it because they were told it was based on Google's work.
As for datasets being too big for RDBMS engines to handle, WTF are you talking about? MS SQL can handle all the data you throw at it and has complete clustering capabilities. If your database is designed properly there's no problem. Oracle is the same.
https://msdn.microsoft.com/en-...
For SQL Server 2014, individual files are limited to a mere 16 TB, and you can have only 32,767 filegroups per database.
The maximum size of a single database is 524,272 TB, and you can have 32,767 databases per instance, and you can have 50 instances per server.
The number of rows per table is limited only by available storage. The max size of any in-page row is 8,060 bytes, with anything larger being moved off-row and the row maintaining a pointer.
Please tell me what sort of dataset exceeds the 800 YB maximum you get from SQL Server 2014.
Did I trip into a time warp and come out a decade in the past?
Who the fuck is actually talking about hadoop or map reduce in 2015? The same retards that were creaming their little cunts about it in 2005?
Even when you ignore the joke that is Java, hadoop is unwieldy, unreliable shit if you actually care about storing and retrieving correct, synchronized data.
If you're fine with throwing all of your data in a pot and getting some sort of result that looks mostly correct, then knock yourself out and use hadoop.
If your data needs to be correct, define it and its relationships then use SQL. You will have to pay someone decent money to do this correctly.
twenty automated levels before you can speak to a person , hit the wrong option oops have to redial and start again. Then you to valdiate with a person before they will transfer you through to the appeals dept. Where you have to validate again. After 25 attempts the appeals department wont tell you how you appeal .
All for an item the that never arrived because the courrier company delievered it to the wrong house number , wrong street , wrong postcode - but as it was signed for according to ebay it was successfully delivered.
Which is why you pay with a credit card and issue a chargeback at the first sign of bullshit.
everyone has a price, and if you have the dollars, you can use the dollars from your monopoly to poach anyone. This isn't an anti-collusion suit; this is a civil suit about monopoly abuses.
Globex Corporation couldn't buy Waylon Smithers.
You could try reading the fucking thing.
http://biblehub.com/john/8-1.h...
The teachers of the law and the Pharisees brought in a woman caught in adultery. They made her stand before the group and said to Jesus, "Teacher, this woman was caught in the act of adultery. In the Law Moses commanded us to stone such women. Now what do you say?"
They were using this question as a trap,in order to have a basis for accusing him. But Jesus bent down and started to write on the ground with his finger. When they kept on questioning him, he straightened up and said to them, "Let any one of you who is without sin be the first to throw a stone at her."
Again he stooped down and wrote on the ground. At this, those who heard began to go away one at a time, the older ones first, until only Jesus was left, with the woman still standing there. Jesus straightened up and asked her, "Woman, where are they? Has no one condemned you?"
"No one, sir," she said. "Then neither do I condemn you," Jesus declared. "Go now and leave your life of sin."
Kinda like the one that says divorced women should be killed, and stuff?
Not everything in the bible is a prescription of what should be. Much of it is accounts of the various ways people, governments, and society were horrible.
If you're having trouble distinguishing between what is a religious tenet and what is an account, you may want to try thinking, or you may want to give up.
Sure if you cherry pick your applications to suit your case then you could argue that. To me I see open source vulnerabilities which are called CVE-215-3456 which someone happens to have an alternate name for. I see programs called StarOffice, and Libre Office. I see MySQL, openLDAP, and systemd. All very descriptive of what they do.
Let's not over generalise.
What does "Star Office" do? How is it different from "Libre Office" or "Open Office"? Wait, "Open Office" IS "Star Office"? Oh, it's NOT? Then why does installing "Open Office" give me and "soffice" executable?!
What's "MySQL"? Is it mine? Whose is it? Is it a server? Can I only use it for personal use?
What's an "LDAP"? Do I want an open one or a closed one? I need it to be secure, so I probably don't want an open one.
Oh, you included systemd. Your entire post is a troll.
Given the report you show is from September last year and this bug was discovered in April this year, chances are that these are unrelated...
You don't know when the bug was first discovered or by whom it was first discovered.
Yet everyone's champing at the bit to get browsers to implement shit that used to be handled by optional plugins and calling it more secure.
I can choose not to install a plugin, but I can't remove the analogous code in the browser - at best I can turn the feature off in the hidden settings page and hope it's actually disabled, never loaded into memory, and a bug can't be used to reenable/jump to the code and leverage it in an attack.
Less is more.
Anything that just runs current through a stick of metal to achieve the desired effect.
Heaters, electric stoves, electric blankets, light bulbs, etc.
Light bulbs are easily broken, but the other three can take a beating and have enough metal in them to stand the test of time. The blanket has less, but it's insulated heavily to protect it from corrosion. For all of these devices, you can bypass any temperature controls, safety mechanisms, etc. and get the device to work by simply applying your voltage directly to the heating element.
No need to click - the "three leading possibilities" are exactly what you guessed:
- Ice
- Dry Ice
- Different rocks that have a different albedo
If you only guessed "ice" and "different rocks" you still get full credit.
As usual, The Simpsons did it.
http://watchonlinefree.tv/tv/t...
Skip to 19:30 (or watch the whole thing)
Don't suffer from single study syndrome.
Yeah! Learn to throw out studies you don't like and include the ones you do like to suit your agenda! And then champion the fact that the best study you can come up with is the one that says "Uh, I dunno."!
Shit traveling near the speed of light experiences much less time than shit at non-relativistic speeds.
I don't think relativity enters into this. In space, light travels at the speed of light. And to a photon, time means nothing.
Light travels at the speed of light, but time is relative.
And you don't know that time means nothing to a photon. They could be sentient spacefarers for all you know.
If investors have been dumb enough to prop up the company for this long without seeing any sort of profit (and instead, big fat losses) why should I be worried about whether or not it can turn the tables? The worst that can happen is the service gradually winding down before the name is sold off to some other schlubs who will either:
A - repeat the mistake and run their own version of it at a loss
B - change some shit and run their own, slightly worse (for users) version of it at a mild profit
C - change a lot of shit and kill it in the same way Napster was killed
D - sit on it and do nothing
In A and B, users win.
In C and D, users lose until a new copycat (or 5) come along and get the same idiot investors to buy in and keep it running for free (to users) and at a loss (to investors) for years to come.
TFA says it was 11,000 light years away, so it took 11,000 years for the light to get to Earth. We should have seen it 300 years ago, but the explosion was a long time before that. So the summary's opening line of "A little over 300 years ago, a supernova ... exploded" is incorrect.
To a relatively stationary you 11000 ly from the source, it was about 11000 years ago.
To the light emanating from that explosion that reached us (unnoticed), it was 300 years ago.
The the light emanating from that explosion that reached us via reflection, it was however long ago we detected those reflections.
Time is relative. Shit traveling near the speed of light experiences much less time than shit at non-relativistic speeds.
HEY! Maybe that's why it's called relativity!
White House Press Goons:
"Ed joins a growing number of techies at the White House working to further President Obama’s vision to ensure policy decisions are informed by our best understanding of state-of-the-art technology and innovation, to quickly and efficiently deliver great services for the American people, and to broaden and deepen the American people’s engagement with their government."
Dr. Evil:
"Riiiiiiiiight."