Reddit Programming – Telegram
Reddit Programming
211 subscribers
1.22K photos
125K links
I will send you newest post from subreddit /r/programming
Download Telegram
Building a Custom DatePicker in Java Swing and Persisting Dates in MySQL
https://www.reddit.com/r/programming/comments/1pooqzj/building_a_custom_datepicker_in_java_swing_and/

<!-- SC_OFF -->Java Swing doesn’t provide a modern DatePicker by default, so I built a custom calendar component in pure Swing and connected it to MySQL using JDBC. The calendar supports month/year navigation, date selection, and saving the selected date directly into a DATE column in MySQL. This is useful for forms like birth date, registration, or appointments. I shared a short video walkthrough and the full source code for anyone learning Java Swing or working on desktop projects. 📺 Video: Java Swing Custom Calendar DatePicker | Save Selected Date into MySQL Database (https://www.youtube.com/watch?v=pLI2I6TCiFw&t=426s)
💻 Code: Love2Programming (https://love2programming.com/post-list/2034) <!-- SC_ON --> submitted by /u/Substantial-Log-9305 (https://www.reddit.com/user/Substantial-Log-9305)
[link] (https://www.youtube.com/watch?v=pLI2I6TCiFw&t=426s) [comments] (https://www.reddit.com/r/programming/comments/1pooqzj/building_a_custom_datepicker_in_java_swing_and/)
System calls: how programs talk to the Linux kernel
https://www.reddit.com/r/programming/comments/1poy70l/system_calls_how_programs_talk_to_the_linux_kernel/

<!-- SC_OFF -->Hello everyone, I've just published the second post in my Linux Inside Out series. In the first post we demystified the Linux kernel a bit: where it lives, how to boot it in a VM, and we even wrote a tiny init program. In this second post we go one layer deeper and look at how programs actually talk to the kernel.
We'll do a few small experiments to see: how our init program (that we wrote in the first post) communicates with the kernel via system calls how something like `echo "hello"` ends up printing text on your screen how to trace system calls to understand what a program is doing I’m mainly targeting developers and self-hosters who use Linux daily and are curious about the internals of a Linux-based operating system. This is part 2 of a longer series, going layer by layer through a Linux system while trying to keep things practical and approachable. Link (part 2): https://serversfor.dev/linux-inside-out/system-calls-how-programs-talk-to-the-linux-kernel/
Link (part 1): https://serversfor.dev/linux-inside-out/the-linux-kernel-is-just-a-program/ Any feedback is appreciated. <!-- SC_ON --> submitted by /u/indieHungary (https://www.reddit.com/user/indieHungary)
[link] (https://serversfor.dev/linux-inside-out/system-calls-how-programs-talk-to-the-linux-kernel/) [comments] (https://www.reddit.com/r/programming/comments/1poy70l/system_calls_how_programs_talk_to_the_linux_kernel/)
Stack Overflow Annual Survey
https://www.reddit.com/r/programming/comments/1pozw5i/stack_overflow_annual_survey/

<!-- SC_OFF -->Some of my (subjective) surprising takeaways: Haskell, Clojure, Nix didn't make list of languages, only write-ins. Clojure really surprised me as it's not in top listed but Lisp is! Maybe it's because programmers of all Lisp dialects (including Clojure) self-reported as Lisp users. Emacs didnt make list of top editors, only write-in Gleam is one of most admired langs (never heard of it before!) Rust, Cargo most admired language & build tool - not surprising considering Rust hype uv is most admired tech tag - not surprising as it's a popular Python tool implemented in Rust What do you all think of this year's survey results? Did you participate? <!-- SC_ON --> submitted by /u/sohang-3112 (https://www.reddit.com/user/sohang-3112)
[link] (https://survey.stackoverflow.co/2025/technology/) [comments] (https://www.reddit.com/r/programming/comments/1pozw5i/stack_overflow_annual_survey/)
Further Optimizing my Java SwissTable: Profile Pollution and SWAR Probing
https://www.reddit.com/r/programming/comments/1pp0wg2/further_optimizing_my_java_swisstable_profile/

<!-- SC_OFF -->Hey everyone. Follow-up to my last post where I built a SwissTable-ish hash map on the JVM: https://www.reddit.com/r/programming/comments/1plbpzg/building_a_fast_memoryefficient_hash_table_in/ This time I went back with a profiler and optimized the actual hot path (findIndex). A huge chunk of time was going to Objects.equals() because of profile pollution / missed devirtualization. After fixing that, the next bottleneck was ARM/NEON “movemask” pain (VectorMask.toLong()), so I tried SWAR… and it ended up faster (even on x86, which I did not expect). <!-- SC_ON --> submitted by /u/Charming-Top-8583 (https://www.reddit.com/user/Charming-Top-8583)
[link] (https://bluuewhale.github.io/posts/further-optimizing-my-java-swiss-table/) [comments] (https://www.reddit.com/r/programming/comments/1pp0wg2/further_optimizing_my_java_swisstable_profile/)
Greptile publishes their State of AI coding 2025 report
https://www.reddit.com/r/programming/comments/1ppexvk/greptile_publishes_their_state_of_ai_coding_2025/

<!-- SC_OFF -->Greptile, a company that does AI Code reviews for 1 billion lines of code from 2000 companies a month, has published some metrics on the code they've processed.: * Lines of code per developer grew from 4,450 to 7,839 in 2025. * Median PR size increased 33% from March to November 2025, rising from 57 to 76 lines changed per PR. * Medium teams (6-15 devs) increased output from 7,005 to 13,227 lines per developer. ^Median lines changed per file grew from 18 to 22 as PRs become denser. <!-- SC_ON --> submitted by /u/humanquester (https://www.reddit.com/user/humanquester)
[link] (https://www.greptile.com/state-of-ai-coding-2025) [comments] (https://www.reddit.com/r/programming/comments/1ppexvk/greptile_publishes_their_state_of_ai_coding_2025/)
What writing a tiny bytecode VM taught me about debugging long-running programs
https://www.reddit.com/r/programming/comments/1pplwnm/what_writing_a_tiny_bytecode_vm_taught_me_about/

<!-- SC_OFF -->While working on a small bytecode VM for learning purposes, I ran into an issue that surprised me: bugs that were invisible in short programs became obvious only once the runtime stayed “alive” for a while (loops, timers, simple games). One example was a Pong-like loop that ran continuously. It exposed: subtle stack growth due to mismatched push/pop paths error handling paths that didn’t unwind state correctly how logging per instruction was far more useful than stepping through source code What helped most wasn’t adding more language features, but: dumping VM state (stack, frames, instruction pointer) at well-defined boundaries diffing dumps between iterations to spot drift treating the VM like a long-running system rather than a noscript runner The takeaway for me was that continuous programs are a better stress test for runtimes than one-shot noscripts, even when the program itself is trivial. I’m curious: What small programs do you use to shake out runtime or interpreter bugs? Have you found VM-level tooling more useful than source-level debugging for this kind of work? (Implementation details intentionally omitted — this is about the debugging approach rather than a specific project.) <!-- SC_ON --> submitted by /u/Imaginary-Pound-1729 (https://www.reddit.com/user/Imaginary-Pound-1729)
[link] (https://vexonlang.blogspot.com/2025/12/vexon-what-building-small-bytecode.html) [comments] (https://www.reddit.com/r/programming/comments/1pplwnm/what_writing_a_tiny_bytecode_vm_taught_me_about/)