Urgent.News

What's breaking now, across thousands of outlets.

Tech

Government Plans Petroleum Levy Cut While Seeking Rs. 1.5 Trillion Elsewhere

The government is examining a proposal to gradually reduce the Petroleum Levy to Rs. 5 to Rs. 10 per liter … Read More The post Government Plans Petroleum Levy Cut While Seeking Rs. 1.5 Trillion Elsewhere appeared first on ProPakistani .

Government Plans Petroleum Levy Cut While Seeking Rs. 1.5 Trillion Elsewhere

The government is considering a proposal to gradually reduce the Petroleum Levy and generate additional revenue through new taxes, reduced exemptions, spending cuts, and better enforcement. The proposal, which aims to raise Rs. 1.5 trillion annually, includes measures such as higher Federal Excise Duty and regulatory duties on luxury imports, expensive vehicles, and high-end consumption.

The plan also explores additional taxes on large companies and high-income individuals, withdrawal of selected tax exemptions, agriculture income, and wealth taxes, as well as a carbon levy. Technology-based tax enforcement, including the use of data from various transactions and GIS and satellite technology, is also part of the plan.

The proposal estimates that these measures could generate hundreds of billions of rupees, although it acknowledges that actual collections may fall short of theoretical potential. The proposal seeks feedback from relevant institutions and will require IMF approval and provincial coordination.

Brief written by urgent.news from ProPakistani's own syndicated text. Machine-written — may contain errors; check the original before relying on it.

Read the original at propakistani.pk →

More in Tech

One rounding, not many: why a provably-fair verifier must match the server bit for bit

Originally published on the Betkyo Journal , where every figure is read from the game engine's source. Every provably fair round on this site turns a 256-bit hash into a number between 0 and 1 and…

  • Provably-fair verifier must match server bit for bit
  • Hash conversion involves rounding due to precision limits
  • Single rounding ensures accurate game outcome verification

Nothing could start without the dependency we had filed as optional

Our configuration service was tier three. No SLO, no pager, a single replica for a long time, and a line in the architecture document describing it as a soft dependency because clients cache their…

  • Configuration service deemed soft dependency, but crucial for client startup
  • Node pool rotation caused service outage, triggering cascade failures
  • Service reclassified as tier one with added redundancy and monitoring

I Made Four Authorization Engines Answer the Same Questions

"Which authorization engine should I use" always gets answered with a table. Cedar is analyzable, Rego is expressive, Zanzibar is relationship-based. I could never feel the difference from any of it.

  • Four authorization engines tested with identical rules and simultaneous requests
  • Cedar, Rego, Zanzibar, and Casbin engines each with unique strengths and weaknesses
  • ReBAC failed to handle time-based constraints during business hours

Stop Slamming Downstream Services: Singleflight Request Coalescing with Java Virtual Threads

Stop Slamming Downstream Services: Singleflight Request Coalescing with Java Virtual Threads Virtual threads solved your JVM I/O bottlenecks, but downstream internal services are now on fire because…

  • Singleflight request coalescing pattern addresses virtual thread load on services.
  • Developers often use Redis or synchronized blocks, worsening the issue.
  • JVM-based Singleflight ensures efficient, scalable high-throughput handling.

More from Saturday 12 September →