skysight-inc/HackerNews huggingface dataset:
We make laws based on the lowest denominator. You literally cannot trust people to not take advantages of the systems in place when it's a choice between living in the most free country on Earth and their home country.

If you argue American isn't free or better then why are they trying to immigrate in the first place? Everyone I've ever talked to who immigrated here said America is better.

Don't believe everything you hear on the news buddy, they're selling the ad space just as much as Google and Facebook are.
If you can't afford a dog, a full sized mirror could be a wise investment.
What if I don’t tell the FEC?

What if I run an ad that’s not directly affiliated with a political campaign like via PragerU?
To me it sounds like there is glut in treasuries due to the huge government deficit and there are not enough buyers. This event is the banks not having enough on hand on hand for the treasuries and the corporate tax event at once, so the fed is stepping in to provide temporary liquidity.

Is it possible, or are we close to to where the banks (or other buyers) won't be able absorb the glut in treasuries themselves, and the fed has to buy them, effectively monetizing our deficits?
This article was well balanced. I find title just a bit misleading, since "What ORMs have taught me: just learn SQL", to me, carries a slightly different message than "What ORMs have taught me: learn SQL".

The second sentence is a little more compatible with the first line, "they can be used to nicely augment working with SQL in a program, but they should not replace it."

That's certainly how I use them. ORMs can save you a lot of irritating typing where it comes to insert and update statements. Aside from that, I write a lot of raw SQL.

I have seen what I would describe as ORM-induced, yaml-induced database damage. This isn't meant as a criticism of these tools per se, they're perfectly compatible with a well designed app. But I have noticed that people sometimes create databases that are useful only in the context of their configuration-file/ORM heavy app. Essentially, the programmers conceive of their data as a set of objects, and they use the config file to store global constants and the ORM to persist files, almost as if they're pickling and retrieving objects back into the system.

The result is a database that can't really be queried with SQL, more or less useless outside the context of the application. I firmly agree with developers who maintain that information will outlive an application, a database will outlive the software that was originally designed to use it (perhaps in parallel with it). I think a SQL database should be useful all on its own as a data source. If you got rid of the app, you'd lose a lot of operations on that data, a lot of UI, a lot of valuable things, but you'd be able to get at and use your data. If that's not the case, I'd seriously reconsider the design.

Kind of hard to do that without understanding SQL, so yeah, definitely learn it.
I don't really hard-disagree with any of that; we're all guessing. The co. sending chiplets where they fetch the most also doesn't seem outlandish as a factor, though.

FWIW, here's the price-per-core chart for the whole second-gen server line:

https://www.servethehome.com/wp-content/uploads/2019/09/AMD-...

(Doesn't factor in voltage/freq needs for different SKUs, some of them needing fully-working chiplets, etc. Still.)

The low pricing on the 7282 and a few others is interesting, too. Wonder if it's a factor that it can use partially-working chiplets since the server I/O die can take up to eight chiplets and the client die only two, or if that's totally unrelated.
Personal opinion only;

If you are delivering vehicles today, then the technology that you have validated is (although not vapourware) older than today. And to meet people’s expectation of a cheap vehicle without operating at a loss (no VC money), there are realities imposed by cost.

Someone like Rivian with lots of VC money isn’t concerned with surviving between sales, so they can afford to take the risk of selling things that don’t exist yet, at a loss if they desire, and so their marketing department is constantly walking on water.
Everyone believes that trying to keep guns out of the hands of people that would harm themselves and others is a part of the solution. That's why there are laws against felons possessing them.
Oral History of Ken Thompson (2005) [pdf]
... is probably still your enemy, but may be useful.
Nah. If they feel inclined to do something more powerful than the Content Blocker API then they should build the ad blocker themselves into Safari. It can be off by default and configurable by users.

It'd make the Content Blocker API kind of pointless but that'd be safer than letting third parties in.
I didn't quite understand fully how your solution worked in the end, are you storing the entire object graph as a JSON blob alongside the relational data in the table, or are you simply storing the JSON blob instead of using relational data?

Its difficult for me to picture how Dapper even comes into play when you're doing this trick with the JSON blob.

Why not use NoSQL?

Also 1000+ properties on an object? I know some domains sometimes surface these kind of extreme cases, but is there not an alternative to having 1000 properties in one object?
It's a safe bet that any organization with a name like "Free and Fair Markets Initiative" is corporate astroturfing.
Why do electric cars have such different wheels, almost closed discs style? I still have to see the first Tesla with chrome rims.
Right. 7 billion people is an unfathomable amount.

You don't understand what it means.
I don't understand what it means.

A person can tackle a bug in a tracker.

A company can tackle a bug tracker.

A few cities' worth can tackle manufacturing the computer.

The world? We got this. All in.

If we're enough to fuck it up, we're enough to sort it out.
I watch and listen to plenty of good long-form audio/video.

This ain't it.

10 minutes is 60x 10 seconds.

And if you can't get the meat of your argument out in a few minutes, there's something wrong with it.

(And that's windbag-me saying this.)

You're also going a bit overboard with the Actualized videos of late. Might want to give it a break.
Well, in the case of heartbleed where first the NSA found it, and an independent researcher found it, and the DoD uses Linux and OpenSSL all over the place, you'd think that the information assurance side would be better represented. Who knows how many adversaries were using that as well before it was public (hence the whole point of responsible disclosure).

Edit: Like, stuff like cryptanalysis of SM4 is for sure on the table. I can even see their neat Diffie-Hellman hack that costs $100m per nonce. But a trivially remotely exploitable memory safety bug in software that runs large sections of the military? Like, come on.
I am almost equally worried about other very popular CDNs. However, being the most used CDN makes some people short-circuit and not think about the dangers any longer Just like with captchas from Google. Many people simply put them onto their websites without ever thinking about that, "because everyone does it". If so many people put stuff behind Cloudflare, then at some point the same kind of people, who put captchas without thinking, will put stuff behind Cloudflare without thinking.

Scripts and other stuff from first party usually seem to me at least more trustworthy than something from a third party. It also saves me the mental step of thinking: "Hmmm, why are there scripts loaded from a third party? Is this some kind of ads stuff?"

If a website does not work without unblocking third party scripts, there is some chance, that I will simply abandon it. When a website's purpose is to inform me about something and I do not see the need for any interactivity, I might also abandon it, if it does not show content without unblocking scripts in general, including first party. Web frameworks, which do not take care of at least presenting something when scripts are not unblocked, thus make a website less trustworthy for me.
We do know a great deal about Julius Caesar. He wrote books on what he was doing, and we have letters written about him from his contemporaries.
Yves Klein
You speak the Trough Trough
As someone who has been developing for WP for over ten years, no, it's not difficult at all. It's just a very minor about of planning, and working with a process.
> If you don't pick an ORM to help manage this translation layer, then you'll end up re-implementing your own.

Only in the loose sense that you have to put the data into an object. That's a tiny portion of what most ORMs actually do.

I just cloned the hibernate-orm repo and, even excluding the .git files and /test/ directories, it has about 30 MB of source. There's a lot in there.
You might be underestimating the negative health effects of "burning stuff", have a look at page 3 of [1]. Replacing coal with gas should give a 10x improvement on air pollution related deaths and serious illness. If we could go full renewable (or fusion, if it wasn't always 25 years away), we could get rid of even more averse health effects.

Note: your argument of coal based electric energy is better than burning stuff at home is strongly supported by [1]. But this is not what we are arguing about. No one was proposing to abandon electric energy from the grid and go back to burn wood at home. The question was, if there maybe is a health argument to switch from coal (or generally burning stuff) to renewable energy.

[1] (This has been published in The Lancet, sorry for the potentially biased looking link, but due to the paywall at the original publisher I had to resort to google for an alternate provider) http://www.scotianwindfields.ca/sites/default/files/publicat...
> With SQL you will also have a lot of uncheckable strings containing code.

A good SQL access library can validate queries against the database itself at build time.
I think it was in the mid-to-late 90s as the internet was just becoming more available to lower income groups.

"Nobody buys physical encyclopedias anymore, everything else is going to go that way soon too"

In high school debated on the side of the demise of books (2002) and I won. Back then I convinced myself of my side for the sake of my debate performance, but I'm pretty sure today that books are going nowhere in a hurry.
Trademarks: What do do and what not to do
This is pretty obvious 50 Cent Party crap. America's fucked up, but ya'll are leaps and bounds more fucked up.
Can't we all agree ORMs are just leaky wrappers of SQL? Almost all of them need a backdrop workaround to issue raw SQL to the backend DB to avoid being a blocker at some point.
> The single-core score of 1,275 is pretty much the same as for the current flagship Threadripper 2990WX, and is actually slightly lower than the 1,334 that the Intel i9-9900K scores.

In what world is this a valid comparison? No one shopping for a $500 8 core consumer cpu is looking at a $1700 32 core hedt chip. They're entirely different markets. If you can use 32 cores you'd be looking at intels x series at a minimum, if not xeons. This is silly at best, if not intentionally misleading.
> avoiding price fluctuations from e.g. future gas supply shocks.

Yes, especially in Europe where the dominant natural gas supplier, Russia, has shown itself more than willing to use their position as a political hammer. And I know, that's not just a Russia issue, other countries do the same, they're just the most applicable when talking about gas in Europe.
The better the PW, the less you have to change it
> Deserializing a JSON blob to/from a column into/from a model containing 1000+ properties in complex nested hierarchies

> complex, rapidly-shifting business models

Your business logic classes have 1000+ properties. And you plan to not migrate them when the schema changes but leave many instances with old versions of the schema sitting in the datastore. Your application logic is going to get nasty!
On paper they look great, they passed interviews because they mastered how to answer questions in interviews. It's not as black and white as you seem to believe.
I hope if you know spanish you can read my essay about "the end of books made of paper" http://minid.net/2013/02/07/el-inevitable-fin-de-los-libros-... if you don't I think Google Translate will do a good justice. Basically, it is clear that the concept of books will be difficult to eradicate. I find it hard to believe that we lose this great cultural format; the compilation of writings with a particular objective. Reports will continue to exist, but books, as a format, they will dissapear on paper format but they will continue on digital. Because of this, it is probably that some things will change.

I have an startup right now about resuming books on audio. It's becoming increibly popular among the new generations: they don't want to read an entire book, they want the best highlights of it. Maybe in the future we will face a change in the format we write books: ultra resumed, different grammar, different format.
Lower air resistance gives longer range.

The Tesla Model S has spoked aluminum rims in black. For some reason, nobody customizes them.
No. That's what MESI-based cache protocols are all about. Multiple cores/processors can have the same cache line in a shared/read-only state. Only writes require exclusive access.
The more joins or when you need more performance, drop into SQL.

SQLAlchemy's expression language is a good middle ground. I will start there if I need to do more than a couple of joins.

As some people have noted here, I think the biggest problem is that people who only know ORMs will have trouble because their understanding of the database will be limited by their lack of SQL knowledge.
What’s Biting You at Night?
All links are Amazon affiliate links (&tag=whatsonweibo-20)
This is true. When eBooks started becoming big, my wife threw out all of her books figuring that electronic was the future.

She really regrets doing that.
Do they openly share these advances & techniques? I know, it's a competitive advantage so I wouldn't fault them too much if they don't, I'm just curious.
I see query builders as a learning tool for fresh developers, and as a job aid for business analysts. For some this can be the final destination, but for any developer I would push hard to get them writing SQL by hand ASAP.

A few weeks of suffering through DIY SQL is really the only way to fundamentally understand how the database is working for (or against) you. Once you learn it, it really does become like a second language. You can fade in and out of proficiency based on recency of exposure, but it is mostly like riding a bicycle. One other advantage is you can take it across any SQL platform without a second thought. Many ORMs have provider-specific compatibility woes to contend with.
I used ORMs JPA/Hibernate in several projects/teams and the outcome is always the same: things always get messy and overcomplicated, few reasons :

- they push developers to design super-normalized db schemas that look beautiful on paper but are horrible in practice

- the average developer has a very superficial knowledge of how ORMs work and this often leads to bad code/performance

- soon or later you will find yourself fighting the "framework" because what you are trying to do does not fit their model (e.g: upsert)

In my experience, this whole idea of abstracting from the DB is faulty at its root. You want your code to be close to the DB so that you can use all the greatest and latest functionalities without waiting for the framework X to support it.

I have found that JOOQ or simply Spring JdbcTemplate in most cases are more than enough.
>How fast does the CPU step up and down the throttling caused by AVX-512?

It's actually really, really slow. On newer (I think around Skylake-X, which is when AVX-512 was introduced) CPUs it takes up to 500 microseconds i.e. millions of cycles to activate AVX-512. This can't really be made faster because they actually need to give the voltage regulators time to adjust or the chip literally brows out. During this time AVX-512 instructions execute on the AVX-256 datapath¹.

Once AVX-512 is activated the clock of that core is reduced by about 25% and it starts a 2ms timer which is reset whenever another AVX-512 instruction is issued. AFAIK Intel doesn't say how long it takes to raise the frequency again once the timer expires.

(This is something of a simplification because there are actually two AVX power licenses, the first allowing AVX-256 and a limited set² of AVX-512 instructions, reducing clock by about 15%, and the second allowing everything. Also, executing a single AVX-512 instruction doesn't immediately request a higher power license, you have to execute a certain number of them.)

―

This is actually the better version. On Haswell executing any AVX-256 instruction would reduce the frequency of every core by about 15-20%. But hey, at least it only takes about 150k cycles to activate (not much of a consolation, I know). Beats me how long it stays throttled for.

(I don't know what exactly Broadwell did. I don't think it throttled all cores, but it didn't have the additional power license with reduced throttling that Skylake has.)

―

¹ Or the 128-bit datapath if the core is at the lowest power license (which still lets you use 128-bit SSE instructions, and basic AVX-256 instructions).

² Basically anything that doesn't execute on the floating-point unit, which means no floating point and no integer multiplication (which uses the FPU). This is actually kinda the saving grace of the whole thing, since it means you can vectorize things like memcmp and strlen without requiring the highest power license.
> you automatically invalidate one of ORMs biggest selling points which is being SQL-database agnostic.

The biggest selling point is a massive reduction in boilerplate code. Database agnostism is a feature that almost nobody ever uses, so who cares! Your proposed alternative is engine-specific SQL so you lose either way. At least with an ORM, you'd lose significantly less. You'd just have to deal with the places you used SQL. Which, in my experience, is pretty small and pretty specific.

> this typically means writing custom stitching code that stitches the SQL cursor results back into the models again.

I often feel like people who complain about ORMs have either actually never used one or used a poor one. As long as my query matches the structure of my object(s) I don't need any stitching code. And if they didn't match, I wouldn't write stitching code because that would be waste of time.

If I'm writing a custom query, I'm probably not looking to integrate into the model anyway -- if it's used for reporting I'd just take the results as is. If I'm writing a query specifically to get a matching model object (to manipulate) I'm going to get the whole model and no stitching would be required.
Wow, that's unbelievably fucked up....
> What we need to do is to suck out more than we put in.

Doesn’t it violate the first law of thermodynamics or something like that?
You're worried about CO2 emissions resulting from war? You do realize the role climate change itself can play in migration, refugees, wars, catastrophes..? You need to be worried about climate change resulting in war...
Not really, any window/tab that is not in focus gets heavily throttled by the browser, gradma is probably not running any extensions and single websites are still single threaded for most parts (more and more are adding web workers for various parts though)
I would be deeply surprised if AWS teams use public pypi. Much more reasonable would be to mirror public packages they use internally.

What if a minor version change contains a relicensing of the library, for instance?
Kaggle CEO here.

Agree with a mild version of the author's statement: that for many competitions, the difference between top n spots is not statistically significant. However, the author's statement (as represented by this chart https://lukeoakdenrayner.files.wordpress.com/2019/09/ai-comp...) is far too strong.

The actual best model may not always win, but will typically be in the top 0.1%.

There are people on this thread who have poked holes in the author's sample size calculator (I'm not going to rehash that).

But an empirical observation: the same top ranked Kagglers consistently perform well in competition after competition.

You can see this by digging through the profiles of top ranked Kagglers (https://www.kaggle.com/rankings). Or by looking at competition leaderboards. For example the leaderboard screenshot the author shared in the post (https://lukeoakdenrayner.files.wordpress.com/2019/09/pneumo-...) shows 11 of the 13 top performers are Masters and Grandmasters, which puts them at the top ranked 1.5K members of our community of 3.4MM data scientists (orange and gold dots under the profile pictures indicate Master and Grandmaster rank).

I actually think the author's headline is often correct: there are many cases where machine learning competitions don't produce useful models. But for a completely different reason: Competitions sometimes have leakage.
Not through lack of trying. It's just that iAds was unsuccessful.
What I saw when I was looking (a few years ago) is the Beagle bone is oriented towards the industrial market/dev board for TI Industrial processors. Totally different than the hobbyist market.
Getting Started with Python
Steven Pinker's book ‘The Language Instinct’ talks about pretty much everything a layman would want to know about the basics of language, in layman's terms. It covers syntax, Chomskian grammars, prescriptive vs descriptive grammar, history and relations of languages, Sapir-Whorf hypothesis, biological and evolutionary basis for languages, language acquisition in children, differences between human languages and animals' attempts (spoiler: Pinker doesn't give any credit to claims that animals learn language). Big plus of the book is that it uses Chomsky's theories extensively but explains them without need for specialized knowledge (it's explicitly mentioned how Chomsky is unreadable without linguistic training). All in all, much recommended. The book even works well as an audiobook.

Also: in preparation to diving in Kafka's books I learned about a peculiar feature of his style:

> Kafka often made extensive use of a characteristic particular to the German language which permits long sentences that sometimes can span an entire page. Kafka's sentences then deliver an unexpected impact just before the full stop—this being the finalizing meaning and focus. This is due to the construction of subordinate clauses in German which require that the verb be positioned at the end of the sentence.

>> “Als Gregor Samsa eines Morgens aus unruhigen Träumen erwachte, fand er sich in seinem Bett zu einem ungeheuren Ungeziefer verwandelt.” (original)

> “As Gregor Samsa one morning from restless dreams awoke, found he himself in his bed into an enormous vermin transformed.”

There's a neat picture illustrating the difference in the order of the parse tree: https://en.m.wikipedia.org/wiki/Franz_Kafka_bibliography#Eng...
History proves that nothing is more resilient than dead trees.

Plus, trees are at least renewable, compared to all the e-waste in landfills now.
Taleb might say this is a sibling to the Lindy Effect

https://en.m.wikipedia.org/wiki/Lindy_effect
I knew sql before using ORMs. It can never substitute that.

What it can do is abstract most common operations to do with your dB, and also help with mocking some tests.

I really don’t see the point in these articles. It’s not supposed to save you from learning SQL
Because that's what the world needs more of: Pitchfork Over/Under-styled hot takes about dense philosophy.

Perhaps there are things that are worth trying to understand, even if they are difficult to comprehend. You can miss out on a lot if you're in the habit of dismissing things out-of-hand.