There's no WASM involved and the BEAM is not running on the device. It works like LiveView, except instead of an HTML DOM you have a SwiftUI hierarchy. The client side of LiveView is a SwiftUI view itself, you can use many standard SwiftUI views, and also add your own custom ones for when you need something bespoke. It can be the whole app or just part of one.
This was posted previously[1]. I am reposting because the "Permissive Security" option that appeared to allow operation of the operating systems has been removed. Wayback Machine[2] has captured the original page. I'm not sure if they are changing their stance or what, I was under the impression this would be allowed. I had to add a new param to bypass dupe detection, I think this warrants a new story. The heading you want to look at is here[3]
Poking around in the weirdness that is Solaris is so much fun. The comments in the source code are legendary as are the man pages, seemingly much more helpful than other platforms, with a focus on providing good examples. Zones, DTrace, ZFS, and SMF are incredible tools that were over a decade ahead of their time. Zones in particular seem to still offer isolation advantages over the various implementations of containers on Linux. Designing a cohesive system for containing multitenant workloads had its advantages. I'm glad enthusiasts have been able to keep Illumos going, it would be a shame for nobody to be running all that code.
This is a very cool project, running Erlang on an ESP32 is impressive. The supervisor trees and other parts of OTP make the platform a good fit for certain embedded projects. Nerves is a great tool as well but of course it's much higher level, with a full Linux distro running under it on a Rasperry Pi or Beaglebone Black, which are much much more power-hungry than an ESP32.
There is a middle ground developing in the GRiSP[1] project as well. It uses the RTEMS RTOS to provide basic POSIX compatibility that allows the full BEAM VM to operate on lower powered hardware[2]. Work on GRiSP 2 seems to be progressing slowly, but it's a cool project and definitely worth a look if you find projects like AtomVM interesting.
I really look forward to seeing what can be done with Postgres's pluggable storage backends that were recently added. It seems that some of the issues with treating a table as a queue could be mitigated with special storage backends designed for such a job.
Yes, I've reported a bunch of these as well. Basically any sort of corporate action (split, reverse split, merger, etc) seems to completely screw up their "gain" calculations, which are prominently displayed throughout their app. This basically makes it impossible to determine your returns, unless you have a paper record somewhere. Many of the cases I've run into here also completely lose the record of what you paid and how many shares it was for. I'm hoping their new home-grown clearinghouse generates my tax info properly...Still looking for a better option.
I'm an experienced director looking for new opportunities. I've spent most of my career in health tech startups, so I have a lot of experience with healthcare integrations, but also domain knowledge like billing codes, HEDIS measures, HIPAA compliance, etc. I would love a position where I can utilize this experience, but am not locked in to health tech. I have a lot of tolerance for decrepit systems, and find the challenge of making their data available to those who need it an enjoyable experience. I'm a big proponent of async work culture, so I'm seeking remote leadership positions (management if you're fully distributed, or IC), for the right opportunity (> director level, top IC on a new and exciting project, great learning opportunity) I will commute to an office. Contract work considered on a case-by-case basis. If any of this sounds like you, please get in touch. You can book time with me directly at https://bbhoss.io/hireme
I'm an experienced director looking for new opportunities. I've spent most of my career in health tech startups, so I have a lot of experience with healthcare integrations, but also domain knowledge like billing codes, HEDIS measures, HIPAA compliance, etc. I would love a position where I can utilize this experience, but am not locked in to health tech. I have a lot of tolerance for decrepit systems, and find the challenge of making their data available to those who need it an enjoyable experience. I'm a big proponent of async work culture, so I'm seeking remote leadership positions (management if you're fully distributed, or IC), for the right opportunity (> director level, top IC on a new and exciting project, great learning opportunity) I will commute to an office. Contract work considered on a case-by-case basis. If any of this sounds like you, please get in touch. You can book time with me directly at https://bbhoss.io/hireme
Heaven forbid users choose to trade performance for a more usable browsing experience. Ads/tracking vs blocking is a war, and preventing blockers from running arbitrary code will cripple blockers, allowing technology to be developed by hugely funded ad companies that effectively bypass blockers due to these limitations. Providing a blocklist is completely insufficient for totally blocking ads and tracking, as anyone that has used the content blockers on iOS has observed.
Reforming private prisons is just a small part of criminal justice reform. This is a good step but it seems like many are unaware or are ignoring the impact that labor unions have on overcriminalization. Police and corrections unions exist all across the country and share many of the perverse incentives that private prisons do.
There's still a lot to learn about this incident, but most likely the RubyGems account was compromised, allowing the attacker to upload whatever they wanted. Signed releases with a web of trust would be ideal, but I doubt we'll ever see that world. A simple and pragmatic solution would be to have the next version of bundler support the ability to only install packages published with 2 factor enabled, then the next major rails version default it to on, with plenty of advanced warning in 6.x/bundler. This still has plenty of gaps, such as an attacker being able to take over even with 2 factor, and then re-enabling it with their own keys, or RubyGems.org itself being compromised. It still represents a major upgrade in security for the entire Ruby ecosystem without causing much pain to authors and users.
Unfortunately the problem is much greater than engineers not understanding doctors and other clinical staff, in my experience. For startups that want to sell to health systems and similar-sized/larger entities (really this is the minimum size that can work for most startups, practice sales usually have more friction than value), you unfortunately have to focus on the buyer, which is very rarely someone who is "in the trenches." Best case scenario, having software that is compelling to the end users can help you get your foot in the door early on, but actual adoption will only happen if you can convince the business stakeholders of your value.
In the US healthcare system, clinicians and the business often have opposing objectives and values. This is starting to change with value based care becoming more popular, but it's still all about providing what the business wants, it just happens to align with the clinicians more these days. You'll still need to support IE9 due to that botched Vista upgrade, build out a custom EMR integration, and deliver whatever random feature the sales folks promised (can you automatically fax things?) before you can move on to the features that the clinicians actually want.
The system itself is how we ended up with billing-driven documentation EHRs like Epic. Paradoxically, due to massive adoption, I think Epic and Cerner are some of the only places where real innovation could happen. I think even huge companies like Apple, Amazon, and Google will have a hard time breaking into the space, no matter how much cash they throw at it. For them, the only answer is to go fully vertical like Kaiser-Permanente, but I doubt they have the stomach for this.