4 ms·
Micro also has zero drpendencies after it's compiled. And Go makes cross compiling easy as childsplay: just set two env vars, type go build and you're done. I'
by petre 9y ago
Micro also has zero drpendencies after it's compiled. And Go makes cross compiling easy as childsplay: just set two env vars, type go build and you're done.
I'd love a working replacement for Sublime Text written in Go rather than all of these Electron based editors. Lime Text is kind of alpha quality.
- ericfrederich 9y agoAs easy as childsplay as long as your target is supported. I cannot run Go code on my router which runs OpenWRT... Nano works there just fine.
- petre 9y agoGo was likely never intended to run on space constrained platforms like Broadcom MIPS, but point taken.
- lewiseason 9y agoWhat?
- int_19h 9y agoFun fact: on Linux, mac OS and BSDs, it does that by invoking syscalls directly. Syscalls are not considered a stable API on those systems by their respective developers. This means that your precompiled zero-dependency binary will just stop working next time Apple changes or removes a syscall: https://github.com/golang/go/issues/16570 https://github.com/golang/go/issues/16570. Coincidentally, code written in C doesn't have that problem.
- exDM69 9y agoLinux considers syscall API stable and there's a pretty hard rule of not breaking user space.
- int_19h 9y agoLinux does, yes. MacOS and BSDs do not. (Neither does Windows - but so far as I can see, Go doesn't try to invoke the NT APIs directly there.) Stability is guaranteed on userspace API level - e.g. libc. So well-behaving apps are supposed to just use that, and let it handle syscalls. But Go doesn't.
- mnd999 9y agoFreeBSD also doesn’t break the ABI on major versions.
- int_19h 9y agoThat's good to know, but it still means potential breakage every 2 years on average.
- pjmlp 9y agoHistorical accident, it is all a matter how libc of a specific compiler was implemented.
- int_19h 9y agoI would rather say, it's a matter of having libc and kernel developed as a single package ("base system") by the same people, and versioned together, versus having the kernel and the userland separate.
- yazan94 9y agoI am not all that familiar with kernel/low level programming, but wouldn't the C API/library internally use syscalls as well? If a C program is written with a dependency on a syscall, and this syscall is changed. Does the code still work after, or does it need to be recompiled with an updated compiler?
- jjnoakes 9y agoThe system's C library would use the syscalls directly and the application would use the C library routines. So if/when the OS updates the syscall ABI, it would also update the system's C library to use the new syscalls, and the application would continue to use the stable C library API and get the new syscalls under the covers automatically.
- int_19h 9y agoThe compiler doesn't really play a role in this. If a syscall changes, then you'll need to change the arguments in the C code that invokes it. The system libraries like libc themselves use syscalls internally, yes. But on those platforms I'm talking about, they're maintained by the same people who maintain the kernel, and both components are versioned together. So they can go and change a syscall, and then also make the corresponding change to libc (without changing the latter's public ABI), and ship the updated versions together as the new OS release. Well-behaved apps dynamically link against libc, so the change is completely transparent to them. On Linux, different people maintain the kernel and libc (and, in fact, there's no single officially blessed libc - this is one case where the old adage that "Linux is just a kernel" is in full force). Consequently, the interface between the two has to be treated as a public API, with stability guarantees.
- deleted 9y ago[deleted]
- atilaneves 9y agoUnless you'd want to contribute, why would you care what language it's written in? Why Go and not C++, Rust, D... ?
- FullyFunctional 9y agoBecause you want to run it on your favorite platform, which might not be x86 and thus need compiler support? I wrote my own editor for exactly this reason: to always be able to have it on any platform.