Ask HN: Anyone else use FreePascal as their low level language?
41–50 of 58 posts
Re: Ask HN: Anyone else use FreePascal as their low level language?
#42If you consider Go as a low level language, you might want to try C# which can be as low level as Go while having a lot of high level features. NativeAOT compiler allows you to statically link native libraries or create native shared libraries (.dll/.dylib/.so) that can be consumed from other languages. It's kind of 2-in-1 language, but the ecosystem is primarily focused on the high level part, so you can only depend…
Re: Ask HN: Anyone else use FreePascal as their low level language?
#43If you like go, modern pascal is basically that with less curly braces. The other way around is true, too. There’s zero technical reasons to not use pascal. Popularity, library availability, programmer availability and LLM quality of responses may be, but the technical foundation is there and has been for at least a decade (if not since turbo pascal from early nineties.)
Re: Ask HN: Anyone else use FreePascal as their low level language?
#44If you consider Go as a low level language, you might want to try C# which can be as low level as Go while having a lot of high level features. NativeAOT compiler allows you to statically link native libraries or create native shared libraries (.dll/.dylib/.so) that can be consumed from other languages. It's kind of 2-in-1 language, but the ecosystem is primarily focused on the high level part, so you can only depend…
Last time I checked, NativeAOT was only for console apps, i.e. didn't support any GUI frameworks.
Re: Ask HN: Anyone else use FreePascal as their low level language?
#45If you consider Go as a low level language, you might want to try C# which can be as low level as Go while having a lot of high level features. NativeAOT compiler allows you to statically link native libraries or create native shared libraries (.dll/.dylib/.so) that can be consumed from other languages. It's kind of 2-in-1 language, but the ecosystem is primarily focused on the high level part, so you can only depend…
You can get very low-level in C# but at the point you start using unsafe the nature of the language changes very suddenly. Unsafe C# is the most unsafe language I've ever worked with. Really terrifying stuff.
There's an interesting comparison of these C# features with Rust: https://em-tg.github.io/csborrow/
Re: Ask HN: Anyone else use FreePascal as their low level language?
#46Earlier quoted context omitted.
Last time I checked, NativeAOT was only for console apps, i.e. didn't support any GUI frameworks.
Avalonia and Uno both support NativeAOT: https://avaloniaui.net/ https://platform.uno/
ImGui.Forms is another one that supports NativeAOT.
Re: Ask HN: Anyone else use FreePascal as their low level language?
#47I've also been using Oxygene, which is a different Object Pascal dialect. (This started because I have begun working with RemObjects - I have to admit, I have wondered why I never used it earlier.) It had design decisions to evolve it more like newer languages (eg it has inbuilt async/await and did on .Net before C#, tuples, nullables etc) and sanitised the syntax somewhat. I like it a lot. https://www.remobjects.com/elements/oxygene/language
Re: Ask HN: Anyone else use FreePascal as their low level language?
#48Re: Ask HN: Anyone else use FreePascal as their low level language?
#49FP is an interesting language. In my opinion, it is somewhat problematic that different language concepts (Delphi, etc.) have been more or less merged into FP, resulting in redundant object models, for example. Pascal as a language also has various historical legacy issues (dangling else, block overhead, global namespace, etc.), which Wirth corrected in Modula and Oberon. The compiler is huge and apparently difficult…
Re: Ask HN: Anyone else use FreePascal as their low level language?
#50If you consider Go as a low level language, you might want to try C# which can be as low level as Go while having a lot of high level features. NativeAOT compiler allows you to statically link native libraries or create native shared libraries (.dll/.dylib/.so) that can be consumed from other languages. It's kind of 2-in-1 language, but the ecosystem is primarily focused on the high level part, so you can only depend…