You don’t need unsafe. Just keep pushing to a vec and never remove anything. Memory leaks are more than lost memory allocations. You can even have them with rc/arc cycles
You don’t need unsafe. Just keep pushing to a vec and never remove anything. Memory leaks are more than lost memory allocations. You can even have them with rc/arc cycles
Rust doesn’t prevent memory leaks. You can do that in every language
VRR is variable refresh rate. Not sure about the others
Maybe they’re referring to “where clauses”?
Can we get those settings for adults too?
It’s really nice seeing the project continue to move forward after Mozilla took out support.
risc v is not a concern because they could just build risc v chips themselves, likely more efficient than competitors too. I would be VERY surprised if they didn’t have a team working on it internally. Arm and quality are their big issues right now.
You would be surprised at how little investors know about the things they invest in. They only look at the money flow. The case will likely go nowhere though since a small gap in processes isn’t the same as a complete lack of processes that the lawsuit is implying.
You having regrets depends on your expectations. If you want a very stable system with little maintenance then you’ll be happy. Packages will be older but that’s what makes it easy to keep stable.
I’m not personally a fan of vanilla Debian because the stable versions are a bit too outdated for the things I like to work with. I do use Debian derivatives though the LTS versions.
Do you mean the tablet/PC combos?
The issue with that is it leaves no room for paying the engineers who actually designed the device. The cost of designing the parts is really expensive. I have no issue with a small markup. I definitely agree though that the costs shouldn’t be so absurdly prohibitive to repair though.
I don’t see how that can be used to make performant code though. I usually want to make my locked regions as small as possible to avoid how long other threads are blocked for.
Please do Amazon next
File a complaint with the labor board. They can investigate and if they find out they used your solution you can get paid and they can get a fine on top of that.
But how do I know if the WHERE clause is AND or OR?
The plug is becoming a standard. There are still many more stations needed to increase EV usage for people who live in apartments or doing road trips. Not everyone is relying on them for providing charging. It’s sad that they’re the only ones who actually maintain their infrastructure
Not a lawyer, but worked closely with them in the past. It REALLY depends on your employment contract. Changing variable names and language still makes it a derivative work, so it would depend on the original license. I’m assuming it doesn’t have a license which would mean either you or the company owns the copyright: depends on your employment contract. Whether you’re a contractor or full time also affects ownership.
Without ownership or a license, you do not have the legal right to copy the work or make a derivative of it.
I’m not clear on whether you actually wrote any code though. If that’s the case (that no code was written) then I’m not really sure how that works out. If you do post it and they find out, AND they’re mad about it, you could definitely get fired. I’m not sure if there could also be legal trouble or not.
If you need it for a resume item, you can just list it on your resume and talk about it. You could also implement it on your own time (but not share it until you’re sure you’re safe from legal action), that way you could talk about tradeoffs you’ve made, etc. in the real implementation.
In general, if you’re not sure and you’re worried about getting sued, you should ask a lawyer.
HD encryption only helps if they get physical access to the disk when the device is locked or powered off. If they get it via a backdoor or virus, then it doesn’t help.
How would you make money as a mastodon instance? Pay to be a member? I don’t see the incentive for the average user to pay when it’s so easy to join a free instance (I’m considering the average person doesn’t know how to host their own).
You can have a memory leak when items are still in scope in some loop or when you have a reference count cycle. The latter happens with the Rc/Arc types in rust.
An example for the former can be a web server that keeps track of every request it’s ever received in memory. You will eventually run out of memory. But you did not violate any memory rules (dangling pointer, etc.). Memory leaks can be caused by design issues.