@@ -647,7 +647,7 @@ October updates include:
647
647
648
648
Join the [ Discord server] ( https://discord.com/invite/ajour ) and say hi.
649
649
650
- [ ![ Ajour UI] ( ajour-ui.png )] [ Ajour ]
650
+ ![ Ajour UI] ( ajour-ui.png )
651
651
652
652
[ Ajour ] : https://getajour.com
653
653
[ Iced ] : https://github.com/hecrj/iced
@@ -668,6 +668,46 @@ on the module's [repository][Proton-Media-Converter-Github]
668
668
[ Proton-Github ] : https://github.com/ValveSoftware/Proton
669
669
[ Proton-Media-Converter-Github ] : https://github.com/ValveSoftware/Proton/tree/proton_5.13/media-converter
670
670
671
+ ### [ Rust GPU] [ RustGPU-Github ] v0.1
672
+
673
+ [ ![ Rust GPU Sky] ( rustgpu.jpg )] [ Ajour ] _ Sky example in Rust GPU_
674
+
675
+ Rust GPU is a very early stage project to make Rust a first-class language and
676
+ ecosystem for building GPU code.
677
+
678
+ [ Rust GPU released v0.1 in October] [ RustGPU-Twitter ] , and has already garnered
679
+ over 2000 stars on Github. There are also threads about it [ on Hacker
680
+ News] [ RustGPU-HackerNews ] and [ Reddit] [ RustGPU-Reddit ] . Currently, compiling and
681
+ running very simple shaders works, and a significant portion of the core library
682
+ also compiles. However, many things aren't implemented yet: for example, loops
683
+ and switches aren't supported yet! That means that while being technically
684
+ usable, Rust GPU is far from being production-ready.
685
+
686
+ Here is a description of the project:
687
+
688
+ ```
689
+ Historically in games, GPU programming has been done through writing either HLSL,
690
+ or to a lesser extent GLSL. These are simple programming languages that have
691
+ evolved along with rendering APIs over the years. However, as game engines have
692
+ evolved, these languages have failed to provide mechanisms for dealing with
693
+ large codebases, and have generally stayed behind the curve compared to other
694
+ programming languages.
695
+
696
+ In part this is because it's a niche language for a niche market, and in part
697
+ this has been because the industry as a whole has sunk quite a lot of time and
698
+ effort into the status quo. While over-all better alternatives to both languages
699
+ exist, none of them are in a place to replace HLSL or GLSL. Either because they
700
+ are vendor locked, or because they don't support the traditional graphics
701
+ pipeline. Examples of this include CUDA and OpenCL. And while attempts have been
702
+ made to create language in this space, none of them have gained any notable
703
+ traction in the gamedev community.
704
+ ```
705
+
706
+ [ RustGPU-Github] : https://github.com/ValveSoftware/Proton [ RustGPU-Twitter] :
707
+ https://twitter.com/repi/status/1319274584915365888 [ RustGPU-HackerNews] :
708
+ https://news.ycombinator.com/item?id=24858172 [ RustGPU-Reddit] :
709
+ https://www.reddit.com/r/rust/comments/jg056t/introducing_rustgpu_v01_embarkstudiosrustgpu/
710
+
671
711
## Popular Workgroup Issues in Github
672
712
673
713
<!-- Up to 10 links to interesting issues -->
0 commit comments