Eric Müllenbach

hol up, why does anyone use rocksdb over lmdb github.com/cberner/redb

optimizeForDeveloperTime redd.it/1ghw02g

junge hahaha ist das akkurat 10/10

WSL does not get enough credit for what an amazing piece of tech it is. I've used it almost exclusively for dev for the last ~5 years and have run into less issues than I did developing on MacOS or Windows natively.

when you tune out in church and start to wonder who would get killed if the light fixtures fell from the ceiling

A gentle reminder for software engineers (you'll thank me later): • Learn SQL before ORM. • Learn Git before Jenkins. • Learn SQL before NoSQL. • Learn CSS before Tailwind. • Learn Linux before Docker. • Learn English before Python. • Learn JavaScript before React. • Learn REST before GraphQL. • Learn HTML before JavaScript. • Learn Containers before Kubernetes. • Learn Monolith before Microservices. • Learn Data Structures before Leetcode. The bottom line: Learn fundamentals before going deep. What else would you add?

It looks like Google Translate just recently added Canadian French as one of its new languages, check it out

13 years in America, still on a visa. Which party is going to make it easy for *legal* immigrants from India get at least a residency permit faster?

Sieht man sich das Diagramm an, fällt auf, dass in einem großen Bereich, das Haushaltseinkommen nicht mehr verhältnismäßig ansteigt. Der steigende Nettolohn wird fast komplett von sinkenden Sozialleistungen "aufgefressen", so dass die Familie kaum mehr in der Kasse hat. 4/9

I'm sick tired of people pushing their "memory-safe language" agenda when a viable solution is within reach.

This Louis CK bit, rent free forever captures the great chasm of our times

Hetzner is offering an S3-compatible object store (currently Beta), and the pricing is insane compared to AWS. Storage: 4X cheaper — $4.9/TB-mo vs $21/TB-mo Traffic: 50X cheaper — $51/TB vs $1/TB And no request fees. AWS charges $0.4-$5/M requests. docs.hetzner.com/storage/object…

𝗪𝗵𝗲𝗻 𝘁𝗼 𝘂𝘀𝗲 𝗚𝗿𝗮𝗽𝗵𝗤𝗟, 𝗴𝗥𝗣𝗖, 𝗮𝗻𝗱 𝗥𝗘𝗦𝗧? Developers can choose from various client-server communication protocols when designing an application. Utilizing GraphQL, gRPC, and REST is relatively common in modern projects. Each protocol can provide multiple advantages depending on the application's requirements. 𝗚𝗿𝗮𝗽𝗵𝗤𝗟 is a flexible approach for making data requests that focuses on specific requests and provides only necessary ones. The fact that GraphQL is client-driven distinguishes it from other APIs. The client makes all the decisions instead of handling them the standard way. Its 𝗮𝗱𝘃𝗮𝗻𝘁𝗮𝗴𝗲 is that it is language agnostic, requests are made through a single endpoint, and it is strongly typed, as it has schemas. 𝗥𝗘𝗦𝗧 is the most popular one. It is a great fit when a domain can be described as a set of resources. REST is a stateless architecture for data transfer. Some 𝗮𝗱𝘃𝗮𝗻𝘁𝗮𝗴𝗲𝘀 of REST are that it is a well-established standard, is simple to use, and has good caching support. 𝗴𝗥𝗣𝗖 is a method that offers a lightweight and rapid system for obtaining data. Here, the primary distinction is how it describes its contract negotiations. It relies on contracts; the architecture is not what governs the negotiation; it is the relationship between the server and the client. While handling and calculations are delegated to a remote server housing the resource, most power is used on the client side. Its main 𝗮𝗱𝘃𝗮𝗻𝘁𝗮𝗴𝗲𝘀 are that it has lightweight clients, is highly efficient as it uses protocol buffers to send/receive data, and is open source, too. So, 𝘄𝗵𝗲𝗻 𝘁𝗼 𝗰𝗵𝗼𝗼𝘀𝗲 each of those protocols: ✅ Use 𝗥𝗘𝗦𝗧 if you're building a CRUD-style web application or you work with well-structured data. ✅ Use 𝗴𝗥𝗣𝗖 if your API is private and about actions or if performances are essential. ✅ Use 𝗚𝗿𝗮𝗽𝗵𝗤𝗟 if you have a public API that needs to be flexible in customizing requests and want to add data from different sources into a public API. Each of these choices has specific uses and benefits. In this case, there is no clear winner, so what you should use—or, more, what you want to use—depends on your objectives and strategy. Read more about the choice of API protocols in the text in the comments. #programming #apidesign #api

Just learned someone's building a Minecraft server in Rust. CPU usage is 20x better and RAM is 100x 😳

I just want to tweet out this C. S. Lewis quote every weekend

Man kann in Deutschland ein anderes Auto rammen, fast zwei Menschen umbringen, Fahrerflucht begehen und mit 100 Sozialstunden und 12 Monaten Führerscheinverlust davonkommen. Unser Justizsystem ist ein schlechter Witz. x.com/RTLWEST/status…

If you have an .io domain you should read this. When the British government announced last week that it was transferring sovereignty of an island in the Indian Ocean to the country of Mauritius, Gareth immediately realized its online implications: the end of the .io domain suffix. every.to/p/the-disappea…

today is the last day to register to vote in georgia and arizona. please register in your state (you can do it online). voting is important, which is why as a noncitizen in california, ive already voted 16 times.

Companies need to occasionally delete all recurrent meetings to stay healthy. This works because it creates back pressure that all meetings have to be rejustified on merit. Fewer meetings: more focus on craft. (h/t @amandaorson for img)