return_0e
Joined 12 years ago
Karma
848
Submissions
63
Member since
Sep 2
[ my public key: https://keybase.io/return; my proof: https://keybase.io/return/sigs/h3qu1Dsu0pfzOTaYFmVrKiZu6j8Y39IzW63uesY2zDU ]
View on Hacker NewsRecent submissions
Comment · 2 years ago
I can't change the link now but this should be the correct link to the post: https://discuss.haiku-os.org/t/progress-on-porting-firefox/1...
Comment · 7 years ago
Not an optimising one (yet) but a safe implementation of a malbolge interpreter written in Rust, which can run malbolge programs. Just for fun.
Comment · 7 years ago
Yes, I find that The Dragon Book to be a fundamental reference in my university days of studying compilers. Even so, many sections of it are still relevant to this day.
Also, I think I might have seen your name before whilst looking at the Solaris port of Go years back. Mind you, I'm looking at bringing Golang to Haiku (0) with similar changes like Solaris and Windows.
(0) https://github.com/golang-haiku/go/tree/golang-1.11-haiku
Comment · 7 years ago
This is very interesting as this is almost identical to how the Haiku Operating System does package management using their own packaging format (hpkg) which uses packagefs. [0] [1]
This format is used more than just to package applications, but to update the whole OS in a consistent manner [2] as it is also versioned in with shared-libraries and this was implemented in 2013.
[0] - https://www.haiku-os.org/blog/zooey/2011-01-08_package_manag...
[1] - https://www.haiku-os.org/guides/daily-tasks/install-applicat...
[2] - https://www.haiku-os.org/blog/bonefish/2011-06-20_package_ma...
Comment · 7 years ago
I haven't implemented PASETO but I was thinking about adding support for another language. If I were to implement it, I would just use libsodium for most of the cryptographic primitives whenever possible since the reference PASETO implementation uses it as well as most of the other language implementations too (Except for the Go version).
PASETO does seem like a cryptographic secure alternative that addresses the pitfalls of the JOSE standard and has most of the mitigations mentioned in this blog-post (No cryptographic-algorithm agility) and it supports the same functionalities of JWT/JWE and JWS. So I am convinced on getting that standardized, but it also needs XChaCha20-Poly1305 AEAD to be standardized too [0].
Fernet was also around as being a secure alternative, but it has been mostly replaced by Branca [1] and PASETO.v2.
[0] - https://github.com/bikeshedders/xchacha-rfc
[1] - https://branca.io
Comment · 7 years ago
Newgrounds.com [0] is a community of artists, creatives and game devs that still use Flash for their content and they are still alive and well today.
[0] - https://newgrounds.com
Comment · 7 years ago
As for virtualization, Fuchsia already has its own KVM equivalent called Machina which so far can run Debian on top of Zircon and with several compatibility changes for supporting the ART runtime in Zircon already merged in, it should be also possible to run Android apps with this.
But perhaps the reason Fuchsia won't struggle unlike the other OSes you mention, is that it is possible that it will be compatible to run all the Android apps in the play store from day one, thanks to Machina; allowing a smoother transition, a process similar to what Apple did with the PowerPC to X86 switch but in Google's case, its for a completely different OS.