I don’t understand how this language is planning on ever seeing adoption when it’s been restricted from open use since it’s inception. Seems like vaporware.
Porting 58k lines of D and C++ to Jai
11–20 of 264 posts
Re: Porting 58k lines of D and C++ to Jai
#12“In the beginning I hinted at expecting the porting process to go somewhat smoothly (which I’m sure I won’t regret later). The reason for this is that I have two systems in my game that will hopefully be immensely helpful in this endeavor:
- The game records the inputs (HID, loaded files, network, …) of a play-session into a file and replay them later. When replaying, feeding recorded input into the deterministic game loop leads to the exact same state, down to the bit.
- The game hashes game state at various points during execution and saves these hashes to a different file. When replaying, the contents of this file can be used to check that the execution of the replayed session exactly matches the original execution.”
Re: Porting 58k lines of D and C++ to Jai
#13Hard to get much out of this since the language is not available to everyone.
Re: Porting 58k lines of D and C++ to Jai
#14I don’t understand how this language is planning on ever seeing adoption when it’s been restricted from open use since it’s inception. Seems like vaporware.
See https://github.com/Jai-Community/Jai-Community-Library/wiki/... and https://github.com/Ivo-Balbaert/The_Way_to_Jai
Your links back up the statement.
The first says the compiler is proprietary and unavailable outside of some beta testers, but may be open in the great and nebulous future.
Re: Porting 58k lines of D and C++ to Jai
#15I don’t understand how this language is planning on ever seeing adoption when it’s been restricted from open use since it’s inception. Seems like vaporware.
See https://github.com/Jai-Community/Jai-Community-Library/wiki/... and https://github.com/Ivo-Balbaert/The_Way_to_Jai
> Supports x86 architecture only
No native macOS then?
> No virtual functions
> Jai is less dogmatic
okay
Re: Porting 58k lines of D and C++ to Jai
#16> ldc2 is awfully slow to compile5
LDC = LLVM backend
it's slow for D, for C++, for Zig and also slow for Jai
The reference compiler "DMD" is what you use to get fast iteration time
> (jai) Reducing compile times from about 60s right now to under 5s, hopefully around 1s
Try to compile the DMD compiler and notice how fast it is at compilation
So that sounds like it's a "your code" problem, my game engine takes 1.2 seconds to fully recompile with DMD
> the documentation is lacking
https://dlang.org/phobos/index.html
Looks complete with exhaustive code examples that you can run online
> Ok, so I don’t like D and C++ and jai looks good. But what about all the other languages?
Ok so that explains everything
Re: Porting 58k lines of D and C++ to Jai
#17I'd love to see more about Jai.
I don't understand why they are not working in the open, this is a tool, not a game, input for a large community is extremely valuable.
But as brilliant as Jon Blow is, he is at least equally as stubborn.
Fast compilation and nice, easy to read syntax with good default is exactly what I am looking for.
I can understand the hype about metaprogramming, and its potential usefulness, but I also think this is a pandora box.
Pretty much like C macros and C++ templates, overuse can lead to a very messy codebase, hard to read, hard to debug, with a lot of unexpected side effects.
Re: Porting 58k lines of D and C++ to Jai
#18It's worth mentioning that DMD is a reference compiler and not meant as a production tool. DMD is for fast compile time during dev cycles and testing new language features early. You've got the LLVM and GCC compilers for production. The problem with lack of debug info on Windows in D is solved by using LDC with LLDB/GDB to debug You can also ask the compiler to emit CodeView debugging info if you want to stick with M…
The author's chief complaint appears to be that dmd produces incorrect debug info on Windows, something I'd expect a reference compiler to do. A reference compiler doesn't have to be fast, but it does need to be correct.
Re: Porting 58k lines of D and C++ to Jai
#19I don’t understand how this language is planning on ever seeing adoption when it’s been restricted from open use since it’s inception. Seems like vaporware.
Maybe it's a marketing thing. Creating a perception of exclusivity. Making Jai the Maserati and Gucci of programming languages.
That's ridiculous but seeing the odd level of interest in this language that almost nobody can use means maybe it's working.
Re: Porting 58k lines of D and C++ to Jai
#20I don’t understand how this language is planning on ever seeing adoption when it’s been restricted from open use since it’s inception. Seems like vaporware.
Over the past decade, I watched HN's and Reddit's hype waves cycle through server-side JavaScript, Golang, Haskell, and now Rust. With plenty of secondary favorites in the mix like Julia, Nim, Zig, etc.
A lot of these things do find some modest niche to survive in. But none really take over the world as originally forecast by the hype wave.
Ultimately, you either enjoy tinkering with programming languages for personal enrichment, or you do not. Hardly anyone is actually using anything else at our Java/C#/Python/C++ day jobs.