skysight-inc/HackerNews huggingface dataset:
This fear of exploding pressure cookers seems to be a uniquely American phenomenon. Pressure cookers are used by pretty much every middle class Indian household and I have never heard of an explosion. They all come fitted with a 'safety valve' that pops to let out the pressure before it can reach a dangerous point.

It also reminds me if this: https://en.m.wikipedia.org/wiki/Fan_death
Never, but the extent to which it shapes a person's identity is probably more ample then it ever was.
Net Neutrality Repeal Will Be Felt by America's Schools
I really miss his infectious laugh. He saw humor in everything.
Migrations are orthogonal to ORMs.
Building ML/DL application with Image processing/ Object Recognition with OpenCV, Tensorflow,CNN
Object-relational mapping is in many cases an excessively leaky abstraction. I try keep away from it.

A DSL for writing SQL in a nice, composable way is a useful thing.

Some libraries, like SQLAlchemy, provide both levels, not insisting on using the object mapper.
Old marijuana crime convictions in California might go away thanks to legal pot
It is, which is my point. Why would you brag about being less diverse? The OP responded and said he made a mistake and got the order wrong.
Traditionally in Germany the catholics--like in Bavaria--are more relaxed and fun-loving. The real straight-lacers are the protestants and Prussians.
This doesn't surprise me at all. Based on my observations, I would say that at least the bottom 80% lives solely on income from labor, and accumulates no wealth. Of the upper 20%, some live below their means, some earn slightly more from their labor than necessary to live, and others make enough to accumulate capital. Once you begin to accumulate capital, you earn money from the capital itself. Some accumulate enough capital to earn enough income to quit earning income from labor entirely. Some use the excess capital income to accumulate even more capital. Capital is then passed down to heirs. So the accumulated capital is about equal to new capital generated.
LINQ isn't a ORM. I assume you mean Entity Framework?

EF definitely has the foreign key issue. We have around a thousand tables, we tried to generate the classes for all of them including foreign keys, problem is that when you create a context that references even only a single table, it will load everything that is foreign keyed including siblings of siblings of siblings, until you run out of memory.

Only way around it is to not set up foreign keys which massively diminishes the value of using EF, so we wound up creating two copies of each table's classes, one with and one without foreign keys. That causes its own issues.
Hammers are fine. I went to German Kindergarten and still have all my appendages.
You're right and we're on the same page about the solution. The reasoning behind my comment of "interesting" is that formula you gave is not well-defined for p=infinity, although we can define it as the limit of that expression as p-->infinity. Furthermore, for p < infinity the lp-norm can assign a well-defined penalty to each x, and the goal is to minimize the sum of the penalties. But that's not really true for p=infinity.
Um, to seal the pot that's in the fridge?
Has the decline of violence reversed since 2011? [pdf]
Those of you who have seen me post over the years know that I am passionate about this topic. I wind up linking to my own project to provide more info but let me know if that's bad form on HN.

In 2011 I started a company to decentralize facebook. I thought there was no reason that signals needed to go through server farms in California just to organize a local dinner, have a local marketplace, classes, dating, or a host of other things. I wanted to build a platform like Wordpress that communities could host and then install social apps the same way they install wordpress plugins.

The developer model would be pretty cool, too: no gatekeepers to kick you out of the app store or revoke your API keys while they compete with you. Instead, you sell your apps to entire communities. Over time we built apps like:

Group rides (uber for friends)
Group activities
Group chat
Collaborative docs
Marketplace
Pitching in for a gift

As time went on, I realized that eventually communities will have their own mesh networks and we would have built the social software they would need to run on them! Right now, they don't really have software uilt to run on the local networks, they still need to connect to centralized services on the global internet.

We asked some guys to build router firmware for us, so that we can have local software run on the wifi networks of cruise ships, classrooms etc. It is great for taking attendance for example, as phones automatically connect to the wifi and the cookie does the attendance bit.

You can literally have a superfast social network for a university or company or whatever, and signals go over the internet only when they have to.

If you want more in depth info I give a talk about it here: https://youtu.be/WzMm7-j7yIY

And we blogged about the details here: https://qbix.com/blog/index.php/2017/08/centralization-and-o...

Now we went one step further and made a spinoff company, Intercoin Inc to allow communities to issue and democratically manage their own local currency! (https://intercoin.org)

IPFS and SAFE a great fit for an even further future where no elites control anything. But that's a little further on.

Here is what I would like to see eventually replace the Web: https://github.com/Qbix/architecture/wiki/Internet-2.0
Religion? Or just 1/3 of a pull up?

(I fully expect to be crucified for this)
> Will coinbase honor the price when order is placed ie if it shows $19700 then will it let me buy 0.1 BTC at this price?

No, neither the price at which they actually allow you to buy or sell BTC matches the price they display. They set the price for you, which is different in both operations (and on top they charge a fee).
GDAX on the other hand (same company as coinbase, different service) is an actual market where you can place orders at whatever price you want, and somebody will take them if your price matches theirs.
You keep hyping up this alt coin. How many do you own?
It depends on what you're after.

I'm very comfortable in SQL, and would prefer to write my queries. But our team has grown, and we've found that developers say they know SQL, but they really don't. In general, I've found that it's not the syntax that messes people up. There's a significant mental "jump" between the usual procedural coding paradigm and the "set based" paradigm offered by SQL. Some people just never catch on.

So we're going to start using an ORM (Entity Framework Core 2) so that the "mere mortal" developers can pitch in. I know there's a way to run raw SQL, so I know that when we find spots where the ORM fails, we can just rewrite it with some good SQL if we decide that's best.

But maybe that'll never happen? We've been trying to do simpler SQL stuff as of late so that the heavier lifting in the system is done by the application/client instead of the database (bottleneck). As the database sees simpler, less unique queries, more stay in the plan cache, indexes are more reliably hit as expected, and performance increases.
I've found ORMs (such as Entity Framework) great for operations that can be described as "find a single thing by PK and update it." For read operations I've favored this strategy: "Imagine the ideal result set for the task at hand. Use SQL to deliver that result set. Do the rest of the work in your app language of choice."

Edit: I guess I should clarify that I would favor using any library that maps result sets to lists of objects. And I would consider that to be part of "do the rest of the work in your app language of choice."
Not who, but what. Fate and/or hard and smart work determine who gets the wealth. Don't worry about it and get busy and be persistent. Right?
That is incredibly American centric. There is plenty of diversity in the way things work in the world. It will only take one country to use self driving cars as an economic advantage (by optimizing infrastructure investments) for the other countries to follow to keep up their competitiveness.
Why did you hold on to the keepsake?
AlphaZero's chess strategies turned out to be quite different from how humans have traditionally come up with chess heuristics/strategies. I wonder what paradigms will be used by AI that does computer programming. Will it organize code into some bits of functional programming, some OOO? Will it structure things into MVC? My guess it whatever AI does will be completely inscrutable to us. It may be optimized for efficiency rather than understandability, which humans need for maintainability.
The article states "The singular “price” of Bitcoin doesn’t exist — it’s a made-up number."

This is the same for every stock traded on any stock exchange in the world. The "singular price" is, in most cases, just the mean of the closest bid and offer listed on the exchange and is thus a "made-up number"

On top of this, it obviously doesn't take into account everything from transaction costs to the fact that attempts to purchase substantial volume at this price would not be possible.
It has the same incurable disease other websites have of being cool in the very beginning then degrading to useless junk once it became more well-known. At this point it's worthless for true product showcases.
If it is useful, then it does not need to have an inflating price. That people think the only reason why a cryptocurrency would ever be popular is if the price rises is a huge problem with the community.
I do agree every one who needs to get data from an SQL database should know SQL, and mostly, should know about indexes and how and why queries can be slow.

But a query builder is extremely useful and in any complex application, if you don't use one, you end up bulding one yourself, which may not be a very good idea if you don't understand things like query injection.

So learn SQL, learn ORM, and choose in a case by case basis.
imo this is basic supply and demand.

Bitcoin comes into this world at a fixed supply rate. Demand is currently exceeding supply, so the price goes up. With bitcoin so far, the higher the price, the more press is generated, which increases demand, so we have a feedback loop.

The only difference is, demand can change very quickly, causing drastic swings in price. Which then generates press, which generates demand.

Most every crypto currency will follow the same model. As long as enough demand outpaces supply, the price will rise.
Keeping logic in the database like that means you can’t version those procedures alongside the rest of your code. That’s a pretty big downside.
I think that this article[1] (written by the researchers themselves) gives a better overview of the paper and context.

The important context is that there's legislation being discussed at the moment that would criminalise re-identification of published government data[2]. This link provides the important context that this legislation would only achieve a silencing of researchers, rather than actual protections.

[1] https://pursuit.unimelb.edu.au/articles/the-simple-process-o...

[2] https://www.attorneygeneral.gov.au/Mediareleases/Pages/2016/...
SQLalchemy is kind of a pain in the ass to actually use, though. The DSL doesn't feel very Pythonic, it's weird and confusing. The way it traverses the Object graph when loading associations between models is magical and opaque and I could never predict when it was going to automatically work and when it wouldn't.

I actually would rather be writing Ruby on Rails, because it's _less magic_ than SQLalchemy.
He was trying to legitimize info wars
Any word yet on whether this was a cyber attack?
How does the ORM detract from sqlalchemy? I’ve been very happy with it for years, and I’m not clear on where an advantage is explicitly not using mappers.
I would stop for the dog...
> You'll most likely end up implementing an ORM anyway,

This is a really good point. Many people start with the "no ORM" philosophy, realize their application needs some way to map the SQL to the code, time passes..., they have implemented their own half-baked ORM.
"So when Japan said they would accept Bitcoin for payment of taxes ... ?"

I'm not able to find any reference to such a move, which I would think would be widely reported in English. So I suspect you may have your facts wrong. I read that Japan no longer collects sales tax on digital currency transactions, but that is not at all the same.

If, hypothetically, a major government accepted all tax payments and equivalents in XBT as well as their own currency, and credibly promised to keep doing so no matter what, they wouldn't so much be backing Bitcoin as "unbacking" their own currency. It would leave their citizens free to stop using fiat currency if they wanted, and if enough were eager to do that the value could go to zero. (In principle, that could be fine. In practice, contracts and other nominal rigidities would probably make the transition period... problematic)

If a major government decided to accept tax payments only in Bitcoin, they would be backing it in the sense intended.

(I'm not necessarily taking a bearish position on Bitcoin. Rather, I'm arguing that fiat currencies are not the right model for understanding its economics)
This is more of an argument against pollution and cars, and for teaching kids how to properly report any attempts at molestation; than against free-ranging?
1. the stock market, other than the IPO is a secondary market. You are not providing capital to the company but just paying another trader for his shares.

2. The majority of stocks do not provide (and will never) dividends and the majority of buyers have no voting rights.

but you are right. For practical purposes, the stock market is not pure gambling. There are institutions that make it legitimate. Such as the SEC, pensions, 401ks and brokerage firms. And the fact the government cares so much about it going up (because it funds so many pensions and social security might go away)

But lets not fool ourselves in thinking the stock market is a virtuous piece of infrastructure. The vast majority of stock holders dont know anything about the conpanies they invest nor how stocks even work. They invest blindly in it through mutual funds or 401ks.
Is that different for 20 year olds?
Any price is just the amount someone is willing to pay. This is why prices change even for things that do have intrinsic value like food commodities, oil, etc.

More specifically, price is a function of supply and demand. Bitcoin was created with a very specific bootstrapping plan baked into the design.

What people are missing is that the bootstrapping plan is well known and obvious to investors, and is meant to incentivize a speculative motivation for mining, which it has done successfully.

But think about it this way, the price of a currency is only loosely linked to supply and demand. Nobody really knows how many dollars exist, yet the currency has characteristics that make it trustworthy.

Bitcoin is the same phenomenon. The price is based on the success of the governance model and the appealing characteristics of the ecosystem.

Based on these appealing characteristics, there is the widespread expectation that Bitcoin will win market share from other currencies over the long term.

We know there will be a finite number of Bitcoin mined, what we don't know is how much market share Bitcoin will have in comparison to other currencies.

Market share is not a function of money supply as much as it is a function of the holders of the currency that rely on the currency because of its governance mechanism, fungibility, etc. Many countries hold USD in reserve because they find the governance characteristics of the USD appealing. Bitcoin is just a novel way of doing currency governance.

For all uses of currency other than holding inventory, the governance mechanism matters very little, since there is little risk exposure to price fluctuations or the risks associated with bad governance.

Critiques of Bitcoin get mired in an imprecise understanding of all of the above, but the most notable blind spot is that Bitcoin is a governance mechanism first and a currency second, and investors are pleased because the governance mechanism has been tested a few times and has (thus far) performed admirably.
True, kinda. I love SQLalchemy and it does feel different to use than every other python package I've used, but I'm not sure if I could do it better.

It's pure magic.
I mentioned it twice because it was relevant to the discussion. Vast majority of my posts have nothing to do with Monero.

I prefer not to disclose my personal finances. If you think I'm hyping alt coins on HN for personal gain well then I guess there's nothing I'm willing to do to disprove that hypothesis.
No. Migrations can be auto generated from Model changes.
I can see that hanging out in the forest and building fires etc, would definitely attract me (as a guy) more towards childcare than having to be bored indoors all year.
I’m guessing car manufacturers have caught onto this. I drove a year 2000 car whose speakers would know I was about to receive a text/call several seconds before receiving it. I don’t think I’ve been in a model later than 2008 that’s had this problem. The noise, like the AOL dialup modem beeps, are one of those things that become cemented in your brain and immediately recall themselves as soon as you think about them. I heard the short succession of beep patterns in my head as I read your comment.
I guess my experience is limited, but I’ve not seen much of this despite working in an ORM environment with around 75 entities for the last few years (my recent experience anyway, the rest goes back 16 years). Maybe that is small potatoes, I don’t know, but I’ve found that anyone who understands JPA well enough can work to avoid any pitfalls of using ORM. It seems to me that having a good mix of understanding SQL and ORM is a good thing; and especially understanding exactly what the ORM system is doing for you and how it is doing it. Dropping ORM altogether sounds like a bad idea since it provides a number of built-in security features as well as an abstract modeling paradigm that is fairly easy to conceive and maintain; provided, of course, that you learn to say “No” to protect the integrity of the model (such as rejecting the attribute creep the article warns about).

I have found, in my experience, that people who tend to want to write SQL over ORM usually want to do so because they simply know SQL better. That’s okay, there is nothing wrong with that. But that doesn’t immediately mean ORM systems are bad. No need to be tribal about it.

The problem I see is that many new software developers these days sometimes can’t see the forest for the trees because they dwell too much on what they think is better instead of simply seeing the software and abstractions as nothing more than tools in the tool belt. It happens everywhere — PC vs Mac, iOS vs Android, Scala vs Java, SQL vs ORM. It’s fine to have opinions, I have many, but as I’ve aged I’ve become acutely aware that my biases are almost solely rooted in the limitations of my understanding.
We should not use biometrics to unlock anyway. I keep waiting for apple to combine biometrics with passcode, but they don't and seem unwilling do offer that as an option... why is that?

To be clear: face ID should authenticate you are the valid user, then prompt you for your passcode. Wrong face? No passcode challenge.
This is one of those things that you don't really need, but may REALLY need at some point in the future.

Also who names emojis, are they author named!?

Also, Also. Github could use some optimization, forking this froze my browser. Rendering the page took like 20 seconds.
Dex the world (kill the web)
Wait, it ran out of memory because it couldn't hold the class structure?
Ask HN: How does your engineering team manage knowledge?
I've been thinking recently about how my team manages knowledge. The 5 of us keep engineering notebooks committed in git, but we also try to maintain a wiki. There's also a ton of information lost in git commits, jira comments, javadocs, readmes, etc.

Our main method of sharing information has become Q&A in slack. I encourage communication, but a lot of questions are purely from information loss during development.

some generic examples:
"I ran project X with <query> and received error Y. Has anyone seen this error before?"
"Where is system Z deployed?"
"The search algorithm for system Z should return I, but
I think it should return K. Where can i find background on the algorithm's development?"

I've considered something like a private stack overflow, but I don't think we'd gain anything without some sort of smart plugin for our notebooks and code.

Are other teams experiencing this? We have a PM for external information sharing, and I'm the tech/team lead. I feel like if we could optimize some of this information sharing, the team would work more efficiently.

* How are you guys documenting what you learn in development?
* Who is responsible for documenting?
* How do you keep track of it, manage it, and search it efficiently?
How the oldest Senate ever is taking a toll on the business of Washington
`create proc if not exists get_customer_v1243(params)`

.. I've seen this.
This may be off topic, but could this be used for classifying the trustworthiness or Amazon/App Store/etc reviews? Or does anyone perhaps know about an open source project that can be used to achieve this by someone who doesn't know anything about machine learning?
In the East it wasn't about affordability in price, but about rationing. You had to wait 18 years for a new car at the end.
I wish there was a commonly agreed upon name for "query builder" that isn't "ORM". Actually mapping relational data to objects often rubs people the wrong way, for good reasons, but the query-building layer underneath is pretty universally useful.

But in general I agree with you: Why just learn SQL? Learn all the layers!
This doesn't look especially safe. In addition to the fact that the crypto is delivered by the server, and so every browser/server transaction is an opportunity for the server to surreptitiously backdoor the crypto operations, the underlying crypto here appears to be CBC+HMAC where the payloads are decrypted before the HMAC is checked.
I mean you could, but it’d need to be through some kind of migration system to update it.
Sure you can, just store them in .sql files and have your CI system auto deploy them.
FYI OP claims $400mm USD was withdrawn to make a counterpoint about liquidity, but did not specify the exchange. Not sure why this would generate an argument? In addition, how can anyone infer that a sell indicates liquidity? A sell on an exchange only indicates one asset was exchanged for another.

FWIW I saw several large buys on the GDAX history today at the $18.4k price point. One was for 36 bitcoins, and I've never seen a purchase over 5. I shortly after saw another for 18.
Yeah EF is great for CRUD. The way I distinguish whether EF is going to be used or not is simply whether the workload is OLTP or OLAP. At OLTP EF excels. It's terrible at OLAP (ORMs generally are) so I'll drop to raw ADO.NET and (if lots of data has to go in to SQL Server) table valued parameters.

Use the right tool for the job.
> I don't hear people complaining about say LINQ.

LINQ isn’t ORM; ADO.NET and, on top of that, Entity Framework are the (core) ORMs that work with LINQ.

ADO.NET and EF get plenty of complaints.
Submitter here: sorry for the paywall. (I didn't notice, because I have some extensions to bypass them.)
Humans require little training, but lack attention.

Computers have the attention, but require near infinite training.
>With bitcoin so far, the higher the price, the more press is generated, which increases demand, so we have a feedback loop.

The technical term for this feedback loop is "bubble".