Sure, but my point is that you’ll end up with one “main” remote where you have all git forge stuff even if you push to multiple remotes. By all means, don’t make github the main one!
For git itself sure, but all the other things that come with a git forge, like issue management, are probably things that you don’t want spread out over multiple websites
There’s a lot here that I could comment on, but I’m particularly fascinated that you make a big deal about const by default.
First of all, it’s not particularly good evidence that rust is functional, you could just as easily have a const-by-default java or c. Rust still has mutable data structures which is decidedly non-functional. I do actually think that rust is more inspired by fp than a lot of other languages so it’s not even that you’re completely wrong here, it’s just an odd example.
Secondly, do you actually think that const variables is a bad default? Personally I find that it makes it code easier to read when the author is explicit that a variable is going to be mutated down the line because it makes the intention clearer. It also makes it easier for the compiler to make certain optimizations which is significant in a low-level language.
Caring about the syntax of a programming language is a sign that you haven’t properly engaged with it. While not completely unimportant, what matters at the end of the day is the languages semantics. If you program in rust for more than ‘a few hours’ you will stop thinking about the syntax directly. Trust me, I do a fair bit of work in the cmake language, you can learn to work with any syntax.
Is the decompiled code guaranteed to be equivalent to the compiled code? While this might be cool it doesn’t seem that useful if you can’t reason about the correctness of the output. I skimmed the README and didn’t manage to figure it out
Comments can become outdated, but so can variable and function names. “Self-documenting” code often relies on appropriate naming, yet this is also subject to rot as the code develops.
You can tailor the rust standard library to be more embedded friendly in several way, like if you don’t have dynamic memory allocation or a filesystem, you can get the standard library sans those features.
Rust also gives you a very fine grained level of control of memory, I think equivalent to C (maybe there’s some gotcha that I’m not aware of but if not equivalent very close).
It really doesn’t sound like you know that much about Rust here and are just making things up, you certainly don’t need “gigabytes of storage and memory”
What makes you say that?
Another option if you don’t have a family is to use DLNA for streaming to the TV, most TV’s have native support for that and you can just set up your computer to work as a DLNA server.
I do use a media server but I could probably get away with just syncthing to sync my computer and phone, it would probably be easier even. Of course, if you have more than 2tb and you want it all at your fingertips then a media server is probably the right call.
I think that AI is the most useful when you’re doing something that you’re bad at so that makes perfect sense. The drawback is that you probably won’t improve as much at writing as if you where struggling with it by hand. Maybe you’re fine with that though, it’s hard to dedicate the time to get good at everything.
One thought I’ve had about AI and programing is that you’ll run in to a similar problem. Code is a bit special because it’s a language that’s understandable by both humans and computers, and when you’re programing you’re essentially writing for both audiences at once.
Voice is maybe not as important when writing code (although you still want to keep the coding style consistent) but even so I think that writing code by hand has the advantage of you being able to express your thoughts in a more coherent way than the output of a handful prompts will. The problem isn’t just with however powerful the AI model is, but that prompting is a kind of vague and indirect way of interacting with the system and it necessarily introduces another layer between the author and whoever ends up reading it.
Ok I understand that you don’t like bluesky for whatever reason, but could you actually formulate why so that it’s possible to have a discussion instead?
https://tangled.sh/ is looking like an interesting alternative imo.
It uses ATProto (the bluesky protocol) and allows you to self host the git part and/or your personal data (e.g. comments that you leave on other repos). It’s still very much in development as is the ATProto itself, so it doesn’t seem mature enough for serious use yet. ATProto does for example not handle private accounts/posts yet which means that all your tangled repos have to be public.
Oh my bad I don’t know where I got that from lol
Making a u32 pointer from two u16’s isn’t a generic operation because it has to make assumptions about how the pointers work endianess
Edit: Actually, I’m wrong, didn’t think this through properly. See the replies
If you find yourself writing regexes often enough that speeding up that process would increase your productivity by “a lot”, then you should get good at writing them yourself which means practicing without an LLM. If its something that you don’t do often enough to warrant getting good at then the productivity increase is negligible.
I think the main benefit here isn’t really productivity but developer comfort by saving them from having to step out of their comfort zone.
I try to write comments whenever what the code isn’t obvious on its own. A “never write comments” proponent might argue that you should never write code that isn’t obvious on its own, but that doesn’t always work in practice
If you’re contributing to a larger project, it might not be trivial to modify the
.gitignorefile, because you might have to go through a review process and so on. It might be easier to just ignore something locally.