fruit-economy VS ripgrep

Fruit Economy - itch.io | latest devlog | ghHey Everyone, For the second week in a row things have been rather crazy at work, so I've not been too upset about my disrupted plans... Most of the performance-related code changes I wanted to get done were complete on Wed [0], but there were still some annoying rendering artefacts mostly around resizing the screen and mouse movement. I could hide the mouse movement issue, but I'd rather fix it properly. It's mostly a case of not passing enough context or too much context to the memoisation. Basically, at the moment I'm re-rendering everything if anything changes on the game-state side when I really should be splitting up the re-renders to be more specific to rendering only the subset of tiles that have changed or grouping tiles into small regions and rendering stuff at a region at a time. Also, because of this, I didn't tie re-rendering to non-game-state stuff, things like resizing and mouse movement are waiting on a game tick to actually be updated. Bad on me for being lazy I guess, so that's a thing to get sorted out, but I'd like to also add in a gameplay thing, two weeks is getting dangerously close to going a month without making any gameplay improvements, which is bad. So that's definitely something I need to prioritise for next week.As always, questions welcome!- Folcon `-[0]: You can peak at stuff on github if you're interested ;)...

Apologies for how much junk is in here[0], I finally figured out notarization and then lost the will to touch it. I'm planning on circling back to clean it up in a few weeks when that entire pile of stress is a bit more of a distant memory, but hopefully it's helpful? =)...

- [0]: https://github.com/Folcon/fruit-economy/blob/185d49f120bac18...

Fruit Economy - itch.io | latest devlog | gh

Last June I decided to try and figure out how to make a game or bust, I didn't really care what, just that I made something, so I took part in the GMTK 2021, that went ok so I decided to try and take what I learned about focus, scoping and getting a small playable thing up and running asap and made a new project[2].

It's super rough, the gameplay is still sort of non-existent, performance is pretty bad and code quality is kind of all over the place as I'm still really trying to work out how to build stuff like this and I know if I let my dev side have too much leeway it's going to take over and I'll probably no longer be able to figure out what my creative side wants to do.

It's a fiddly balance that I'm still trying to figure out.

I've intentionally not said anything about the game itself, you're welcome to ask me for details, but there are also bits of info littered about here and there[3].

- [0]: https://web.archive.org/web/20130124211012/http://www.dev.gd..., original HN discussion [1]

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

- [2]: Itch: https://folcon.itch.io/fruit-economy, GH: https://github.com/Folcon/fruit-economy

- [3]: https://news.ycombinator.com/item?id=22791490

ripgrep - https://github.com/BurntSushi/ripgrep

Basic code searching skills seems like something new developers are never explicitly taught, but which is an absolutely crucial skill to build early on.

I guess the knowledge progression I would recommend would look something kind this:

- Learning about Ctrl+F, which works basically everywhere.

- Transitioning to ripgrep https://github.com/BurntSushi/ripgrep - I wouldn't even call this optional, it's truly an incredible and very discoverable tool. Requires keeping a terminal open, but that's a good thing for a newbie!

- Optional, but highly recommended: Learning one of the powerhouse command line editors. Teenage me recommended Emacs; current me recommends vanilla vim, purely because some flavor of it is installed almost everywhere. This is so that you can grep around and edit in the same window.

- In the same vein, moving back from ripgrep and learning about good old fashioned grep, with a few flags rg uses by default: `grep -r` for recursive search, `grep -ri` for case insensitive recursive search, and `grep -ril` for case insensitive recursive "just show me which files this string is found in" search. Some others too, season to taste.

- Finally hitting the wall with what ripgrep can do for you and switching to an actual indexed, dedicated code search tool.

live grep: ripgrep

The world has moved on though to opinionated tools, and Rust isn't even the furthest in that direction (That would be Go). The equivalent of those two lines in Cargo.toml would be this example of a basic configuration from the jacoco-maven-plugin: https://www.jacoco.org/jacoco/trunk/doc/examples/build/pom.x... - That's 40 lines in the section to do the "defaults".

Yes, you could add a load of config for files to include/exclude from coverage and so on, but the idea that that's a norm is way more common in Java projects than other languages. Like here's some example Cargo.toml files from complicated Rust projects:

Servo: https://github.com/servo/servo/blob/main/Cargo.toml

rust-gdext: https://github.com/godot-rust/gdext/blob/master/godot-core/C...

ripgrep: https://github.com/BurntSushi/ripgrep/blob/master/Cargo.toml

socketio: https://github.com/1c3t3a/rust-socketio/blob/main/socketio/C...

I'm not clear on why you're seeing the results you are. It could be because your haystack is so small that you're mostly just measuring noise. ripgrep 14 did introduce some optimizations in workloads like this by reducing match overhead, but I don't think it's anything huge in this case. (And I just tried ripgrep 13 on the same commands above and the timings are similar if a tiny bit slower.)

[1]: https://github.com/radare/ired

[2]: https://github.com/BurntSushi/ripgrep/discussions/2597

Explore o Ripgrep no repositório oficial: https://github.com/BurntSushi/ripgrep

🔎🗃️ ripgrep or ugrep (search fast, use regex patterns or fuzzy search, pipe output to bash/zsh shell for further processing V coloring)