I’m sure 99+% of them knew, but I’m not ruling out someone waking up to: “what? But the company that was paying me millions to convince people that Ukraine was the enemy was based in Illinois! There’s no way they they were Russian”. Every time I underestimate the stupidity of people they tend to surprise me, so I no longer do.
Why would they limit themselves to serve propaganda only to left wingers when they can also serve propaganda to right wingers. And centrists, and fascists and tankies and anarchists. I’m pretty sure they’re trying with the full political spectrum.
To be fair. I don’t think it’s impossible that some of these were so stupid to even realize that the ones paying them were Russian.
To be fair, mechanic items, and especially electronic ones were far more repairable back then.
You could see, desolder and solder components without issue. Nowadays most of the electronics are inside chips, and only the components that need to be physically big (like those responsible for the power supply) are human sized. Sure, there are some small SMD that can be manually diagnosed and replaced, but even then you often need a lot of skill and equipment.
This is the talk that convinced me that C is the only language more cult-like than rust.
The good thing about Box::leak() is that it returns a raw *mut pointer. So you need unsafe{} to dereference it. Might as well: let my_ref = &mut unsafe{*ptr}; while you are at it, so you have a perfectly normal rust reference, so the function signatures don’t need any change.
The problem with Rc is that it would also require a RefCell most of the time. So the whole thing would be filled with Rc<RefCell<T>>. With the required .borrow_mut(). It would both do a pain to do and undo.
And of course I want to undo it, because RC is a shitty GC.
I’ve re-thought about the problem and I think for prototyping I should just Box::leak() and work with raw pointers.
This approach also doesn’t allow you to not learn the borrow checker, since leaking everything is not a good memory management strategy, but might be fine for rapidly iterating on a design.
EDIT: maybe use a leak!() Macro that does Box::leak(Box::new()) in debug mode but panics on release (as long as you execute once in release it should be fine).
Another user already proposed Odin, but no one yet Jonathan blow’s unnamed programming language (people call it jay). Those are the 2 programming languages that came to mind when I think of game development.
I haven’t tried either so I don’t know if they fit you, but they are new languages so they should avoid java’s and C++'s pitfalls.
Interfaces (traits in rust) are the best imo. Way better than raw structs in C or the mess that is inheritance.
What I don’t like about go’s interfaces is that they’re implemented implicitly. I much prefer java’s and Rust’s way to implicitly say which classes/structs extend/implement which interfaces.
Using “clever” ways to disable the borrow checker is one of the few things I don’t like about rust. I much rather it having a “borrow checker version” and a “garbage collector version”. That way we could rapidly iterate through design choices with the GC, and once the design has proven good, apply lifetimes and such to use with the borrow checker. The only downside to this I can think of is that most would just leave it in the GC version and not bother to move to borrow checker. But that’s fine by me, rust has many other features to take advantage of. As long as no GC libraries are allowed in crates.io, it should be fine.
You can just. Have datastruct be mutable if you want. Immutable by default doesn’t mean you can’t make variables mutable.
HTML is hard to parse because it allows mistakes.
I don’t know the answer to your question. But if it was me, I’d run the HTML parser until it encounters an error, manually fix the error, then try to parse again. Until it parses correctly.
Criticizing the Chinese government is xenophobia! Straight to the gulag.
My favourite is when every error is an HTTP Bad Request with no body. Absolutely wonderful to use those APIs
Yes.it is hype. Because it is a product still in development. Windows is not yet officially supported, and they announced Linux like one month ago.
It still lacks some basic features. However, what they already have looks good, it is much more performant that vscode.
The point of WNBA is not to look pretty. They are there because they are good.
If straight men want to look at women there’s plenty of environments where the point is that the women are pretty.
Storing them in files with correct permissions.
Don’t need evidence to support a feeling.
It doesn’t make sense that they would only serve propaganda to right-wingers and tankies. Maybe they’re focusing them because it’s easier, but it wouldn’t make sense to only do it to approximately half the population when they can do it to the full spectrum.
Or maybe there’s evidence of the right wing because it was easier to catch.
We should all be critical of propaganda, if you think “ah, it’s the other guys that are getting all the propaganda”, you’ve just become an easier target.