Reddit Programming – Telegram
Reddit Programming
212 subscribers
1.22K photos
125K links
I will send you newest post from subreddit /r/programming
Download Telegram
1.0.8 @tnf-dev/mui 1.0.8 @tnf-dev/react 1.0.8 @ui-ux-gang/devextreme-angular-rpk 24.1.7 @yoobic/design-system 6.5.17 @yoobic/jpeg-camera-es6 1.0.13 @yoobic/yobi 8.7.53 airchief 0.3.1 airpilot 0.8.8 angulartics2 14.1.1, 14.1.2 browser-webdriver-downloader 3.0.8 capacitor-notificationhandler 0.0.2, 0.0.3 capacitor-plugin-healthapp 0.0.2, 0.0.3 capacitor-plugin-ihealth 1.1.8, 1.1.9 capacitor-plugin-vonage 1.0.2, 1.0.3 capacitorandroidpermissions 0.0.4, 0.0.5 config-cordova 0.8.5 cordova-plugin-voxeet2 1.0.24 cordova-voxeet 1.0.32 create-hest-app 0.1.9 db-evo 1.1.4, 1.1.5 devextreme-angular-rpk 21.2.8 ember-browser-services 5.0.2, 5.0.3 ember-headless-form 1.1.2, 1.1.3 ember-headless-form-yup 1.0.1 ember-headless-table 2.1.5, 2.1.6 ember-url-hash-polyfill 1.0.12, 1.0.13 ember-velcro 2.2.1, 2.2.2 encounter-playground 0.0.2, 0.0.3, 0.0.4, 0.0.5 eslint-config-crowdstrike 11.0.2, 11.0.3 eslint-config-crowdstrike-node 4.0.3, 4.0.4 eslint-config-teselagen 6.1.7 globalize-rpk 1.7.4 graphql-sequelize-teselagen 5.3.8 html-to-base64-image 1.0.2 json-rules-engine-simplified 0.2.1 jumpgate 0.0.2 koa2-swagger-ui 5.11.1, 5.11.2 mcfly-semantic-release 1.3.1 mcp-knowledge-base 0.0.2 mcp-knowledge-graph 1.2.1 mobioffice-cli 1.0.3 monorepo-next 13.0.1, 13.0.2 mstate-angular 0.4.4 mstate-cli 0.4.7 mstate-dev-react 1.1.1 mstate-react 1.6.5 ng2-file-upload 7.0.2, 7.0.3, 8.0.1, 8.0.2, 8.0.3, 9.0.1 ngx-bootstrap 18.1.4, 19.0.3, 19.0.4, 20.0.3, 20.0.4, 20.0.5 ngx-color 10.0.1, 10.0.2 ngx-toastr 19.0.1, 19.0.2 ngx-trend 8.0.1 ngx-ws 1.1.5, 1.1.6 oradm-to-gql 35.0.14, 35.0.15 oradm-to-sqlz 1.1.2 ove-auto-annotate 0.0.9 pm2-gelf-json 1.0.4, 1.0.5 printjs-rpk 1.6.1 react-complaint-image 0.0.32 react-jsonschema-form-conditionals 0.3.18 remark-preset-lint-crowdstrike 4.0.1, 4.0.2 rxnt-authentication 0.0.3, 0.0.4, 0.0.5, 0.0.6 rxnt-healthchecks-nestjs 1.0.2, 1.0.3, 1.0.4, 1.0.5 rxnt-kue 1.0.4, 1.0.5, 1.0.6, 1.0.7 swc-plugin-component-annotate 1.9.1, 1.9.2 tbssnch 1.0.2 teselagen-interval-tree 1.1.2 tg-client-query-builder 2.14.4, 2.14.5 tg-redbird 1.3.1 tg-seq-gen 1.0.9, 1.0.10 thangved-react-grid 1.0.3 ts-gaussian 3.0.5, 3.0.6 ts-imports 1.0.1, 1.0.2 tvi-cli 0.1.5 ve-bamreader 0.2.6 ve-editor 1.0.1 verror-extra 6.0.1 voip-callkit 1.0.2, 1.0.3 wdio-web-reporter 0.1.3 yargs-help-output 5.0.3 yoo-styles 6.0.326 <!-- SC_ON --> submitted by /u/Advocatemack (https://www.reddit.com/user/Advocatemack)
[link] (https://www.aikido.dev/blog/s1ngularity-nx-attackers-strike-again) [comments] (https://www.reddit.com/r/programming/comments/1nihrpt/crowdstrike_packages_infected_with_malware_and/)
A new experiment: making Protobuf in C++ less painful (inspired by the old “why is Protobuf so clunky?” thread)
https://www.reddit.com/r/programming/comments/1niuy6j/a_new_experiment_making_protobuf_in_c_less/

<!-- SC_OFF -->Hey folks, Some hours back there was a lively discussion here: Why is Protobuf’s C API so clunky? (https://www.reddit.com/r/programming/comments/1nibv4y/why_is_protobufs_c_api_so_clunky_would_a/) I was in that thread too, tossing around ideas like “what if we could do user["id"] = 123; and have it fail at compile time if you tried user["id"] = "oops";”. The feedback I got there was super helpful — a few people pointed out I was basically forcing JSON-style dynamics into a static Protobuf world, which doesn’t really fit. That clicked with me. Since then I hacked on a small library/plugin called Sugar-Proto. It’s a protoc plugin that generates wrappers around your .proto messages, giving you something closer to a nlohmann/json feel, but still 100% type-safe and zero runtime reflection. Example: User user; UserWrapped u(user); u.name = "Alice"; u.id = 42; u.posts.push_back({{"noscript", "Hello"}, {"comments", {{"text", "Nice!"}}}}); Under the hood it’s just normal protobuf fields, no hidden runtime map lookups. The idea is: make the API less clunky without pretending it’s JSON. It’s early, not production-ready yet, but I’d love for people to kick the tires and tell me what feels right/wrong. Curious to hear if anyone else tried wrapping protobuf in a more ergonomic C++ way. Do you think this direction has legs, or is protobuf doomed to always feel a bit Java-ish in C++? <!-- SC_ON --> submitted by /u/Humble-Plastic-5285 (https://www.reddit.com/user/Humble-Plastic-5285)
[link] (https://github.com/illegal-instruction-co/sugar-proto) [comments] (https://www.reddit.com/r/programming/comments/1niuy6j/a_new_experiment_making_protobuf_in_c_less/)
Load Balancing: The "Zombie Server" Problem
https://www.reddit.com/r/programming/comments/1nj3sgn/load_balancing_the_zombie_server_problem/

<!-- SC_OFF --> Zombie Server Anatomy: Understanding servers that lie about their health Health Check Evolution: From basic pings to intelligent application-level checks Detection Strategies: Multi-layered approaches for catching zombie behaviors Real-World Patterns: How Netflix, Uber, and Amazon solve this problem Hands-On Implementation: Build a complete zombie detection system The Zombie Server Phenomenon A zombie server looks alive to your load balancer but cannot serve real user requests. Unlike completely dead servers that fail health checks, zombies pass basic connectivity tests while silently corrupting user experiences. <!-- SC_ON --> submitted by /u/Extra_Ear_10 (https://www.reddit.com/user/Extra_Ear_10)
[link] (https://systemdr.substack.com/p/load-balancing-the-zombie-server) [comments] (https://www.reddit.com/r/programming/comments/1nj3sgn/load_balancing_the_zombie_server_problem/)
UUIDv47: keep v7 in your DB, emit v4 outside (SipHash-masked timestamp)
https://www.reddit.com/r/programming/comments/1njebn0/uuidv47_keep_v7_in_your_db_emit_v4_outside/

<!-- SC_OFF -->Hi, I’m the author of uuidv47. The idea is simple: keep UUIDv7 internally for database indexing and sortability, but emit UUIDv4-looking façades externally so clients don’t see timing patterns. How it works: the 48-bit timestamp is XOR-masked with a keyed SipHash-2-4 stream derived from the UUID’s random field. The random bits are preserved, the version flips between 7 (inside) and 4 (outside), and the RFC variant is kept. The mapping is injective: (ts, rand) → (encTS, rand). Decode is just encTS ⊕ mask, so round-trip is exact. Security: SipHash is a PRF, so observing façades doesn’t leak the key. Wrong key = wrong timestamp. Rotation can be done with a key-ID outside the UUID. Performance: one SipHash over 10 bytes + a couple of 48-bit loads/stores. Nanosecond overhead, header-only C89, no deps, allocation-free. Tests: SipHash reference vectors, round-trip encode/decode, and version/variant invariants. Curious to hear feedback! EDIT: Precision, In the database, we keep the ID as UUIDv7. When it goes outside, it’s converted into a masked UUIDv4. One global key is all that’s needed there’s no risk of leaks and the performance impact is effectively zero. <!-- SC_ON --> submitted by /u/aabbdev (https://www.reddit.com/user/aabbdev)
[link] (https://github.com/stateless-me/uuidv47) [comments] (https://www.reddit.com/r/programming/comments/1njebn0/uuidv47_keep_v7_in_your_db_emit_v4_outside/)
Read free..“Microsoft Interview Experience Compensation : 45LPA Role: SDE 2 (Backend) 📩 Application Process…“
https://www.reddit.com/r/programming/comments/1nk0efk/read_freemicrosoft_interview_experience/

<!-- SC_OFF -->Read free“Microsoft Interview Experience Compensation : 45LPA Role: SDE 2 (Backend) 📩 Application Process…“ by 🥷Byte Ninja on Medium: <!-- SC_ON --> submitted by /u/ajit_45288 (https://www.reddit.com/user/ajit_45288)
[link] (https://medium.com/@ajit34555/microsoft-interview-experience-compensation-45lpa-role-sde-2-backend-application-process-e077d95fd9f7) [comments] (https://www.reddit.com/r/programming/comments/1nk0efk/read_freemicrosoft_interview_experience/)