HHVM VS ent

Learned of this in https://news.ycombinator.com/item?id=37186869 it was posted 2 years ago to no discussion https://news.ycombinator.com/item?id=30291459 seems far more interesting than that.

https://github.com/facebook/hhvm/blob/master/hphp/hack/doc/H... appears to be where it was proposed, and has more background than the current docs.

also fredemmott is not working on it any more https://github.com/facebook/hhvm/issues/9376

Hack and Flow are also written in OCaml.

Here is a commit generated by clippy fix without Cargo involved: https://github.com/facebook/hhvm/commit/efea2c4dcc12fdbf3a2e3ce383bbdca2de5f93a9

Compared to PHP, with its visible community, Hack/HHVM does seem like a dead-end technology. But it’s very actively maintained and it powers the largest website on the planet. It definitely doesn’t make sense for the average PHP developer to switch (and the article steers clear of evangelising) but it also definitely doesn’t make sense for us to switch back.

PHP is nearly as old as the web. Change the conversation and say: I use Hack on the Hip Hop Virtual Machine

In this article, we'll delve into the world of concurrency control in Go, specifically focusing on the optimistic locking approach. We'll explore its implementation using Ent ORM to illustrate how to manage data consistency when multiple users interact with the same resource. Keep in mind that this example serves as a simplified illustration, and real-world booking systems involve a many of additional complexities. However, the core concepts presented here provide a solid foundation for understanding optimistic locking in Go applications. Feel free to explore the complete source code in my GitHub repository for a more in-depth look at the implementation.

ent is a fairly recent ORM that uses a code-first approach where you define your schema in Go code. Ent is popular thanks to its ability to handle complex data models and relationships elegantly. It's statically typed, which can help catch errors at compile time. However, the learning curve might be steeper compared to more straightforward ORMs like GORM. It's a good fit for applications where complex data models and type safety are priorities.

If you found this article, than you are probably similar to how I was a few months ago. I started a project in Go that required a SQL backend and I wanted to use any tool that would help me build this backend quickly. I stumbled upon entgo (an ORM for Go) and decided to give it a try.

The ent orm for golang actually does some useful work for you. https://github.com/ent/ent

Backend Database interaction with entgo

You can use entgo.io for ORM stuff, it also has entgql extension that integrated with GQLGen. See more at the document: https://entgo.io/docs/tutorial-todo-gql