Our great sponsors
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
-
Nim
Nim is a statically typed compiled systems programming language. It combines successful concepts from mature languages like Python, Ada and Modula. Its design focuses on efficiency, expressiveness, and elegance (in that order of priority).
-
zig
General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
-
v
Simple, fast, safe, compiled language for developing maintainable software. Compiles itself in <1s with zero library dependencies. Supports automatic C => V translation. https://vlang.io
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
nelua-lang
Minimal, efficient, statically-typed and meta-programmable systems programming language heavily inspired by Lua, which compiles to C and native code.
-
All can compile to C and I find it somewhat important as would be very happy to share same code base with microcontrollers (SDCC), Android, Linux, Windows and web wasm. Unfortunately (to my knowledge) not all offer optional or selective garbage collection, some look immature and so on :-(
This is what spooks me out most for now: https://github.com/vlang/v/issues
Yeah, I find the license on V UI to be a bit weird. Not understanding the logic behind it, as GPL is a definite way to cause massive headaches, drama, and confusion. GPL can give an unfriendly impression to those they probably could use help or support from.
It's still the early stages of the library and the language, so maybe it won't turn into some kind of mess. Still, not seeing why they didn't at least go LGPL, like many other projects have done who went. Seems like LGPL would have been the right balance to prevent sending mixed or "warning" signals.
There is also VIUP (https://github.com/kjlaw89/viup), which is a port of IUP. That's under the expected MIT license. So, it's not like more adventurous types can't go play with that.
You've inspired me to create this: https://github.com/xigoi/nimdenter/
>Whoever writes such code should be shot. There are newlines for a reason. And I am glad we have format-on-save these days. Less bikeshedding, exactly of the kind we're doing right now.
So do you use indentation or braces to read code? If the former, what are you complaining about? If the latter, why would you use a tool that adds indentation when you already have braces?