We have like 250, mostly remote and on Slack all the time. There’s the occasional hiccup here and there, but generally it’s pretty seamless.
We have like 250, mostly remote and on Slack all the time. There’s the occasional hiccup here and there, but generally it’s pretty seamless.
I’ve personally never had an issue with Slack, mic/video included. My connection has always been solid, though. Never tried on a shit connection.
Probably.
It’s delusional to think he was ever going to do anything but accelerate the genocide.
In absolute terms, they aren’t the majority. 73m voted for him out of the 161m eligible voters in the US, or ~45% (Harris has ~43%). Still a frighteningly high number, but it also means it’s possible to find support for resistance, at least if things start to get bad enough. Unfortunately, there are a lot of Americans that like to think that politics don’t concern them and that we should just be apolitical. So they’re going to need a wake-up call first before they would lend their support. Trump will likely give it to them in short order as his fascist policies start to directly affect them.
Also, keep in mind that the total population (~334m as of 2023) is much larger than the population that is eligible to vote. There are many young people that are too young to vote now but still old enough to fight tyranny, former felons who are ineligible to vote but eager to fight oppressive systems, not to mention the scores of people not counted among eligible voters due to not being registered to vote, either through complacency/disillusionment (see above) or active sabotage and disenfranchisement by Republicans (and in many ways, you could say these are one in the same).
Fascists may have power and have won the popular vote, but it doesn’t mean it’s the will of the people. It means they’ve successfully gamed our very broken system. But real, average people living their lives will fight when the oppression comes to them. Maybe it will be too late, but maybe not. Revolution only needs a single spark.
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.
In Nebraska, I get my ballot by mail way in advance. I fill it out at my leisure, doing research on candidates as needed. I can then either mail the ballot back or drop it off at one of several locations around town (including any of the public libraries). I haven’t voted in person in years. This method is so much better.
Yeah our corporate machines won’t run any external media. I assumed that was standard practice.
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/.
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):
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.
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/
Ah could be hardware/OS, yeah. I believe everyone at our company are on MacBooks (I’m a Linux guy myself, but orgs don’t usually like that).
My personal laptop is a Dell XPS 13 and while I like it for various reasons, it has had plenty of problems with the built-in mic and video (mostly the mic). So it very well could be that.