If that is what you believe, I would encourage you to check out these two books on the subject [0][1]. Both are engrossing reads, and paint a damning picture of the regime from different perspectives.
I have taken a strong amateur interest in North Korea for years, and the full body of press, reporting, and firsthand accounts I have read would support the comparison to Nazi Germany.
operating from the premise that most applet exploits functioned by elevating a sandboxed applet out of its sandbox (no idea if thats accurate), perhaps because java applets had an un-sandboxed mode built in, whereas wasm is always sandboxed and has no equivalent to applet's un-sandboxed mode.
It's a bit tricky. I don't know if you can categorically say wasm is or will be more secure than applets. Both of them rely on a runtime that is more privileged than the code being executed, of course. Both of them can have runtime bugs that allow privilege escalation of various forms. There was a recent perma-root bug in ChromeOS and one of the exploits along the chain was based on exploiting a WebAssembly runtime bug.
If you look at Java's security track record in recent years, there's been just a couple of zero days in the past five years. That's probably a mix of genuinely better security and less attention due to being kicked out of web browsers. But if you go look at the security histories of other sandboxes like browsers or kernels, it starts to look pretty good. A new paper that just came out introduced a new Linux kernel fuzzer and discovered, I think, over 30 zero day exploits across several different Android phones. So ordinary UNIX style process isolation is pretty useless if you can reach device drivers from inside the processes. Even the quite aggressive and resource intensive browser sandboxes that browsers use routinely have escapes, often because they're always adding large new attack surfaces like WebAssembly, WebGL etc (all written in C++).
very interesting, did you read about the linux kernel fuzzer and the ChromeOS root here or elsewhere? regardless if you can provide a link either sound like very interesting topics.
I brought in outside help (partner). Business is still ticking along nearly 3 decades later (though original partner has since left), so I guess it sort of worked. Hardest times though, was one of us forgot to wear one of the hats for an extended period, and just got comfortable or focused on wearing it.
Wow, congrats on your success. Very impressive. The Blaze site looks great BTW. Would you be willing to share some of the secret sauce of running a successful software shop for nearly 30 years?
Thank you! Full disclosure, Blaze is my second software business, and has been going for 22 years now. My previous one ran for about 8 years.
In short, it is really about providing great customer service. I am lucky enough to work in a small town where word of mouth referrals are critical, and doing a good job and genuinely caring about your customers gets you noticed and gets people to stick to you loyally.
Plus I have a genuine love of learning about how other businesses operate, and get a kick out of improving how they can run using my software.
But as I get older, I find that my energy levels aren't suited to one on one development and constant support, hence my second all cloud based SaaS startup in my sig - really it is phase 2 while I scale back my personalised face to face customer support and explore a more distributed way of doing things on a global scale, rather than local.
I'm just getting started on this path, and I'm really starting to see that like you said, excellent customer service--not beautiful code or elegantly applied computer science principles, etc.--is the most important thing.
Now I just need to figure out how to establish that network and reputation. Thanks again!
are you referring to the lifecycle events like onResume and onPause? You can approximate those with iOS using a combination of viewWillAppear and UIApplicationWillEnterForegroundNotification
I am referring to those. If someone just tries to make Swift the platform, I think they will have to put as much thought into their tooling as xamarin, cordova, etc.
