3 ms·
What? Why wouldn't you have access to node? Source is available for those, and node even specifically addresses the BSDs[1]. I heard go does something kind o
by kbenson 10y ago
What? Why wouldn't you have access to node? Source is available for those, and node even specifically addresses the BSDs[1]. I heard go does something kind of odd with system calls, so I could see if possibly having a problem (but I really don't know enough to state definitively).
I'm not sure if rust targets that platform/arch combo, but I could see it being deferred while they focus on more common ones.
Edit: It just occurred to me that Node's (V8's) optimized JIT probably uses ASM or at least routines optimized for x86, so that would complicate deployment.
1: https://nodejs.org/en/download/package-manager/#freebsd-and-openbsd https://nodejs.org/en/download/package-manager/#freebsd-and-...
- TD-Linux 10y agoYeah, v8 is pretty famous for its lack of interpreter, though it looks like IBM is working on a port. You could also use the Chakra or SpiderMonkey ports.
- steveklabnik 10y ago> I'm not sure if rust targets that platform/arch combo It's the PPC bit that's tough at the moment, we do provide tier 2 support for {free,net}BSD on x86_64.
- kbenson 10y agoI figured. Although this isn't PowerPC, but Power, and what little I was able to find quickly seems to indicate the instruction set has evolved since it was branched for PowerPC. I imagine even if PowerPC targeted binaries work on Power, they wouldn't use the platform to the fullest.
- steveklabnik 10y agoOh yeah, right. Point is, yeah, not yet. I wonder what LLVM's support of these arches is.
- ajdlinux 10y agoI know that there is some work on porting Rust to ppc64le which is gradually coming together.