Yeah, standard practice is to set up source control before doing any work at all. Then you add whatever project template/scaffolding files to an initial commit and make it, and keep committing from there.

You should always be committing early and often. Saves you a lot of headache and make it a lot easier to clean up your history later too.

Monorepos are a thing. But obviously this is something entirely different.

Reviewers are not infallible and are largely focused on the meat of the MR rather than every single detail.

It reflects much more poorly on you than it does on them.

Don’t need the Ord instance for equality, just Eq is sufficient. Ord is for inequalities.

The point of the post is that most mainstream languages don’t provide a way to automatically derive point-wise equality by value, even though it’s pervasively used everywhere. They instead need IDEs to generate the boilerplate rather than the compiler handling it.

I wasn’t suggesting making JSON “REST” APIs (not actually REST, more accurately you might call them JSON data APIs or something). I meant protocols that are specifically meant for RPC, like gRPC, JSON-RPC, etc. Or message queues like RabbitMQ.

Ah I see, my bad. You mentioned Ruby on rails and GraphQL so I assumed you were talking about some kind of MPA situation.

Yeah htmx doesn’t replace data APIs for sure. Still not a fan of GraphQL for that purpose for the reasons above. There’s a lot of good options for RPC stuff, or even better, you can use message queues. GraphQL is just a bad idea for production systems, IMO.

I was replying to someone talking about GraphQL and Ruby on rails, not the OP of this post.

I don’t know what you mean by an API standard, but yes, it is technically a JavaScript library. But that’s only an implementation detail and the spirit of htmx is that you write very little JavaScript. Javascript is simply used to extend the HTML standard to support the full concept of hypermedia for interactive applications. An htmx-driven application embraces hypertext as the engine of application state, rather than the common thick client SPAs hitting data APIs. In such a model, clients are truly thin clients and very little logic of their own. Instead, view logic is driven by the server. It has been around for quite a long time and is very mature.

It’s fundamentally different than most JavaScript libraries out there, which are focused on thick clients by and large.

This is something often repeated by OOP people but that doesn’t actually hold up in practice. Maintainability comes from true separation of concerns, which OOP is really bad at because it encourages implicit, invisible, stateful manipulation across disparate parts of a codebase.

I work on a Haskell codebase in production of half a million lines of Haskell supported by 11 developers including myself, and the codebase is rapidly expanding with new features. This would be incredibly difficult in an OOP language. It’s very challenging to read unfamiliar code in an OOP language and quickly understand what it’s doing; there’s so much implicit behavior that you have to track down before any of it makes sense. It is far, far easier to reason about a program when the bulk of it is comprised of pure functions taking in some input and producing some output. There’s a reason that pure functions are the textbook example of testable code, and that reason is because they are much easier to understand. Code that’s easier to understand is code that’s easier to maintain.

Obligatory “JSON APIs are not REST because JSON is not hypermedia”.

GraphQL is a mess too as you throw out any ability to reason about query performance and it still requires thick clients with complicated/duplicated business logic.

If you’re doing RoR anyway, then go for https://htmx.org/. It’s much, much simpler and closer to how the web was originally designed. Highly recommend this book the author wrote on the subject (also provides tutorials walking through building an app): https://hypermedia.systems/book/contents/.

Spoken like someone who knows absolutely nothing about vim/unix.

That’s what the diff tool is for.

Interactive rebase? There’s no GUI that actually does that well, if at all. And it’s a massive part of my daily workflow.

The CLI is far, far more powerful and has many features that GUIs do not.

It’s also scriptable. For example, I often like to see just the commits I’ve made that diverge from master, along with the files changed in each. This can be accomplished with git log --oneline --stat --name-status origin/master..HEAD. What’s more, since this is just a CLI command, I can very easily make a keybind in vim to execute the command and stick it’s output into a split window. This lets me use git as a navigation tool as I can then very quickly jump to files that I’ve changed in some recent commit.

This is all using a standard, uniform interface without mucking around with IDE plugin settings (if they even can do such a thing). I have many, many other examples of scripting with it, such as loading side-by-side diffs for all files in the worktree against some particular commit (defaulting to master) in vim in a tabpage-per-file, which I often use to review all of my changes before making a commit.

It can be nice when you successfully do a rebase (after resolving conflicts), but change your mind about the resolution and want to redo it.

Doesn’t come up that much, but it’s been handy once or twice, for me. It’s also just nice security: no matter how I edit commits, I can always go back if I need to.

I’m sure it’s fine for small-scale usage, but overall it’s extremely inflexible and doesn’t really scale well at all. There’s also a lot of very basic functionality that’s straight up missing. For example, there’s no way to have a global epic priority. You can rearrange epics in an epic board, but the ordering of the epics there is not persisted elsewhere. There were many, many other shortcomings we kept running into.

Oh, and after a lot of our tickets had been imported (which itself was a huge undertaking since the auto import tools are complete trash), it started to be very slow. It feels like a very unfinished, unpolished product.

We use Gitlab’s CI/CD features extensively at my current job and it’s very, very nice. That’s what they are actually good at, not project management.

I also wonder if people complaining about Jira are still on Jira Server. Jira Cloud is a much nicer experience. Certainly not perfect, but I’ve yet to see an actual viable alternative (once worked someplace that tried to move all project management to Gitlab… 🤮).

If you do want to go the web route, I’d highly recommend avoiding SPAs and going with https://htmx.org/ instead. Much simpler, less code, entirely driven by your backend, while still giving you the ability to make nice interactive applications.

As a bonus, since you presumably have been working with Python anyway, the author of htmx has a whole book online walking you through building an app using htmx and Flask, a web framework for Python: https://hypermedia.systems/book/contents/

Uh, there are an absolute fuckload of Java libs out there with nothing more than auto-generated garbage Javadocs.

I dunno, plenty of those sound pretty reasonable.

Paw Patrol is a very fascist show meant to teach fascist ideology to kids, just so you know: https://www.cnn.com/2017/12/22/health/thomas-tank-engine-paw-patrol-fascist-cartoon-strauss/index.html

This isn’t a criticism, it’s easy to for stuff like this to slip past parents’ radar. But I’d strongly recommend switching to a different show.