TehPers

One note about Sagas - they tick up on your first main phase, so you’d copy the Binding the Old Gods again before getting the forest.

Edit: but yes, you’d get the forest in your main phase after it re-entered on your upkeep.

Is this supposed to be a leading question? I’m not making the decisions, but there’s no reason to be happy about losing contributors in any case.

It’s supposed to put the LF in line with sanctions rather than at risk. They have no control over the invasion (aside from pushing a malicious patch that shuts down all Linux systems or something)

I’ve been uninterested in standard since they changed the rotation to 3y. With this, I know I’m done now. It was fun while it lasted.

I had no issues with UB sets and products as fun eternal format content, but if they’re adding more nonsense to standard, no thanks. I much preferred the old, smaller standards.

My understanding is that users can edit the chat themselves.

I don’t use c.ai myself, but my wife was able to get a chat log with the bot telling her to end herself pretty easily. The follow-up to the conversation was the bot trying to salvage itself after the sabotage by calling the message a joke.

If you’re hoping for the standard lib to have things built on evolving standards and ecosystems like HTTP clients, then I doubt that will ever happen. There are plenty of examples of why that would be a terrible idea (urllib, std::regex, etc).

Sometimes when I don’t leave comments like that, I get review comments asking what the line does. Code like ThisMethodInitsTheService() with comments like “what does this do?” in the review.

So now I comment a lot. Apparently reading code is hard for some people, even code that tells you exactly what it does in very simple terms.

I won’t be getting any of the Marvel UB content, but I love that Captain America is a Jeskai card.

That’s my guess too. This would be way too many changes otherwise, with unsafe attributes, syntax changes, and feature additions (like use syntax).

I’ll give it about two weeks before some random court in Texas tries to block it.

newly manufactured vehicles should not already rust.

Seems to be a trend these days, unfortunately.

200V refers to the gen then? I saw the article mention some CPUs in the 200s so I guess that makes sense.

Odd choice to go with a V suffix though for a part that would probably explode if provided 200V power (at the usual current levels it draws anyway). Imagine a laptop CPU that draws 2000W and is somehow an improvement over previous gen - actually, that’s a very Intel thing to do now that I’m thinking about it.

I think we’re gonna need some updated naming wheels for the new generations of processors. I have no clue if a “Ryzen AI 300” is supposed to be a high-end, mid tier, or budget processor, nor what the Intel Core Plus Ultra whatever (that somehow draws 200V power?) is.

Rather than modifying your dependencies in the cache directory (which is really not a good idea), consider cloning the repo directly. You can use a patch entry in your Cargo.toml to have all references to iced_wgpu point to your local modified copy.

I’m not going to say that C is unusable by any means (and I’m not saying you are saying that). It’s a perfectly usable language. I do think that more people would benefit from exploring other options though. Programming languages are tools, not sports teams. People should familiarize themselves with many tools so they always have a good tool to use for any job.

I think a lot of people believe this because there is some truth to parts of it. I think we see languages like Rust and Zig (and others) popping up to try and solve specific problems better than others.

As for OP’s post, there is no single “C successor” or anything like that. People will use the best tool they know of for the job whether that’s C, Rust, C++, Zig, Python, C#, etc. Many languages will “replace” C in some projects, and at the same time, C will replace other languages in some projects (likely to a lesser extent though).

(Not /s this time)

Honestly C is the future. I don’t know why people would move from C to any other language. It does the job well enough that there’s no reason not to use it.

Think about it. Every modern application depends on a piece of code written in C, not Rust or Zig or any other language (except assembly). It can be used to solve any problem, and works in more places than any other language.

These arguments about “security” and “memory safety” are all pointless anyway in the face of modern code scanning tools. Cross-platform dev can be done trivially with preprocessors. If that’s not enough, I don’t know what to say. Get better at writing C obviously.

Lifetimes and UB should all be kept in mind at all times. You can explicitly mark lifetimes in your C code if you want using comments. Any index-out-of-bounds bugs, use-after-free, etc are just signs that your team needs more training and better code scanning utils. Write more tests!

Anything more complex than a simple typedef is just a sign that you’re over-engineering your solution. #include is both simple, and does exactly what you’d expect any reasonable language to do - paste your referenced code inline. It’s genius, and doesn’t require any complicated explanations on namespaces and classes and subclasses and so on.

So which will be the future? C obviously.

/s

Correct - Rust’s attribute grammar allows any parseable sequence of tokens enclosed in #[attr ...] basically. Serde specifically requires things to be in strings, but this is not a requirement of modern Rust or modern versions of syn (if you’re comfortable writing your own parser for the meta).

The author is not a Rust expert though, so I’m not surprised to see this assumption. It doesn’t take away from the article though.

Edit: for fun, syn has an example parsing an attribute in an attribute

Reddit makes an anti-user change. In other news, grass is green.

I haven’t been on the site in over a year and nothing since then has convinced me to go back. Maybe I’m lucky that I’m not in any Reddit-only communities, but it could also just be that I treat those communities as though they don’t exist and never had a reason to join one as a result.

Reject assembly, return to machine code. Assembly is an inaccurate projection of what the machine truly does. Writing the binary by hand hardens us, and brings us closer to the computer. We better understand what our machine is doing when we calculate our jumps by hand.

The “‘modern’ development stack” we used at my school when I was in a CS program was C++98 or something, compiled using gcc directly. This was in the last decade. It technically wasn’t C!

But we did use C in my computer engineering classes so I guess they technically did teach it. I feel very fortunate that I haven’t needed to use it since then.