• 0 Posts
  • 84 Comments
Joined 1 year ago
cake
Cake day: July 3rd, 2023

help-circle
  • 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.





  • Exactly, heavy taxation on the ultra wealthy and wealth caps are incredibly popular topics in liberal circles. I swear some people have never actually talked to a liberal and just attack some strawman they’ve lumped in together with conservatives.

    I’m leftist and anti-capitalist, but I also recognize that most liberals are people who want the same things leftists do, but simply haven’t thought deeply enough about what the true root causes of society’s issues are. It’s an issue of tactics rather than a fundamental disconnect in core principles and values. Ultimately they want a more equitable, less stratified society where society helps and supports the disenfranchised. The same thing leftists want. They just don’t understand that capitalism has to go in order to achieve it.

    Liberals, unlike conservatives, are actually generally quite reasonable people since they aren’t motivated by hatred. As leftists, we should be doing everything we can to educate them and bring them into the fold, rather than tearing them down.




  • 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.






  • Let’s give it a shot. I live in the suburbs of Lincoln, Nebraska, which is an average-sized college town in the US (about 300k residents):

    • Nearest convenience store: 1.1 miles/1.7km (we often do walk there, takes about 20 minutes)
    • Nearest chain supermarket/big supermarket (they are often one in the same here): Target @ 1.5 miles/2.4km
    • Bus stop: 1.3 miles/2.1km
    • Nearest park: 0.6 miles/965m
    • Nearest public library: 3.5 miles/5.6km
    • Nearest train station: 9.1 miles/14.6km (we don’t really use trains much at all in the US, though)



  • 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.



  • 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.