In my view there's two parts to learning, creation and taste, and both need to be balanced to make progress. Creation is, in essence, the process of forming pathways that enable you to do things, developing taste is the process of pruning and refining pathways to doing things better.
You can't become a chef without cooking, and you can't become a great one without cultivating a taste (pun intended) for what works and what it means for something to be good.
From interactions with our interns and new-grads, they lack the taste, and rely too much on the AI for generation. The consequence is that when you have conversations with them, they straggle to understand the concepts and tools they are using because they lack the familiarity that comes with creation, and they lack the skills to refine the produced code into something good.
You might be safe as long as the ad is on a website but stupid laws that shouldn't exist like the DMCA can make it illegal to block ads when you have to circumvent a technological measure in order to block those ads. Blocking ads and the steps needed to block them might also violate some product's EULA which could result in civil judgements against you.
> DMCA can make it illegal to block ads when you have to circumvent a technological measure in order to block those ads. Blocking ads and the steps needed to block them might also violate some product's EULA which could result in civil judgements against you.
Your issue there is with the government. No disagreement from me in this regard :)
The problem of course isn't the fact that government and laws exist. Most of us are happy that we have government and laws. The alternative is very ugly and doesn't lend itself to progress or prosperity.
The problem is that our government was allowed to be bribed/corrupted by corporate interests to pass bad laws designed to protect their profits and enforce control by taking freedom from consumers. The true villain here isn't government, government was just the tool they leveraged against us.
It's supposed to be our job to insist that our government work for the interests of "we the people" and we failed. The solution now is to get rid of corrupt politicians and the bad laws they passed and replace them with good ones that preserve our freedoms and don't put corporate interest ahead of the people's.
Sadly, our entire political system has been carefully refined over centuries to make it harder and harder to keep our government accountable to the people but hopefully it's not too late to change that situation within the democratic framework we've created.
The founding fathers knew that the system wasn't perfect and would need to be modified as things changed and flaws were discovered. Making it work by "doing it right this time" was the point. That's not a sign of a bad system, it's a good thing!
Of course, nothing about government itself prevents adults from engaging in consensual transactions, and only a tiny percentage of laws do. Sometimes those laws are stupid and sometimes they are good to have. The original plan (and I still think it was a good one) was that we would have the ability to remove the bad laws and add good ones as needed. That process mostly even works, but with corruption and bribery in our government going unchecked it usually just works for a small few and the rest of us get shafted as a result.
That is a very weak argument. I don't have any way to decline seeing the ads before I do. I can't disable tracking by disabling js because, like a parasite, tracking software has uses what is necessary technology for websites to function.
Otherwise this is a very weak argument. Using the Internet is approximately mandatory in our current society. "Don't use the Internet" is not useful advice.
In rust, there are two kinds of references, exclusive (&mut) and shared(&). Rustc guarantees you that if you provide an exclusive reference, no other thread will have that. If your thread has an exclusive reference, then it can mutate the contents of the memory. Rustc also guarantees that you won't end up with a dropped reference inside of your threads, so you will always have allocated memory.
Because rust guarantees you won't have multiple exclusive (and thus mutable refs), you won't have a specific class of race conditions.
Sometimes however, these programs are very strict, and you need to relax these guarantees. To handle those cases, there are structures that can give you the same shared/exclusive references and borrowing rules (ie single exclusive, many shared refs) but at runtime. Meaning that you have an object, which you can reference (borrow) in multiple locations, however, if you have an active shared reference, you can't get an exclusive reference as the program will (by design) panic, and if you have an active exclusive reference, you can't get any more references.
This however isn't sufficient for multithreaded applications. That is sufficient when you have lots of pieces of memory referencing the same object in a single thread. For multi-threaded programs, we have RwLocks.
That creates more trading opportunities tbh and eventually the market will calibrate. Similar has happened to trump and his tarrifs plus all those truth/xitter messages.
For example, if the framework provides text storage, adding text processing might be a mistake. Instead, make another framework that can be strung onto the text storage one.
It increases the granularity, and the usefulness of the modules. You could have multiple processing frameworks.
In addition, it allows you to refine discrete functionality domains (which can also be personnel assignment domains), and reduces the places for bugs to manifest. You can devote more tests to each framework.
I see. I follow the same approach; with my interns I try to force them to define logical boundaries and think / design their software as libraries / components that compose together nicely.
> 1) not true as evidenced by this bug
Code used unsafe, putting us out of "safe" rust.