Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

24 Hours of Rust Game Development

iolivia.me

Post reply on HN
Print view View original

11–20 of 78 posts

Re: 24 Hours of Rust Game Development

#11

Post by reificator »

m0meni wrote: post #7
StavrosK wrote: post #5

Earlier quoted context omitted.

"ggez" is what someone says to piss you off, kind of like "haha, loser, you suck, beating you wasn't even hard". People who say this are trash, and it's a big part of the reason why I disconnect from games seconds before I lose. It is not a good name for anything.

You seem disproportionately angry about this because of your personal experiences. It means you can create a "Good Game Easily"

I've not been on the receiving end of `ggez` in online games, and it wouldn't really get to me if I were. (I should note, I also have not been on the sending end. Just preempting that question...)

That said, I don't think it's reasonable to pretend it's not a common, rude saying in the online gaming community. It absolutely is. And the online gaming community and game development communities are inextricably linked, like it or not.

I avoided even starting to look into `ggez` for a long time because I assumed a frat bro culture around it, entirely because of the name.

I don't get that feeling from using it, from reading the documentation or reading issues on Github. (though it's been awhile since I did any of those things)

But because it's named that, potential contributors and users are going to skip over it for Amethyst or Piston because they don't start off alienating people just from their names.

Re: 24 Hours of Rust Game Development

#12

Post by [deleted] »

tenaciousDaniel wrote: post #3
codetrotter wrote: post #2

> ggez Off-topic but that’s a darn nice name for a game engine. Certainly ggez means “good game easy”. At least that’s how I read it. Clever because “gg” and “ez” is gamer terminology used by people that play video games, with “gg” meaning a match was good (equivalent of “thanks for the match”) and putting them together you get a new meaning which is that it will be easy to create a good game.

The challenge is gathering consensus on how to pronounce it :p

[deleted]

Re: 24 Hours of Rust Game Development

#13

Post by taneq »

reificator wrote: post #8
codetrotter wrote: post #2

> ggez Off-topic but that’s a darn nice name for a game engine. Certainly ggez means “good game easy”. At least that’s how I read it. Clever because “gg” and “ez” is gamer terminology used by people that play video games, with “gg” meaning a match was good (equivalent of “thanks for the match”) and putting them together you get a new meaning which is that it will be easy to create a good game.

The trouble is, `gg` means `good game` and `ez` means `easy`. But `ggez` means `you suck and I'm better than you`.

Still works because your adversary in this case is the game you want to play not existing. So you can make a good game easily and taunt your defeated adversary. It works on a bunch of levels.

Re: 24 Hours of Rust Game Development

#14

Post by [deleted] »

slavik81 wrote: post #9
codetrotter wrote: post #2

> ggez Off-topic but that’s a darn nice name for a game engine. Certainly ggez means “good game easy”. At least that’s how I read it. Clever because “gg” and “ez” is gamer terminology used by people that play video games, with “gg” meaning a match was good (equivalent of “thanks for the match”) and putting them together you get a new meaning which is that it will be easy to create a good game.

"gg ez" is a taunt some players use when they win. Overwatch chat infamously auto-replaces that phrase with messages like, "I'm wrestling with some insecurity issues in my life but thank you for playing with me." That being said, it is a clever name for an engine for the reasons you stated. And it's short, which is always nice.

[deleted]

Re: 24 Hours of Rust Game Development

#15

Post by codetrotter »

reificator wrote: post #8
codetrotter wrote: post #2

> ggez Off-topic but that’s a darn nice name for a game engine. Certainly ggez means “good game easy”. At least that’s how I read it. Clever because “gg” and “ez” is gamer terminology used by people that play video games, with “gg” meaning a match was good (equivalent of “thanks for the match”) and putting them together you get a new meaning which is that it will be easy to create a good game.

The trouble is, `gg` means `good game` and `ez` means `easy`. But `ggez` means `you suck and I'm better than you`.

Hm, I only knew about the individual meanings of gg and ez, didn’t know they were already used in conjunction and with such negative meaning. That’s unfortunate :(

Re: 24 Hours of Rust Game Development

#16

Post by jblow »

It is fine that people are experimenting with putting graphics on the screen and playing with new languages.

But I just wanted to comment that you don't need an "Entity Component System" in a game, and especially not for a very simple not-yet-a-game like shown here. (You also don't need inheritance or composition).

It bothers me that so many people are buying into this hive-mind marketing on ECS, when in reality it is just overengineering + procrastination in almost all cases.

(None of my games have ever had anything as complicated as a component system).

If you want to make a simple game like this, just sit down and program it in the obvious way. It will work. You don't need to be fancy.

Re: 24 Hours of Rust Game Development

#17

Post by whatshisface »

jblow wrote: post #16

It is fine that people are experimenting with putting graphics on the screen and playing with new languages. But I just wanted to comment that you don't need an "Entity Component System" in a game, and especially not for a very simple not-yet-a-game like shown here. (You also don't need inheritance or composition). It bothers me that so many people are buying into this hive-mind marketing on ECS, when in reality it i…

>If you want to make a simple game like this, just sit down and program it in the obvious way. It will work.

I have heard that the restrictions imposed by the Rust compiler make it surprisingly hard to get it working the normal way. The first time I heard of ECS was in a Rust talk about how it helped them stop fighting the borrow checker.

Re: 24 Hours of Rust Game Development

#18

Post by woolvalley »

jblow wrote: post #16

It is fine that people are experimenting with putting graphics on the screen and playing with new languages. But I just wanted to comment that you don't need an "Entity Component System" in a game, and especially not for a very simple not-yet-a-game like shown here. (You also don't need inheritance or composition). It bothers me that so many people are buying into this hive-mind marketing on ECS, when in reality it i…

Sometimes when you prototype something, half the reason is to try out these new fancy architectural styles :p

Usually it's for this kind of project: http://www.commitstrip.com/en/2014/11/25/west-side-project-s...

Re: 24 Hours of Rust Game Development

#19

Post by dang »

jabagawee wrote: post #4

Title seems to have been changed to meet the following rule: > If the original title begins with a number or number + gratuitous adjective, we'd appreciate it if you'd crop it. E.g. translate "10 Ways To Do X" to "How To Do X," and "14 Amazing Ys" to "Ys." Exception: when the number is meaningful, e.g. "The 5 Platonic Solids." However, I believe the "24" in "24 Hours of Rust Game Development" is pretty crucial.

Yup, we've added 24 back.

Re: 24 Hours of Rust Game Development

#20

Post by visualphoenix »

jblow wrote: post #16

It is fine that people are experimenting with putting graphics on the screen and playing with new languages. But I just wanted to comment that you don't need an "Entity Component System" in a game, and especially not for a very simple not-yet-a-game like shown here. (You also don't need inheritance or composition). It bothers me that so many people are buying into this hive-mind marketing on ECS, when in reality it i…

+1.

Like you, I've seen both sides. Unreal lineage evolved from inheritance-based into ECS-like. Frostbyte is heavily ECS.

Googling... the author is ex-amazon, ex-microsoft - with xbone and 360 title experience. Perhaps the author was exposed to that pattern at one of those institutions, or perhaps the author saw the 2018 Rust Conf Closing Keynote[0] and was inspired to continue down that path.

I think people tend to either go with what they've seen work in the past, or heard works well. Maybe it's cargo culting, or maybe in the case of rust (which I have no current experience with), it helps? Either way, the most important point is to focus on the fun and not let technologies get in the way of making a good game.

[0] - https://www.youtube.com/watch?v=aKLntZcp27M

Post reply on HN