654 karma · joined September 22, 2011
People could not have voted with their wallet because there was no alternative. We're approaching the same type of problem with tech giants. People just want to ensure that components can be replaced and that the tech giants aren't going out of their way to prevent that.
I can't help but think about how someone with that mental state would feel while in the waiting room.
It is a legitimate question. People get heart inflammation from things like court visits.
If you know something then please share.
I can imagine the heart rate during this ordeal is way higher than normal and could trigger inflammation.
Not saying that the science here is invalid, just actually curious to know how this gets ruled out.
Also, the OP doesn't need to get rid of Google Photos. They can keep Google Photos as a off-site back-up.
We're probably going to see a wave of disruptions from technologies like GPT3.
For example, we might see something like this in the long term:
A) Someone will create a model to accurately convert low level source code to higher level source code that does the same thing when compiled down. Think assembly / machine code to high level code or even English descriptions of the underlying semantics.
B) At this point, why not pipe in some DNA/RNA into the model from A) to get high level insights
C) Give it a couple iterations and it might be possible to create a compiler. For example... C to RNA
D) Finally... solve problems by creating sequences from scratch instead of re-using bits from mother nature
If we ever do get to D), I sure hope no country tries to use this in a terrible way...
source: I've done this mod on a couple cameras and wouldn't recommend it for performance gains alone. It's a fun project, not much more.
Additionally, there are lots of people doing similar diy mods to DSLR cameras on youtube for astrophotography, usually with sub-zero cooling capabilities.
Simple code is easy to write, maintain, and optimize later. Despite the code looking messy, I find it easy to understand and navigate.
A counter example of truly confusing code, which kind of does similar things, would be something like this: https://github.com/ImageMagick/dcraw/blob/master/dcraw.c
Take a look at these:
Functionaly, I'm having trouble finding things. Half of it is just because it's new but honestly some of it is due to stretching information apart.
edit: author just changed it to shift-click
Another tip would be to give django-admin a try when building dashboard projects (you can customize the look and feel quite a bit, ours are usually unrecognizable).
If you ever find yourself bored, we could really use a reliable method of removing a camera senor bayer matrix. Bonus points if you can figure out how to deposit microlenses back onto the photosites after removal.
https://stargazerslounge.com/topic/166334-debayering-a-dslrs...