News for hackers. Stuff that matters.
Re:Sadly, I must say goodbye to Leaf, my programming language by mikekchar on Tuesday August 07, 2018 @09:06PM (#17712371)
I had a similar thought process (but luckily without spending time implementing something). I want to write a game. I thought, "None of the current languages works quite the way I want. I know! I'll write a language specifically for my game and just keep implementing the bits I need".

Then I thought, "Wait. If I do that, I'll spend 90% of my time writing a language and 10% of my time writing a game".

So I was saved. Except I still haven't even started writing the game, so I suppose it's completely moot :-D

Re:Sadly, I must say goodbye to Leaf, my programming language by WalterBright on Tuesday August 07, 2018 @10:01PM (#17712632)
One of my motivations for writing a compiler was to get my game Empire to run faster.

Wound up with a career writing compilers, not games.

Re:Sadly, I must say goodbye to Leaf, my programming language by jamesmunns on Wednesday August 08, 2018 @02:51AM (#17713711)
Wow, I was not expecting this, but "Empire" was the name of the game I have been looking for for a few years. I even asked on Reddit about a year ago (https://www.reddit.com/r/tipofmytongue/comments/6wq2t1/tomtg...), but without any luck.

I played empire (in the classic text mode) together with my dad probably more than 20 years ago.

Thank you for the game (I have lots of fond memories playing this with my dad), and for reminding me what the name was!

Re:Sadly, I must say goodbye to Leaf, my programming language by NegativeLatency on Wednesday August 08, 2018 @12:04AM (#17713123)
For anyone else who was wondering https://en.wikipedia.org/wiki/Walter_Bright
Re:Sadly, I must say goodbye to Leaf, my programming language by eatbitseveryday on Wednesday August 08, 2018 @12:21AM (#17713187)
Why not just link to the homepage itself, instead of wikipedia... ? Has much more information.

http://www.walterbright.com/

Re:Sadly, I must say goodbye to Leaf, my programming language by saagarjha on Wednesday August 08, 2018 @12:58AM (#17713301)
Might be considered as a less biased list of achievements (not that I'm saying that Walter Bright's list on his website is biased).
Re:Sadly, I must say goodbye to Leaf, my programming language by WalterBright on Wednesday August 08, 2018 @01:12AM (#17713349)
One's name is one's brand, and where practical I recommend that people buy yourname.com and own your brand, rather than relying on the vagaries of what others may say about you.
Re:Sadly, I must say goodbye to Leaf, my programming language by saagarjha on Wednesday August 08, 2018 @02:53AM (#17713721)
Sure, it's fine to own your own brand–but personally (being blessed to not have a brand image), I tend to put more weight on what other people have to say about someone than what they say about themselves. Though, of course, it's often interesting to see what people tend to put on their personal pages; often what they're proud about differs significantly from what they're famous about.
Re:Sadly, I must say goodbye to Leaf, my programming language by NegativeLatency on Thursday August 09, 2018 @11:06AM (#17724793)
When I googled his name, the Wikipedia page was the top result.
Re:Sadly, I must say goodbye to Leaf, my programming language by mrec on Wednesday August 08, 2018 @08:10AM (#17715187)
That's an impressively smooth yak.
Re:Sadly, I must say goodbye to Leaf, my programming language by danbolt on Wednesday August 08, 2018 @07:23PM (#17720493)
Do you think you'd ever go back and try to make a game once again? [1]

[1] https://news.ycombinator.com/item?id=14877776

Re:Sadly, I must say goodbye to Leaf, my programming language by Bekwnn on Tuesday August 07, 2018 @10:35PM (#17712794)
Games are still in need of a better language. I have some skepticism and hope for Jai. I really wish D as better C worked better in that realm, but it's missing a few crucial things. Rust asserts too much control over memory. I'm all ears for anything that's somewhere between C and C++ as an alternative to write games in.

Most new languages just don't get the things right that C++ did, which is why despite it having a ton of deficiencies when it comes to game development, it's still what everyone in AAA is using. Companies in AAA spend so much money on software to even just somewhat improve places where C++ has gaping flaws. A better language should have been developed by now and I don't even want to think about how much money C++ has cost the industry as a whole, even just purely on iteration speed.

Re:Sadly, I must say goodbye to Leaf, my programming language by AnIdiotOnTheNet on Tuesday August 07, 2018 @11:46PM (#17713064)
I was almost like OP for a while. Working on game, fed up with existing languages (even C), wanted a better C. I was excited about Jai, but as time goes on I'm finding it looks less and less what I want from a language. Seriously considered making my own.

Then I started working with Zig[0]. It's about 90% the language I want and even though it's still immature and the syntax, std lib, and semantics are in flux, I still find the quality of life improvement so huge that all my current projects are in Zig.

Zig is a better C to Jai's better C++, I think. It's a small language, it favors simplicity and explicitness, it has entirely manual memory management to the point that there isn't even a default allocator (we pass one in to anything that requires one). It even lets you import C headers directly to interface with C libraries.

[0] https://ziglang.org/

(skip the "stable" 2.0 download, it's way out of date from master)

Re:Sadly, I must say goodbye to Leaf, my programming language by annywhey on Wednesday August 08, 2018 @12:15AM (#17713169)
Zig is on my "must follow" list right now. It's still early enough in the going that I don't want to maintain code in it, but it's developing in a promising direction and making the kind of commitments that are reasonable to keep.

A lot of language devs want to play with semantics but aren't into the whole "let's do the hard work of actually getting off of C as the baseline" idea so it's nice to have a project that does and has a fairly explicit goal of absorbing and replacing the existing infrastructure step by step.

Re:Sadly, I must say goodbye to Leaf, my programming language by ndh2 on Wednesday August 08, 2018 @04:29AM (#17714077)
Zig is Linux-first, though. I don't think they have any dev who runs Windows. For games especially, you don't want Windows to be an afterthought. Maybe they'll get to it eventually, but it doesn't seem a priority.
Re:Sadly, I must say goodbye to Leaf, my programming language by AnIdiotOnTheNet on Wednesday August 08, 2018 @07:09AM (#17714837)
I pretty much exclusively dev on Windows, and the only thing that's a problem for me is the lack of error and assert traces. Someone started implementing the support for it, but never finished it. It is complicated by the fact that Microsoft does not distribute DIA with Windows and Zig can't include it in its own distribution.
Re:Sadly, I must say goodbye to Leaf, my programming language by Bjartr on Wednesday August 08, 2018 @09:54AM (#17715957)
I expect this is a side effect of it being early in development.
Re:Sadly, I must say goodbye to Leaf, my programming language by Bekwnn on Wednesday August 08, 2018 @02:02PM (#17717988)
Thanks I'll check it out. First glance looks promising.
Re:Sadly, I must say goodbye to Leaf, my programming language by hzhou321 on Wednesday August 08, 2018 @01:03AM (#17713317)
Here is a direction if you are all ears : instead of a new language, add a new layer.

I tried creating my own languages before, some 15 years ago. While I had fun writing compilers, I missed a lot more writing actual programs. One day I suddenly realized I don't really need new language, what I needed is simply context dependent syntax and code block organization, which can easily implemented on the spot. It become MyDef and I have been programing with it entirely for more than 10 years now and wondering how others don't go down the same path.

Actually in a broad sense, Knuth's literate programing adventure is very similar to mine. He also wondered how others were not as excited as he was.

So rather than a new language, try a new dimension.

Re:Sadly, I must say goodbye to Leaf, my programming language by dajomu on Wednesday August 08, 2018 @06:36AM (#17714662)
This sounds really interesting, can you provide a link so I can read some more about it?
Re:Sadly, I must say goodbye to Leaf, my programming language by akuji1993 on Wednesday August 08, 2018 @07:35AM (#17714973)
This seems to be the Github repository for it: https://github.com/hzhou/MyDef
Re:Sadly, I must say goodbye to Leaf, my programming language by co_dh on Wednesday August 08, 2018 @08:50AM (#17715434)
The problem is, your coworker need to modify the generated code.
Re:Sadly, I must say goodbye to Leaf, my programming language by hzhou321 on Wednesday August 08, 2018 @08:58AM (#17715495)
Just share with coworkers the C (or whichever) code that MyDef translated. MyDef is not a language, it only dresses the code. So if coworkers don't like to work with the dresses, simply remove the dress.
Re:Sadly, I must say goodbye to Leaf, my programming language by humanrebar on Wednesday August 08, 2018 @07:23AM (#17714916)
How is MyDef not another language?
Re:Sadly, I must say goodbye to Leaf, my programming language by hzhou321 on Wednesday August 08, 2018 @08:53AM (#17715462)
Because when using MyDef, you are still thinking in the end language -- how the function, variable, type, stack works are all defined by the end language. With MyDef, you are just changing the way of expressing them -- just like giving creatures different clothes, but they are not new creatures.

Here is a short example:

    page: test, basic_frame
        module: c

        $local int A[3]
        $for i=0:3
           A[i] = i
        $dump A[0], A[1], A[2]
Despite the look, if you know c, you recognize it as c. And as you get familiar, you see it exactly as C. `basic_frame` is merely a custom template so one doesn't have to always write the main function signature. $for is shorthand for `for-loop`, `$dump` is simply printf with simple type translations.

Now that you had this meta layer, there is no limit on how you want to dress up your code. Examples:

    $local A[3]: int
    $sumcode(3) A[i]=i+3
    $foreach A
        $dump $(t)
or

    page: test, basic_frame
        $call declare
        $call init
        $call report

    subcode: declare
         $local pn_A[3] = {1, 2, 3}

    subcode: init
         $foreach pn_A
             $(t) = $(t)^2

    subcode: report
         $(set:print_to=stderr)
         $foreach pn_A
             $print "%d: %d", $(i), $(t)

There are lots of idioms and conventions, but it is not a problem as long as you recognize them only as clothing.

Lastly, when dressing up the code makes little sense or you simply don't know better way of dressing them, you can simply write vanila C (or any languages that you are writing). MyDef never tried to compile your language.

Re:Sadly, I must say goodbye to Leaf, my programming language by WalterBright on Wednesday August 08, 2018 @01:05AM (#17713323)
> I really wish D as better C worked better in that realm, but it's missing a few crucial things.

Like ?

Re:Sadly, I must say goodbye to Leaf, my programming language by nicwilson on Wednesday August 08, 2018 @12:50AM (#17713273)
> I really wish D as better C worked better in that realm, but it's missing a few crucial things.

Such as? We are always looking for for things that get in the way of use.

Re:Sadly, I must say goodbye to Leaf, my programming language by Bekwnn on Wednesday August 08, 2018 @02:03AM (#17713540)
Under "unavailable features" https://dlang.org/spec/betterc.html#consequences

3, 4, and 5 are all pretty sore points. 2 would be as well if it weren't extremely likely that for any game you create roll some sort of reflection system. It would be a sore spot for small projects.

3 - No access to classes and polymorphism is a bit of a downer. Although I'm a big believer of data-oriented design, I think there are still many cases where modelling things as objects is the best way to go, especially for things like scene actors and game objects.

4 - No built in threading (core.thread) puts a hamper on any sort of distributed updating or performance optimizations you'd want to do. I'd imagine the workaround is external multi-threaded dlls or something, but it sounds like a pain to manage and deal with in a workflow.

5 - No dynamic arrays. This container is used abundantly in game development. It shows up 5 or more times for every heap/stack/queue. This may not be an issue if you want to write a special memory environment and your own containers, which is common in game development, but not having access to a standard one certainly hurts when it comes to smaller projects or graphics programming experiments.

I may be somewhat off base here since what happened is that I read about those being missing and decided not to try it.

Another note is that a big thing I'm looking for is massively improved compile times, which is one of the biggest things Jai looks to have over C++ in addition to its compiler hooks and #run.

Re:Sadly, I must say goodbye to Leaf, my programming language by p0nce on Wednesday August 08, 2018 @07:45AM (#17715020)
I have a smallish D game on Steam and trust me, you can absolutely use the D runtime instead of -betterC. -betterC is a work in progress and not representative of D.

You will say that you don't want a GC but in reality the GC can be optimized as much as you wan't, and in the mean time you'll get precious _developement time_ to optimize further.

If you can afford the D runtime by all means take it ; for some products I'm doing without the D runtime, and the surprise was that it did't make things any faster _at all_ without the runtime (we did it for other reasons). The only real gain is memory consumption of GC vs manual and that is achievable without going through extreme coercitive measures like -betterC.

Re:Sadly, I must say goodbye to Leaf, my programming language by FeepingCreature on Wednesday August 08, 2018 @03:36AM (#17713892)
It seems to me like you should just be using D, not "Better C-style D"? All those features are not in BetterC because they need a garbage collector, but they are of course in D proper. For smaller projects, I'd recommend just ignoring the GC until you run into actual issues with it, then optimizing for the specific issues.
Re:Sadly, I must say goodbye to Leaf, my programming language by comex on Wednesday August 08, 2018 @04:57AM (#17714176)
That's easy to say, but as long as C++ and other languages can do those things without a garbage collector, D seems somewhat less attractive. (I'm not the OP but I've had a similar experience with D.)
Re:Sadly, I must say goodbye to Leaf, my programming language by WalterBright on Wednesday August 08, 2018 @02:41PM (#17718305)
You can do all of them without a garbage collector - you just have explicitly manage the memory yourself.
Re:Sadly, I must say goodbye to Leaf, my programming language by makomk on Wednesday August 08, 2018 @05:00AM (#17714190)
As I understand it, garbage collection is kind of a non-starter for games programming because it leads to unpredictable pauses in what should be a low-latency, interactive application.
Re:Sadly, I must say goodbye to Leaf, my programming language by qznc on Wednesday August 08, 2018 @08:00AM (#17715123)
You can put the low-latency stuff in a non-gc thread which will not be interrupted [0] and still use the convenient garbage collector for the rest.

[0] https://p0nce.github.io/d-idioms/#The-impossible-real-time-t...

Re:Sadly, I must say goodbye to Leaf, my programming language by p0nce on Wednesday August 08, 2018 @07:49AM (#17715042)
Infognition has found that if you keep the D GC heap under 100k the max pauses will be about 1 ms. The means to reduce GC usage have only grown more diverse in recent years:

- std.experimental.allocator

- @nogc to ensure, well, no GC usage

- various things built on placement new (`emplace`)

- GC profiling with -profile=gc, will display number of allocations and size

None of this existed when people were already making high-performance systems with D...

Re:Sadly, I must say goodbye to Leaf, my programming language by bausshf on Wednesday August 08, 2018 @05:16AM (#17714235)
It is optional however and you can use custom allocators to get around it.
Re:Sadly, I must say goodbye to Leaf, my programming language by xxs on Wednesday August 08, 2018 @08:03AM (#17715143)
You can have low pause, fully concurrent GC even in Java. A GC can utilize read barriers and overall eliminate stop-the-world pauses.

--- A popular example is minecraft that uses mainstream G1 GC.

Re:Sadly, I must say goodbye to Leaf, my programming language by atilaneves on Wednesday August 08, 2018 @07:39AM (#17714991)
That page should be updated.

I was suspicious about #3 since classes in D don't necessarily need the GC. For starters D supports C++ classes, so this works:

https://gist.github.com/atilaneves/b69ed0399efac21bb7a977afd...

I used `scope` with `new` to allocate on the stack, but `emplace` should just work as well to "placement new" a class in malloc'ed memory.

#4 is annoying but one could always use the OS threading API. It's doable to write a library solution to do that akin to boost or Qt before C++11. You do it once and it's there.

#5 No dynamic arrays are also annoying. But... writing a clone of std::vector isn't hard, and there's a unique array in my automem library that _should_ be usable in betterC (but I haven't checked): https://github.com/atilaneves/automem/blob/master/source/aut...

> Another note is that a big thing I'm looking for is massively improved compile times

You get that with D.

Re:Sadly, I must say goodbye to Leaf, my programming language by WalterBright on Wednesday August 08, 2018 @02:41PM (#17718294)
> 3,4,5

Those rely on the garbage collector. If you are willing to do C style memory management, they are all available with betterC.

Re:Sadly, I must say goodbye to Leaf, my programming language by z92 on Wednesday August 08, 2018 @04:38AM (#17714112)
These "unavailable features" are available in D. But NOT when you compile with a specific switch on.
Re:Sadly, I must say goodbye to Leaf, my programming language by moopsit on Wednesday August 08, 2018 @09:44AM (#17715845)
I feel like with languages (in games or anything else), it all boils down to "where there's a will, there's a way". People come up with a lot of reasons Language X won't be suitable for a project, but in the end it's the people who use whatever tools are at hand, who get the job done while the perfectionists are stuck at the starting line. Classic Tortoise vs. Hare situation.

If you want to write games, use your favorite language, and just START. All limitations can be circumvented somehow.

Re:Sadly, I must say goodbye to Leaf, my programming language by tdsamardzhiev on Wednesday August 08, 2018 @12:49AM (#17713269)
The AAA company I work for has tried everything possible to work around C++, and let me tell you, had they not started any such efforts, they'd have been way better off. Seeing the results of it all makes me super sceptical of any C++-killers.
Re:Sadly, I must say goodbye to Leaf, my programming language by seventhtiger on Wednesday August 08, 2018 @04:24AM (#17714053)
Pure OOP is a poor fit for implementing games, but it's a fine base to build a entity-component-system layer on top of which is excellent for games.
Re:Sadly, I must say goodbye to Leaf, my programming language by je42 on Wednesday August 08, 2018 @01:42PM (#17717815)
C++ is not pure OOP. you can write functional stuff quite well. the more recent C++ standard you are willing/are able to adopt the better it gets ;) C++17 is quite awesome.
Re:Sadly, I must say goodbye to Leaf, my programming language by pjmlp on Wednesday August 08, 2018 @02:32PM (#17718217)
Yep, one can even go Haskell like crazy if one feels like to.

The only nagging point is the copy-paste compatibility with C. :\

Re:Sadly, I must say goodbye to Leaf, my programming language by redahs on Tuesday August 07, 2018 @11:15PM (#17712955)
Use regular C, but write the code in literate programming files which can be rendered into a portable design document describing the implementation and interaction of every subsystem in the codebase. 'Standard written English' is the best language available for modeling abstractions.
Re:Sadly, I must say goodbye to Leaf, my programming language by tdsamardzhiev on Wednesday August 08, 2018 @12:51AM (#17713276)
Do you happen to know any open-source games that do this?
Re:Sadly, I must say goodbye to Leaf, my programming language by Razengan on Tuesday August 07, 2018 @11:50PM (#17713079)
> Games are still in need of a better language.

I find Swift to be the best so far, its strong ties to the Apple ecosystem notwithstanding.

Having tinkered with various environments since the Sinclair Spectrum's BASIC (though back then I had no idea what I was doing) I've successively fallen in love with Visual Basic (6.0, not the .NET impostor) and then C#, and now I'm smitten with Swift.

In Microsoft land I was let down by their usual dichotomies that did not allow you full access to all their APIs (or hardware performance) from anything but C++ (though I did manage to make playable DirectX games in VB6). I don't know how that has changed in the last decade since I jumped ship to Apple, but .NET was treated as a second-class citizen for too long.

With Swift, not only do I have access to everything that Apple's operating systems offer, it's also a modern language which feels naturally suited to game design patterns. Although until Swift 2 I often had to fight the language, since Swift 3 and especially now in Swift 4.2 I find it effortless to reason about most game architectures while sticking to the language's idioms.

I also appreciate it for enforcing good practices and getting rid of most sources of ambiguity (such as the ++/-- operators and the legacy `for` syntax, or being specific about %/modulo and so on), even if it may feel annoying in the beginning if you're coming from "looser" languages. It also compiles to native code and can easily interop with C [0], but best of all: I am glad to be able to finally leave semicolons behind. C# honestly feels archaic in comparison now.

As for the elephant in the room – that Swift is only good for iOS, macOS, tvOS and watchOS – well, those platforms have a combined userbase of over a billion users, and the most successful app market [1]; I don't feel that it's such a downside to be limited to those platforms. I do wish that the Apple TV came with a proper gamepad so we could only target that without losing users. It could be a serious contender to existing game consoles if Apple took that route.

If you're in love with Swift too, I'm writing an open-source game engine which offers an Entity-Component-System architecture on top of Apple's APIs [2].

[0] https://theswiftdev.com/2018/01/15/how-to-call-c-code-from-s...

[1] https://www.google.com/search?Apple+App+Store+payouts

[2] https://github.com/invadingoctopus/octopuskit

Re:Sadly, I must say goodbye to Leaf, my programming language by pjmlp on Wednesday August 08, 2018 @07:15AM (#17714870)
With UWP and .NET Native, .NET (C#/VB) is as first class as C++.

To the point the Windows UI team does all their graphics demos in C#.

Re:Sadly, I must say goodbye to Leaf, my programming language by Razengan on Wednesday August 08, 2018 @09:14AM (#17715612)
Ah. My crankiness towards MS may no longer be justified.

I’m too deeply entrenched in Swift though and disgusted by the sight of semicolons in a language anymore :P (maybe I’ll dip into VB.NET and see how it’s doing.)

Re:Sadly, I must say goodbye to Leaf, my programming language by taneq on Tuesday August 07, 2018 @09:59PM (#17712619)
Language Syndrome sounds like Engine Syndrome in hard mode. You want to write a game, so you start working on a game engine, only to realise that a game engine is a never-ending project and you'll never have spare energy to actually write the game. I fell prey to this a couple of times back in the day.
Re:Sadly, I must say goodbye to Leaf, my programming language by rzzzt on Wednesday August 08, 2018 @02:19AM (#17713578)
Both are examples of the push-down goal stack in action: http://wiki.c2.com/?PushDownGoalStack
Re:Sadly, I must say goodbye to Leaf, my programming language by skadamat on Tuesday August 07, 2018 @11:33PM (#17713032)
Jon Blow's been working on a programming languages for games (intro / philosophy here): https://www.youtube.com/watch?v=TH9VCN6UkyQ

Series of videos here - https://www.youtube.com/user/jblow888/videos - I don't program games but it looks super interesting

Re:Sadly, I must say goodbye to Leaf, my programming language by foota on Tuesday August 07, 2018 @09:13PM (#17712411)
I hit a similar roadblock for a long time, always spending time writing low level graphics utilities (which I do rather enjoy) but never getting around to writing a game.

If you find yourself in a similar situation and want to get around it I would suggest trying unity, which I was hesitant to do since:

1. It felt like giving up and cheating, and

2. I don't like how unity interfaces with the developer, since I mostly wanted to implement games without using the world editor that seems to be the focus of unity.

But I've enjoyed using it so far and would suggest giving it a shot.

Re:Sadly, I must say goodbye to Leaf, my programming language by pixelbash on Tuesday August 07, 2018 @10:14PM (#17712691)
Re the second point did you manage to get around this? Played with it a bit and it felt almost like flash back in the day where you could eschew the timeline and do everything programmatically. In the end ran into a problem where I wanted to move the universe around the player and couldn’t get the particle engine to cope..
Re:Sadly, I must say goodbye to Leaf, my programming language by tlarkworthy on Tuesday August 07, 2018 @10:34PM (#17712792)
You can do anything programmatically in unity. I think professionals tend towards this. You use the world editor only for artistic expression, the spatial layout and tuning etc. where previewing layout really saves time.

For very specific effects like universe turning, you have to do a lot of code work in a niche area, but it's still quicker than building a particle engine from scratch. Sometimes you can cheat the effect in shaders or camera tranform manipulation. Or skip the effect altogether if the volume of custom code is not worth it and you are prioritizing shipping. Ask yourself, does it make or break your game?

Re:Sadly, I must say goodbye to Leaf, my programming language by foota on Tuesday August 07, 2018 @11:17PM (#17712964)
What in the world is universe turning?
Re:Sadly, I must say goodbye to Leaf, my programming language by tlarkworthy on Wednesday August 08, 2018 @06:33PM (#17720147)
The OP roadblock (turning the particle system).
Re:Sadly, I must say goodbye to Leaf, my programming language by scraft on Tuesday August 07, 2018 @10:53PM (#17712859)
I started our my games development career as a low level programmer and moved to a lead programmer in the technology department and then founded a games studio where we wrote our own engine and released several games.

My role meant I had to make the correct business decisions using my technological knowledge and as much as writing engines and technology ran through my blood, the right answer was to switch to Unity. The man cost of constantly writing all the technology we need and then maintain it was too great compared to the ever diminishing wins we got from it.

One scary part of this decision was then hiring Unity programmers and initially having these new hires knowing more about Unity than I did. I needed to make calls about what is possible, time frames, performance, meeting client requirements etc without being an expert of the most important part of our development process. Luckily we made the right hires and it didn't take so long until I had been converted to the Unity mindset. Initially I would always be saying "oh well I would normally tackle this in this way" and wanted to coerce Unity to work in a familiar way. But overtime this disappeared and I became increasingly interested in working out the best way to achieve things in the "Unity way" which ultimately returns much greater dividends.

The first game we released, called Bloody Zombies came out last year on Steam, Oculus, Xbox One, PS4 and Nintendo Switch. It can be played in VR (on supporting platforms) and non VR. It is multiplayer, both in the sense of multiple people on one machine (you can do things like 1 VR player and 3 TV players or 4 TV players) but also online multiplayer (where you can do one player per machine or any combinations say one tv player on one machine playing with 1 VR players and 2 tv players on another machine).

VR meant we had to maintain a constant frame rate (60 or 90 depending on platforms). We used stereoscopic rendering, offloaded graphics work to a special job system. We used custom shaders (the game is like a graphical novel so outline shaded characters) we have spherical fog, lightmaps, FXAA, colour post processing etc.

Online multiplayer meant a packet system, ability to establish connections, matchmake, a system for making parts of the game world communicate, handling so many error cases, etc.

For variety of platforms meant lots of variety on the rendering, controller input etc.

For Switch it meant the ability to play on Switches close to each other on a different protocol to online multiplayer.

I shudder to think how much time and effort this would have been without Unity. I suspect we would have needed several new hires working on platform specific tech, full time network engineers, at least one full time graphics dev, at least one full time audio dev, one full time physics dev, the list goes on. Instead we had 3 programmers (which includes me where my time was heavily comprised being a founder/MD/Tech Director/coffee maker) and whilst the other programmers were very good they had both only graduated a few years prior.

Did Unity solve everything? Absolutely not. We hit loads of huge problems with Unity. Without help of their engineers some problems we would never have been able to solve. We helped Unity fix lots of issues at their end. We found issues that could have been solved trivially without Unity. We felt the strain of waiting days for an answer to a mission critical Unity issue. But in the grand scheme, the pain was less than 10% of what we would have experienced doing it with our own engine.

My big worry was not doing "tech" anymore, but that simply isn't true. But instead of having to write loads of architecture and code to even be able to write the "real" tech, instead you can write the more interesting stuff. For shaders you just write the shaders, not the system for passing in shader constants and setting up vertex streams. Post effects is similar. Coming from a strong engine/Tech background has been massively helpful, whilst unity trained hires are amazing it has been really useful for our studio for me to be able to get into the lower level to add feature, fix stuff, debug stuff, etc.

Re:Sadly, I must say goodbye to Leaf, my programming language by je42 on Tuesday August 07, 2018 @11:36PM (#17713040)
> We felt the strain of waiting days for an answer to a mission critical Unity issue. But in the grand scheme, the pain was less than 10% of what we would have experienced doing it with our own engine.

Wouldn't that make you feel nervous ? To totally depend on unity's merit to ship a game when you cannot address blocker bugs yourself ?

Re:Sadly, I must say goodbye to Leaf, my programming language by scraft on Wednesday August 08, 2018 @02:32AM (#17713631)
Yes, but not unusual, as well as Unity we have similar blocks from MS, Sony, Oculus, Nintendo.

One good thing is that rather than us hitting lots of blocks with the hardware manufacturers with regards to the engine, Unity handles this instead and Unity is in a much better position to resolve issues due to their relationship with the hardware manufacturers but also the size of the dev team.

We still had several issues we had to deal directly with Sony/MS/Nintendo. Some issues they could resolve and others they could not (meaning we had to find elaborate workarounds or key changes to the game we didn't ideally want to make).

Re:Sadly, I must say goodbye to Leaf, my programming language by foota on Tuesday August 07, 2018 @11:16PM (#17712961)
Perhaps I'm missing something here, but you should just need to move the player in the opposite direction of the world's desired movement? No game system I'm aware does it the other way around, as it requires changing all the other models transforms.

But yes, I am dealing with the interface, primarily by ignoring it. I'm still trying to get down the right way to organize my code, but it's making sense.

Re:Sadly, I must say goodbye to Leaf, my programming language by gmueckl on Wednesday August 08, 2018 @07:34AM (#17714969)
Once your game world size crosses a specific threshold, you need to move the world instead of the player because numerical accuracy starts to become troublesome (most engine code runs with floats, which gives about 6 decimal digits of precision). The first engine that I am aware of that did that was that of Dungeon Siege. There's an excellent post mortem around about the challenges of this approach.
Re:Sadly, I must say goodbye to Leaf, my programming language by mamcx on Tuesday August 07, 2018 @11:04PM (#17712905)
I'm in the same, but get the opposite idea. I procastinate in build the language I want (a relational engine, not a DB, a language) always thinking "Is better to let that to pros".

But more time I do the same things over and over, more I'm convinved I could abstract my main tasks (around data manipulation) in a simple language:

https://www.reddit.com/r/rust/comments/8ygbvy/state_of_rust_...

But the idiot of me think "and the let's use Rust... how hard it can be?". And now.. is HARD! Sadly, Swift was ruled out:

https://www.reddit.com/r/swift/comments/8zb9y1/state_of_swif...

and don't wanna do C/C++.

I expect the language to be a glorified DSL that is just about data, parsing, loading data, moving data, converting from this to that and a way better (I hope!) than ORM for interfacing to RDBMS.

Re:Sadly, I must say goodbye to Leaf, my programming language by jrumbut on Tuesday August 07, 2018 @11:14PM (#17712952)
This isn't my area per se but have you considered Lisp/Haskell (even Ruby) or one of the other languages with good metaprogramming/DSL creation facilities?

Or perhaps making a small extension to one of the above, I know many languages have the ability to be extended through modules added at compile (meaning when you compile the interpreter/compiler/runtime itself, not the program) time, or used as a target for a preprocessor. That makes it so it's at least a little easier to get a userbase going, maybe some existing libraries can work with your language.

If that's not possible, I'd be curious to learn what makes it not feasible. Fresh approaches to data processing are really desirable right now, since so many of us are working with data that is different from what language designers intended.

Re:Sadly, I must say goodbye to Leaf, my programming language by mamcx on Tuesday August 07, 2018 @11:23PM (#17712987)
>If that's not possible, I'd be curious to learn what makes it not feasible. Fresh approaches to data processing are really desirable right now, since so many of us are working with data that is different from what language designers intended.

I wish to use instead swift, that hit a sweet spot. Using other lang (like python, that I loved!) make hard to target iOS/Android. This is the main crux of mine. This mean that I need to re-code a lot of stuff across platforms and targets, because nothing is good enough. I also use xamarin/F# and the integration with android/ios is not as good as I imagine (ie: xamarin.forms sucks. And is damm hard to integrate yourself anything (ie: ios/android libraries) outside it).

I also try with nim but is too crude and lack a lot of libraries I will need. I'm also thinking on using pascal, that I also like much, so now is just looking how good could be the use of rust...

Re:Sadly, I must say goodbye to Leaf, my programming language by jhasse on Wednesday August 08, 2018 @04:08AM (#17714010)
> and don't wanna do C/C++.

Give C++17 a try :)

Re:Sadly, I must say goodbye to Leaf, my programming language by mamcx on Wednesday August 08, 2018 @06:59PM (#17720369)
C++ have a lot of nice stuff now, but anyway soon or later need to take from the old mess. If I wanna suffer, I prefer something with a more consistence...
Re:Sadly, I must say goodbye to Leaf, my programming language by rqs on Wednesday August 08, 2018 @05:56AM (#17714464)
10% for writing the game? you maybe too optimistic :D

I found myself having the same problem, luckily I don't know how to write a language.

I'm currently working on a part-time project in Go, it involve a HTTP service.

As you may already knew, there is a built-in HTTP server that came with Go, so I COULD just took it and go ahead directly start to implement my service logic.

But hell no, it's too slow. So instead, I made my own HTTP/1.1 server, which is bit faster than Go's.

It was pretty fun to write that server indeed, but I don't think it's worth the trouble. In fact, I really really hope somebody stopped me when I was creating that `http.go` file.

Now, I'm wandering around, thinking the `html/template` is too slow ...

Re:Sadly, I must say goodbye to Leaf, my programming language by ckok on Wednesday August 08, 2018 @04:27AM (#17714070)
I did end up going the way of writing that compiler and never writing the thing I wanted to write the compiler for, even forgot what it was.

But it was and is a good experience, the last 13 years of writing a compiler. Especially if you like solving problems with no or few searchable solutions.