skysight-inc/HackerNews huggingface dataset:
I had the task of replicating data from DynamoDB to Redshift on AWS on two large projects on the last few years. The primary factor in using DynamoDB is that is's cheap and scales like nothing else in the galaxy.

Then the other shoe fell. The data was needed for reports. Reports require a static schema. NoSQL (and the developers who love it) despises static schema. "I can add properties whenever I want!"

This process of analyzing and reporting on production data becomes a very time-consuming, costly, and brittle exercise.

So then you have to determine, did we save enough money on the design side (using NoSQL over SQL) and then piss it away on reporting?

I'd argue AWS and other cloud providers need to create a SQL capable relational database as a service. This would (I hope) solve the problem.

But in the meantime, let's build our micro-services on relational databases so we can actually get aggregate data to stakeholders in real-time.
You can be barred entry for a DUI so I don't know what she was expecting. She could seek a waver which may or may not be granted.
Voting back Congress in is not an option i would choose.
You know what's even better than that?

Downloading the 1080p torrent off TPB.
I've always found it a little funny that SQL was originally designed for non-programmers, sort of like AppleScript. I used to think neither of those panned out, but in fact there really are a lot of smart not-programmers who can use it. At a company I work with many of the support staff have been learning SQL to help customers pull reports from our data warehousey reporting database. So maybe the article is onto something about the value of the language.

On the other hand, SQL-the-language isn't essential to relational databases. I have often wondered where C.J. Date has been the last few years. I actually love SQL, but it does have its limitations. I wouldn't mind a solid relational database with an alternative query language. It's such a missed opportunity for a great VC pitch: Tutorial D, NoSQL before it was cool. :-)
My personal belief on this is that there is no upside for the Cubans to be involved in this. I believe there was something but I would look at the Russians or the North Koreans for this. They benefit from allowing the Trump administration to have an outlet for theirs need to dismantle our Cuban engagement.

You want democracy in Cuba, given them Starbucks and Amazon. Our policy has been a complete failure.
This doesn't really have anything to do with *nix, but rather the customer being an idiot.
> I'd argue AWS and other cloud providers need to create a SQL capable relational database as a service. This would (I hope) solve the problem.

Isn’t that Aurora?
Careful. If the security answers are verified by a human, they may accept "oh, I think I just put in a bunch of random characters" as an answer.
Should I take this to mean that cryptocurrencies are all scams that demand SEC intervention, or that cryptocurrencies are legitimate and here to stay?
Debunking in a world of tribes
Speaking of maths, I'd like to see a cheaper TI-83.

Obligatory XKCD: https://xkcd.com/768/
> I'd argue AWS and other cloud providers need to create a SQL capable relational database as a service.

Like Google's Cloud SQL? https://cloud.google.com/sql/
You mean UPA's Nirmal Bharat campaign which Modiji rebranded as Swach Bharat?
It should be Buyer Beware, with only those convicted of engaging in fraud facing legal restrictions. No one is forced to invest their cryptocurrency into these token sales. A blanket ban on an entire category of digital information/value exchange, which effectively punishes millions of people in the name of preempting scams, is busy bodies sticking their nose where it doesn't belong, to control the actions of their fellow citizens to an extent that they have no right to.

Emulating the Chinese government, which rules a country with a much less developed tradition of civil liberties than the West, would be a giant move backwards.
For me the author nailed it when he brought up the PostgreSQL JSON datatype. I just couldn't ever get into MongoDB, but recognized the value of JSON structure data. Perfect balance for me.
Also, SQL was designed back when most programming was done in assembler or C. Compared to assembler, SQL is easy. Programming itself has gotten a lot easier since.
Do you have a white paper?
SSD's.
Another example of one large customer murdering a small business, basically.
I am not saying that China is good. I am saying that both US and China are bad and that choosing between them is like choosing between plague and cholera.

> but they have a decades long history of protecting and supporting bad actors

- Saudi Arabia

- Talebans

- Pakistan

- Pinochet

- Putin

To name a few "nice" people who received a lot of support from the US.

> Whatever the failure of the USA, North Korea would not be a new breakout nuclear power threatening to become the most likely scenario for nuclear war without major backing and even encouragement from China.

The turning point for NK was in the 2000s. US had invaded Iraq on the obviously false pretense it had WMD. It had not. Had it, it may have repelled an invasion by using them. NK's stance on nuclear deterrence is a direct (and actually rational) reaction to GWB's foreign relations approach. Dubya's administration's lack of diplomacy skills caused that mess.

And yes, decades of lack of US plans in a place where it still has a lot of soldiers led to this situation and led to China (and a bit Russia) having the higher hand just because they kept their diplomatic channels open instead of speaking loudly and doing nothing. USA has bases in Japan and South Korea, of course China wants to keep a buffer.

Imagine if China had huge naval bases in Mexico, Cuba and Canada. You would be happy to give it an enemy to focus on rather than on yourself. De-escalation could have happened in the 2000s but I fear we now are past that point.

Now after 8 years of GWB and God knows how many more of Trump Japan is slowly coming to the idea that going full militaristic is not a bad idea and that they can't rely on US for managing the area. And they are right: China is becoming the dominant power in Asia and USA apparently decided to let it do.

> China also has multiple ongoing, top-down, programmed genocides happening in several territories, including cultural and institutional colonization of Hong Kong and Taiwan.

Calling that genocide is really disingenuous. This is just cultural influence by a behemoth. Calling it a genocide is as ridiculous as calling the US influence over EU culture a genocide.

If you want something closer to human rights violations by China, better look into what is happening in Tibet. You'll get things that look a lot dire, a bit like what US' allies are doing in Yemen or in Palestine (where, btw, there does not seem to be a plan other than a progressive ethnic cleansing).

Both are evil and supporting evil actors. None is interested in deescalation and solving the human rights violations in the world. Fuck both of these countries. And if I ever have to choose between the racist and imperialist ideology that the American spirit has become and the cold-hearted efficiency seeking technocracy of China, I'll just toss a coin. I would feel like Finland during WWII, stuck between the 3rd Reich and USSR. Both are bad, both are evil. The world would be better off without them.
Right, but a huge amount of the population is concentrated in those areas,
Yes, and all the new poverty alleviation schemes are just rebranding of Garibi Hatao of 1970s, right?
There is no basis to assume that cultures are similar in their power distance. More traditional cultures generally have more power distance.

Whose propaganda is the higher acceptance of authority of Americans compared to many European countries?

PDI (Power distance index):

81 MEXICO
80 CHINA
68 HONG KONG
58 TAIWAN
54 JAPAN
40 UNITED STATES
31 SWEDEN
18 DENMARK

http://www.clearlycultural.com/geert-hofstede-cultural-dimen...
What percentage of internet scammers and financial criminals are within the SEC's jurisdiction (the USA)?
Yes

MasterCard (then known as Master Charge): http://i.imgur.com/BzZONEG.jpg

Visa (then known as Bank Americard): http://creditcardforum.com/blog/wp-content/uploads/2010/10/b...

AMEX: https://i.pinimg.com/236x/15/6c/5d/156c5d0e135a6f2014a95608e...

Fun fact, American Express still to this day uses the name Charles F Frost (usually written C F Frost) for all their credit card ads. He was an advertising executive in the 60s.
Many households already have electricity :)
Unless any of you have done work that is not proportional to the others (for more, or for less) I believe that everybody should get the same amount of equity.

The leaving problem is easily fixed by adding a vesting period where no one would be actual owners of their part before N months/years.

Payment should be also equal. Otherwise, at some point resentment is going to build and things might get weird and start to fall off (I speak from experience). If one person adds more money at the start of the company they should be repaid (reimbursed) as soon as there is company money. Unless, once again, it is a disproportional amount of money. If that's the case some other arrangement (maybe more equity?) should be made.

Leave the unequal payment thing for when (and if) things go really well and the company actually has profits to distribute. At the beginning, everybody gets paid the same as salary and it's also all or nothing. Unless all involved get paid, no one gets paid.

When it comes to deciding who calls the shots I believe it doesn't really matter unless there is someone who clearly is a better fit for it. Also, being the CEO or giving directions to others doesn't mean someone is more important than the others. It just means that it is a different role.

My last bit of advice is about all the other things you guys didn't think about. Especially when it comes to things that can go bad. I would leverage the fact that this is the beginning and everybody is committed and excited and use this time to think about what to do when bad times come (they will). You should never get into a contract without knowing how to leave it. Find a shareholder agreement and use it as a base to come up with your own rules and agreements.
Neuroscientists restore patient’s consciousness with vagus nerve stimulation
I love my KINDLE
our experience was about 5-6k users when hitting the front page. it really depends on how many people upvote your posts. good luck!
Uh oh, here comes Quantum Basic.
Agreed, tis quite nice.
The giant space crystal was just hungry.
Because other services already rooted in other areas. Japan got Line, South Korea got Kabaotalk.
Australia to create its own space agency for economic boost
Thank you so much for spreading FUD around my article without actually addressing any element of it, you are just what the Catalans need right now. Did you have anything to say about its content, or did you find it well sourced and accurate?
Interesting study, could have been more clear about its meaning and methods, but I have one quibble...

>"In particular, we compare how users usually consuming proven (scientific) and unsubstantiated (conspiracy-like) information on Facebook US interact with specific debunking posts"

Science does not prove anything! Scientific results are not proof!
> In this talk we'll draw a direct connection between this ubiquitous insecurity and basic computer science concepts of Turing completeness and theory of languages. We will show how well-meant protocol designs are doomed to their implementations becoming clusters of 0day, and will show where to look for these 0day. We will also discuss simple principles of how to avoid designing such protocols.

Sounds like you want the next-gen version of what https://en.wikipedia.org/wiki/Project_Xanadu was supposed to be. Unfortunately while you were discussing the above with like-minded peers other people were shipping things that users (not designers, users) want. The latter always trumps the former.

I agree with you philosophically - how could you not - but how do you have your cake and eat it, too, in this regard? Xanadu was impossible enough, and expecting to have all its trappings with the best parts of TimBL seems like the recipe for a classic Borges tragicomic short story.
Way back when I took my first database class by Mike Stonebraker, he talked of some of the old war stories between RDBMS and network-based database, which was hot before RDBMS. He said the relational model by Date and Codd had won out back then, for the simple fact that relational data stood by themselves while the network-based data were tightly coupled with the applications. When NoSQL came around, yep, it looked like the old network-based database again. History has repeated itself.

Relational model, where SQL is merely the querying language, will win again and again, for the simple fact that it enables data to stand by themselves, and data tend to outlive applications, both in longevity and in scope.

Edit: PostgreSQL came from Postgres, the research project started by Stonebraker and others in UCB.
Also, the unstructured data is another thing. For example, lets say you need to store a bunch of contracts (as in your industry) in PDF/TIFF or whatever. The filesystem isn't a really good place to store it because you have a loose coupling between the index in the table and the file on the filesystem. That can get messy and unless security is tight, some developer or admin could muck something up on the filesystem. This is particularly dangerous when you need to keep contracts over a period of time (say 7 years). If you have a really large amount of files, you'll either need a huge array, or figure out a way to distribute them across several NAS's or whatever, then that gets complicated.

The RDBMS is a little better at storing this type of data, but it has it's own problems. Backups quickly become huge and a massive undertaking. Development databases now have a bunch of missing data (because who wants to replicate that down to lower levels), you still have the same problem when you have a large amount of data that you need to shard across NAS/arrays, etc.

The NoSQL seems like a third option that may well be worth looking into. Again this is for unstructured data that you just need to reference and not necessarily query against. (like stored contracts).
I like how it pretty much just glosses over decades of familiarity. If there is anything the last 20 years prove, it is that the majority of developers will stick with what they know over what might be a good fit for the job. It goes even deeper in the SQL world down to the specific database flavor.

From the ops side I actually find RDBMS more difficult to deal with cause the power of relationships is easy to abuse and they are not anti-fragile. Instead of smartly reasoning about the data, it is all to easy to just "JOIN ALL THE THINGS WITH MEGA TEMP TABLES!". I've taken more database outages from bad queries then anything else.

There are bad implementations on both sides. There are reasons to pick both sides over the other given a set a circumstances. At the end of the day, the technical facts don't matter to most people's decision making though.
Thats the typical Spanish response. We own you and you cannot declare independence unless we say so, typical Spanish arrogance towards their colonies, we saw it in the Philippines too just before you got thrown out my the Americans.

No necesitan permiso de Madrid.
Check out datalog. Datomic seems promising. It's from Rick Hickey (the guy behind clojure).
Come on, check out Nature Index and see CAS. Or you can see the FAST telescope project located in China. Why you are so pride about the west. Every civilization has their ups and downs. In Song dynasty, what the West was doing?
If Data Is the New Oil, Are Tech Companies Robbing Us Blind?
You are not Catalan or a resident of the region clearly, which means you don't get to vote. The Spanish do not have a say in Catalan independence and all you have left is violence.

Watch the Guardia Civil show the world how fascist the Spaniards are and remind us of who won the civil war.
1, Chrome complains the newtimes link illegal.
2, Don't say what you don't know. The copy machine stating is the old fashion. Didn't you know china and typography thousands years ago? fine. there is a little thing. at jroller/qinxianscript, there is a antialias tec, no none knows the better one, even Nvidia and AMD. sigh, looking at your mouth pronounce trends, maybe you wanna say China maybe copy the benefit from the little place GBE colonization. Did you know the civil servants system of English copied from where? So from a man view, there should be developing and applying, should not be evil. Din't you know you live in a les miserables?
This is what I personally can't stand about internet posters. Posting forcefully about things they have done no research on.

The borough of the Bronx compared to a number of cities
Using total crime as that's what was used.

Chances of being a victim of property/violent crime
Bronx 1 in 95, 1 in 54
Cleveland 1 in 63, 1 in 16
Denver 1 in 148, 1 in 28
San Francisco 1 in 127, 1 in 16

25% more likely to be a affected by violent crime than in San Francisco. And Less likely to be affected by property crime.

No one is saying all areas of the Bronx are utopias (definitely not), but from what I've experienced, people posting comments like the above are either made to disparage, or often are just blindly repeating what someone has read with zero knowledge of facts.

> With a crime rate of 70 per one thousand residents, San Francisco has one of the highest crime rates in America compared to all communities of all sizes - from the smallest towns to the very largest cities. One's chance of becoming a victim of either violent or property crime here is one in 14.

https://www.neighborhoodscout.com/ny/bronx/crime
https://www.neighborhoodscout.com/mo/st-louis/crime
https://www.neighborhoodscout.com/oh/cleveland/crime
https://www.neighborhoodscout.com/co/denver/crime
https://www.neighborhoodscout.com/ca/san-francisco/crime
(Disclaimer: I work at Databricks.)

I really believe that Spark's "more-than-SQL" query interface is how things should be. SQL is of course the gold standard and probably represents north of 90% of analytic workloads, but there a lot of queries that (especially for us programmers) are much easier to express procedurally/functionally, rather than purely declaratively.
The Cure for Obesity Is Processed Food: When the Poison Is the Antidote (Part 1)
Very nice of you to spread disinformation around my posts Oletros, but you are terrible at it. Any fool can see that rather than address my article you prefer to spread FUD.

Did you disagree with any of my well sourced analysis in particular or are you just barking como el perro que eres?
That, and they like to believe they need to scale like Facebook.
You said:

> Once people get married and have kids, men take on additional work to pay for their kids.

You now claim:

> I also did not say that MEN do more paid work.

???
I told you to shut up because you bring nothing to the conversation except your badly written objections which clearly have no relation to my article except in your head.

If you have any insights that relate to my article, its actual content, or why the Spanish are not fascists, I would love to hear them. Please tell us why my article is wrong.
Filter it through logstash (or something) and then structure it :D Literally just "collect everything", store in ES, model what you need later.

It's a bit weird, but logstash & elasticsearch (and relating/extracting data when and where I need it into postgres) have made my life so much easier
Otherwise, como te dijo antes, callate.
> it is that the majority of developers will stick with what they know over what might be a good fit for the job

Anecdotally, I have seen this shift quite a bit in the last decade. There has been a big move toward "try whatever is new and shiny" and I think a lot of that drove the NoSQL craze.

And don't get me wrong, there are some great NoSQL options if you select the right tool for the right job.

But a lot of people who gravitated to NoSQL did so because they designed poor queries in RDBMS. Guilty myself. Often the quick reaction was "wow, this is faster" instead of "well of course it's faster, I'm not getting X, Y and Z features of a relational database. Do I need those? Did I abuse the RDBMS?" etc.
That's not true, more and more students are coming back to China after they finish their education in the West. Not imaginable 20 years ago. Some PhDs are tapping the 1000plan.
I don't buy it. The makers of the software that this appears to be a carefully written advertisement for, came to the same conclusion as the rest of the IT world (that some of us saw a mile away): NoSQL was, and still is, only good for very specific things in very specific cases; it's generally dreadful for anything that SQL engines could already do well.

The subtitle for this contains: "After years of being left for dead" and the author throws phrases around like: "And boy did the software developer community eat up NoSQL, embracing it arguably much more broadly than the original Google/Amazon authors intended."

Who? Where's the data? This blog post has a lot of links, references, and studies, but where's the data to back up the premise?

A quick search on Google Trends comparing SQL databases to NoSQL as an entire term, or any of the popular flavors of NoSQL, reveals that it is not even a blip in comparison.

But don't take my word for it, the author and their company had the "DUH" moment too (emphasis mine):

> ...we soon realized that we’d have to do a lot more work: e.g., deciding syntax, building various connectors, educating users, etc. We also found ourselves constantly looking up the proper syntax to queries that we could already express in SQL, for a query language we had written ourselves! One day we realized that building our own query language made no sense. That the key was to embrace SQL.

You might have had hubris stemming from discarding or not knowing all of the history that you decided to share with us in this blog post. A great deal of the NoSQL community was completely unpalatable for this reason. The folks who had been doing data for decades, and built stable and powerful systems on top of many prior decades of mistakes, built them for a reason.

And here we see the author trying to proclaim that suddenly SQL is back?

SQL never went anywhere. NoSQL is a neat tool that was developed and continues to be developed and probably isn't going anywhere. But the idea that NoSQL suddenly overtook SQL, and now SQL is seeing some huge resurgence, feels like it comes from the perspective of someone who only saw a window into the last 6-8 years of development.

The king is dead. Long live the king.
Algebraic Geometry [pdf]
It sounds like Germany is just catching up with the rest of Europe.
If SSDs solve your scaling problem, you never had a scaling problem
I definitely see where you're coming from, but I think the danger there is not necessarily anything to do with the coupling of assessment and learning but the coupling of assessment with the learned, i.e those who possess a skill/piece of knowledge/trait should be the ones who define the assessments around it. I like that you bring up guilds because that's very much baked into their process I think.
To add onto this, you could theoretically call SQL a logic programming language and we've had good success teaching some of our non-programmers a different logic programming language (sort of like datalog) to do some work in.

Could be something there with logic programming. Or could not be something there.
> So the long and short of it is SQL would be a good common language for relational and NoSQL style databases.

Yes, I'm sure the inevitable "SQL for NoSQL Databases" book will be a good read :)