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?

I think if you do host your own PDS you can just tell it to say that you are age verified, they can only enforce this on the parts hosted by bluesky

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 2tband 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

• Sometimes you have to write cryptic code for performance reasons
• Sometimes you have to deal with unintuitive edge cases
• Sometimes you have to work around bugs in 3rd party code
• Sometimes you are dealing with a problem that is inherently complex or unintuitive, no matter how you put it in to code

What are the odds that you’re actually going to get a bounty out of it? Seems unlikely that an AI would hallucinate an actually correct bug.

Maybe the people doing this are much more optimistic about how useful LLMs are for this than I am but it’s possible that there’s some more malicious idea behind it.

I use wezterm. It’s more configurable than the windows terminal and also works on linux. It has an appropriately linux-y feel imo.

It’s another c/c++ competitor along with rust and zig. https://odin-lang.org/

Don’t think it has anything to do with electron. VSCode is just the largest editor that people install extensions for, so it’s what makes the most sense to write malware for. If vim was more popular, I’m sure there would be more crypto mining extensions for that (I wonder how many there are? Surely more than zero?)

This article uses the term “parsing” in a non-standard way - it’s not just about transforming text into structured data, it’s about transforming more general data in to more specific data. For example, you could have a function that “parses” valid dates into valid shipping dates, which returns an error if the input date is in the past for instance and returns a valid_shipping_date type. This type would likely be identical to a normal date, but it would carry extra semantic meaning and would help you to leverage the type checker to make sure that this check actually gets performed.

Doing this would arguably be a bit overzealous, maybe it makes more sense to just parse strings into valid dates and merely validate that they also make sense as shipping dates. Still, any validation can be transformed into a “parse” by simply adding extra type-level information to the validation.

Why do you think it’s a bad idea? Both you and OP are in agreement that you should validate early, which seemed to be what your first comment was about. Is it encoding that the data has been validated in the typesystem that you disagree with?

fd is a lot faster than find. This might not matter if you’re searching through small directories but if you’re working in a very large project it does make things a lot nicer.