4 ms·
Minor nit. Every language you mentioned with a GC is not a systems language.
by echelon 8y ago
Minor nit. Every language you mentioned with a GC is not a systems language.
- sl1ck731 8y agoGo is a systems language. The term isn't confined to device drivers. It includes platform/backend software such as web servers and things like message queues or the Docker ecosystem. The term is nebulous though.
- echelon 8y agoThat's wrong! Those fall squarely in the application domain. By your argument Ruby and Python are also systems languages because they can be used to write servers and job queues. You're not doing real time programming with Go. Don't make systems programming lose its meaning by promulgating this myth.
- sl1ck731 8y agoReal-time programming can be done in any language, Java for example. I think you're conflating writing device drivers/kernels with systems programming, which includes those things but is not limited by them. Regardless, the term's meaning can't be lost if its apparently this hazy.
- zepolen 8y agoI don't think you understand what real time programming is.
- sl1ck731 8y agoEnlighten me, please. https://www.aicas.com/cms/rtsj https://www.aicas.com/cms/rtsj http://blogs.windriver.com/wind_river_blog/2017/05/java-on-vxworks-using-micro-runtime.html http://blogs.windriver.com/wind_river_blog/2017/05/java-on-v...
- echelon 8y agoThis is swapping out the JVM. It's not even the same language at that point.
- sl1ck731 8y agoMaybe it would be easier for both of us if you wrote the definition for real-time or systems programming, rather than just saying something isn't one or the other.
- crimsonalucard 8y agoLook, a good systems language should have predictable assembly instructions that the code compiles into. You should be able to literally with your eye map from code to asm and jump back and forth in a systems level language. GC enabled languages don't have this property as the assembly would be littered with GC code to clean up things. You won't be able to map back and forth. You will note that rust advertises themselves as a systems level language and it is deliberately designed with the term zero cost abstraction. All this means is predictable asm from code. No black magic. Rust is advertised as systems level and this is the property that enables it. I hope that allows you to understand what it means to be systems level. I truly believe that you are completely wrong and only few languages nowadays are system languages without a GC. C++, C, D (when used without the GC) and rust are examples. All the other languages you listed aren't.
- sl1ck731 8y agoThis is what I was looking for, and I truly believe you are completely wrong as well. I follow the line of thinking that includes utility software and backend services/platforms as described here: https://en.wikipedia.org/wiki/System_programming_language https://en.wikipedia.org/wiki/System_programming_language Hence, the word has different meaning from person to person. So there is no wrong, or at least it exists on a spectrum, and everyone complaining about the original comment's word choice is just jerking their ego off.
- nimmer 8y agoWrong. A system language should at least build shared objects for other languages. Nim can, Go cannot.
- tedunangst 8y agoEh... https://github.com/mit-pdos/biscuit https://github.com/mit-pdos/biscuit
- meruru 8y agoThat's not a minor nit, that's a digression from object-level discussion to arguing about word definitions.
- pjmlp 8y agoHaving a GC is not an impediment for systems language, for example: - Algol 68 - Mesa/Cedar - Sing# - System C# - Modula-2+ - Modula-3 - Oberon - Oberon-2 - Active Oberon - Oberon-07 - Component Pascal - Lisp (regarding Lisp Machines and its derivatives) - Java (when deployed bare metal on embedded devices, e.g. Aicas, PTC) - Swift - D - C# (when used alongside .NET Native, IL2CPP, CoreRT, Netduino, meadow)
- rurban 8y agoYour argument that a systems language must be memory unsafe relates only to current practices but not to science. science would rather prefer memory safety in systems.