Duckton
What is you basis for saying that?
> Nobody cares if you "experienced" something in the comfort of your own home.
By that rationale nobody would play vide games.
I believe it comes down to the experience. The experience of VR is simply not good enough to attract people.
Immutable, as a patient you would want to know exactly what your data looks like at any given time. Again insurance is a good example.
If the blockchain is private, could it not be part of the implementation that does the access checking? Can't part of the ledger be unencrypted while other parts are not?
It might be wishful thinking. It's just an idea I have floating in my head, as an actually useful real world implementation for a blockchain.
I shared the link in another comment, but you might find it interesting as well: https://journals.sagepub.com/doi/full/10.1177/14604582198663...
But as far as I understand, it should be possible for a user on a blockchain, to have their set of data encrypted in the ledger. It should also be possible to implement a sort of permission scheme.
So I am imagining, instead of relying on things like Epic Systems and other EHR systems, that control your data and might have incentives to not share them with other systems. One could imagine a EHR system based on a blockchain. The patient can then grant permission to, say a hospital, to read certain data from the ledger. This could be scoped to what is necessary in the context of their visit or procedure. After the visit to the hospital, the patient has full transparency to read what data has been added to their own records.
Anyway, I am not capable to give a full technical solution, since I have not thought it fully through, and not nearly knowledgable enough to actually know. So I might be very wrong in my assumptions, and would gladly be told otherwise if that is the case.
Then there's the whole issues of how do you get existing systems as Epic to integrate with said "blockchain EHR".
Edit: This might be of interest: https://journals.sagepub.com/doi/full/10.1177/14604582198663...
But the points you raise, are exactly the issues I've been thinking could be solved with web3. I am imagining using it to give control to the patient of who has read access(to what and when), who can add data, etc.
I.e. give full transparency and control to the patient. Instead of the current situation where a patients data is on different systems, you don't know what it actually says, besides what a doctor tells you.
Close is when I am done with that particular window/workspace.
Command+Q is when I’m done working in VS code entirely.
I love the fact that clicking the close icon of a window doesn’t terminate the application
Haven’t experienced this, not sure what you are referring to.
Also something I like. The fact that an installation is just moving an executable, is to me, superior to an entire process with regedit and what not.
As I said somewhere below, it might just come down to what one is used to and not objective facts.
I switch regularly between macOS and Fedora, and have windows on a ssd for gaming. I agree on the Command vs. CTRL bindings thing. It’s annoying when switching between the two systems.
I recently wanted to pick up unity, and decided to try it on windows. I have to say, as strongly as you find macOS annoying I find windows annoying. Fx system settings, for some reason when I have to change something it takes me ages to navigate through the UI to find what I’m looking for. But maybe it’s all just personal preference and what one is used to.
Just like you can have an app for iPhone, iPad and Apple Watch, all with their own UI to a more or less degree, you will now be able toinclude a macOS build as well.
I think it's about consolidating the UIKIt and Cocoa frameworks, making it easier for developers to share code between platforms, but not necessarily creating a UI that's the same for both.
I think attempting to use Swift on a Linux server would be a big nuisance
I beg to differ. Look at Vapor, Kitura & Perfect.
I know Foundation is missing implementations for Linux, but it is not something that makes it a big nuisance IMO.You can quickly have a setup with Swift on Linux running a simle CRUD app.