This is the part that worries me. If something happened like this even 300-400 years ago, it would probably just wipe out that village.
559 karma · joined December 6, 2019
This is the part that worries me. If something happened like this even 300-400 years ago, it would probably just wipe out that village.
Important takeaway though is Microsoft didn't give up even though the first XBox as a whole was a loss for them AFAIR.
That wouldn't be a viable business model for the ransom group; Any accessory manufacturer or news site would likely get in a legal entanglement for buying trade secrets.
I had stuff like this happen to me in school; my family was not well off, so it was a fun prank for the kids who had money to 'accidentally' break or lose my things that I couldn't get replaced.
Remember, classism is taught early.
I really like the Logitech K700 solar keyboards, with two caveats:
- In a couple of mine, the included battery seems to have lost the ability to keep a charge well before you would expect (i.e. a year). This is a bit of an annoyance in that it is a rechargable button cell, not your run of the mill AA/AAA sized NIMH/Lithium bit.
- The build quality on these as far as sturdiness/etc isn't great. And if it ever gets 'flexed' too much, you wind up with broken traces internally, leading to issues where the juice doesn't flow one way or another unless you flex it back in the right way.
I love them in the office, but at home they just don't handle the use of clumsy roommates.
Sounds about right. When my brother was green in his automotive supply logistics career, there were a couple of times he got thrown on an airplane with a carry-on of parts...
If your entries are simple enough (add/remove/update) and can be expressed as messages, wiring up a simple pub-sub cache is an afternoon project.
That time range (probably-not-coincidentally) is when the Gas shortages happen.
This is interesting to think about. Transportation/logistic advancements in the first half of the 1900s allowed pricing at worst to stay consistent over a long period of time, at best allowed companies to increase their profits as supply chains were established that made transporting completed product cheaper. Thinking about things like trucks etc here.
- arrays (which most collections use under the covers) will need to allocate `elements*size_of_struct`. Unless the structs are the same size, you'd have to do some level of thunking/offsetting.
- Even if they are the same size, when you're iterating the list, how would the runtime know whether it's `A`, `B`, or `C`? Structs don't have header information that can be used to infer the type, it's only whatever fields you've defined (with padding potentially). Part of 'boxing' is essentially thunking the struct by wrapping a methodtable for the struct into the object [0].
If you need something like polymorphism with structs, your best bet is to make the struct itself quasi-polymorphic (i.e. with enums) and/or start abusing generics in some fashion I haven't yet figured out.
[0] - https://mattwarren.org/2017/08/02/A-look-at-the-internals-of...
Devil's in the details, but there -is- AOT compilation[0]. While it hasn't been released as an official product, it has been used for a few projects including a commercial game [1]. And yes, they're looking into the next steps to make it a 'released' thing.[2]
[0] - https://github.com/dotnet/corert/
[1] - https://github.com/dotnet/corert/issues/8233#issuecomment-65...
[2] - https://github.com/dotnet/runtimelab/tree/feature/NativeAOT
EF Core -can- be better than the older, much more reviled EF as far as generated SQL, but in EF core 3 they did a pretty big breaking change on joins, bringing behavior closer to EF6's tendency to do a cartesian asplosion
On some level it depends on what 'slacking off' means.
I've had employers where 'slacking off' meant actively doing some %mundane/repetitive/unnecessary% task with every moment of my free time. We were literally pulling the finish off the counters; there was no need to keep dusting them.
I've had software shops where reading integration documentation was 'slacking off'.
An interesting data point; In Germany, MS Office doesn't track how long you have been editing a document. My understanding is this is because the law there more or less says if you pay someone to do a task, you aren't supposed to (i.e. can't) care about how long it took them to actually do it as long as it was done on time.
So I guess that's my problem. There's a very fine line between employers using surveillance to catch 'bad actors' and employers using surveillance as another tool to bully substandard work conditions onto people.
This is just a near-NCAA tier play by the company to make money off child labor. Change my mind.
That doesn't answer whether they were less optimized because someone on the Red team realized that was a good idea.
Screw actual utility, this is about revenue, plain and simple.
For most cases yes. I don't know the exposure risk of Hertz in this regard, but in a Chapter 11 it's worth remembering that any people who are legally owed money (i.e. unpaid lawsuits) are counted as 'creditors', I think based on how the GM/Chrysler bankruptcies played out, 'unsecured' ones at that.
After the CD-I debacle, Nintendo was not at all on-board with the idea of disc-based storage. One of those reasons was loading times.
Another was likely that they had concerns about games that were more 'FMV' than game; This really -was- a legit problem in the 90s. By keeping things constrained, it limits the temptation for a publisher to push out a crappy title filled with cutscenes.
Due to the hilarious nature of the business, getting an S3 account to use for 'local' (i.e. dev machine) development was a huge chore.
We wound up creating an Interface to abstract our usage of S3, and wrote a 'local' provider that just used the local filesystem. Of course, many use cases that would not work....
But the big -advantage- of it was, we at least knew that if we ever wanted to switch away from S3, it wouldn't be hard. The Interface had a spec that could be used to ensure that any plugin would work with our application's usage.
It wasn't -that- much more work.
There's only so much fresh water you can take from a natural source before you have an impact on wildlife order(s) of magnitude greater than what we've already done.
No but it could speed it up. I'm certain plenty of big enough retail operation has a spreadsheet somewhere tracking the ROI on potential automation endeavors.
> Fortunately, I have other grocery stores in the area and can spend my money at the one with the best quality AND service.
Agreed, but are you in the majority with that? There's people who don't care about the long term impacts of, say, buying from an online retailer versus a local bike shop, but there's also a decent portion who's incomes mean it's either take the choice that's a little destructive to society, or not have any even-close-to-nice things for yourself.
You can look up carrier data on a phone number easily enough, and if you're in the industry you have a general idea of which carriers are the ones that actually follow the rules for registering a number. You filter on the ones that don't.
Is it a genuine desire to forgive? Or is it out of fear/undesire to relive the experience?
I honestly don't know and it's not my place to guess, but it's a problem that we see in other areas too. This line of reasoning is part of why DV cases move forward even if the victim doesn't want to.