csharptwdec19

At the end of the day though, Atlassian won't even sign NDAs with it's clients.

Make of that what you will.

The issue with remote unlock is that someone can enter the vehicle while it is off and wait inside.

> My wife once saw some AT&T contractors digging too close to the wrong fiber line at her facility when she was working for the Navy at a contractor site and unmarked black SUVs were there to take those guys away to God knows where within two minutes.

I used to do design/permitting for fiber networks and going around DOD areas/Fiber was always fun. You wind up having to submit your routes, and get vague feedback as to what you need to move, but never how far away/etc. Usually your best bet is to just go to the other side of the road if possible.

Same for C#. Any narrowing truncation needs to be an explicit cast. Widening is typically allowed implicitly, although in the case of the 'decimal' (128 bit struct representing a 'higher precision' floating point) type you still need an explicit cast from a 'double', since there are cases where that conversion can still change the value or fail (i.e. Infinity/NaN)

It's malice but from a different aspect; willful malice in the name of 'cost cutting'.

> 14nm was the first that everyone was on their own, because IBM failed their research. In the end, Samsung managed to get it done, and GloFo either failed or... didn't try really hard ? This is where I'm gonna speculate a tiny bit and be less charitable, I don't think that GloFo was sufficiently funded in terms of process development, despite their parent owner being able to.

For whatever it's worth, it feels like GloFo has had various process issues for a -long- time. While there were issues with the Bulldozer design itself from a deep pipeline perspective etc, the other factor in it's lukewarm lifetime (especially the first couple gens) was issues with GloFo's processes even back then. I know some of that was that they were trying to gear more towards bulk silicon vs CPUs but I think there were other issues too.

Fun fact: Actual Gambling machines are also audited on the reg.

A college friend works for my state's gaming commission. During a 'drinking talk' about digital signatures, she told me an interesting part of her job; not just going through the slot machines and validating the payout settings, but also checking the EEProms MD5 Hash* to make sure that it was in a list of 'approved' code hashes.

* - This was 15 years ago, I -really- hope they use something better nowadays.

Would that be a bad thing? Or would that mean we'd have healthier competition?

In Rural/cold areas, you might not be able to go full electric. CNG is an option in those cases though.

Not a perfect solution but sometimes perfect is the enemy of good.

The DC is a lot more watchable. The biggest benefit is the CG Sequences, which are used to replace some of the 'staring at the viewscreen' type reaction shots.

As for why it wasn't remastered at 4k, let alone 1080p back then, my guess is that the cost of rendering CG above DVD resolutions was a major factor.

It does make one wonder about oral traditions of 'cursed' lands...

Or if you are an elected official that gets lobbying from Buckeye Cable...

Frankly, there could be some value to OSS contributors in saying 'There is Telemetry' very up front, but also in the same breath telling people that instructions for disabling Telemetry is in the Docs.

Could help lower the number of GH issues that are filed because people don't read said docs...

You can get a 2 door cab on The Colorado, I think you still can on the Silverado and F150.

Most folks go with the 4 door option, so that's what dealers tend to stock, so you don't see them often.