NewApp Digest
search bot

creation

2026's best RPG might look like Disco Elysium, but it was heavily inspired by Deus Ex, and its creator wants 'to do a first-person game at some point'
AppWizard
July 12, 2026

2026’s best RPG might look like Disco Elysium, but it was heavily inspired by Deus Ex, and its creator wants ‘to do a first-person game at some point’

Christoffer Bodegård began his journey into PC gaming with a DOS machine from his father and first played Disney's The Jungle Book. His passion for role-playing games was ignited by Dragon Age: Origins, which led him to explore many titles, including Planescape: Torment. After eight years of development, his game Esoteric Ebb launched in March to critical acclaim. Currently, he is playing Victoria 3, having logged around 400 hours, and previously played Abiotic Factor. The oldest games on his PC are Heroes of Might and Magic 3, King of Dragon Pass, Deus Ex, and Diablo 2, with Heroes 3 being a favorite. He has logged around 1,000 hours in Esoteric Ebb and is particularly fond of Europa Universalis IV, especially the Anbennar mod. Bodegård has never uninstalled Deus Ex, which greatly influences his design philosophy. He relies on Notepad++ for scripting and has improved his desktop organization from a cluttered state to a cleaner setup.
What Is Serverless PostgreSQL?
Tech Optimizer
July 12, 2026

What Is Serverless PostgreSQL?

Serverless PostgreSQL is a fully managed cloud database model that separates compute and storage, allowing them to scale independently and automatically based on demand. It eliminates the need for manual infrastructure provisioning and capacity planning, charging only for active usage. Unlike traditional PostgreSQL setups, which require continuous resource allocation and manual scaling, serverless PostgreSQL provisions resources on demand and can scale down to zero during idle periods. Serverless PostgreSQL integrates with serverless compute platforms, enabling analytical queries to access the same data within a unified architecture. Key differences between traditional and serverless PostgreSQL include manual versus automatic provisioning and scaling, fixed versus usage-based billing, and high versus reduced operational overhead. Lakebase architecture is an emerging model that combines transactional databases with lakehouse foundations, allowing operational and analytical workloads to coexist on a single platform. This architecture minimizes data duplication and simplifies access, enhancing data management and analysis. Serverless PostgreSQL operates on a cloud-native architecture that enhances efficiency by allowing compute and storage to scale autonomously. It features scale-to-zero behavior, where compute resources are suspended when inactive and reactivated upon new queries. Major providers include Databricks Lakebase, Amazon Aurora Serverless v2, and Neon, each offering varying capabilities and integrations. Pricing for serverless PostgreSQL typically includes charges for compute resources, storage, and data transfer, with costs fluctuating based on workload activity. Cold start latency is a performance consideration, as reactivating compute resources can introduce delays. Strategies to mitigate this include keeping resources partially active or selecting providers with minimal cold start impacts. Serverless PostgreSQL is well-suited for OLTP workloads, while lakebase architecture is better for AI development, variable workloads, and environments requiring rapid iteration. Setting up serverless PostgreSQL involves choosing a provider, creating a database instance, and configuring access settings. It can also be used alongside serverless compute platforms for analytics, further extending its capabilities.
Running pgvector in production on Amazon Aurora PostgreSQL
Tech Optimizer
July 12, 2026

Running pgvector in production on Amazon Aurora PostgreSQL

Running pgvector on Amazon Aurora PostgreSQL-Compatible Edition offers a vector store with operational capabilities, high availability, and scalability. It is favored for Retrieval Augmented Generation (RAG) workloads transitioning to production, but increased traffic introduces challenges like query latency and memory management. Key operational practices for pgvector workloads include selecting the appropriate index type (HNSW or IVFFlat), establishing a baseline schema, choosing a suitable distance operator, scaling the index through quantization and partitioning, and preparing for churn and observability. The prerequisites for using pgvector include an Aurora PostgreSQL-Compatible cluster with specific PostgreSQL versions and the vector extension enabled. The embedding model used in examples is Amazon Titan Text Embeddings V2, which produces 1024-dimensional embeddings. pgvector supports two Approximate Nearest Neighbor (ANN) index types: HNSW, which is efficient for querying and allows for incremental insertions, and IVFFlat, which is less resource-intensive but requires rebuilding if data changes. There are scenarios where forgoing an index is beneficial, such as small datasets or partitioned datasets requiring 100% recall. A baseline schema for a multi-tenant document store includes creating a table for documents with an embedding vector and establishing indexes for tenant IDs and embeddings using HNSW. The recommended parameters for HNSW include m = 16 and ef_construction = 128. Scaling to millions of vectors involves quantization, tuning HNSW parameters, and partitioning. Aurora Optimized Reads can extend effective cache capacity, and managing index churn is crucial for maintaining performance. Observability metrics include query-level statistics, instance-level metrics, and custom application-defined metrics. To clean up after testing, it is advisable to drop the created indexes and tables, and delete the Aurora PostgreSQL-Compatible cluster and any manual snapshots taken during testing.
A piece of GTA modding history that was considered lost has been rebuilt from scratch and fixed 22 years later
AppWizard
July 11, 2026

A piece of GTA modding history that was considered lost has been rebuilt from scratch and fixed 22 years later

The Ghost City in Grand Theft Auto 3 was a hidden location that became lost over time, particularly after the original mod allowing access to it was hosted on a now-defunct site. ModSaver, a hobbyist, recreated the mod from scratch after the original was deemed "Lost Media," enhancing it by adding new collision files to make the area fully playable for the first time in over two decades. This revival highlights the gaming community's dedication to preserving gaming history.
Minecraft Movie Build Challenge winner announcement
AppWizard
July 11, 2026

Minecraft Movie Build Challenge winner announcement

The Tree Village Build was removed from Grand Prize consideration due to an oversight in the admission process, as it incorporated blocks from multiple biomes. However, it will receive a special mention and be featured in the movie alongside the finalists and overall winner. The Tranquil Taiga Tower, another semifinalist, will also be included in the final movie. A Minecraft Movie Squared is set to release on July 23, 2027. All Finalist Builds will transition to the movie, with minor adjustments possible. The exact placements of the Builds in the movie are not disclosed, and the Tree Village Build is included to honor its popularity within the community. Warner Bros. will determine the placement of the Build in the movie.
Logical replication improvements in Amazon RDS for PostgreSQL 18
Tech Optimizer
July 8, 2026

Logical replication improvements in Amazon RDS for PostgreSQL 18

PostgreSQL logical replication has operational challenges, such as the absence of generated columns in the replication stream, replication conflicts causing apply worker halts, and lingering replication slots consuming write-ahead log (WAL) files. PostgreSQL 18 introduces enhancements to address these issues, including the ability to include STORED generated columns in the replication stream with a new publication parameter, detailed conflict counters in pg_stat_subscription_stats, automatic invalidation of idle replication slots, and the ability to toggle two-phase commit settings on live subscriptions. To set up a test environment, two PostgreSQL 18 instances (one publisher and one subscriber) are required, along with an EC2 instance for executing commands. The publisher and subscriber must have specific configurations for logical replication, including enabling logical replication and setting appropriate parameters. PostgreSQL 18 allows the replication of STORED generated columns by using the publish_generated_columns parameter. The subscriber must define these columns as regular columns. The new version also enhances conflict monitoring by providing detailed counters for different types of replication conflicts. Parallel streaming is now the default behavior for subscriptions, improving efficiency. The two-phase commit feature can now be modified on existing subscriptions without needing to recreate them. PostgreSQL 18 also introduces automatic cleanup of idle replication slots, which can be configured to invalidate unused slots after a specified duration. Considerations for implementation include ensuring that the subscriber's column types match those of the publisher for generated columns, the requirement for track_commit_timestamp for certain conflict counters, and the fact that sequences are not replicated. Cleanup of replication resources is recommended after testing to prevent unnecessary costs and WAL accumulation.
Search