Define ethically sourced.

Lack of important features, no asset store, not as mature (more bugs), no native console support, no low-level rendering access, no texture streaming, and on and on.

Spot-on, this would be my bet too.

It is classic internet outrage complely disconnected from what smaller game devs have to go through. Don’t get in the way of a good internet outrage as a legit, actual gamedev who knows why this is damn near impossible, or you’ll get downvoted.

The whole argument of leaving Unity hinge on the fact that Godot is a close replacement, it is not.

Godot is fine for solo/very small indies and people trying to learn gamedev, but it is not ready quite yet. Most devs still are stuck using proprietary engines.

Context menu key is kinda essential for navigating without a mouse. I don’t use it all that often but I am very glad it is there.

It is crazy how Steam users seem to interact with the platform exclusively in bad faith. The reviews are filled with memes, joke reviews and drama. You will lose IQ points just by opening the forums. And of course, people troll the awards. Not that I would expect a mainstream gaming platform to attract geniuses, but Steam community is definitely bottom of the barrel.

Style over substance, and a ugly style at that. Of course lots of people are gonna love it and say it is the best thing ever.

I don’t think he’s a lawyer.

Yep, it is mostly apparent in big companies I would say. I could go on and on, but basically your work is so disconnected from the final output that what end up actually “mattering” is a bunch of made-up bullshit. Putting in quality work and improving your product/service does not benefit most of the people you interact with directly, unless of course you’re working on the popular thing that will get people promoted.

Anyways, I also left the corporate world to start my own business. Life is so much easier when all you need to care about is the quality of your work and not political points. I like my hard work to rewards me, and not just some guy spending his days in meetings claiming credit for “his” “initiatives”. Some of those folks would never survive a job that isn’t a mega corp paying them to improv all day in meetings.

I get that a lot when I put butter on my pizza crust, I mean it is bread?

Whatever social economic model which can funnel power and authority to the very top is bond to ruin us. Humans are too greedy to sit at the top of such hierarchies.

There is a nuance though, because a language simply being interpreted does not mean it is being used as a scripting language. Take for example Java and C#, those languages are interpreted by default which allow you to ship platform-agnostic binaries and a bunch of other neat features. C# can be used as a scripting language, whenever it is interpreted, but it does not have too. It is an important nuance and this is why you can’t just replace the term “scripting language” entirely. You can also compile C# directly into machine code, skipping the interpreter entirely. Technically, there is nothing stopping you from writing an application that use C# as a scripting language even without the interpreter, since you can compile c# to machine code and simply dynamically load the library at runtime (kind of like Unity does). I guess you could call those “embedded languages”, and it would mean almost exactly the same thing, but then, aren’t we back to the same problem of some developers taking offence from that? I mean, it does imply that the language does not stand on its own without machine code just as well, which is true. This is one weird hill to have a bruised ego over for those developers you’ve met. Words have meaning and this one just happen to be a right fit given the description. I have a feeling from this whole exchange that you didn’t know what scripting languages were, considering how you replied to my first post. I worked in development for over a decade and I have never seen it be used with negative implications. I really just think you personally projected your own feeling onto a term you didn’t understand. No offence intended, it happens.

There are definitely people out there shitting on all sort of languages, and JS is a huge target, but those have been referred to as scripting language for as long as they existed. It stern from the fact those languages are embedded into existing applications, as opposed to being built into binaries. Nowadays you have hybrids like C# which can used as either a scripting language or to build native app (or in-betwee), so it is really just a matter of the context you’re using the language in. There is inherently no hidden meaning or elitism in the term. It is a very old term and I think you simply got the wrong impression from your internet experiences. It is how those languages are defined basically everywhere. Even some of those languages official definition from their own website self-define as scripting languages. There is no ambiguity here at all.

I wanted to get back to you, because you are so very right, and I spent the last 10 years or so trying to evangelize the fact that implementing algorithm and logic isn’t the hard part, it is a trivial concern really. Everything that go wrong with development usually involve the flow of data, and figuring out how to get this data from over here to over there without making a big mess. To do that, you absolutely need to write small module with few dependencies. You gotta think about the life-cycle of your objects, and generally follow all the principles of s.o.l.i.d if you’re doing OOP. Personally, I really love using dependency injection when the project allows for it.

It is as you said really, you can have thousands of hours of programming experience but if you never tried to solve those issues you’re really limiting yourself. Some devs think designing software around your data instead of your algorithms is overthinking it, or “overengineering” as I have been told. Well, I would not hire those people for sure.

I have seen clean project made up of small modules, with clear boundaries between data, functions and the lifecycle configurations. It is night and day compared to most code bases. It is really striking just how much of the hidden, and not-so-hidden complexity and goo and hacks and big-ass functions in most code base really just exist because the application life cycle management is often non-existent. In a “proper” code base, you shouldn’t have to wonder how to fetch a dependency, or if an object is initialized and valid, and where to instantiate your module, or even what constructor to invoke to build a new object. This take care of so much useless code it is insane.

To close on this, I like scripting languages a lot as well, and you can do great things with some of them even if lot of developers don’t. JS has Typescript, ReactiveX, dependency injection framework, and etc. It is a great language with a lot of possibility, and you’re not forced into OOP which I think is great (OOP and functional programming are orthogonal solutions imo). But the reality is that the language is really easy to misuse and you can definitely learn bad traits from it. Same as you, I would be wary of a developer with no experience with strongly-typed languages, or at the very least TS. I am very happy to hear this take randomly on the internet, because in my experience, this is not how most developers operate, and imo it is demonstrably wrong to not design applications around your data.

I freaking love you and I’ll try to write a worthy reply when I am home.

True that, this was pretty much the intended meaning of my reply but you worded it better.

Python and Js are by definition scripting languages in the classical sense. I am not using the term in a derogatory way and I myself learnt programming this way as a 90s kid. No offense but I think you took my comment way too personal.

I worked under a self-proclamed Python/JavaScript programmer, and part of the job involved doing rather advanced stuff in various other typed languages like c# and c++. It was hell. The code review were hell. For every little tiny weenie little things we had to go through “why coding c++ like it is python” is a very bad idea.

What is crazy about developers who exclusively work with scripting languages is that they have no conception of why general good practices exist, and they often will make up their own rules based on their own quirks. In my previous example, the developer in question was the author of a codebase that was in literal development hell, but he was adamant on not changing his ways. I’d definitely be wary of hiring someone who exclusively worked with scripting language, and sometime it is less work to train someone who is a blank slate rather than try to deprogram years of bad habits.

It has been patched.