u/Sad_Egg_2313

Hi Everyone,

Want to share a little project that I have been working on. It's a PC port of Ace Combat 3.

Some features:

• 3 Graphic modes: Original, Clean, Remaster
• 2 HUDs: Classic, Modern
• Support for XInput controllers
• Runs fully native on PC without emulation.
• Draw distance all the way to the horizon
• Global illumination with atmospheric effects
• Ocean simulation
• Forest simulation
• Upgraded city terrain
• Widescreen support

In the roadmap (Not in order and I'm planning to do weekly releases)

• Volumetric cloud system
• Upgrade Aircraft 3D models and Effects (Missiles, explosions etc)
• Port all the missions
• Swap to the Japanese version with the full story

Anything that you would like to see or added, let me know.

Download: https://github.com/i5han/ac3-remix

Follow me on reddit, patreon, twitter for updates

https://www.patreon.com/cw/i5han

https://x.com/Ishanv9hj

Our saas has a feature that monitors Cloudflare, Supabase, Vercel, and a couple of other platforms. It opens an investigation and alerts the team when production degrades. That could be disk filling up, request error rates climbing, or queries slowing to a crawl.

Which creates an awkward testing problem. Our system does its job only when something else is broken. Everything we need to do a proper test lives behind third-party APIs, in the edge case, when someone else's system is having a bad day.

We considered two options to solve this:

1. The standard toolset: Mockoon, WireMock, etc. Going that route meant proxy settings, routing rules, custom response definitions basically stuff that we didn't like to do.

2. Build our own simulator, with a custom UI built to create and test our failure scenarois with a few clicks. yay! we get to build something (natural escape hatch instead of focusing on distribution)

We went with option two naturally. We needed easy to use scenarios like "95% disk full on Supabase" or "Cloudflare starts returning 8% errors" that anyone on the team could trigger from a UI.

So this is What building it actually looked like:

I asked Claude to build a simulator that could create failure scenarios against our alerting and resolution systems, one platform at a time. The conversation went something like this:

"Let me simulate 95% disk usage on Supabase."
"Let me simulate error type percentages on Cloudflare."
"Add a dropdown to select the project affected by the test."

And a whole lot of this in between (maybe most of it):

"No no that's not what i need, do it like this"
"Its not working check again"
"the alignment in the button is not right"

It took a bit longer than we planned to get the full thing working. But not as long as coding a full simulator from scratch.

Once it was done, we deployed the simulator, started the drill. And to no one's surprise we did find some bugs and luckily managed to fix them all before getting yelled at by a customer. This alone justified building it.

How it works

Under the hood, the simulator uses mitmproxy to programmatically control the request/response flow based on whatever scenario is configured in the UI. When we run a scenario our main application is unaware that its a drill. There are no code changes or divergent code paths to miss. This is why it makes this testing approach more accurate.

Demo

What's next

The goal is to have it run continuously and randomly against our test projects in production. Pick a platform, pick a scenario, fire. Then verify the alert and inspection started. If the alerting path breaks we want to be the first to know.

The lesson

The economics of building custom tooling has changed for certain tasks. It used to be that getting something off the shelf especially mature open source solutions made a good default choice. Now its worth considering the alternative of building depending on your use case.

Would love to know if you have done or considered something similar and what you chose and why?

Hi Everyone

My V8's second battery is on its last legs after 8 years of service. I'm thinking of whether to replace the battery which cost about $100 in my country or upgrade to a newer version.

From the information that I was able to gather every model after the V8 seems to have some sort of downside or issue.

Did any of you upgrade recently? which model did you go for and why?

I'm not tied to Dyson but prefer them for the long term support. This will be another 8-10y purchase if I go for it.

The slowest part of inspecting JSON was never the parsing, it's the ritual. Copy the payload, switch to the browser, find that formatter site, paste, wait. And the moment the file is actually big, the tab freezes anyway.

jsonbolt removes the ritual. Hit a global hotkey (WinKey + J or ⌃ + ⌥ + J)and whatever's in your clipboard opens instantly. Raw JSON or a URL, it fetches and renders either. No browser, no paste box, no upload.

And because the engine parses at ~3GB/s (Rust, GPU-rendered tree that only draws visible rows), "big" stops being a category. A 1GB file opens before your finger leaves the trackpad. Search is SIMD-accelerated across the whole document, and it handles 100M+ nodes without breaking a sweat.

There's also a CLI on the same engine (jb paths / jb schema / jb search --where) for scripting, or for slicing huge files down to something an LLM can actually read. Works really great with terminal AI agents like claude

Everything runs locally. Free for personal use, no account: jsonbolt.com (macOS Apple Silicon + Windows)

If you've got a file that chokes it, send it this way the 1GB+ range is what we optimize against.

https://preview.redd.it/447z2os3h7dh1.png?width=2624&format=png&auto=webp&s=e633370bffabfba2af4561558c27c6f25e3d021a