Hacker News Reader

Let me put it differently. Who won World War II?

dventimihasuraon Everything we know about spies is wrong

Here's just some of what these "librarians, professors, and researchers" were up to:

https://www.npr.org/2014/11/05/361427276/how-thousands-of-na...

https://en.wikipedia.org/wiki/Operation_Midnight_Climax

dventimihasuraon Everything we know about spies is wrong

"What the hell do you think spies are? Moral philosophers measuring everything they do against the word of God or Karl Marx? They're not! They're just a bunch of seedy, squalid bastards like me: little men, drunkards, queers, henpecked husbands, civil servants playing cowboys and Indians to brighten their rotten little lives."

https://youtu.be/lNrjAMV0HJk?si=Fbk3fE-Ufm3ACxgv&t=86

dventimihasuraon The Erie Canal: The man-made waterway that transformed the US

The Chapo Traphouse podcast touched on the Erie Canal in Episode 557 "The Inebriated Past 10: Mormons, pt. 1", especially as the backdrop for the story of Joseph Smith and the creation, of course, of the Mormon church. It's a rousing tale told well beginning around 15 minutes in. The general thrust is that the burst of economic activity that both motivated the creation of and was in part sustained by the Erie Canal extended a tentacle of capitalistic social dislocation which, in part, was a factor in religious revival movements in upstate New York like the Mormons.

I can't vouch for the accuracy of any of this, of course. It could be just some guy yelling on the internet. I just thought it was interesting.

https://youtu.be/-cMs2BYo9nY?si=1AC8CidLpifN3Mno

dventimihasuraon Roku update turns on hated motion-smoothing feature, with no off switch

Perhaps The New York Times recommending it has something to do with it:

https://www.nytimes.com/wirecutter/reviews/best-media-stream...

dventimihasuraon Half a century of SQL

pgTAP is pretty good for PostgreSQL, but I don't know what if any options are available for other databases.

https://pgtap.org/

dventimihasuraon Half a century of SQL

That's a good point about MySQL. PostgreSQL wasn't quite ready for primetime at that time, and Oracle and MSSQL aren't free. That left MySQL to fill the gap, but it's not really built for this style of development.

dventimihasuraon Half a century of SQL

That depends. I worked with customers 25 years ago who put loads of business logic in very long and involved T-SQL stored procedures in MSSQL or PL/SQL stored procedures in Oracle. That may have made maintenance more difficult for the database developers who wrote them. It did make maintenance more difficult for the Java and .Net developers when they had to look at them, but that may have been a skill issue. These days, between (custom) data types, domains, defaults, constraints, views, materialized views, and triggers, I think there's more opportunity to regard "stored procedures" as a measure-of-last-resort. When that's invoked, I think application of the "Single Responsibility Principle" can take you a long way.

dventimihasuraon Half a century of SQL

I'm aware of that belief, but I do not share it.

dventimihasuraon Half a century of SQL

The customers I work with tend to use database migration tools like Flyway or Liquibase, have their DDL in source control, run tests, and have fairly conventional CI/CD. As I said above, I've never personally worked on a large team doing this, but our customers seem to make it work.

dventimihasuraon Half a century of SQL

That's a matter of taste. I find most of the business logic I need to express involves finding and transforming relational data, a task to which SQL is better suited than any general purpose programming language. Often, SQL is all that's needed. Less often, I have to resort to PLpgSQL, PL/SQL, or T-SQL. When that happens, it's not that bad.

dventimihasuraon Half a century of SQL

Fair. I've only ever had success with this strategy as a solo hacker. It was once claimed to me that this would be a disaster on large teams and I had to admit that I had no evidence one way or the other. Don't know if that resonates with your experience. Just anecdotal.

dventimihasuraon Half a century of SQL

I see it differently. In the 25 years I've been working in this industry I see a welcome trend toward doing more in the database, such that the impedance mismatch dissipates. This is from a low-water mark 20 years ago or so, when most Java developers I knew kept the database at arm's length, insisting it met them on their terms rather than the other way around.

https://gist.github.com/cpursley/c8fb81fe8a7e5df038158bdfe0f...

https://supabase.com/

One way to eliminate the Java-SQL impedance (for example) mismatch is to delete Java altogether, along with JOOQ, Hibernate, and Spring (for example).

dventimihasuraon Half a century of SQL

One way to have tighter integration between the database and the application logic is to abandon the application code altogether. Express the application logic right in the database using (custom) data types, domains, defaults, constraints, views, triggers, and procedures. Then you can delete much or all of the "application tier", delete the ORM, and simplify the entire stack. That's one way to avoid having "the database [feel] very separate from the rest of the project."

dventimihasuraon After 6 years, I'm over GraphQL

Nice!

dventimihasuraon After 6 years, I'm over GraphQL

Ahh, I see. Yeah, I suppose some examples in the docs would be nice.

Anyway, here's an example with Hasura:

https://gist.github.com/dventimihasura/b3f3c9e7ef1442d8e7f16...

dventimihasuraon Tinygrad 0.9.0

Is "readers here [ARE] drooling morons and [DON'T] know what a github is and [CAN'T] click on the link to the repo and find the README.MD" the only other alternative? There's no middle ground? There's no "readers here aren't drooling morons and know what a github is and can click the link to the repo and find the README.md, but they're also busy and their attention is limited and so some of them won't be bothered to take those extra steps to learn about your project if you can't be bothered to put your best foot forward, and it's not a moral failing on either side, it's just the way it is"?

dventimihasuraon After 6 years, I'm over GraphQL

PostGraphile compiles GraphQL directly to SQL. The SQL is "custom" in that it's specific to the GraphQL operation, though naturally it does follow rules. For example, Hasura does the same thing, and among the rules that it follows is that it uses `LEFT LATERAL JOIN` between tables (at least, on PostgreSQL). Full disclosure, I work for Hasura, so I'm not super familiar with the style of SQL PostGraphile generates but one thing you can do is just have PostGraphile report back the generated SQL for inspection:

https://www.graphile.org/postgraphile/debugging/#via-postgra...

dventimihasuraon Tinygrad 0.9.0

And yet, I never encountered any of those other posts. I bet that's true for most HN readers.

But, suit yourself. I just think you'll get higher engagement if you put your best food forward by helping newcomers understand what this thing is. But hey, maybe I'm wrong.

dventimihasuraon Tinygrad 0.9.0

You might consider posting not the release page, but rather the repo page:

https://github.com/tinygrad/tinygrad

Another good alternative would be:

https://tinygrad.org/#tinygrad

dventimihasuraon The API database architecture – Stop writing HTTP-GET endpoints

> That login service can be written to be virtually immune to SQL attacks because it doesn't have to handle generalized queries. Ban all the SQL control characters in usernames/passwords

Why? If that login service is a third-party provider, what does this accomplish?

dventimihasuraon Grats: A More Pleasant Way to Build TypeScript GraphQL Servers

Not in enterprise companies, it's not.

dventimihasuraon Grats: A More Pleasant Way to Build TypeScript GraphQL Servers

Incidentally, I see no evidence in those links or elsewhere that either Walmart or Netflix is using node to meditate interactions with upstream data sources. What I do see elsewhere is the usual suspects: some databases and message queues, and then lots of Java

https://blog.bytebytego.com/p/ep76-netflixs-tech-stack

dventimihasuraon Grats: A More Pleasant Way to Build TypeScript GraphQL Servers

Of course, Hibernate (Java) dwarfs them all.

https://trends.google.com/trends/explore?date=all&geo=US&q=S...

dventimihasuraon Grats: A More Pleasant Way to Build TypeScript GraphQL Servers

In San Francisco, currently Indeed has ~2600 jobs for "Java", ~600 for "Typescript".

dventimihasuraon Grats: A More Pleasant Way to Build TypeScript GraphQL Servers

It's dodgy finding the right search term, but at first blush it looks like sequelize is most popular, though the gap has narrowed considerably.

dventimihasuraon Grats: A More Pleasant Way to Build TypeScript GraphQL Servers

I'm just trying to get a sense of what tools are most commonly used.

dventimihasuraon Grats: A More Pleasant Way to Build TypeScript GraphQL Servers

Do you want to meet people where they are and help them with solutions given their constraints?

Or, do you want to offer solutions using your preferred tools?

There are no wrong answers, as far as I'm concerned. I'm just curious which you would prefer.

dventimihasuraon Grats: A More Pleasant Way to Build TypeScript GraphQL Servers

Ok. How do you recommend I go about Googling it, and what do you predict will be the results?

dventimihasuraon Grats: A More Pleasant Way to Build TypeScript GraphQL Servers

The point of the comment is to confront the following question:

"What exactly are we trying to do here?"

Are we trying to offer GraphQL servers? Or are we trying to offer GraphQL servers in Node? Because, if it's the latter, then I'll move on my merry way. If it's the former, then a new way of building GraphQL servers in Node may not be all that relevant if there's a majority of developers who already aren't building servers of any type in Node.