Thanks for your work! Out of curiosity, do you know why this project chose to go with Java as it's core? Great to see you're also supporting TS + Rust out of the gate
Zero. There's no market for consumer archival-only storage; magnetic tape has been an enterprise-only product for 20+ years. Even write-once formats are barely holding on; recordable Blu-Ray production ended earlier this year.
Great product, congrats on the quick sales! Big fan of robotics for a long time myself. If you're in need of some website development, I'd love to chat >>hello at joshmleslie dot com<<
I've just started reading that link so I apologize if this is redundant, but would you elaborate some? What sorts of considerations / limitations exist? What would allow an app/site to run better on this platform?
TLDR-Cloud Phone is actively developed and newer, while Opera Mini is outdated and hasn’t received a major update in many years
There are two components to a remote browser like Cloud Phone or Opera Mini: the thin client that runs on device, and the server that performs remote transcoding and rendering
Opera Mini uses servers with the Presto rendering engine that hasn’t been updated in over 10 years. It’s officially discontinued, and not used by any modern Opera browser for desktop. Opera Mini is also intentionally limited to reduce potential for abuse, since it’s a general purpose web browser. Abuse often looks like websites taking advantage of servers to perform expensive computation, like crypto mining. The Opera Mini Native client also hasn’t been updated in 5 years. It doesn’t support media playback (audio or video streaming), or asynchronous JavaScript execution
Cloud Phone is much newer, actively developed, and only allows published “widgets” to be accessed. Because widgets must be approved, the potential for abuse is much lower. It uses Chromium (currently v128), and supports many more modern Web APIs and asynchronous execution. SPAs and JS-heavy websites will work well on Cloud Phone, but probably don’t work at all on Opera Mini. Finally, the Cloud Phone client offers more capabilities including multimedia playback, access to the camera/ microphone, and other Web APIs like vibration and soon notifications and badging
I noticed your physician-view is just raw JSON. I had time on my hands and this sounded cool so I whipped up a quick desktop dashboard [1] based on the JSON I saw. Feel free to use / adapt / reach out about it. Either way a great resource!
Hey this seems like a great idea and has a lot of promise! If you're looking for a frontend / UI / UX engineer, I'd love to get involved. Either way, best of luck! Let me know - hello (at) joshmleslie.com
Technologies: Frontend Web (Angular, React, TypeScript, JS, etc.)
Résumé/CV: joshmleslie.com/resume
Email: hello@joshmleslie.com
Hello,
Senior engineer here with a broad background across the corporate and non-profit worlds. Experience in both engineering and leadership roles, looking for either, but preferring leadership, especially product management.
My background in industrial design and years of fabrication experience have given me a unique vantage compared to your run-of-the-mill software engineer. Read more on my website www.joshmleslie.com
in my exp, there's only a few good UI libraries out there which is part of it, but I think generally the "standard UI" is a thing much like it happened to architecture and then we got the reset of brutalist / modernism, to highly generalize.
Just thinking aloud, choosing between novel, unknown, and interesting UI/UX vs proven, reliable, and commonplace (read: boring) is always a toss up, coming down to the audience. Biz interests usually tend to the latter, which imo is good because you want people using the product, not thinking about how to use the product.
