[{"data":1,"prerenderedAt":822},["ShallowReactive",2],{"tag-labels":3,"site-header":4,"article-rust-di-kernel-linux-revolusi-atau-cuma-hype-id":72},{},{"featuredPost":5,"navigations":29},{"id":6,"title":7,"title_en":8,"slug":9,"excerpt":10,"excerpt_en":11,"has_translation":12,"published_at":13,"reading_time":14,"hidden_from_listing":15,"tags":16,"thumbnail_image":21,"og_image":22,"series":23,"authors":28},110,"Ketika Pilih Framework Cuma Biar Kelihatan Beda","When You Pick a Framework Just to Look Different","ketika-pilih-framework-cuma-biar-kelihatan-beda","Terakhir kali kamu milih framework atau library baru, itu karena masalahmu butuh alat itu, atau karena alatnya kedengaran keren dan belum banyak yang pakai? Pertanyaan ini nggak enak dijawab. Soalnya keputusan teknologi sering diambil dengan alasan yang nggak pernah ditulis di dokumen teknis mana pun.","The last time you chose a new framework or library, was it because your problem needed that tool, or because it sounded cool and few people around you were using it? That question is uncomfortable. Technology decisions are often made for reasons that never appear in any technical document.",true,"2026-10-06T15:25:21.000Z",5,false,[17,18,19,20],"karier","framework","opini","pengalaman",null,"\u002Fog\u002Fketika-pilih-framework-cuma-biar-kelihatan-beda.png",{"id":24,"title":25,"title_en":26,"slug":27},9,"Artikel","Articles","all",[],[30,46,67],{"collection":31,"item":32},"series",{"__typename":31,"title":25,"title_en":26,"slug":27,"children_series":33},[34,38,42],{"title":35,"title_en":36,"slug":37},"Kecerdasan Artifisial","Artificial Intelligence","kecerdasan-artifisial",{"title":39,"title_en":40,"slug":41},"Konsep Dasar Pemrograman","Programming Fundamentals","konsep-dasar-pemrograman",{"title":43,"title_en":44,"slug":45},"Algoritma dan Struktur Data","Algorithms and Data Structures","algoritma-struktur-data",{"collection":31,"item":47},{"__typename":31,"title":48,"title_en":48,"slug":49,"children_series":50},"Tutorial","tutorial",[51,55,59,63],{"title":52,"title_en":53,"slug":54},"Belajar Python","Learning Python","belajar-python",{"title":56,"title_en":57,"slug":58},"Belajar Golang","Learning Go","belajar-golang",{"title":60,"title_en":61,"slug":62},"Belajar Java","Learning Java","belajar-java",{"title":64,"title_en":65,"slug":66},"Belajar Pascal","Learning Pascal","belajar-pascal",{"collection":31,"item":68},{"__typename":31,"title":69,"title_en":69,"slug":70,"children_series":71},"Lab","lab",[],{"article":73,"renderedBody":707,"renderedTakeaway":708,"latestArticles":709,"toc":806},{"id":74,"title":75,"title_en":76,"slug":77,"excerpt":78,"excerpt_en":79,"has_translation":12,"published_at":80,"reading_time":81,"hidden_from_listing":15,"tags":82,"thumbnail_image":21,"og_image":88,"series":89,"authors":699,"body_locale":702,"available_locales":703,"body":705,"takeway":706,"prerequisite":21},111,"Rust Masuk Kernel Linux: Revolusi Nyata atau Cuma Euforia RIIR?","Rust Enters the Linux Kernel: A Real Revolution or Just RIIR Euphoria?","rust-di-kernel-linux-revolusi-atau-cuma-hype","Selama lebih dari 30 tahun kernel Linux cuma mau bahasa C, lalu tiba-tiba Rust resmi masuk di Linux 6.1. Itu revolusi beneran atau cuma kebawa euforia meme Rewrite It In Rust? Yuk lihat datanya, bukan cuma opininya.","For more than 30 years the Linux kernel only wanted C, then Rust officially landed in Linux 6.1. Is that a real revolution, or just the pull of the Rewrite It In Rust meme? Let's look at the data, not the opinions.","2026-10-07T03:40:24.000Z",6,[83,84,85,86,87],"rust","linux","kernel","system-programming","memory-safety","\u002Fog\u002Frust-di-kernel-linux-revolusi-atau-cuma-hype.png",{"id":24,"title":25,"title_en":26,"slug":27,"description":21,"description_en":90,"articles":91,"children_series":692,"parent_series":21},"Everything that isn't a tutorial or a lab: explainers, opinions, and notes from building things.",[92,107,122,135,148,163,178,192,207,221,233,248,272,290,310,328,346,366,382,399,417,432,447,463,478,493,507,523,541,560,575,591,608,620,624,629,643,658,674],{"id":93,"title":94,"title_en":95,"slug":96,"excerpt":97,"excerpt_en":98,"has_translation":12,"published_at":99,"reading_time":14,"hidden_from_listing":15,"tags":100,"thumbnail_image":21,"og_image":104,"series":105,"authors":106},11,"Apa Kabar JavaScript? Rilis State of JS 2022","How's JavaScript Doing? The State of JS 2022 Results Are In","apa-kabar-javascript-rilis-state-of-js-2022","Survei State of JS 2022 resmi dirilis dengan lonjakan responden yang luar biasa! Framework dan build tool apa saja yang berhasil mencuri perhatian tahun ini?","The State of JS 2022 survey is out, and the respondent count jumped hard. Which frameworks and build tools actually stole the year?","2026-06-15T02:36:30.205Z",[101,102,103],"javascript","web","news","\u002Fog\u002Fapa-kabar-javascript-rilis-state-of-js-2022.png",{"id":24,"title":25,"title_en":26,"slug":27},[],{"id":108,"title":109,"title_en":110,"slug":111,"excerpt":112,"excerpt_en":113,"has_translation":12,"published_at":114,"reading_time":14,"hidden_from_listing":15,"tags":115,"thumbnail_image":21,"og_image":119,"series":120,"authors":121},12,"Buat PowerShell Lebih Berwarna dengan Starship","Make PowerShell More Colorful with Starship","buat-powershell-lebih-berwarna-dengan-starship","Bosen sama tampilan PowerShell yang hitam putih dan kaku? Yuk, sulap terminalmu jadi lebih interaktif, estetik, dan berwarna pakai Starship!","Tired of PowerShell looking black, white, and stiff? Turn your terminal into something interactive, aesthetic, and colorful with Starship!","2026-06-15T02:37:24.143Z",[116,117,118],"shell","windows","powershell","\u002Fog\u002Fbuat-powershell-lebih-berwarna-dengan-starship.png",{"id":24,"title":25,"title_en":26,"slug":27},[],{"id":123,"title":124,"title_en":125,"slug":126,"excerpt":127,"excerpt_en":128,"has_translation":12,"published_at":129,"reading_time":14,"hidden_from_listing":15,"tags":130,"thumbnail_image":21,"og_image":132,"series":133,"authors":134},13,"Hal yang Perlu Diperhatikan Sebelum Pindah ke Linux","Things to Consider Before Switching to Linux","hal-yang-perlu-diperhatikan-sebelum-pindah-ke-linux","Tertarik migrasi dari Windows ke Linux tapi masih ragu? Yuk, pelajari kelebihan, kekurangan, dan persiapan penting sebelum kamu benar-benar pindah!","Tempted to migrate from Windows to Linux but still unsure? Learn the upsides, the downsides, and the prep you need before you actually switch.","2026-06-15T02:37:24.570Z",[84,117,131],"foss","\u002Fog\u002Fhal-yang-perlu-diperhatikan-sebelum-pindah-ke-linux.png",{"id":24,"title":25,"title_en":26,"slug":27},[],{"id":136,"title":137,"title_en":138,"slug":139,"excerpt":140,"excerpt_en":141,"has_translation":12,"published_at":142,"reading_time":14,"hidden_from_listing":15,"tags":143,"thumbnail_image":21,"og_image":145,"series":146,"authors":147},15,"Kenapa Ada Banyak Sekali Distro Linux?","Why Are There So Many Linux Distros?","kenapa-ada-banyak-sekali-distro-linux","Pernah bingung pas mau install Linux tapi malah disuguhi puluhan pilihan distro? Tenang, kalian nggak sendirian. Yuk, cari tahu kenapa distro Linux bisa sebanyak itu dan apa bedanya!","Were you confused when installing Linux handed you dozens of distro options? You're not alone. Here's why there are so many, and what actually differs.","2026-06-15T02:38:14.569Z",[84,144],"distro","\u002Fog\u002Fkenapa-ada-banyak-sekali-distro-linux.png",{"id":24,"title":25,"title_en":26,"slug":27},[],{"id":149,"title":150,"title_en":151,"slug":152,"excerpt":153,"excerpt_en":154,"has_translation":12,"published_at":155,"reading_time":14,"hidden_from_listing":15,"tags":156,"thumbnail_image":21,"og_image":160,"series":161,"authors":162},16,"Menggunakan TypeScript dengan Node.js dan Express","Using TypeScript with Node.js and Express","menggunakan-typescript-dengan-node-js-dan-express","Pengen bikin server Express di Node.js tapi pakai fitur-fitur keren TypeScript? Yuk, intip cara setup lengkapnya dari nol di sini!","Want to build an Express server on Node.js but use TypeScript's nicer features? Here's the complete setup from scratch.","2026-06-15T02:38:30.735Z",[101,157,158,159],"nodejs","express","typescript","\u002Fog\u002Fmenggunakan-typescript-dengan-node-js-dan-express.png",{"id":24,"title":25,"title_en":26,"slug":27},[],{"id":164,"title":165,"title_en":166,"slug":167,"excerpt":168,"excerpt_en":169,"has_translation":12,"published_at":170,"reading_time":14,"hidden_from_listing":15,"tags":171,"thumbnail_image":21,"og_image":175,"series":176,"authors":177},17,"Pemrograman Asynchronous vs Multithreading, Apa Sih Bedanya?","Asynchronous Programming vs Multithreading: What's the Real Difference?","pemrograman-asynchronous-dan-multithreading-apa-bedanya","Sering dengar istilah asynchronous dan multithreading pas ngoding tapi masih bingung bedanya? Yuk, kita bedah perbedaannya lewat analogi bikin mi instan yang gampang dipahami!","You keep hearing asynchronous and multithreading while coding, but the difference stays fuzzy? Let's take it apart with an instant-noodle analogy you can follow.","2026-06-15T02:38:31.093Z",[172,173,174],"pemrograman","concurrency","tips-coding","\u002Fog\u002Fpemrograman-asynchronous-dan-multithreading-apa-bedanya.png",{"id":24,"title":25,"title_en":26,"slug":27},[],{"id":179,"title":180,"title_en":181,"slug":182,"excerpt":183,"excerpt_en":184,"has_translation":12,"published_at":185,"reading_time":14,"hidden_from_listing":15,"tags":186,"thumbnail_image":21,"og_image":189,"series":190,"authors":191},18,"React, Angular, atau Vue: Pilih Framework yang Mana?","React, Angular, or Vue: Which Framework Should You Pick?","react-angular-vue-pilih-framework-yang-mana","Bingung menentukan pilihan di antara React, Angular, dan Vue untuk proyek web kalian berikutnya? Tenang, yuk kita bandingkan kelebihan masing-masing di sini!","Stuck choosing between React, Angular, and Vue for your next web project? Here's a side-by-side look at what each one actually does well.","2026-06-15T02:38:31.431Z",[187,188,18],"web-development","frontend","\u002Fog\u002Freact-angular-vue-pilih-framework-yang-mana.png",{"id":24,"title":25,"title_en":26,"slug":27},[],{"id":193,"title":194,"title_en":195,"slug":196,"excerpt":197,"excerpt_en":198,"has_translation":12,"published_at":199,"reading_time":14,"hidden_from_listing":15,"tags":200,"thumbnail_image":21,"og_image":204,"series":205,"authors":206},19,"Static Typing dan Dynamic Typing: Apa Bedanya?","Static Typing vs Dynamic Typing: What's the Difference?","static-typing-dan-dynamic-typing-apa-bedanya","Pernah bingung kenapa di Java tipe data harus dideklarasikan, sementara di Python tinggal pakai aja? Yuk, cari tahu perbedaan static typing dan dynamic typing di sini!","Ever wondered why Java makes you declare a type while Python just takes the value? Here's the difference between static typing and dynamic typing.","2026-06-15T02:39:15.869Z",[201,202,203],"programming","types","comparison","\u002Fog\u002Fstatic-typing-dan-dynamic-typing-apa-bedanya.png",{"id":24,"title":25,"title_en":26,"slug":27},[],{"id":208,"title":209,"title_en":210,"slug":211,"excerpt":212,"excerpt_en":213,"has_translation":12,"published_at":214,"reading_time":14,"hidden_from_listing":15,"tags":215,"thumbnail_image":21,"og_image":218,"series":219,"authors":220},20,"Tailwind v3.0 Rilis: Ada JIT, Arbitrary Values, dan Banyak Lagi!","Tailwind v3.0 Is Out: JIT, Arbitrary Values, and Plenty More","tailwind-v3-0-rilis-jit-arbitrary-dan-banyak-lagi","Tailwind CSS v3.0 resmi dirilis dengan segudang peningkatan performa yang bikin proses coding makin asyik. Apa aja sih fitur andalan yang wajib dicoba?","Tailwind CSS v3.0 shipped with a pile of performance upgrades that make styling more fun. Which features are worth trying first?","2026-06-15T02:39:25.372Z",[216,217,187],"tailwind-css","css-framework","\u002Fog\u002Ftailwind-v3-0-rilis-jit-arbitrary-dan-banyak-lagi.png",{"id":24,"title":25,"title_en":26,"slug":27},[],{"id":222,"title":223,"title_en":224,"slug":225,"excerpt":226,"excerpt_en":227,"has_translation":12,"published_at":228,"reading_time":14,"hidden_from_listing":15,"tags":229,"thumbnail_image":21,"og_image":230,"series":231,"authors":232},21,"TypeScript: JavaScript dengan Gaya dan Tipe Data Statis","TypeScript: JavaScript with Style and Static Types","typescript-javascript-dengan-gaya","Pernah pusing gara-gara runtime error di JavaScript? Yuk, kenalan dengan TypeScript yang bawa fitur static typing biar kode kalian makin rapi dan aman!","Tired of runtime errors in JavaScript? Meet TypeScript, which brings static typing so your code stays tidier and safer.","2026-06-15T02:39:25.712Z",[159,101,187],"\u002Fog\u002Ftypescript-javascript-dengan-gaya.png",{"id":24,"title":25,"title_en":26,"slug":27},[],{"id":234,"title":235,"title_en":236,"slug":237,"excerpt":238,"excerpt_en":239,"has_translation":12,"published_at":240,"reading_time":14,"hidden_from_listing":15,"tags":241,"thumbnail_image":21,"og_image":245,"series":246,"authors":247},22,"Yang Baru di Nuxt 3: Nitro Engine, Vite, dan Fitur Keren Lainnya","What's New in Nuxt 3: Nitro Engine, Vite, and Other Sharp Features","yang-baru-di-nuxt-3-nitro-vite-dan-banyak-lagi","Nuxt 3 hadir membawa perubahan arsitektur besar-besaran untuk menyelaraskan dengan Vue 3. Penasaran apa saja peningkatan performa dan fitur barunya?","Nuxt 3 brings a sweeping architecture change to line up with Vue 3. Here's what got faster and which new features are worth trying.","2026-06-15T02:39:26.086Z",[242,243,244],"nuxt-3","vue-3","frontend-framework","\u002Fog\u002Fyang-baru-di-nuxt-3-nitro-vite-dan-banyak-lagi.png",{"id":24,"title":25,"title_en":26,"slug":27},[],{"id":249,"title":250,"title_en":251,"slug":252,"excerpt":253,"excerpt_en":254,"has_translation":12,"published_at":255,"reading_time":256,"hidden_from_listing":15,"tags":257,"thumbnail_image":21,"og_image":263,"series":264,"authors":265},23,"Kenapa Pakai FastAPI dan Kenapa Dia Kenceng Banget?","Why Use FastAPI, and Why Is It So Fast?","kenapa-pakai-fastapi-dan-kenapa-dia-kenceng-banget","Sering dengar FastAPI tapi masih bingung kenapa dia bisa ngebut kayak NodeJS dan Go? Yuk, kita bedah bareng rahasia ASGI, sihir Pydantic, sampai dokumentasi otomatisnya!","You keep hearing about FastAPI but still wonder how it can keep pace with NodeJS and Go? Let's take apart ASGI, the Pydantic magic, and the automatic docs.","2026-08-16T13:22:46.956Z",4,[258,259,260,261,262],"fastapi","python","backend","asgi","pydantic","\u002Fog\u002Fkenapa-pakai-fastapi-dan-kenapa-dia-kenceng-banget.png",{"id":24,"title":25,"title_en":26,"slug":27},[266],{"authors_id":267},{"id":268,"name":269,"slug":270,"role":271,"profile_picture":21},2,"Inva","inva","Writer",{"id":273,"title":274,"title_en":275,"slug":276,"excerpt":277,"excerpt_en":278,"has_translation":12,"published_at":279,"reading_time":256,"hidden_from_listing":15,"tags":280,"thumbnail_image":21,"og_image":285,"series":286,"authors":287},24,"Kenapa Butuh Rate Limiting?","Why Do You Need Rate Limiting?","kenapa-butuh-rate-limiting","Pernah nggak sih endpoint login kalian diserbu bot yang nyoba nembak ribuan password cuma dalam semenit? Yuk, kita bahas kenapa Rate Limiting itu wajib, plus cara masangnya di FastAPI!","Has your login endpoint ever been hammered by a bot trying thousands of passwords in a single minute? Here is why rate limiting is mandatory, and how to wire it into FastAPI.","2026-08-17T04:00:27.728Z",[260,281,282,283,284,258],"rate-limiting","system-design","api","redis","\u002Fog\u002Fkenapa-butuh-rate-limiting.png",{"id":24,"title":25,"title_en":26,"slug":27},[288],{"authors_id":289},{"id":268,"name":269,"slug":270,"role":271,"profile_picture":21},{"id":291,"title":292,"title_en":293,"slug":294,"excerpt":295,"excerpt_en":296,"has_translation":12,"published_at":297,"reading_time":14,"hidden_from_listing":15,"tags":298,"thumbnail_image":21,"og_image":302,"series":303,"authors":304},25,"Kenapa Event Queue Bikin Backend Kalian Nggak Gampang Tumbang?","Why an Event Queue Keeps Your Backend From Collapsing","kenapa-event-queue-bikin-backend-kamu-nggak-gampang-tumbang","Pernah klik tombol Beli Sekarang dan notifikasi suksesnya muncul dalam sekejap, padahal di belakang layar ada invoice, email, sampai push notification yang harus dibuat? Rahasianya Event Queue. Yuk, kita bedah!","You hit Buy Now and the success notice appears instantly, while an invoice, an email, and a push notification still have to be built behind the scenes. The secret is the event queue.","2026-08-17T04:11:23.685Z",[260,282,299,300,301],"event-queue","message-broker","architecture","\u002Fog\u002Fkenapa-event-queue-bikin-backend-kamu-nggak-gampang-tumbang.png",{"id":24,"title":25,"title_en":26,"slug":27},[305],{"authors_id":306},{"id":307,"name":308,"slug":309,"role":271,"profile_picture":21},1,"Daffa Izzuddin","izzudd",{"id":311,"title":312,"title_en":313,"slug":314,"excerpt":315,"excerpt_en":316,"has_translation":12,"published_at":317,"reading_time":14,"hidden_from_listing":15,"tags":318,"thumbnail_image":21,"og_image":323,"series":324,"authors":325},26,"REST API vs gRPC: Kapan Sebaiknya Mulai Pindah dari JSON?","REST API vs gRPC: When Should You Start Moving Off JSON?","rest-api-vs-grpc-kapan-sebaiknya-pindah-dari-json","Pernah nggak sih sistem mikroservis kalian mulai kerasa berat padahal cuma tuker-tukeran data internal? Belum tentu masalah servernya. Yuk, kita bahas kapan REST + JSON masih juara dan kapan gRPC jadi jawabannya!","Has your microservice system started feeling heavy even though it only shuffles internal data? The server may not be the problem. Here is when REST + JSON still wins, and when gRPC is the answer.","2026-08-17T04:26:10.249Z",[260,319,320,321,322,282],"grpc","rest-api","microservices","protobuf","\u002Fog\u002Frest-api-vs-grpc-kapan-sebaiknya-pindah-dari-json.png",{"id":24,"title":25,"title_en":26,"slug":27},[326],{"authors_id":327},{"id":268,"name":269,"slug":270,"role":271,"profile_picture":21},{"id":329,"title":330,"title_en":331,"slug":332,"excerpt":333,"excerpt_en":334,"has_translation":12,"published_at":335,"reading_time":14,"hidden_from_listing":15,"tags":336,"thumbnail_image":21,"og_image":341,"series":342,"authors":343},27,"Background Worker & Task Queue: Jangan Jalankan Proses Berat di Request HTTP!","Background Workers & Task Queues: Don't Run Heavy Work Inside an HTTP Request","background-worker-task-queue-jangan-jalankan-proses-berat-di-http","Pernah nggak sih kalian klik Daftar Akun lalu halaman loading muter sampai 15 detik tanpa kepastian? Penyebabnya klasik banget. Yuk, kita bahas kenapa proses berat nggak boleh dijalanin di request HTTP!","You tap Create Account and the loading page spins for 15 seconds with no answer? The cause is classic. Here is why heavy work does not belong in an HTTP request.","2026-08-17T04:26:10.284Z",[260,337,338,258,339,284,340],"task-queue","celery","rabbitmq","async","\u002Fog\u002Fbackground-worker-task-queue-jangan-jalankan-proses-berat-di-http.png",{"id":24,"title":25,"title_en":26,"slug":27},[344],{"authors_id":345},{"id":307,"name":308,"slug":309,"role":271,"profile_picture":21},{"id":347,"title":348,"title_en":349,"slug":350,"excerpt":351,"excerpt_en":352,"has_translation":12,"published_at":353,"reading_time":14,"hidden_from_listing":15,"tags":354,"thumbnail_image":21,"og_image":361,"series":362,"authors":363},28,"Mengatasi N+1 Query Problem: Musuh Tersembunyi Performa Backend","Taming the N+1 Query Problem: The Hidden Enemy of Backend Performance","mengatasi-n-plus-1-query-problem-musuh-tersembunyi-backend","Pernah bikin endpoint yang cuma nampilin 50 postingan beserta nama penulisnya, tapi response-nya lambat banget? Bisa jadi kalian kena N+1 Query. Yuk, kita bedah penyebabnya dan cara memberantasnya!","You built an endpoint that only lists 50 posts with their author names, and the response takes 2-3 seconds? You may have hit N+1 Query. Here is the cause, and the cure.","2026-08-17T04:26:10.309Z",[355,356,357,358,359,360,260],"database","sql","orm","sqlalchemy","django","performance","\u002Fog\u002Fmengatasi-n-plus-1-query-problem-musuh-tersembunyi-backend.png",{"id":24,"title":25,"title_en":26,"slug":27},[364],{"authors_id":365},{"id":307,"name":308,"slug":309,"role":271,"profile_picture":21},{"id":367,"title":368,"title_en":369,"slug":370,"excerpt":371,"excerpt_en":372,"has_translation":12,"published_at":373,"reading_time":256,"hidden_from_listing":15,"tags":374,"thumbnail_image":21,"og_image":377,"series":378,"authors":379},29,"Memahami Database Indexing: Rahasia Query Super Cepat","Understanding Database Indexing: The Secret to Very Fast Queries","memahami-database-indexing-rahasia-query-super-cepat","Query kalian mulai lelet padahal data baru nembus jutaan baris? Sebelum buru-buru *upgrade* server, yuk cek dulu *index*-nya. Yuk, kita bedah gimana *database indexing* sebenernya kerja!","Your queries have gone sluggish even though the data only just crossed a million rows? Before you rush to upgrade the server, check the indexes. Here is how database indexing actually works.","2026-08-17T04:26:10.325Z",[355,356,375,376,360,260],"postgresql","indexing","\u002Fog\u002Fmemahami-database-indexing-rahasia-query-super-cepat.png",{"id":24,"title":25,"title_en":26,"slug":27},[380],{"authors_id":381},{"id":307,"name":308,"slug":309,"role":271,"profile_picture":21},{"id":383,"title":384,"title_en":385,"slug":386,"excerpt":387,"excerpt_en":388,"has_translation":12,"published_at":389,"reading_time":256,"hidden_from_listing":15,"tags":390,"thumbnail_image":21,"og_image":394,"series":395,"authors":396},31,"Mengenal Redis: Lebih dari Sekadar In-Memory Cache","Getting to Know Redis: More Than Just an In-Memory Cache","mengenal-redis-lebih-dari-sekadar-in-memory-cache","Masih nganggep Redis cuma buat caching? Padahal dia bisa jadi leaderboard, message broker, sampai rate limiter lho. Yuk, kita bedah semua kemampuannya!","Still treating Redis as nothing but a cache? It can be a leaderboard, a message broker, even a rate limiter. Let's take apart everything it can do.","2026-08-17T04:26:10.360Z",[284,260,391,392,393,259],"cache","nosql","in-memory","\u002Fog\u002Fmengenal-redis-lebih-dari-sekadar-in-memory-cache.png",{"id":24,"title":25,"title_en":26,"slug":27},[397],{"authors_id":398},{"id":307,"name":308,"slug":309,"role":271,"profile_picture":21},{"id":400,"title":401,"title_en":402,"slug":403,"excerpt":404,"excerpt_en":405,"has_translation":12,"published_at":406,"reading_time":256,"hidden_from_listing":15,"tags":407,"thumbnail_image":21,"og_image":412,"series":413,"authors":414},32,"Docker Compose untuk Developer Santai: Satu Perintah Buat Jalankan Semua Service","Docker Compose for the Relaxed Developer: One Command to Run Every Service","docker-compose-untuk-developer-santai","Pernah nggak kalian ngulang-ngulang perintah `docker run` cuma buat nyalain web, database, dan cache satu-satu? Capek, kan? Yuk, kita rapikan semuanya jadi satu file dan satu perintah!","Do you keep retyping `docker run` just to bring up the web app, the database, and the cache one at a time? Here is how to fold all of them into one file and one command.","2026-08-17T04:26:10.375Z",[408,409,410,411,260],"docker","docker-compose","devops","containers","\u002Fog\u002Fdocker-compose-untuk-developer-santai.png",{"id":24,"title":25,"title_en":26,"slug":27},[415],{"authors_id":416},{"id":307,"name":308,"slug":309,"role":271,"profile_picture":21},{"id":418,"title":419,"title_en":420,"slug":421,"excerpt":422,"excerpt_en":423,"has_translation":12,"published_at":424,"reading_time":256,"hidden_from_listing":15,"tags":425,"thumbnail_image":21,"og_image":427,"series":428,"authors":429},33,"Berkenalan dengan RabbitMQ: Si Kurir Pesan Serba Bisa","Meet RabbitMQ: The Versatile Message Courier","berkenalan-dengan-rabbitmq-si-kurir-pesan-serba-bisa","Pernah nggak sih kalian klik Bayar Sekarang dan notifikasi suksesnya muncul seketika, padahal email konfirmasi baru nyampe beberapa detik kemudian? Rahasianya ada di satu kurir tak terlihat. Yuk, kita kenalan sama RabbitMQ!","You tap Pay Now and the success notice appears instantly, while the confirmation email only lands a few seconds later? The secret is one invisible courier. Meet RabbitMQ.","2026-08-17T04:26:10.388Z",[339,300,260,321,340,426],"queue","\u002Fog\u002Fberkenalan-dengan-rabbitmq-si-kurir-pesan-serba-bisa.png",{"id":24,"title":25,"title_en":26,"slug":27},[430],{"authors_id":431},{"id":268,"name":269,"slug":270,"role":271,"profile_picture":21},{"id":433,"title":434,"title_en":435,"slug":436,"excerpt":437,"excerpt_en":438,"has_translation":12,"published_at":439,"reading_time":256,"hidden_from_listing":15,"tags":440,"thumbnail_image":21,"og_image":442,"series":443,"authors":444},34,"Kenapa Backend Butuh Database Connection Pooling?","Why Does a Backend Need Database Connection Pooling?","kenapa-backend-butuh-database-connection-pooling","Pernah kena error Too many connections padahal CPU server masih santai di angka 30%? Masalahnya bukan di query kalian, tapi di cara aplikasi ngobrol sama database. Yuk, kenalan sama Connection Pooling!","Ever hit Too many connections while server CPU is still lounging at 30%? The problem is not your queries, it is how the application talks to the database. Meet connection pooling.","2026-08-24T06:06:47.088Z",[260,355,375,441,282,360],"connection-pooling","\u002Fog\u002Fkenapa-backend-butuh-database-connection-pooling.png",{"id":24,"title":25,"title_en":26,"slug":27},[445],{"authors_id":446},{"id":268,"name":269,"slug":270,"role":271,"profile_picture":21},{"id":448,"title":449,"title_en":450,"slug":451,"excerpt":452,"excerpt_en":453,"has_translation":12,"published_at":454,"reading_time":14,"hidden_from_listing":15,"tags":455,"thumbnail_image":21,"og_image":458,"series":459,"authors":460},35,"Mengenal Idempotency Key: Rahasia Anti-Double Charge di API Pembayaran","Idempotency Keys: The Secret to No Double Charges in Payment APIs","mengenal-idempotency-key-rahasia-anti-double-charge-di-api-pembayaran","Pernah internet kalian ngadat pas lagi nekan tombol Bayar, terus panik ngekliknya tiga kali? Kalau endpoint-nya nggak idempotent, saldo bisa kepotong berkali-kali. Yuk, kenalan sama Idempotency Key!","Ever had your connection stall right as you hit Pay, then panic-clicked three times? If the endpoint is not idempotent, the balance can be cut more than once. Meet the idempotency key.","2026-08-24T06:09:11.645Z",[260,283,456,282,457,258,284],"idempotency","payment","\u002Fog\u002Fmengenal-idempotency-key-rahasia-anti-double-charge-di-api-pembayaran.png",{"id":24,"title":25,"title_en":26,"slug":27},[461],{"authors_id":462},{"id":268,"name":269,"slug":270,"role":271,"profile_picture":21},{"id":464,"title":465,"title_en":466,"slug":467,"excerpt":468,"excerpt_en":469,"has_translation":12,"published_at":470,"reading_time":14,"hidden_from_listing":15,"tags":471,"thumbnail_image":21,"og_image":473,"series":474,"authors":475},36,"Mencegah Efek Domino di Mikroservis dengan Circuit Breaker Pattern","Stopping the Domino Effect in Microservices With the Circuit Breaker Pattern","mencegah-efek-domino-di-mikroservis-dengan-circuit-breaker-pattern","Pernah nggak sih, satu fitur minor di aplikasi kalian mendadak lelet, eh malah bikin halaman checkout dan login ikut down total? Itu namanya *cascading failure*. Yuk, kita bahas gimana *circuit breaker pattern* (pemutus arus) nyelametin arsitektur kalian!","Ever had one minor feature go slow and take the checkout page and login down with it? That is a cascading failure. Here is how the circuit breaker pattern saves your architecture.","2026-08-24T06:13:36.734Z",[260,321,472,282,301],"circuit-breaker","\u002Fog\u002Fmencegah-efek-domino-di-mikroservis-dengan-circuit-breaker-pattern.png",{"id":24,"title":25,"title_en":26,"slug":27},[476],{"authors_id":477},{"id":268,"name":269,"slug":270,"role":271,"profile_picture":21},{"id":479,"title":480,"title_en":481,"slug":482,"excerpt":483,"excerpt_en":484,"has_translation":12,"published_at":485,"reading_time":14,"hidden_from_listing":15,"tags":486,"thumbnail_image":21,"og_image":488,"series":489,"authors":490},37,"Kenapa Backend Butuh Graceful Shutdown? Jangan Asal Cabut Kabel Server!","Why Does a Backend Need Graceful Shutdown? Don't Yank the Server Cable","kenapa-backend-butuh-graceful-shutdown-jangan-asal-cabut-kabel-server","Pernah nggak sih, abis kalian nge-*deploy* backend, beberapa detik kemudian monitoring malah banjir *alert* **502 Bad Gateway** dari pengguna? Saldo udah kepotong tapi status order belum keburu ter-*update* di *database*. Yuk, kita bahas kenapa *graceful shutdown* itu wajib banget!","You deploy the backend and seconds later monitoring floods with 502 Bad Gateway alerts. The balance was cut but the order status never reached the database. Here is why graceful shutdown is mandatory.","2026-08-24T06:15:59.150Z",[260,410,258,408,487,282,301],"kubernetes","\u002Fog\u002Fkenapa-backend-butuh-graceful-shutdown-jangan-asal-cabut-kabel-server.png",{"id":24,"title":25,"title_en":26,"slug":27},[491],{"authors_id":492},{"id":268,"name":269,"slug":270,"role":271,"profile_picture":21},{"id":494,"title":495,"title_en":496,"slug":497,"excerpt":498,"excerpt_en":499,"has_translation":12,"published_at":500,"reading_time":14,"hidden_from_listing":15,"tags":501,"thumbnail_image":21,"og_image":502,"series":503,"authors":504},38,"Optimistic vs Pessimistic Locking: Mengatasi Rebutan Data di Database","Optimistic vs Pessimistic Locking: Handling the Data Fight in a Database","optimistic-vs-pessimistic-locking-mengatasi-rebutan-data-di-database","Seribu orang ngeklik \"Beli Sekarang\" di detik yang sama buat rebutan 1 tiket terakhir. Kira-kira apa yang bakal terjadi di server kalian? Yuk, kita banding *pessimistic* sama *optimistic locking*!","A thousand people tap Buy Now in the same second, fighting over the last ticket. What happens on your server? Here is pessimistic against optimistic locking.","2026-08-24T06:16:37.198Z",[260,355,173,375,282,301,356],"\u002Fog\u002Foptimistic-vs-pessimistic-locking-mengatasi-rebutan-data-di-database.png",{"id":24,"title":25,"title_en":26,"slug":27},[505],{"authors_id":506},{"id":268,"name":269,"slug":270,"role":271,"profile_picture":21},{"id":508,"title":509,"title_en":510,"slug":511,"excerpt":512,"excerpt_en":513,"has_translation":12,"published_at":514,"reading_time":14,"hidden_from_listing":15,"tags":515,"thumbnail_image":21,"og_image":518,"series":519,"authors":520},39,"Database Sharding vs Partitioning: Kapan Data Perlu Dipecah?","Database Sharding vs Partitioning: When Does Data Need Splitting?","database-sharding-vs-partitioning-kapan-data-perlu-dipecah","Tabel transaksi kalian udah nembus miliaran baris dan tiap *query* laporan bikin *CPU* melonjak 100%? Sebelum asal pecah data, yuk kita pahami dulu beda *sharding* sama *partitioning*!","Your transaction table has crossed a billion rows and every report query spikes CPU to 100%? Before splitting data blindly, understand the difference between sharding and partitioning.","2026-08-24T06:17:10.104Z",[260,355,375,282,301,516,517],"sharding","scaling","\u002Fog\u002Fdatabase-sharding-vs-partitioning-kapan-data-perlu-dipecah.png",{"id":24,"title":25,"title_en":26,"slug":27},[521],{"authors_id":522},{"id":268,"name":269,"slug":270,"role":271,"profile_picture":21},{"id":524,"title":525,"title_en":526,"slug":527,"excerpt":528,"excerpt_en":529,"has_translation":12,"published_at":530,"reading_time":14,"hidden_from_listing":15,"tags":531,"thumbnail_image":21,"og_image":536,"series":537,"authors":538},40,"Menyelami Distributed Tracing: Melacak Jejak Request di Balik Keruwetan Microservices","Inside Distributed Tracing: Following a Request Through Microservice Chaos","menyelami-distributed-tracing-melacak-jejak-request-microservices","Satu klik Checkout di backend kalian bisa memicu puluhan network call antar-service, tapi pas ada yang lambat, service mana sebenernya yang salah? Log aja nggak cukup buat njawab itu. Yuk, kita bedah Distributed Tracing!","One Checkout click in your backend can trigger dozens of network calls between services, but when one is slow, which service is at fault? Logs alone cannot answer that. Here is distributed tracing.","2026-08-31T02:33:31.602Z",[260,532,533,534,321,301,535],"distributed-systems","observability","open-telemetry","tracing","\u002Fog\u002Fmenyelami-distributed-tracing-melacak-jejak-request-microservices.png",{"id":24,"title":25,"title_en":26,"slug":27},[539],{"authors_id":540},{"id":268,"name":269,"slug":270,"role":271,"profile_picture":21},{"id":542,"title":543,"title_en":544,"slug":545,"excerpt":546,"excerpt_en":547,"has_translation":12,"published_at":548,"reading_time":14,"hidden_from_listing":15,"tags":549,"thumbnail_image":21,"og_image":555,"series":556,"authors":557},41,"Log Aggregation Modern dengan Grafana Loki dan Vector: Hemat Storage Tanpa Indeks Raksasa","Modern Log Aggregation With Grafana Loki and Vector: Save Storage Without a Giant Index","log-aggregation-modern-grafana-loki-vector-hemat-storage","Klaster Elasticsearch kalian rakus RAM dan boros storage, ya? Padahal nggak semua kata di log perlu diindeks, lho. Yuk, kita kenalan sama duet Grafana Loki dan Vector yang jauh lebih ramah kantong!","Your Elasticsearch cluster is greedy for RAM and wasteful with storage? Not every word in a log needs indexing. Meet the duo of Grafana Loki and Vector, far kinder to your wallet.","2026-09-01T15:45:01.066Z",[260,550,551,552,553,554,410,282],"observa","logging","grafana","loki","vector","\u002Fog\u002Flog-aggregation-modern-grafana-loki-vector-hemat-storage.png",{"id":24,"title":25,"title_en":26,"slug":27},[558],{"authors_id":559},{"id":268,"name":269,"slug":270,"role":271,"profile_picture":21},{"id":561,"title":562,"title_en":562,"slug":563,"excerpt":564,"excerpt_en":565,"has_translation":12,"published_at":566,"reading_time":14,"hidden_from_listing":15,"tags":567,"thumbnail_image":21,"og_image":570,"series":571,"authors":572},45,"Rate Limiting Algorithms: Token Bucket vs Leaky Bucket vs Sliding Window","rate-limiting-algorithms-token-bucket-leaky-bucket-sliding-window","Udah tahu kenapa *rate limiting* itu wajib, tapi masih bingung beda Token Bucket, Leaky Bucket, Fixed Window, dan Sliding Window? Yuk, kita adu empat algoritma ini bareng-bareng dan cari tahu mana yang paling pas buat API kalian!","You already know why *rate limiting* is mandatory, but the difference between Token Bucket, Leaky Bucket, Fixed Window, and Sliding Window is still fuzzy. Let's put all four algorithms side by side and find the one that fits your API.","2026-09-09T01:57:55.886Z",[260,282,281,284,568,301,569],"api-gateway","traffict-management","\u002Fog\u002Frate-limiting-algorithms-token-bucket-leaky-bucket-sliding-window.png",{"id":24,"title":25,"title_en":26,"slug":27},[573],{"authors_id":574},{"id":268,"name":269,"slug":270,"role":271,"profile_picture":21},{"id":576,"title":577,"title_en":578,"slug":579,"excerpt":580,"excerpt_en":581,"has_translation":12,"published_at":582,"reading_time":14,"hidden_from_listing":15,"tags":583,"thumbnail_image":21,"og_image":586,"series":587,"authors":588},46,"Mengapa C Mulai Ditinggalkan: Duel Filosofi Keamanan Rust vs Kesederhanaan Zig","Why C Is Being Left Behind: Rust's Safety Philosophy vs Zig's Simplicity","mengapa-c-mulai-ditinggalkan-duel-filosofi-rust-vs-zig","Pernah denger kalau sekitar 70% celah keamanan kritis software modern itu asalnya dari bahasa C? Iya, bahasa yang udah jadi fondasi internet ini 😅. Yuk, kita bedah duel filosofi Rust vs Zig dan cari tahu mana yang pas buat proyek kalian!","Have you heard that around 70% of critical security holes in modern software come from C? Yes, the language the internet is built on. Let's unpack the philosophy duel between Rust and Zig and see which one fits your project.","2026-09-09T02:19:05.266Z",[86,83,584,585,87],"zig","c","\u002Fog\u002Fmengapa-c-mulai-ditinggalkan-duel-filosofi-rust-vs-zig.png",{"id":24,"title":25,"title_en":26,"slug":27},[589],{"authors_id":590},{"id":268,"name":269,"slug":270,"role":271,"profile_picture":21},{"id":592,"title":593,"title_en":594,"slug":595,"excerpt":596,"excerpt_en":597,"has_translation":12,"published_at":598,"reading_time":599,"hidden_from_listing":15,"tags":600,"thumbnail_image":21,"og_image":605,"series":606,"authors":607},107,"Cara kamu pakai AI lebih menentukan daripada apakah kamu pakai AI","How You Use AI Matters More Than Whether You Use AI","cara-pakai-ai-menentukan-pemahaman-kode","Fiturnya selesai, test-nya hijau, dan dua hari kemudian kamu baca kodenya kayak kode orang lain. Ternyata ada satu cara pakai AI yang bikin kamu paham lebih baik daripada nggak pakai AI sama sekali. Yuk lihat datanya.","The feature is done, the tests are green, and two days later you read the code like a stranger wrote it. It turns out one way of using AI leaves you understanding more than not using AI at all. Here is the data.","2026-10-10T11:08:29.000Z",7,[601,602,603,604],"ai","belajar","kognitif","ai-assisted-coding","\u002Fog\u002Fcara-pakai-ai-menentukan-pemahaman-kode.png",{"id":24,"title":25,"title_en":26,"slug":27},[],{"id":609,"title":610,"title_en":611,"slug":612,"excerpt":613,"excerpt_en":614,"has_translation":12,"published_at":13,"reading_time":14,"hidden_from_listing":15,"tags":615,"thumbnail_image":21,"og_image":617,"series":618,"authors":619},109,"State of JS 2025 Bilang Developer Cuma Pakai 2,6 Framework Sepanjang Karier","State of JS 2025 Says Developers Use Only 2.6 Frameworks in a Whole Career","state-of-js-2025-developer-cuma-pakai-2-6-framework","Coba hitung semua framework yang pernah kamu coba, lalu potong jadi yang beneran dipakai buat kerjaan. Daftarnya jauh lebih pendek dari dugaan. State of JS 2025 nanya ke 13.002 developer, dan rata-ratanya cuma 2,6. Yuk, lihat angkanya bareng-bareng!","Try counting every framework you have ever touched, then cut the list down to what you actually used for work. It comes out far shorter than you would guess. State of JS 2025 asked 13,002 developers, and the average is only 2.6.",[101,616,18,17],"survei","\u002Fog\u002Fstate-of-js-2025-developer-cuma-pakai-2-6-framework.png",{"id":24,"title":25,"title_en":26,"slug":27},[],{"id":6,"title":7,"title_en":8,"slug":9,"excerpt":10,"excerpt_en":11,"has_translation":12,"published_at":13,"reading_time":14,"hidden_from_listing":15,"tags":621,"thumbnail_image":21,"og_image":22,"series":622,"authors":623},[17,18,19,20],{"id":24,"title":25,"title_en":26,"slug":27},[],{"id":74,"title":75,"title_en":76,"slug":77,"excerpt":78,"excerpt_en":79,"has_translation":12,"published_at":80,"reading_time":81,"hidden_from_listing":15,"tags":82,"thumbnail_image":21,"og_image":88,"series":625,"authors":626},{"id":24,"title":25,"title_en":26,"slug":27},[627],{"authors_id":628},{"id":307,"name":308,"slug":309,"role":271,"profile_picture":21},{"id":630,"title":631,"title_en":632,"slug":633,"excerpt":634,"excerpt_en":635,"has_translation":12,"published_at":636,"reading_time":14,"hidden_from_listing":15,"tags":637,"thumbnail_image":21,"og_image":640,"series":641,"authors":642},112,"Aplikasimu lambat, dan kamu udah kepikiran ganti bahasa. Tunggu dulu","Your App Is Slow, and You're Already Thinking About Changing Languages. Wait.","aplikasimu-lambat-dan-kamu-udah-kepikiran-ganti-bahasa-tunggu-dulu","Ada endpoint yang grafiknya spike tiap beberapa menit, dan kepikiran buat pindah dari Go ke Rust? Discord dan Cloudflare beneran melakukannya — tapi cuma setelah kehabisan cara lain dan punya datanya. Yuk, bedah gejala mana yang beneran butuh rewrite, dan mana yang cuma butuh profiling. 🤔","An endpoint spikes every few minutes, and you are thinking of moving from Go to Rust? Discord and Cloudflare really did it, but only after running out of other options and having the data. Let's sort out which symptoms need a rewrite and which only need a profiler.","2026-10-08T09:40:00.000Z",[260,360,638,83,282,639],"golang","profiling","\u002Fog\u002Faplikasimu-lambat-dan-kamu-udah-kepikiran-ganti-bahasa-tunggu-dulu.png",{"id":24,"title":25,"title_en":26,"slug":27},[],{"id":644,"title":645,"title_en":646,"slug":647,"excerpt":648,"excerpt_en":649,"has_translation":12,"published_at":650,"reading_time":599,"hidden_from_listing":15,"tags":651,"thumbnail_image":21,"og_image":655,"series":656,"authors":657},113,"Garbage Collector dituduh bikin aplikasi lemot. Seberapa adil tuduhan itu?","The Garbage Collector Gets Blamed for Slow Apps. How Fair Is That?","garbage-collector-dituduh-bikin-aplikasi-lemot","GC sering jadi tersangka utama tiap aplikasi melambat, dan banyak yang percaya dia jalan pakai timer tiap beberapa detik. Dua-duanya nggak sepenuhnya benar. Yuk bedah cara kerja GC dari dalam, plus satu pengecualian yang bikin Discord kesakitan tiap 2 menit. 🤔","GC is always the prime suspect when an app slows down, and many people believe it runs on a timer every few seconds. Both beliefs are only partly right. Let's open up how GC works inside, plus one exception that made Discord hurt every 2 minutes.","2026-10-09T01:34:00.000Z",[260,360,638,652,653,654],"jvm","garbage-collector","memory","\u002Fog\u002Fgarbage-collector-dituduh-bikin-aplikasi-lemot.png",{"id":24,"title":25,"title_en":26,"slug":27},[],{"id":659,"title":660,"title_en":661,"slug":662,"excerpt":663,"excerpt_en":664,"has_translation":12,"published_at":665,"reading_time":14,"hidden_from_listing":15,"tags":666,"thumbnail_image":21,"og_image":669,"series":670,"authors":671},118,"Belajar Idempotency dari Stok yang Keburu Kebeli","Learning Idempotency from Stock That Got Bought Too Soon","pub-sub-sendiri-lalu-belajar-idempotency","Tugas pertama saya di kerjaan pertama: sistem yang kewalahan menerima webhook. Saya putuskan membangun pub\u002Fsub sendiri dari nol, dan pelajaran yang akhirnya datang bukan dari situ — tapi dari stok gudang yang keburu kebeli orang.","My first task at my first job was a system drowning in webhooks. I decided to build my own pub\u002Fsub from scratch, and the lesson that finally landed came from somewhere else: warehouse stock that got bought before the count caught up.","2026-10-10T14:03:00.000Z",[456,667,338,339,668],"event-driven","post-mortem","\u002Fog\u002Fpub-sub-sendiri-lalu-belajar-idempotency.png",{"id":24,"title":25,"title_en":26,"slug":27},[672],{"authors_id":673},{"id":307,"name":308,"slug":309,"role":271,"profile_picture":21},{"id":675,"title":676,"title_en":677,"slug":678,"excerpt":679,"excerpt_en":680,"has_translation":12,"published_at":681,"reading_time":81,"hidden_from_listing":15,"tags":682,"thumbnail_image":21,"og_image":685,"series":686,"authors":687},124,"Rahasia Zero-Cost Abstraction di Rust, Dibedah dari Assembly","The Secret of Zero-Cost Abstractions in Rust, Opened Up from the Assembly","rahasia-zero-cost-abstraction-di-rust","\"Abstraksi tinggi selalu lebih lambat\" itu anggapan lama. Iterator Rust bisa menyamai loop manual, dan assembly-nya bisa kita baca sendiri. Yuk, kita bongkar!","\"Higher abstractions are always slower\" is an old assumption. Rust iterators can match a hand-written loop, and the assembly is there for you to read. Let's take it apart.","2026-10-13T05:19:00.000Z",[83,360,86,683,684],"compiler","optimasi","\u002Fog\u002Frahasia-zero-cost-abstraction-di-rust.png",{"id":24,"title":25,"title_en":26,"slug":27},[688,690],{"authors_id":689},{"id":307,"name":308,"slug":309,"role":271,"profile_picture":21},{"authors_id":691},{"id":307,"name":308,"slug":309,"role":271,"profile_picture":21},[693,695,697],{"id":694,"title":35,"slug":37,"description":21,"cover_image":21},8,{"id":108,"title":39,"slug":41,"description":696,"cover_image":21},"Mengenal konsep dasar pemrograman. Pada seri ini kita akan membahas tentang bagaimana cara berkutat dengan variabel, mengatur alur program dengan struktur kontrol, me-reuse kode dengan fungsi, dan aturan sintaks pada bahasa pemrograman. Konsep-konsep ini pastinya akan sangat berguna ketika kita mulai mengkoding ceria.",{"id":136,"title":43,"slug":45,"description":698,"cover_image":21},"Algoritma dan struktur data adalah konsep fundamental dalam dunia pemrograman. Keduanya sangat penting dalam menyelesaikan masalah yang kompleks dengan efisien dan efektif. Dalam seri ini kita akan membahas berbagai macam struktur data dan algoritma yang harapannya bisa bikin kode kita lebih efektif dan efisien. Yuk belajar ASD bareng Inva! 👋",[700],{"authors_id":701},{"id":307,"name":308,"slug":309,"role":271,"profile_picture":21},"id",[704,702],"en","Kalau kamu pernah iseng buka isi folder kernel Linux, kamu tahu di sana isinya cuma dua bahasa: C dan Assembly. Susunannya begitu terus selama lebih dari tiga dekade. Linus Torvalds sendiri terkenal sangat protektif soal basis kodenya, dan itu bukan cuma soal selera.\n\nWaktu ada yang mengusulkan adopsi C++ di *mailing list* kernel, [jawabannya keras](https:\u002F\u002Fyarchive.net\u002Fcomp\u002Flinux\u002Fc++.html) dan dikutip orang sampai sekarang. Alasannya klasik: kompleksitas desain, *overhead* kompilasi, dan manajemen memori C++ yang dia anggap nggak bisa diprediksi di *kernel space*. Poin favoritnya waktu itu, bahasa apa pun yang suka menyembunyikan alokasi memori di belakang punggung pembacanya emang bukan pilihan bagus buat kernel.\n\nTerus, di akhir 2022, ada hal yang tiga dekade sebelumnya kedengaran mustahil nih. Lewat inisiatif [Rust for Linux](https:\u002F\u002Frust-for-linux.com\u002F), bahasa [Rust](https:\u002F\u002Fwww.rust-lang.org\u002F) resmi masuk ke pohon kode utama [Linux 6.1](https:\u002F\u002Fkernelnewbies.org\u002FLinux_6.1). Bukan *patch* iseng yang nyangkut di *mailing list*, tapi infrastruktur yang benar-benar di-*merge* — sekitar [12.500 baris](https:\u002F\u002Fwww.phoronix.com\u002Fnews\u002FRust-Is-Merged-Linux-6.1) cuma buat kerangkanya, belum ada satu *driver* pun. 🎉\n\nSejak itu diskusinya ramai terus. Ini revolusi nyata di arsitektur sistem operasi masa depan, atau cuma kebawa euforia meme *\"Rewrite It In Rust\"* (RIIR) sih? Yuk bedah dari sisi teknis, mitigasi celah keamanannya, sampai realita adopsinya di industri. 🙂\n\n## Kenapa Rust baru diterima sekarang?\n\nKlarifikasi dulu biar nggak salah paham: Linux nggak sedang ditulis ulang total ke Rust. Kernel Linux sekarang ada di sekitar [40 juta baris kode](https:\u002F\u002Fnewsletter.pragmaticengineer.com\u002Fp\u002Fhow-linux-is-built-with-greg-kroah). Menurut Greg Kroah-Hartman, bagian *core* yang dijalankan semua orang cuma sekitar 5% dari angka itu. Sisanya dukungan *hardware*: *driver*, arsitektur, dan chip dari ratusan vendor.\n\nJadi kenapa Linus melunak? Jawabannya ada di satu masalah kronis yang menghantui industri *software* selama puluhan tahun: *memory safety*.\n\nDatanya lumayan konsisten kok lintas proyek. Alex Gaynor [mengumpulkan analisis CVE](https:\u002F\u002Falexgaynor.net\u002F2020\u002Fmay\u002F27\u002Fscience-on-memory-unsafety-and-security) dari beberapa vendor, dan hasilnya seragam di kisaran 65-70%. Sampel CVE kernel Ubuntu selama enam bulan menghitung 65% kejadian *memory unsafety*, sementara Microsoft [menyebut sekitar 70%](https:\u002F\u002Fwww.microsoft.com\u002Fen-us\u002Fmsrc\u002Fblog\u002F2019\u002F07\u002Fwe-need-a-safer-systems-programming-language) CVE yang mereka tetapkan tiap tahun berasal dari sana. Buat proyek seukuran kernel, itu bukan angka yang bisa diabaikan.\n\nBentuk kesalahannya juga nggak banyak ragamnya sih. Semuanya sudah jadi kosakata harian buat yang pernah nulis C:\n- *use-after-free* — mengakses memori yang sudah dikembalikan ke sistem\n- *buffer overflow* — menulis atau membaca data melewati batas buffer\n- *double free* — membebaskan blok memori yang sama dua kali\n- *data race* — beberapa *core* mengubah data yang sama tanpa sinkronisasi\n\nDi *user space*, bug seperti ini biasanya berhenti di *crash* atau *Segmentation Fault*. Di *ring 0*, satu *pointer* liar bisa langsung memicu *kernel panic*. Bisa juga merusak *filesystem*, atau membuka jalan bagi penyerang untuk duduk di kursi *root*.\n\n## Yang sebenarnya diincar: rimba *driver hardware*\n\nBanyak orang mengira Rust langsung dipakai buat menggantikan *scheduler* CPU, *virtual memory manager*, atau *filesystem* inti. Padahal sasarannya jauh lebih spesifik nih: *device driver*.\n\nLogikanya sederhana banget. Bagian *core* kernel yang tadi cuma 5% itu diurus oleh sekelompok *maintainer* yang ketat dan saling mengawasi. Sementara 95% sisanya isinya *driver* — GPU, modul Wi-Fi, kontroller NVMe, adaptor Bluetooth, sensor — yang ditulis ribuan *engineer* dari berbagai vendor *hardware*. Standar kualitas kode dan disiplin pengujian mereka beda-beda banget, karena memang nggak ada satu komite yang mengawasi semuanya.\n\nTambahan lagi, kode *driver* berubah paling cepat, dan bug memori paling sering muncul di kode yang baru saja disentuh. Jadi area paling rawan tuh justru area yang paling sulit diawasi manusia. Di situlah *ownership* dan *borrow checker* Rust masuk kerja: kesalahan referensi ditolak di tahap kompilasi, bukan ketahuan tiga tahun kemudian saat ada yang melaporkan *kernel panic* di mesin produksi.\n\n```rust\n\u002F\u002F Contoh struktur dasar modul driver di Rust for Linux (API era 6.1)\nuse kernel::prelude::*;\n\nmodule! {\n    type: InvaSampleDriver,\n    name: \"inva_sample_driver\",\n    author: \"Invasikode Team\",\n    description: \"Contoh registrasi modul driver minimalis berbasis Rust di kernel Linux\",\n    license: \"GPL\",\n}\n\nstruct InvaSampleDriver;\n\nimpl kernel::Module for InvaSampleDriver {\n    fn init(_name: &'static CStr, _module: &'static ThisModule) -> Result\u003CSelf> {\n        pr_info!(\"Rust driver berhasil diinisialisasi ke dalam kernel Linux!\\n\");\n        Ok(InvaSampleDriver)\n    }\n}\n\nimpl Drop for InvaSampleDriver {\n    fn drop(&mut self) {\n        pr_info!(\"Resource driver dibersihkan secara otomatis dan deterministik!\\n\");\n    }\n}\n```\n\nPerhatikan `impl Drop`-nya. Di C, melepas modul *driver* berarti kamu harus ingat membebaskan semua yang kamu alokasikan di `module_exit`, satu per satu, di jalur yang jarang diuji. Di Rust, implementasi `Drop` memastikan sumber daya *hardware* dibebaskan saat modul di-*unload*, dan kompilator menolak kode yang meninggalkan referensi menggantung.\n\nSatu catatan kalau kamu mau coba sendiri: *signature* `init()` di contoh itu mengikuti [API era 6.1](https:\u002F\u002Frust-for-linux.github.io\u002Fdocs\u002Fkernel\u002Ftrait.Module.html). Di rilis yang lebih baru argumennya tinggal `&'static ThisModule`, dan sempat ada usulan untuk menghapus argumen itu sekalian. Cocokkan dulu dengan [dokumentasi kernel](https:\u002F\u002Fdocs.kernel.org\u002Frust\u002Findex.html) yang kamu pakai sebelum *copy-paste* dari artikel mana pun, termasuk yang ini. 😅\n\n## Faktor kedua yang jarang dibahas: regenerasi *maintainer*\n\nDi luar urusan keamanan, ada alasan manusiawi yang sama pentingnya.\n\n*Maintainer* inti kernel Linux didominasi insinyur veteran yang sudah mengurus subsistem C selama 20 sampai 30 tahun. Di sisi lain, generasi *developer* sekarang tumbuh dengan standar bahasa yang beda: manajemen paket terintegrasi, dokumentasi interaktif, sistem tipe yang ekspresif, dan *tooling* yang ngerti maksud kodenya. Bahasa yang nggak menyediakan itu terasa seperti kerja lembur tanpa dibayar.\n\nMendukung Rust di level kernel adalah langkah strategis untuk merangkul generasi baru *developer* sistem operasi. Tujuannya memastikan ada orang yang mau mengambil alih infrastruktur komputasi dunia sebelum angkatan C-nya pensiun. Buat proyek yang umurnya lebih tua dari banyak pembacanya, ini bukan kemewahan, tapi soal keberlanjutan.\n\n## RIIR di luar kernel: menang di CLI, kebablasan di tempat lain\n\nDi luar kernel, antusiasme pada Rust melahirkan gerakan yang populer dengan nama RIIR. Di ekosistem *developer tools*, gerakan ini membuktikan diri secara nyata:\n- [ripgrep](https:\u002F\u002Fgithub.com\u002FBurntSushi\u002Fripgrep) (`rg`) jadi standar baru pengganti `grep`, kencang karena mesin regex-nya pakai *finite automaton* plus optimasi SIMD\n- [fd](https:\u002F\u002Fgithub.com\u002Fsharkdp\u002Ffd) menggantikan `find` dengan antarmuka yang lebih intuitif dan pembacaan direktori paralel bawaan\n- [bat](https:\u002F\u002Fgithub.com\u002Fsharkdp\u002Fbat) menghadirkan versi modern `cat` dengan *syntax highlighting* dan integrasi Git\n- *Bundler* dan *compiler* seperti [SWC](https:\u002F\u002Fswc.rs\u002F), [Biome](https:\u002F\u002Fbiomejs.dev\u002F), dan [Turbopack](https:\u002F\u002Fvercel.com\u002Fblog\u002Fturbopack) menulis ulang *toolchain* JavaScript dan CSS ke Rust, dengan klaim pemangkasan waktu *build* sampai belasan kali lipat\n\nBuat poin terakhir, ada *caveat* yang perlu kamu tahu dulu. Angka \"10x lebih cepat\" dari Vercel pernah [dibantah Evan You](https:\u002F\u002Fgithub.com\u002Fyyx990803\u002Fvite-vs-next-turbo-hmr\u002Fdiscussions\u002F8) karena *benchmark*-nya membandingkan hal yang nggak setara: implementasi Vite-nya masih memakai Babel, sementara Turbopack dan Webpack sama-sama memakai SWC. Yang tetap berdiri adalah alasan arsitekturnya — paralelisme *native* dan komputasi inkremental di Rust menghapus batas *single-thread* yang selama ini menahan *tooling* Node.js. Angka pastinya bergantung proyekmu sendiri, jadi ukur aja, jangan percaya *slide*.\n\nSisi ekstremnya muncul ketika RIIR dipakai untuk menulis ulang proyek yang sudah stabil puluhan tahun tanpa urgensi teknis yang jelas. Menulis ulang kode yang sudah terbukti jalan demi tren bahasa sering menghabiskan biaya *engineering* raksasa tanpa peningkatan nilai yang bisa diukur. Bedanya dengan kasus kernel: di sana ada data CVE yang jelas, di banyak proyek RIIR lain cuma ada perasaan. 🤔\n\n## Jadi, revolusi atau cuma hype?\n\nKehadiran Rust di Linux 6.1 bukan hype sesaat. Ini adaptasi yang terukur dari proyek *open source* terbesar di dunia.\n\nLihat buktinya di Android. Google mendorong Rust untuk kode sistem tingkat rendah di sana, dan hasilnya terukur: porsi celah keamanan memori turun dari 76% di 2019 ke 24% di 2024, lalu di bawah 20% di 2025. [Laporan terbaru mereka](https:\u002F\u002Fblog.google\u002Fsecurity\u002Frust-in-android-move-fast-fix-things) juga mencatat kepadatan kerentanan memori di kode Rust lebih dari seribu kali lebih rendah dibanding C dan C++, dengan *rollback rate* empat kali lebih kecil untuk perubahan berukuran sedang sampai besar, dan waktu *code review* yang 25% lebih singkat. Angka 76% dan 24% itu sendiri berasal dari [post mereka setahun sebelumnya](https:\u002F\u002Fsecurity.googleblog.com\u002F2024\u002F09\u002Feliminating-memory-safety-vulnerabilities-Android.html). Biaya investasi ke Rust terbukti lebih murah daripada menambal *zero-day* di lingkungan produksi.\n\nTapi jangan salah baca arah. C tetap jadi fondasi yang belum tergantikan. Portabilitasnya ke arsitektur prosesor apa pun dan kesederhanaan *toolchain*-nya nggak ada yang menyamai sampai hari ini. Kernel Linux pun nggak dibangun ulang — Rust masuk lewat pintu samping, di area yang paling rawan bug dan paling jarang diawasi, satu *driver* demi satu *driver*.\n\nJadi jawabannya tuh: bukan revolusi, bukan juga hype. Rust datang bukan buat membunuh C, tapi buat menambal kekurangannya tepat di titik yang paling gampang pecah — dan di titik itu, kita memang sedang butuh bantuan siapa pun yang mau menulisnya. Selamat ngoprek *driver*, dan semoga yang kamu tulis nggak perlu *reboot* buat ketahuan salahnya. 👋\n","- Rust masuk ke kernel Linux bukan karena ikut tren, tapi karena data CVE menunjukkan sekitar 65-70% celah keamanan di bahasa *memory-unsafe* berasal dari kesalahan manajemen memori.\n- Sasaran yang dipilih sengaja di *driver hardware*, bagian terbesar kernel yang paling cepat berubah dan paling longgar pengawasannya.\n- Hasilnya sudah terukur di Android: porsi celah memori turun dari 76% di 2019 jadi 24% di 2024, dan di bawah 20% di 2025.\n- C tetap jadi fondasi kernel, dan Rust berperan sebagai lapisan pengaman di titik paling rawan, bukan penggantinya.","\u003Cp>Kalau kamu pernah iseng buka isi folder kernel Linux, kamu tahu di sana isinya cuma dua bahasa: C dan Assembly. Susunannya begitu terus selama lebih dari tiga dekade. Linus Torvalds sendiri terkenal sangat protektif soal basis kodenya, dan itu bukan cuma soal selera.\u003C\u002Fp>\n\u003Cp>Waktu ada yang mengusulkan adopsi C++ di \u003Cem>mailing list\u003C\u002Fem> kernel, \u003Ca href=\"https:\u002F\u002Fyarchive.net\u002Fcomp\u002Flinux\u002Fc++.html\">jawabannya keras\u003C\u002Fa> dan dikutip orang sampai sekarang. Alasannya klasik: kompleksitas desain, \u003Cem>overhead\u003C\u002Fem> kompilasi, dan manajemen memori C++ yang dia anggap nggak bisa diprediksi di \u003Cem>kernel space\u003C\u002Fem>. Poin favoritnya waktu itu, bahasa apa pun yang suka menyembunyikan alokasi memori di belakang punggung pembacanya emang bukan pilihan bagus buat kernel.\u003C\u002Fp>\n\u003Cp>Terus, di akhir 2022, ada hal yang tiga dekade sebelumnya kedengaran mustahil nih. Lewat inisiatif \u003Ca href=\"https:\u002F\u002Frust-for-linux.com\u002F\">Rust for Linux\u003C\u002Fa>, bahasa \u003Ca href=\"https:\u002F\u002Fwww.rust-lang.org\u002F\">Rust\u003C\u002Fa> resmi masuk ke pohon kode utama \u003Ca href=\"https:\u002F\u002Fkernelnewbies.org\u002FLinux_6.1\">Linux 6.1\u003C\u002Fa>. Bukan \u003Cem>patch\u003C\u002Fem> iseng yang nyangkut di \u003Cem>mailing list\u003C\u002Fem>, tapi infrastruktur yang benar-benar di-\u003Cem>merge\u003C\u002Fem> — sekitar \u003Ca href=\"https:\u002F\u002Fwww.phoronix.com\u002Fnews\u002FRust-Is-Merged-Linux-6.1\">12.500 baris\u003C\u002Fa> cuma buat kerangkanya, belum ada satu \u003Cem>driver\u003C\u002Fem> pun. 🎉\u003C\u002Fp>\n\u003Cp>Sejak itu diskusinya ramai terus. Ini revolusi nyata di arsitektur sistem operasi masa depan, atau cuma kebawa euforia meme \u003Cem>"Rewrite It In Rust"\u003C\u002Fem> (RIIR) sih? Yuk bedah dari sisi teknis, mitigasi celah keamanannya, sampai realita adopsinya di industri. 🙂\u003C\u002Fp>\n\u003Ch2 id=\"kenapa-rust-baru-diterima-sekarang\">Kenapa Rust baru diterima sekarang?\u003C\u002Fh2>\n\u003Cp>Klarifikasi dulu biar nggak salah paham: Linux nggak sedang ditulis ulang total ke Rust. Kernel Linux sekarang ada di sekitar \u003Ca href=\"https:\u002F\u002Fnewsletter.pragmaticengineer.com\u002Fp\u002Fhow-linux-is-built-with-greg-kroah\">40 juta baris kode\u003C\u002Fa>. Menurut Greg Kroah-Hartman, bagian \u003Cem>core\u003C\u002Fem> yang dijalankan semua orang cuma sekitar 5% dari angka itu. Sisanya dukungan \u003Cem>hardware\u003C\u002Fem>: \u003Cem>driver\u003C\u002Fem>, arsitektur, dan chip dari ratusan vendor.\u003C\u002Fp>\n\u003Cp>Jadi kenapa Linus melunak? Jawabannya ada di satu masalah kronis yang menghantui industri \u003Cem>software\u003C\u002Fem> selama puluhan tahun: \u003Cem>memory safety\u003C\u002Fem>.\u003C\u002Fp>\n\u003Cp>Datanya lumayan konsisten kok lintas proyek. Alex Gaynor \u003Ca href=\"https:\u002F\u002Falexgaynor.net\u002F2020\u002Fmay\u002F27\u002Fscience-on-memory-unsafety-and-security\">mengumpulkan analisis CVE\u003C\u002Fa> dari beberapa vendor, dan hasilnya seragam di kisaran 65-70%. Sampel CVE kernel Ubuntu selama enam bulan menghitung 65% kejadian \u003Cem>memory unsafety\u003C\u002Fem>, sementara Microsoft \u003Ca href=\"https:\u002F\u002Fwww.microsoft.com\u002Fen-us\u002Fmsrc\u002Fblog\u002F2019\u002F07\u002Fwe-need-a-safer-systems-programming-language\">menyebut sekitar 70%\u003C\u002Fa> CVE yang mereka tetapkan tiap tahun berasal dari sana. Buat proyek seukuran kernel, itu bukan angka yang bisa diabaikan.\u003C\u002Fp>\n\u003Cp>Bentuk kesalahannya juga nggak banyak ragamnya sih. Semuanya sudah jadi kosakata harian buat yang pernah nulis C:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cem>use-after-free\u003C\u002Fem> — mengakses memori yang sudah dikembalikan ke sistem\u003C\u002Fli>\n\u003Cli>\u003Cem>buffer overflow\u003C\u002Fem> — menulis atau membaca data melewati batas buffer\u003C\u002Fli>\n\u003Cli>\u003Cem>double free\u003C\u002Fem> — membebaskan blok memori yang sama dua kali\u003C\u002Fli>\n\u003Cli>\u003Cem>data race\u003C\u002Fem> — beberapa \u003Cem>core\u003C\u002Fem> mengubah data yang sama tanpa sinkronisasi\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Di \u003Cem>user space\u003C\u002Fem>, bug seperti ini biasanya berhenti di \u003Cem>crash\u003C\u002Fem> atau \u003Cem>Segmentation Fault\u003C\u002Fem>. Di \u003Cem>ring 0\u003C\u002Fem>, satu \u003Cem>pointer\u003C\u002Fem> liar bisa langsung memicu \u003Cem>kernel panic\u003C\u002Fem>. Bisa juga merusak \u003Cem>filesystem\u003C\u002Fem>, atau membuka jalan bagi penyerang untuk duduk di kursi \u003Cem>root\u003C\u002Fem>.\u003C\u002Fp>\n\u003Ch2 id=\"yang-sebenarnya-diincar-rimba-driver-hardware\">Yang sebenarnya diincar: rimba \u003Cem>driver hardware\u003C\u002Fem>\u003C\u002Fh2>\n\u003Cp>Banyak orang mengira Rust langsung dipakai buat menggantikan \u003Cem>scheduler\u003C\u002Fem> CPU, \u003Cem>virtual memory manager\u003C\u002Fem>, atau \u003Cem>filesystem\u003C\u002Fem> inti. Padahal sasarannya jauh lebih spesifik nih: \u003Cem>device driver\u003C\u002Fem>.\u003C\u002Fp>\n\u003Cp>Logikanya sederhana banget. Bagian \u003Cem>core\u003C\u002Fem> kernel yang tadi cuma 5% itu diurus oleh sekelompok \u003Cem>maintainer\u003C\u002Fem> yang ketat dan saling mengawasi. Sementara 95% sisanya isinya \u003Cem>driver\u003C\u002Fem> — GPU, modul Wi-Fi, kontroller NVMe, adaptor Bluetooth, sensor — yang ditulis ribuan \u003Cem>engineer\u003C\u002Fem> dari berbagai vendor \u003Cem>hardware\u003C\u002Fem>. Standar kualitas kode dan disiplin pengujian mereka beda-beda banget, karena memang nggak ada satu komite yang mengawasi semuanya.\u003C\u002Fp>\n\u003Cp>Tambahan lagi, kode \u003Cem>driver\u003C\u002Fem> berubah paling cepat, dan bug memori paling sering muncul di kode yang baru saja disentuh. Jadi area paling rawan tuh justru area yang paling sulit diawasi manusia. Di situlah \u003Cem>ownership\u003C\u002Fem> dan \u003Cem>borrow checker\u003C\u002Fem> Rust masuk kerja: kesalahan referensi ditolak di tahap kompilasi, bukan ketahuan tiga tahun kemudian saat ada yang melaporkan \u003Cem>kernel panic\u003C\u002Fem> di mesin produksi.\u003C\u002Fp>\n\n\u003Cdiv class=\"code-block-wrapper my-6 not-prose rounded-xl border-2 border-black dark:border-gray-600 shadow-neo overflow-hidden bg-[#24292e] text-[#e1e4e8] transition-all\">\n  \u003Cdiv class=\"code-block-header flex items-center justify-between px-4 py-2.5 bg-[#1f2428] border-b-2 border-black dark:border-gray-600 font-mono text-xs font-bold text-gray-300 select-none\">\n    \u003Cdiv class=\"flex items-center gap-2\">\n      \u003Cspan class=\"w-3 h-3 rounded-full bg-[#ff5f56] border border-black\u002F40 inline-block\">\u003C\u002Fspan>\n      \u003Cspan class=\"w-3 h-3 rounded-full bg-[#ffbd2e] border border-black\u002F40 inline-block\">\u003C\u002Fspan>\n      \u003Cspan class=\"w-3 h-3 rounded-full bg-[#27c93f] border border-black\u002F40 inline-block\">\u003C\u002Fspan>\n      \u003Cspan class=\"ml-2 font-mono font-bold text-xs uppercase tracking-wider text-gray-300\">RUST\u003C\u002Fspan>\n    \u003C\u002Fdiv>\n    \u003Cbutton type=\"button\" class=\"copy-code-btn flex items-center gap-1.5 px-3 py-1 text-xs font-bold bg-[#2f363d] text-gray-200 border-2 border-black dark:border-gray-500 rounded-lg shadow-neo-sm hover:translate-x-0.5 hover:translate-y-0.5 hover:shadow-none hover:bg-gray-700 transition-all cursor-pointer\" data-code=\"%2F%2F%20Contoh%20struktur%20dasar%20modul%20driver%20di%20Rust%20for%20Linux%20(API%20era%206.1)%0Ause%20kernel%3A%3Aprelude%3A%3A*%3B%0A%0Amodule!%20%7B%0A%20%20%20%20type%3A%20InvaSampleDriver%2C%0A%20%20%20%20name%3A%20%22inva_sample_driver%22%2C%0A%20%20%20%20author%3A%20%22Invasikode%20Team%22%2C%0A%20%20%20%20description%3A%20%22Contoh%20registrasi%20modul%20driver%20minimalis%20berbasis%20Rust%20di%20kernel%20Linux%22%2C%0A%20%20%20%20license%3A%20%22GPL%22%2C%0A%7D%0A%0Astruct%20InvaSampleDriver%3B%0A%0Aimpl%20kernel%3A%3AModule%20for%20InvaSampleDriver%20%7B%0A%20%20%20%20fn%20init(_name%3A%20%26'static%20CStr%2C%20_module%3A%20%26'static%20ThisModule)%20-%3E%20Result%3CSelf%3E%20%7B%0A%20%20%20%20%20%20%20%20pr_info!(%22Rust%20driver%20berhasil%20diinisialisasi%20ke%20dalam%20kernel%20Linux!%5Cn%22)%3B%0A%20%20%20%20%20%20%20%20Ok(InvaSampleDriver)%0A%20%20%20%20%7D%0A%7D%0A%0Aimpl%20Drop%20for%20InvaSampleDriver%20%7B%0A%20%20%20%20fn%20drop(%26mut%20self)%20%7B%0A%20%20%20%20%20%20%20%20pr_info!(%22Resource%20driver%20dibersihkan%20secara%20otomatis%20dan%20deterministik!%5Cn%22)%3B%0A%20%20%20%20%7D%0A%7D\" title=\"Salin kode\">\n      \u003Csvg class=\"w-3.5 h-3.5 copy-icon-svg\" fill=\"none\" stroke=\"currentColor\" viewBox=\"0 0 24 24\">\n        \u003Cpath stroke-linecap=\"round\" stroke-linejoin=\"round\" stroke-width=\"2\" d=\"M8 16H6a2 2 0 01-2-2V6a2 2 0 012-2h8a2 2 0 012 2v2m-6 12h8a2 2 0 002-2v-8a2 2 0 00-2-2h-8a2 2 0 00-2 2v8a2 2 0 002 2z\">\u003C\u002Fpath>\n      \u003C\u002Fsvg>\n      \u003Cspan class=\"copy-text\">Copy\u003C\u002Fspan>\n    \u003C\u002Fbutton>\n  \u003C\u002Fdiv>\n  \u003Cdiv class=\"code-block-content p-4 overflow-x-auto text-sm font-mono leading-relaxed bg-[#24292e]\">\n    \u003Cpre class=\"shiki github-dark\" style=\"background-color:#24292e;color:#e1e4e8\" tabindex=\"0\">\u003Ccode>\u003Cspan class=\"line\">\u003Cspan style=\"color:#6A737D\">\u002F\u002F Contoh struktur dasar modul driver di Rust for Linux (API era 6.1)\u003C\u002Fspan>\u003C\u002Fspan>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#F97583\">use\u003C\u002Fspan>\u003Cspan style=\"color:#B392F0\"> kernel\u003C\u002Fspan>\u003Cspan style=\"color:#F97583\">::\u003C\u002Fspan>\u003Cspan style=\"color:#B392F0\">prelude\u003C\u002Fspan>\u003Cspan style=\"color:#F97583\">::*\u003C\u002Fspan>\u003Cspan style=\"color:#E1E4E8\">;\u003C\u002Fspan>\u003C\u002Fspan>\n\u003Cspan class=\"line\">\u003C\u002Fspan>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#B392F0\">module!\u003C\u002Fspan>\u003Cspan style=\"color:#E1E4E8\"> {\u003C\u002Fspan>\u003C\u002Fspan>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#F97583\">    type:\u003C\u002Fspan>\u003Cspan style=\"color:#B392F0\"> InvaSampleDriver\u003C\u002Fspan>\u003Cspan style=\"color:#E1E4E8\">,\u003C\u002Fspan>\u003C\u002Fspan>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#E1E4E8\">    name\u003C\u002Fspan>\u003Cspan style=\"color:#F97583\">:\u003C\u002Fspan>\u003Cspan style=\"color:#9ECBFF\"> \"inva_sample_driver\"\u003C\u002Fspan>\u003Cspan style=\"color:#E1E4E8\">,\u003C\u002Fspan>\u003C\u002Fspan>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#E1E4E8\">    author\u003C\u002Fspan>\u003Cspan style=\"color:#F97583\">:\u003C\u002Fspan>\u003Cspan style=\"color:#9ECBFF\"> \"Invasikode Team\"\u003C\u002Fspan>\u003Cspan style=\"color:#E1E4E8\">,\u003C\u002Fspan>\u003C\u002Fspan>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#E1E4E8\">    description\u003C\u002Fspan>\u003Cspan style=\"color:#F97583\">:\u003C\u002Fspan>\u003Cspan style=\"color:#9ECBFF\"> \"Contoh registrasi modul driver minimalis berbasis Rust di kernel Linux\"\u003C\u002Fspan>\u003Cspan style=\"color:#E1E4E8\">,\u003C\u002Fspan>\u003C\u002Fspan>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#E1E4E8\">    license\u003C\u002Fspan>\u003Cspan style=\"color:#F97583\">:\u003C\u002Fspan>\u003Cspan style=\"color:#9ECBFF\"> \"GPL\"\u003C\u002Fspan>\u003Cspan style=\"color:#E1E4E8\">,\u003C\u002Fspan>\u003C\u002Fspan>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#E1E4E8\">}\u003C\u002Fspan>\u003C\u002Fspan>\n\u003Cspan class=\"line\">\u003C\u002Fspan>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#F97583\">struct\u003C\u002Fspan>\u003Cspan style=\"color:#B392F0\"> InvaSampleDriver\u003C\u002Fspan>\u003Cspan style=\"color:#E1E4E8\">;\u003C\u002Fspan>\u003C\u002Fspan>\n\u003Cspan class=\"line\">\u003C\u002Fspan>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#F97583\">impl\u003C\u002Fspan>\u003Cspan style=\"color:#B392F0\"> kernel\u003C\u002Fspan>\u003Cspan style=\"color:#F97583\">::\u003C\u002Fspan>\u003Cspan style=\"color:#B392F0\">Module\u003C\u002Fspan>\u003Cspan style=\"color:#F97583\"> for\u003C\u002Fspan>\u003Cspan style=\"color:#B392F0\"> InvaSampleDriver\u003C\u002Fspan>\u003Cspan style=\"color:#E1E4E8\"> {\u003C\u002Fspan>\u003C\u002Fspan>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#F97583\">    fn\u003C\u002Fspan>\u003Cspan style=\"color:#B392F0\"> init\u003C\u002Fspan>\u003Cspan style=\"color:#E1E4E8\">(_name\u003C\u002Fspan>\u003Cspan style=\"color:#F97583\">:\u003C\u002Fspan>\u003Cspan style=\"color:#F97583\"> &\u003C\u002Fspan>\u003Cspan style=\"color:#E1E4E8\">'\u003C\u002Fspan>\u003Cspan style=\"color:#B392F0\">static\u003C\u002Fspan>\u003Cspan style=\"color:#B392F0\"> CStr\u003C\u002Fspan>\u003Cspan style=\"color:#E1E4E8\">, _module\u003C\u002Fspan>\u003Cspan style=\"color:#F97583\">:\u003C\u002Fspan>\u003Cspan style=\"color:#F97583\"> &\u003C\u002Fspan>\u003Cspan style=\"color:#E1E4E8\">'\u003C\u002Fspan>\u003Cspan style=\"color:#B392F0\">static\u003C\u002Fspan>\u003Cspan style=\"color:#B392F0\"> ThisModule\u003C\u002Fspan>\u003Cspan style=\"color:#E1E4E8\">) \u003C\u002Fspan>\u003Cspan style=\"color:#F97583\">->\u003C\u002Fspan>\u003Cspan style=\"color:#B392F0\"> Result\u003C\u002Fspan>\u003Cspan style=\"color:#E1E4E8\"><\u003C\u002Fspan>\u003Cspan style=\"color:#79B8FF\">Self\u003C\u002Fspan>\u003Cspan style=\"color:#E1E4E8\">> {\u003C\u002Fspan>\u003C\u002Fspan>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#B392F0\">        pr_info!\u003C\u002Fspan>\u003Cspan style=\"color:#E1E4E8\">(\u003C\u002Fspan>\u003Cspan style=\"color:#9ECBFF\">\"Rust driver berhasil diinisialisasi ke dalam kernel Linux!\u003C\u002Fspan>\u003Cspan style=\"color:#79B8FF\">\\n\u003C\u002Fspan>\u003Cspan style=\"color:#9ECBFF\">\"\u003C\u002Fspan>\u003Cspan style=\"color:#E1E4E8\">);\u003C\u002Fspan>\u003C\u002Fspan>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#B392F0\">        Ok\u003C\u002Fspan>\u003Cspan style=\"color:#E1E4E8\">(\u003C\u002Fspan>\u003Cspan style=\"color:#B392F0\">InvaSampleDriver\u003C\u002Fspan>\u003Cspan style=\"color:#E1E4E8\">)\u003C\u002Fspan>\u003C\u002Fspan>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#E1E4E8\">    }\u003C\u002Fspan>\u003C\u002Fspan>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#E1E4E8\">}\u003C\u002Fspan>\u003C\u002Fspan>\n\u003Cspan class=\"line\">\u003C\u002Fspan>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#F97583\">impl\u003C\u002Fspan>\u003Cspan style=\"color:#B392F0\"> Drop\u003C\u002Fspan>\u003Cspan style=\"color:#F97583\"> for\u003C\u002Fspan>\u003Cspan style=\"color:#B392F0\"> InvaSampleDriver\u003C\u002Fspan>\u003Cspan style=\"color:#E1E4E8\"> {\u003C\u002Fspan>\u003C\u002Fspan>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#F97583\">    fn\u003C\u002Fspan>\u003Cspan style=\"color:#B392F0\"> drop\u003C\u002Fspan>\u003Cspan style=\"color:#E1E4E8\">(\u003C\u002Fspan>\u003Cspan style=\"color:#F97583\">&mut\u003C\u002Fspan>\u003Cspan style=\"color:#79B8FF\"> self\u003C\u002Fspan>\u003Cspan style=\"color:#E1E4E8\">) {\u003C\u002Fspan>\u003C\u002Fspan>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#B392F0\">        pr_info!\u003C\u002Fspan>\u003Cspan style=\"color:#E1E4E8\">(\u003C\u002Fspan>\u003Cspan style=\"color:#9ECBFF\">\"Resource driver dibersihkan secara otomatis dan deterministik!\u003C\u002Fspan>\u003Cspan style=\"color:#79B8FF\">\\n\u003C\u002Fspan>\u003Cspan style=\"color:#9ECBFF\">\"\u003C\u002Fspan>\u003Cspan style=\"color:#E1E4E8\">);\u003C\u002Fspan>\u003C\u002Fspan>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#E1E4E8\">    }\u003C\u002Fspan>\u003C\u002Fspan>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#E1E4E8\">}\u003C\u002Fspan>\u003C\u002Fspan>\u003C\u002Fcode>\u003C\u002Fpre>\n  \u003C\u002Fdiv>\n\u003C\u002Fdiv>\u003Cp>Perhatikan \u003Ccode>impl Drop\u003C\u002Fcode>-nya. Di C, melepas modul \u003Cem>driver\u003C\u002Fem> berarti kamu harus ingat membebaskan semua yang kamu alokasikan di \u003Ccode>module_exit\u003C\u002Fcode>, satu per satu, di jalur yang jarang diuji. Di Rust, implementasi \u003Ccode>Drop\u003C\u002Fcode> memastikan sumber daya \u003Cem>hardware\u003C\u002Fem> dibebaskan saat modul di-\u003Cem>unload\u003C\u002Fem>, dan kompilator menolak kode yang meninggalkan referensi menggantung.\u003C\u002Fp>\n\u003Cp>Satu catatan kalau kamu mau coba sendiri: \u003Cem>signature\u003C\u002Fem> \u003Ccode>init()\u003C\u002Fcode> di contoh itu mengikuti \u003Ca href=\"https:\u002F\u002Frust-for-linux.github.io\u002Fdocs\u002Fkernel\u002Ftrait.Module.html\">API era 6.1\u003C\u002Fa>. Di rilis yang lebih baru argumennya tinggal \u003Ccode>&'static ThisModule\u003C\u002Fcode>, dan sempat ada usulan untuk menghapus argumen itu sekalian. Cocokkan dulu dengan \u003Ca href=\"https:\u002F\u002Fdocs.kernel.org\u002Frust\u002Findex.html\">dokumentasi kernel\u003C\u002Fa> yang kamu pakai sebelum \u003Cem>copy-paste\u003C\u002Fem> dari artikel mana pun, termasuk yang ini. 😅\u003C\u002Fp>\n\u003Ch2 id=\"faktor-kedua-yang-jarang-dibahas-regenerasi-maintainer\">Faktor kedua yang jarang dibahas: regenerasi \u003Cem>maintainer\u003C\u002Fem>\u003C\u002Fh2>\n\u003Cp>Di luar urusan keamanan, ada alasan manusiawi yang sama pentingnya.\u003C\u002Fp>\n\u003Cp>\u003Cem>Maintainer\u003C\u002Fem> inti kernel Linux didominasi insinyur veteran yang sudah mengurus subsistem C selama 20 sampai 30 tahun. Di sisi lain, generasi \u003Cem>developer\u003C\u002Fem> sekarang tumbuh dengan standar bahasa yang beda: manajemen paket terintegrasi, dokumentasi interaktif, sistem tipe yang ekspresif, dan \u003Cem>tooling\u003C\u002Fem> yang ngerti maksud kodenya. Bahasa yang nggak menyediakan itu terasa seperti kerja lembur tanpa dibayar.\u003C\u002Fp>\n\u003Cp>Mendukung Rust di level kernel adalah langkah strategis untuk merangkul generasi baru \u003Cem>developer\u003C\u002Fem> sistem operasi. Tujuannya memastikan ada orang yang mau mengambil alih infrastruktur komputasi dunia sebelum angkatan C-nya pensiun. Buat proyek yang umurnya lebih tua dari banyak pembacanya, ini bukan kemewahan, tapi soal keberlanjutan.\u003C\u002Fp>\n\u003Ch2 id=\"riir-di-luar-kernel-menang-di-cli-kebablasan-di-tempat-lain\">RIIR di luar kernel: menang di CLI, kebablasan di tempat lain\u003C\u002Fh2>\n\u003Cp>Di luar kernel, antusiasme pada Rust melahirkan gerakan yang populer dengan nama RIIR. Di ekosistem \u003Cem>developer tools\u003C\u002Fem>, gerakan ini membuktikan diri secara nyata:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002FBurntSushi\u002Fripgrep\">ripgrep\u003C\u002Fa> (\u003Ccode>rg\u003C\u002Fcode>) jadi standar baru pengganti \u003Ccode>grep\u003C\u002Fcode>, kencang karena mesin regex-nya pakai \u003Cem>finite automaton\u003C\u002Fem> plus optimasi SIMD\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fsharkdp\u002Ffd\">fd\u003C\u002Fa> menggantikan \u003Ccode>find\u003C\u002Fcode> dengan antarmuka yang lebih intuitif dan pembacaan direktori paralel bawaan\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fsharkdp\u002Fbat\">bat\u003C\u002Fa> menghadirkan versi modern \u003Ccode>cat\u003C\u002Fcode> dengan \u003Cem>syntax highlighting\u003C\u002Fem> dan integrasi Git\u003C\u002Fli>\n\u003Cli>\u003Cem>Bundler\u003C\u002Fem> dan \u003Cem>compiler\u003C\u002Fem> seperti \u003Ca href=\"https:\u002F\u002Fswc.rs\u002F\">SWC\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Fbiomejs.dev\u002F\">Biome\u003C\u002Fa>, dan \u003Ca href=\"https:\u002F\u002Fvercel.com\u002Fblog\u002Fturbopack\">Turbopack\u003C\u002Fa> menulis ulang \u003Cem>toolchain\u003C\u002Fem> JavaScript dan CSS ke Rust, dengan klaim pemangkasan waktu \u003Cem>build\u003C\u002Fem> sampai belasan kali lipat\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Buat poin terakhir, ada \u003Cem>caveat\u003C\u002Fem> yang perlu kamu tahu dulu. Angka "10x lebih cepat" dari Vercel pernah \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fyyx990803\u002Fvite-vs-next-turbo-hmr\u002Fdiscussions\u002F8\">dibantah Evan You\u003C\u002Fa> karena \u003Cem>benchmark\u003C\u002Fem>-nya membandingkan hal yang nggak setara: implementasi Vite-nya masih memakai Babel, sementara Turbopack dan Webpack sama-sama memakai SWC. Yang tetap berdiri adalah alasan arsitekturnya — paralelisme \u003Cem>native\u003C\u002Fem> dan komputasi inkremental di Rust menghapus batas \u003Cem>single-thread\u003C\u002Fem> yang selama ini menahan \u003Cem>tooling\u003C\u002Fem> Node.js. Angka pastinya bergantung proyekmu sendiri, jadi ukur aja, jangan percaya \u003Cem>slide\u003C\u002Fem>.\u003C\u002Fp>\n\u003Cp>Sisi ekstremnya muncul ketika RIIR dipakai untuk menulis ulang proyek yang sudah stabil puluhan tahun tanpa urgensi teknis yang jelas. Menulis ulang kode yang sudah terbukti jalan demi tren bahasa sering menghabiskan biaya \u003Cem>engineering\u003C\u002Fem> raksasa tanpa peningkatan nilai yang bisa diukur. Bedanya dengan kasus kernel: di sana ada data CVE yang jelas, di banyak proyek RIIR lain cuma ada perasaan. 🤔\u003C\u002Fp>\n\u003Ch2 id=\"jadi-revolusi-atau-cuma-hype\">Jadi, revolusi atau cuma hype?\u003C\u002Fh2>\n\u003Cp>Kehadiran Rust di Linux 6.1 bukan hype sesaat. Ini adaptasi yang terukur dari proyek \u003Cem>open source\u003C\u002Fem> terbesar di dunia.\u003C\u002Fp>\n\u003Cp>Lihat buktinya di Android. Google mendorong Rust untuk kode sistem tingkat rendah di sana, dan hasilnya terukur: porsi celah keamanan memori turun dari 76% di 2019 ke 24% di 2024, lalu di bawah 20% di 2025. \u003Ca href=\"https:\u002F\u002Fblog.google\u002Fsecurity\u002Frust-in-android-move-fast-fix-things\">Laporan terbaru mereka\u003C\u002Fa> juga mencatat kepadatan kerentanan memori di kode Rust lebih dari seribu kali lebih rendah dibanding C dan C++, dengan \u003Cem>rollback rate\u003C\u002Fem> empat kali lebih kecil untuk perubahan berukuran sedang sampai besar, dan waktu \u003Cem>code review\u003C\u002Fem> yang 25% lebih singkat. Angka 76% dan 24% itu sendiri berasal dari \u003Ca href=\"https:\u002F\u002Fsecurity.googleblog.com\u002F2024\u002F09\u002Feliminating-memory-safety-vulnerabilities-Android.html\">post mereka setahun sebelumnya\u003C\u002Fa>. Biaya investasi ke Rust terbukti lebih murah daripada menambal \u003Cem>zero-day\u003C\u002Fem> di lingkungan produksi.\u003C\u002Fp>\n\u003Cp>Tapi jangan salah baca arah. C tetap jadi fondasi yang belum tergantikan. Portabilitasnya ke arsitektur prosesor apa pun dan kesederhanaan \u003Cem>toolchain\u003C\u002Fem>-nya nggak ada yang menyamai sampai hari ini. Kernel Linux pun nggak dibangun ulang — Rust masuk lewat pintu samping, di area yang paling rawan bug dan paling jarang diawasi, satu \u003Cem>driver\u003C\u002Fem> demi satu \u003Cem>driver\u003C\u002Fem>.\u003C\u002Fp>\n\u003Cp>Jadi jawabannya tuh: bukan revolusi, bukan juga hype. Rust datang bukan buat membunuh C, tapi buat menambal kekurangannya tepat di titik yang paling gampang pecah — dan di titik itu, kita memang sedang butuh bantuan siapa pun yang mau menulisnya. Selamat ngoprek \u003Cem>driver\u003C\u002Fem>, dan semoga yang kamu tulis nggak perlu \u003Cem>reboot\u003C\u002Fem> buat ketahuan salahnya. 👋\u003C\u002Fp>\n","\u003Cul>\n\u003Cli>Rust masuk ke kernel Linux bukan karena ikut tren, tapi karena data CVE menunjukkan sekitar 65-70% celah keamanan di bahasa \u003Cem>memory-unsafe\u003C\u002Fem> berasal dari kesalahan manajemen memori.\u003C\u002Fli>\n\u003Cli>Sasaran yang dipilih sengaja di \u003Cem>driver hardware\u003C\u002Fem>, bagian terbesar kernel yang paling cepat berubah dan paling longgar pengawasannya.\u003C\u002Fli>\n\u003Cli>Hasilnya sudah terukur di Android: porsi celah memori turun dari 76% di 2019 jadi 24% di 2024, dan di bawah 20% di 2025.\u003C\u002Fli>\n\u003Cli>C tetap jadi fondasi kernel, dan Rust berperan sebagai lapisan pengaman di titik paling rawan, bukan penggantinya.\u003C\u002Fli>\n\u003C\u002Ful>\n",[710,727,740,753,766,786],{"id":711,"title":712,"title_en":21,"slug":713,"excerpt":714,"excerpt_en":21,"has_translation":15,"published_at":715,"reading_time":81,"hidden_from_listing":15,"tags":716,"thumbnail_image":21,"og_image":718,"series":719,"authors":724},133,"Python Strings: the Badge That Only Worked for One Name","python-strings","The badge script printed the right name for the person who wrote it and the wrong name for everybody else. Slicing counts characters, and a name is words.","2026-10-28T13:00:00.000Z",[259,717],"string","\u002Fog\u002Fpython-strings.png",{"id":720,"title":721,"title_en":722,"slug":723},30,"Koleksi dan String","Collections and Strings","python-collections",[725],{"authors_id":726},{"id":307,"name":308,"slug":309,"role":271,"profile_picture":21},{"id":728,"title":729,"title_en":21,"slug":730,"excerpt":731,"excerpt_en":21,"has_translation":15,"published_at":732,"reading_time":81,"hidden_from_listing":15,"tags":733,"thumbnail_image":21,"og_image":735,"series":736,"authors":737},132,"Python Tuples: Why All Three Points Are the Same Point","python-tuples","Three points walk into a loop and come out identical. The list was never copied three times; the name was. A tuple makes that bug impossible.","2026-10-28T12:00:00.000Z",[259,734],"tuple","\u002Fog\u002Fpython-tuples.png",{"id":720,"title":721,"title_en":722,"slug":723},[738],{"authors_id":739},{"id":307,"name":308,"slug":309,"role":271,"profile_picture":21},{"id":741,"title":742,"title_en":21,"slug":743,"excerpt":744,"excerpt_en":21,"has_translation":15,"published_at":745,"reading_time":81,"hidden_from_listing":15,"tags":746,"thumbnail_image":21,"og_image":748,"series":749,"authors":750},131,"Python Sets: the Duplicate That Keeps Coming Back","python-sets","A de-duplication loop that works on clean data leaves four tags where there should be two. The bug is case, and the fix is a `set`.","2026-10-28T11:00:00.000Z",[259,747],"set","\u002Fog\u002Fpython-sets.png",{"id":720,"title":721,"title_en":722,"slug":723},[751],{"authors_id":752},{"id":307,"name":308,"slug":309,"role":271,"profile_picture":21},{"id":754,"title":755,"title_en":21,"slug":756,"excerpt":757,"excerpt_en":21,"has_translation":15,"published_at":758,"reading_time":81,"hidden_from_listing":15,"tags":759,"thumbnail_image":21,"og_image":761,"series":762,"authors":763},130,"Python Dictionaries: the Key That Isn't There","python-dictionary","A word counter dies the first time it meets a word twice. The fix is one line; what takes longer is knowing which of a dict's three lookups to reach for.","2026-10-28T10:00:00.000Z",[259,760],"dictionary","\u002Fog\u002Fpython-dictionary.png",{"id":720,"title":721,"title_en":722,"slug":723},[764],{"authors_id":765},{"id":307,"name":308,"slug":309,"role":271,"profile_picture":21},{"id":767,"title":768,"title_en":769,"slug":770,"excerpt":771,"excerpt_en":772,"has_translation":12,"published_at":773,"reading_time":14,"hidden_from_listing":15,"tags":774,"thumbnail_image":21,"og_image":781,"series":782,"authors":783},129,"Biar RAG nggak kena 504: pisahin jalur query dan ingestion","So Your RAG Stops Hitting 504: Split the Query Path From Ingestion","rag-pisah-jalur-query-dan-ingestion","Satu service RAG yang merangkap parsing dan menjawab kueri bakal tumbang pas ada yang upload PDF 200 halaman. Obatnya dua jalur dan satu queue.","One RAG service that both parses uploads and answers queries will fall over the moment someone uploads a 200-page PDF. The cure is two paths and one queue.","2026-10-22T01:30:00.000Z",[775,776,777,778,779,780],"rag","cloud-run","cloud-tasks","gcp","serverless","arsitektur","\u002Fog\u002Frag-pisah-jalur-query-dan-ingestion.png",{"id":694,"title":35,"title_en":36,"slug":37},[784],{"authors_id":785},{"id":307,"name":308,"slug":309,"role":271,"profile_picture":21},{"id":787,"title":788,"title_en":789,"slug":790,"excerpt":791,"excerpt_en":792,"has_translation":12,"published_at":793,"reading_time":81,"hidden_from_listing":15,"tags":794,"thumbnail_image":21,"og_image":801,"series":802,"authors":803},128,"Linear atau graf: cara mengatur banyak agent tanpa loop abadi","Linear or Graph: How to Run Many Agents Without an Eternal Loop","multi-agen-linear-atau-grafik","Satu agent dengan dua puluh tool gampang kacau. Begitu beberapa agent saling revisi, kamu butuh graf yang mendukung cycle dan angka yang membuatnya berhenti.","One agent with twenty tools gets messy fast. Once several agents revise each other, you need a graph that allows cycles and a number that makes it stop.","2026-10-21T16:05:00.000Z",[795,796,797,798,799,800],"multi-agent","langgraph","autogen","orkestrasi","checkpoint","llm","\u002Fog\u002Fmulti-agen-linear-atau-grafik.png",{"id":694,"title":35,"title_en":36,"slug":37},[804],{"authors_id":805},{"id":307,"name":308,"slug":309,"role":271,"profile_picture":21},[807,810,813,816,819],{"text":808,"depth":268,"id":809},"Kenapa Rust baru diterima sekarang?","kenapa-rust-baru-diterima-sekarang",{"text":811,"depth":268,"id":812},"Yang sebenarnya diincar: rimba driver hardware","yang-sebenarnya-diincar-rimba-driver-hardware",{"text":814,"depth":268,"id":815},"Faktor kedua yang jarang dibahas: regenerasi maintainer","faktor-kedua-yang-jarang-dibahas-regenerasi-maintainer",{"text":817,"depth":268,"id":818},"RIIR di luar kernel: menang di CLI, kebablasan di tempat lain","riir-di-luar-kernel-menang-di-cli-kebablasan-di-tempat-lain",{"text":820,"depth":268,"id":821},"Jadi, revolusi atau cuma hype?","jadi-revolusi-atau-cuma-hype",1793295835188]