Readit NewsDead Comment
Most Facebook users will never even know about this renaming.
It can also speed up your queries as it allows better caching of the query plan.
It always annoys me when SAST products on detecting injection advise using better input validation. No! Use parameterised queries and be done with it.
I am neither an Unreal nor games developer, but in case nobody provides a better answer...
From what I've heard, what makes source control tricky for game development is all of the non-text files.
Git's distributed "everybody has a local copy of the entire repo" approach is not well suited for binary assets, especially large and frequently changing ones. Nearly any "modern" game development project will have gigabytes if not terabytes of these. Imagine you're a game coder and every `get fetch` grabs another 400GB of textures from the level designers.
Last I heard many game dev shops still used Subversion instead of git for precisely this reason.
There are also workarounds/extensions for git; not sure of their maturity/adoption.
Why is it the most important part? As you said this is a main-stream headphone review.
From my experience, most consumers don't enjoy listening to music w/ a flat curve - if that is where you're going with this. I've sunk several thousand dollars into high-end gear, and even I don't want a flat curve. A flat curve is most useful if you are an audio engineer working in a studio. I'd much rather use different headphones for different kinds of music, than compromise and use a flat-curve which sounds incredibly boring (to me).
Take this as an example: https://en.wikipedia.org/wiki/Robotnik_(1894%E2%80%931939) This newspaper was first published around the time of the authors life. It has no connection to the slavery just to the labour and labourers.
There is a lot of misinformation on the web around Vitamin D, such as that even high amounts (>= 5000IU) are tolerable and safe. After a blood test showed me Vitamin D deficient, taking 5000IU (that size is readily available over the counter at my grocery store) daily gave me disturbing heart palpitations, which I didn't realize were related to Vitamin D until after thousands of dollars in tests showed my heart to be perfectly healthy. It wasn't until I had slacked off in taking the vitamins and then started taking them again that I discovered the connection. Apparently magnesium has something to do with it, but IANAD. (I was not taking magnesium supplements at the time.) I can tolerate 1000IU occasionally, but people need to be aware that not everyone tolerates supplements (especially high doses) the same.
I was happy to see the article you linked to above only claims Vitamin D is considered safe up to 4000IU. Although IMHO, after my experience, anything over 1000IU should require a prescription. Of course nothing would stop people from taking five 1000IU OTC doses to get 5000IU, but I think most people know better than to take five of the same type of vitamin daily without talking to their doctor first.
I do not doubt your experience, but it seems incredible to me that just a 5000 IU supplement gave you heart palpitations. Then again, I've also read many reports about incorrectly labeled products (e.g. milk, supplements, etc.) which contained far more D2 or D3 than what was written on the tin, causing toxicity.
Still, they are playing catch-up here.
So from that perspective, Kotlin is playing catch-up.
Usually breaks are caused by humans (ships pulling anchors, sabotage/spying). Sometimes they're natural (caused by wildlife, ocean floor movement, flaws in the cable design).
Fixes usually take a few hours if they happen at the endpoints, or weeks if they happen somewhere under the ocean.
Interestingly, spying breaks always involve three simultaneous breaks in the cable. The cable is broken at two points, and then broken at a third point in the middle to put spy equipment. They do this so the people operating the cable can't tell where the spy equipment was inserted, since otherwise you can tell where a cable is broken or being tampered with by sending light down the cable and seeing how long before light reflects off the broken bit and comes back to the end.
Using statistical methods, you can see how frequently you'd expect a cable to break at different points along it's length simultaneously, and it happens a lot more than raw chance would suggest.
IIRC at BSidesLV last year there was a vendor selling optical splicing modules which were rather difficult to detect using this technique.