Hashex129542
Joined 2 years ago
Joined 2 years ago
I did same hack and rebranded then sold. That's the main concern. Anyways, we are thinking to go with system WebViews. It's still interpreted but requires some hard time.
That said, we're building consumer-facing apps where long-term stability is critical. Our goal is to build once and run on any platform, across versions. Most consumers are already tied to existing platforms that provide services we can't easily replicate, which makes development of apps in a new OS or In a OS look like environment is a tough sell.
I must follow same technical mechanism as Java.
Streaming:
1) In remote, The server will provide chunks of data. Each chunk has predefined length.
Even in Text format you have to identify each chunks to process. `Transfer-Encoding: chunked` HTTP header for example.
> No local streaming in remote computer.
2) In local storage system you can stream any length of data from Storage Drive to RAM
Downloading:
1) In remote, The client will request chunks of data. You can request any length.
You don't need to identify the chunks. You can append the downloaded data without any process.
> There is Local streaming. The remote computer actually streams data from it's storage to RAM.
2) In local copying from peripheral device is also called Downloading. I've seen Downloading label in micro-controller burner.
Presenting, Storing or Deleting the either one data is your choice. Not only stream; also you can watch, listen, read the downloaded content also without storing it into actual drive or without finishing the download. It's all actions nothing to do with techniques behind the terms.
Before Swift 6, I've worked lot of unique projects both macOS and iOS and never spend time on debugging. I don't know what debugging time exactly?
So true.