Reddit Programming – Telegram
Reddit Programming
210 subscribers
1.22K photos
125K links
I will send you newest post from subreddit /r/programming
Download Telegram
Article: Why Big Tech Turns Everything Into a Knife Fight
https://www.reddit.com/r/programming/comments/1q1j104/article_why_big_tech_turns_everything_into_a/

<!-- SC_OFF -->An unhinged but honest read for anyone exhausted by big tech politics, performative collaboration, and endless internal knife fights. I wrote it partly to make sense of my own experience, partly to see if there’s a way to make corporate environments less hostile — or at least to entertain bored engineers who’ve seen this movie before. Thinking about extending it into a full-fledged Tech Bro Saga. Would love feedback, character ideas, or stories you’d want to see folded in. <!-- SC_ON --> submitted by /u/NoVibeCoding (https://www.reddit.com/user/NoVibeCoding)
[link] (https://medium.com/@dmitrytrifonov/why-big-tech-turns-everything-into-a-knife-fight-42e221944ec8) [comments] (https://www.reddit.com/r/programming/comments/1q1j104/article_why_big_tech_turns_everything_into_a/)
coco: a simple stackless, single-threaded, and header-only C++20 coroutine library
https://www.reddit.com/r/programming/comments/1q1nrd8/coco_a_simple_stackless_singlethreaded_and/

<!-- SC_OFF -->Hi all, I have rewritten my coroutine library, coco (https://github.com/kingluo/coco), using the C++20 coroutine API. <!-- SC_ON --> submitted by /u/Ill_Excuse_4291 (https://www.reddit.com/user/Ill_Excuse_4291)
[link] (http://luajit.io/posts/coco-cpp20-coroutine/) [comments] (https://www.reddit.com/r/programming/comments/1q1nrd8/coco_a_simple_stackless_singlethreaded_and/)
Encapsulating audio metadata and edit logic in a single text format
https://www.reddit.com/r/programming/comments/1q2rvgs/encapsulating_audio_metadata_and_edit_logic_in_a/

<!-- SC_OFF -->CUE sheets describe audio timestamps and metadata, but I wanted something a bit more expressive.
I built a CUE-based text format and a tool with SQL-like methods, keeping it small and easy to implement while allowing simple but effective edits.
In the demo, an album medley is created using only MP3 drag & drop and text copy/paste—no waveform editing required. <!-- SC_ON --> submitted by /u/cutandjoin (https://www.reddit.com/user/cutandjoin)
[link] (https://youtu.be/-beNsYuPZaQ) [comments] (https://www.reddit.com/r/programming/comments/1q2rvgs/encapsulating_audio_metadata_and_edit_logic_in_a/)
identity is a physical property, not a digital permission
https://www.reddit.com/r/programming/comments/1q2vf8z/identity_is_a_physical_property_not_a_digital/

<!-- SC_OFF -->The Problem
Almost every anti-counterfeit or authentication system today starts with a digital identity and tries to attach it to a physical thing. QR codes, serial numbers, NFC tags, cloud verification, even ML-based "real vs. fake" image checks—they all share one assumption: the digital layer is the source of truth. The physical object is just a carrier. That assumption started to feel backwards. The Core Idea: Extract, Don't Assign
What if a physical object already has a unique, measurable identity formed during its creation (microscopic misalignments, printing imperfections, layer offsets)?
What if, instead of gluing a digital code onto it, we just measure what's already there and make the digital layer a reference to that physical fingerprint? That’s the premise of PBM (Perspective-Based Markers). It's a simple physical-layer experiment. How It Works (The Simple Version)
The setup is deliberately low-tech: Print two high-frequency grid patterns, one on top of the other, with a tiny, fixed physical gap (millimeters) between them. Capture an image from a slight angle. The physics part: If a real 3D gap exists, you get parallax (the grids shift relative to each other in the image). If it's a flat photo, a screen replay, or a reprint, the parallax field collapses. The math is binary. What It Does NOT Use
This is the important part: No neural networks No "AI confidence score" No cloud API calls for the core verification No training data or heuristics What It DOES Use Deterministic signal processing: FFT and phase correlation. A simple signal-to-noise threshold. Output is PHYSICAL, NON_PHYSICAL, or UNDECIDABLE. The UNDECIDABLE result is intentional. If the signal is ambiguous, the system declares "I don't know." It won't guess. This feels healthier than systems that hallucinate certainty. Tested Bypass Methods (They Fail)
I tried the obvious attacks: Taking a photo of the token and printing it Showing the token on a phone screen High-resolution reprinting To the human eye, they look perfect. They might even pass a "strong signal" check. But the relative parallax between the two grid layers? Zero. Physics doesn't negotiate. You Can Try It Yourself (Seriously)
You don't need a lab. To see the parallax effect: An inkjet printer A4 paper A spacer like a CD case to create the gap A drop of cooking oil (to make the top paper translucent and see both layers) That's enough to observe the core principle. Why Publish This Openly?
I don't want this to turn into: "Trust our proprietary model" "Upload to our verification API" "Enterprise pricing available" This describes a physics-based constraint, not a product. If the method is flawed, I want it broken in public. If it's valid, it should belong to anyone who understands the math. The repository and full technical specification are public (link in comments). I'm happy to discuss why this might be a dead end, or where it could be genuinely useful. Happy New Year. https://github.com/illegal-instruction-co/pbm-core <!-- SC_ON --> submitted by /u/Humble-Plastic-5285 (https://www.reddit.com/user/Humble-Plastic-5285)
[link] (https://github.com/illegal-instruction-co/pbm-core) [comments] (https://www.reddit.com/r/programming/comments/1q2vf8z/identity_is_a_physical_property_not_a_digital/)
Native Android Application Development in Swift
https://www.reddit.com/r/programming/comments/1q2wl9i/native_android_application_development_in_swift/

<!-- SC_OFF -->Hi all, imike here. I just released Swift Stream IDE v1.17.0, which adds full native Android application development written entirely in Swift. That means you can now build Android apps without touching XML, Java, or Kotlin. Swift Stream IDE is an open-source VSCode extension that sets up a ready-to-use Swift development environment in Docker, supporting server-side, web, embedded, and now full Android development. With this release, you can create Android applications using familiar templates like Empty Activity, Basic Views (two fragments), or Navigation UI (tab bar), all in Swift. Under the hood, all projects are powered by SwifDroid, a framework I built to wrap the entire native Android app model. It handles the application lifecycle and manifest, activities and fragments, Android, AndroidX, Material, and Flexbox UI widgets, and even automatically wires Gradle dependencies. Supported SDKs are 28 to 35, and with Swift 6.3, it might go down (https://forums.swift.org/t/android-api-minimum-for-the-swift-sdk-for-android/82874) to 24+. Example UI code: ConstraintLayout { VStack { TextView("Hello from Swift!") .width(.matchParent) .height(.wrapContent) .textColor(.green) MaterialButton("Tap Me") .onClick { print("Button tapped!") } } .centerVertical() .leftToParent() .rightToParent() } The first time you create a project, make yourself a cup of tea/coffee. The IDE pulls the Swift toolchain, Android SDK, and NDK, and caches them in Docker volumes. After that, new projects are created instantly. The first build compiles Swift, generates a full Android project (ready to open in Android Studio), and creates a Gradle wrapper. After that, builds take just a few seconds. Once Swift is compiled, you can simply open the Application folder in Android Studio and hit Run or Restart to see your changes. All the necessary files from Swift Stream IDE are already in place, so iteration is fast and seamless. This is the first public release. Android is huge, and there are still widgets in progress, but the system is real and usable today. Documentation: https://docs.swifdroid.com/app/ <!-- SC_ON --> submitted by /u/imike3049 (https://www.reddit.com/user/imike3049)
[link] (https://docs.swifdroid.com/app/) [comments] (https://www.reddit.com/r/programming/comments/1q2wl9i/native_android_application_development_in_swift/)