kitplummer

Am I the only one wondering why anyone would keep "sensitive" information on a phone?? Let alone taking that "sensitivity" with you where ever you go? And across a border with out-of-control control?

Or am I the only one who thinks that there is equal risk of someone inserting "sensitive" information into any device - for whatever purpose - without the phone's owner even knowing.

Zero trust peeps. Zero trust.

Curious about FIPS compliance of the crypto modules, any insight?

The raw point is valid. Sure this a poorly edited article and lacks the best research - can we agree that like almost everything, we've engineered these things to be commercially short in terms of life-span, let alone not super-sustainable in terms of manufacture or maintenance? Aside from the continuously performance-oriented standardization shifts, the specialization of bicycle types is doing a disservice to sustainability. Also, the "electrification" of bicycles is a completely separate argument - from all angles: manufacture, maintenance and longevity; one that is no different that all EVs. TBH, this article reads like a ChatGPT dialog.

Unfortunate that we've missed another opportunity for healthy dialog around the benefits of the bicycle.

That exists, it is just hidden right now. If my intent was to offer this up and a for-the-public-good I'd turn it back on. But like most of the other comments here, at some point it just doesn't make sense for me to foot the bill to run it. It would be one thing if it was a simple front-end, with a simple back-end. But processing this insight is a little bit resource intensive which creates a cost burden. Academically it wasn't a big deal to run this in a true HPC, the costs have already been covered. Commercially is a different calculus.

Funny...I think posting here has generated a few clicks. Am seeing my background worker dying. :)

Right, so the moral of the story centers on the target user of the CLI tool. If you're building something for the Elixir community - game on I suppose, though there is still the complexity of build-env per OS/arch.

I wonder where WASM/container enters the discussion.

Absolutely both.

But...the issue is packaging/distributing a CLI built with Elixir. Comparatively to building a CLI in something like Rust, there is a lot of overhead that comes with a VM-based language and framework. Especially if you want to target multiple OS and processor architectures (or distributions). Not to say that it is impossible, just maybe not as simple. It is one thing to run Mix tasks, or access the Owl API from REPL, it is another to run an Owl-based app on macOS, Linux and Windows and get it there.

I like my Framework with Ubuntu. Wish it wasn't Ubuntu but everything works.

Is there a Heroku-like service for any of the unikernels yet?

Another interesting aspect of the PS3 is it was one of the first OTS device platforms that integrated hardware DRM.