Every day pretty much with Unix tools. Vim, awk, sed, etc.

Confused what you mean. OpenAPI has nothing to do with JS.

Visual… programming languages? Yikes.

If the MR is anything bigger than a completely trivial change in a file or 2, it most likely should be broken into multiple commits.

A feature is not atomic. It has many parts that comprise the whole.

Commits should be reasonably small, logical, and atomic. MRs represent a larger body of work than a commit in many cases. My average number of (intentionally crafted) commits is like 3-5 in an MR. I do not want these commits squashed. If they should be squashed, I would have done so before making the MR.

People should actually just give a damn and craft a quality history for their MRs. It makes reviewing way easier, makes stuff like git blame and git bisect way more useful, makes it possible to actually make targeted revert commits if necessary, makes cherry picking a lot more useful, and so much more.

Merge squashing everything is just a shitty band-aid on poor commit hygiene. You just get a history of huge, inscrutable commits and actively make it harder for people to understand the history of the repo.

If you mean for programming specifically, I… don’t, really. At most it would be for a quick sanity check on syntax in a language I don’t write often, for which Google is fine. But otherwise I rely on documentation and search features of the various language/tool-specific websites.

The tooling has improved dramatically since then. There’s now a full-fledged language server (https://haskell-language-server.readthedocs.io/en/stable/), ghcup (https://www.haskell.org/ghcup/) is now a thing for installing/managing different versions of GHC/cabal/HLS, there’s now formatters (https://github.com/tweag/ormolu) and cabal has modernized significantly and supports multi-package projects much more comfortably now. Nix-based Haskell infrastructure is also now pretty nice. There’s even stuff like https://github.com/srid/haskell-template/blob/master/flake.nix to very quickly get spun up on a new project using Haskell and nix, including vscode, formatter, HLS, and a full development shell with a bunch of useful commands.

Another great modern thing (which powers HLS) is that GHC can now emit .hie files for each file it compiled, which is basically a standardized representation of the AST for that module that can be consumed/manipulated programatically. Lots of tools can use this. One such tool that’s particularly useful is https://github.com/wz1000/HieDb, which constructs an sqlite database from the information in these files, so you basically can have an index of every symbol definition, reference, export, etc. all readily available to use however you want.

https://www.shellcheck.net/ is probably one of the most well-known.

https://simplex.chat/ is written entirely in Haskell.

https://pandoc.org/ is another big one.

https://serokell.io/blog/best-haskell-open-source-projects has a (non-exhaustive) list of a bunch more.

Haskell. It’s a fantastic language for writing your usual run of the mill DB-backed web APIs (and a bunch of other stuff like compilers, data processing, CLIs, even scripting) and can do a lot of things that other languages simply can’t (obviously not in terms of computation, but in terms of what’s possible with the type system).

I’ve been writing it professionally for a while and am very happy with it. Would be nice if the job market for it was a bit broader. You can definitely get jobs doing it, you just don’t have quite as broad of a pool to choose from.

It’s currently the best tool for doing UX/design work.

Huh, you know what, maybe I’ll give something like that a try. In the past I’ve tried doing one worktree per branch, but it was a pretty big hassle since I’d have to copy over a bunch of files every time (stuff sitting in the directory but not version-controlled). Yeah it can be automated, but it didn’t seem worth it. But a persistent set of work trees that I can use to parallelize when needed sounds pretty good.

No, because raw-dogging JavaScript isn’t something grown-up software shops do.

I mean, it still doesn’t change the fact that no one actually wants this shit.

My pixel 7 pro is perfectly smooth and seamless. Oh and voice assistant is far faster than anything on iPhone thanks to the on-board Tensor chip.

Umm, you can do that on any device. It’s called Google Meet, Zoom, Discord, or any other countless othe video chatting applications out there.

Apple software is pretty overrated no matter if it’s iOS or macOS. I use a MacBook for work and I use exactly zero Apple apps because they just aren’t very good.

The software is pretty overrated. Especially safari, which is a legitimately terrible browser and has been for a long time.

“Lemmy” (the software) doesn’t have any data. It all resides on servers owned by people other than Lemmy’s developers. They have the user data and would absolutely be subject to GDPR.

Again, no matter what Lemmy’s devs put in place, it doesn’t matter because the instance admins can do whatever they want.

GDPR is really designed to target software controlled by a single entity, but this isn’t that. The instances are responsible for their content, full stop. There’s no way of forcing an instance to delete content, and even if there were, since the admins are running it, there’s nothing stopping them from removing such a feature.

There’s also nothing stopping admins from deleting content from their servers (it’s just a database, after all).

Yeah, in most statically-typed languages this is simply the default behavior unless you specifically declare a field as optional.

Rust does a lot more than that. It has a far more powerful, flexible, and higher-level type system than Java all while being much more performant.

Every single time I’ve heard people cite Java’s ecosystem, I’ve yet to see them using anything that Rust doesn’t have a better alternative to. Java’s ecosystem is massive, but most of the time, you don’t actually need it. Unless you are doing a lot of third party integrations that have Java sdks or something, there’s not a lot it buys you. If you’re just making typical web applications with a database, Rust has you completely covered and will do a better job of it to boot.