Shouldn't any returned items go into the "used" stock and not be intermingled with new items?
865 karma · joined August 15, 2016
Shouldn't any returned items go into the "used" stock and not be intermingled with new items?
2. It's not, you just don't want to accept it.
3. Would it surprise you to hear that people are still wearing face masks for that same reason? Your "magic invincibility cloak" is a strawman argument that nobody has ever made.
It's almost like there's a serious and highly infectious virus still circulating. Perhaps one that has a reputation for seriously harming or killing immunocompromised people.
>When is it going to end?
Better question, why do _you_ care when _others_ decide to stop wearing a mask?
This is like a non-asthmatic person criticizing someone with asthma for living in fear by carrying their inhaler in their pocket. When is asthma going to end? Surely they can't just carry around an inhaler for the rest of their lives, right?
>They cannot continue to live the rest of their lives in fear, it's debilitating to their mental health. However social media has enabled this behaviour.
Yet you're here on social media stressing about other people choosing to wear masks. Honestly for many people it's second nature at this point. Other countries like Japan had people wearing masks in public long before 2020.
You don't seem to realize that people have different life experiences than you.
Of course it's because you agree on some level that DIY and "knowing how to use your tools and instead asking cloud providers to know how to do things for you" is simply not worth it. Companies who use these premium managed services are just setting the bar 1 level higher than you do.
Even if these premium services end up costing $200K/year more than doing it yourself on commodity VMs, that's not even the salary of 1 FTE engineer at many companies. It's simply not worth the time and opportunity cost to care about those things if it's distracting engineers from working on the core product.
It was trained on language for the primary purpose of producing text, but that’s not necessarily all it can do. The billions of nodes and parameters it contains allows it to compute ultra complicated equations. Who’s to say some subset of those nodes aren’t forming some basic primitive used for reasoning?
Not to mention, the ToS forbids it due to the experimental nature of the tool. In a few years, I doubt the restrictions will be as tight as they are now.
Before this, there were anecdotal examples of SD outputting an image with some Shutterstock watermark or very similar to some artist's work, but the prompts also seemed highly specific or were asking for something in that artist's style.
This tool at least lets us start to trace back the average image, and so far it does seem SD is adding something novel to its outputs.
At the time at least, it was very clear that Minecraft was written for single player in mind. Nearly everything ran in a single main loop, causing virtually every multiplayer server to only be able to utilized 1 core. This meant most servers couldn't scale beyond ~50 players with vanilla Minecraft. Community optimizations could take this to 200-300, but usually sacrificed something for those performance gains.
Then a ton of work went into workarounds like Bungee, which enabled the next-gen Minecraft servers to host thousands of players on a "single" logical server. Of course, the main game loop was actually still single threaded and those thousands of players couldn't truly interact with each other as you would expect with vanilla Minecraft.
> When the system began having problems Tuesday night, technicians switched to a backup. But because the backup was attempting to access the same damaged data, it also didn’t work, the person said.
Their entire backup plan was to fail over to an identical secondary system that was supposedly redundant. But, it was clearly sharing the same database system as the primary, thus they didn't actually have a fully redundant system. They had 1 system with some parts of it having a secondary, i.e. not an actual DR / failover plan.
>It's okay to not organize your code. It's okay to have files with 10,000 lines. It's okay not to put "business logic" in a special place. It's okay to make merge conflicts.
I absolutely disagree. It's "okay" if you're struggling to survive as a business and worrying about the future 5+ years out is pointless since you don't even know if you'll make it the next 6 months. This mentality of there being no need for discipline or craftsmanship leads to an unmanageable codebase that nobody knows how to maintain, everybody is afraid to touch, and which can never be upgraded.
You don't see the overhead of throwing discipline out the window because it's all being accrued as technical debt that you only encounter years down the road.
At big companies, too often do the people in charge of the product seem to forget what core product really is.
I reported it and it was fixed, but it's beyond me how a supposedly security focused company can let such a severe bug in such an important yet simple feature get to production.