Depends on if you want your data format to be strict ascii. If you don’t care, then sure, why not?

You can still freely use / in branch names. Having remote branches available as remote/branch is just a convenience, and you can delete or modify them locally. It’s common to use / in branch names, too.

Well I’m sorry that you got shitty responses like that. Which platform(s) was this on?

You’ll see when you start your second project why this doesn’t work.

Can you be more specific? I’ve had nothing but great experiences from the rust community.

The US providing this defense however allows Israel to be even more belligerent without fear of retaliation, possibly the only thing stopping them from expanding their genocide faster.

Your default types for that are i32 or u32. It’s the exact same number of characters yet encodes more precise information.

I’m aware of packing, but for my specific niche the main bottleneck is CPU, and it’s important to minimize the amount of memory usage to improve data locality, increasing cache hit rates, ultimately increasing cpu throughout. Any gains we would make by packing such small values would likely be eliminated by the cost of unpacking them, unless it’s a flags-like value where we are primarily comparing individual bits.

I’ll be honest if that’s your complaint, I have a hard time believing you would find the equivalent C or C++ code to be better.

Cargo being an all-in-one tool is actually one of my favorite things about the rust ecosystem. It’s many things, and it does it all seamlessly.

Regarding comparing to C or C++, how can you argue either is designed better? C, while standing the test of time, predates so many modern programming concepts or standards and writing C code is extremely error prone. C++ improves on many of C’s shortfalls, but it wasn’t designed. It’s the result of different things being loosely bolted on to C over the course of 30 years. And it’s still error prone, for example while there are smart pointers and other types that can make writing memory safe code possible, they’re not default and they aren’t always fully supported in the standard library, let alone anything else.

I do systems programming work, sometimes with constrained memory scenarios. We always want to use the smallest types we can for any task, and unless negative numbers are a necessary, always prefer unsigned. That means a lot of u8 and u16 unless we know a value is likely to need more bits to be represented. Probably doesn’t matter as much in we programming but that’s not Rust’s niche (or well not its original niche).

It does define minimum sizes for different types. An int for example is at least two bytes, whatever size those might be!

Why this over a much more popular modern language like Rust?

Incorrect. Open source means using a license that conforms to the open source definition. You can find that here: https://opensource.org/osd

If a license forbids LLM training, it is by definition not open source.

Only if you can reasonably argue that the output is the input (even with exact matches over a certain size being auto-rejected), and that it is enough to qualify as a copyrightable work. I’d argue line completions can never be enough to be copyrightable, and even a short function barely meets the bar unless it is considered creative in some way.

Every open source license grants permission for AI training, and GitHub copilot by default rejects completions that exactly match code from its training. You can’t pretend to be pro-open source or pro-free software but at the same time be upset that people are using licensed software within its license terms.

20k for 791k, about a 2.5% fee

Most streaming services don’t do comment sections. That’s mostly a YouTube and TikTok thing where the sites depend on user submitted content and also function as a social network. Despite this, people talk about shows on those services, just elsewhere.

This is how I would describe my experience. Sometimes it’s crunch time and most of the time it’s fuck around time. After crunch time I always throw a tantrum about how if we only bothered with planning we could largely avoid it.

Probably not. Electron is popular not just for its cross-platform support, but also that its skills are highly transferable from existing web dev.