A bittersweet goodbye! I've had this car for just about 10 years. Tomorrow morning, it's getting traded in. This little Civic has been such a nice car.
@TenebrisNoctua Yeah I have no idea what's going on yet. Other than GPU instancing, I've done nothing to optimize the code yet. And even the setup for instancing is probably a mess with cache misses and such
More fun with engine dev! Spinning 100k sprites at around 75 FPS in debug mode, and almost 1000 FPS in release mode (huge difference). This is obviously a very isolated test, but I think a good start.
@OfficialZidiam I was surprised by how vast the difference was b/w debug and release mode. It's almost suspiciously good. But there's also a potential cache miss issue that isn't being hit with this test, and that's the part I worry about
The sprite system batches things up via instancing based on texture & render layer. The most expensive part is looping through and changing all the data for each sprite. GPU buffer gets pushed once before render. I think quadtrees might help optimize this too for culling groups.
@badgraphix@EvelTM_Games Modern hybrids are quite clever. In terms of price diff: Civic '27 hybrid is $3k more than the non hybrid. I'd have to do the math to figure out the ROI on that
I'm unimpressed by the current electric car market. Are there any noteworthy electric sedans? I don't want a large car. I'm tempted to just go for the hybrid Civic at this point.
@ScriptOff41968 Yeah that's the only other one that would be viable I think! The problem is that the earliest delivery I can get for it is like March, but I'll at least see if I can test drive one
@Conor3D So here's some fun math:
If you got a badge every 1 minute, it would take over 247 YEARS to get 130M badges.
If you got a badge every 1 second, it would still take over 4 years.
I feel like the limit might be ok lol
Today was a hard day. Today I went through my box of cables and threw many of them away.
Do I really need my mini USB cable? Or my FireWire? Or my 10 HDMI cables that are only 3 feet long? Gone.
Will I regret this? Probably.
Two critical vulnerabilities have been identified in PHP, a widely used programming language that powers websites and web applications. These vulnerabilities (CVE-2026-109618 and CVE-2026-109619) could allow malicious cyber actors to remotely execute code in PHP core, potentially compromising sensitive data and networks.
The FBI urges organizations to take the following steps now:
➡️ If an immediate update is not feasible it is recommended that organizations take the system offline until it can be fully mitigated.
➡️ Immediately update affected PHP installations following the guidance on https://t.co/rDrPSxB3zX. Inventory where PHP runs in your environment, prioritizing internet-facing systems and vendor products that bundle PHP.
➡️ Monitor web servers for suspicious activity, including PHP processes unexpectedly launching command shells or downloading files. Ensure appropriate process-monitoring capabilities are in place to help identify potential exploitation.
➡️ If you find signs of compromise, isolate affected systems, preserve your web server and PHP logs, and report it to your local FBI field office or https://t.co/iqgVZIbCru. Those reports help us identify the actors involved and warn other organizations before they become victims.
For the latest information, follow PHP’s announcement on https://t.co/rDrPSxB3zX, CERT-EU Security Advisory 2026-018, and CISA’s Known Exploited Vulnerabilities catalog.