Guilherme Lucas

"Come Here, Rika." ( via @Jujutsu_Kaisen_)

The Legend of Zelda: Ocarina of Time (1998)

A new Starfox game and a Legend of Zelda: Ocarina of Time remake are among numerous unannounced Nintendo games reportedly headed to Switch 2 this year. bit.ly/4t5IJGy

A new Starfox game and a Legend of Zelda: Ocarina of Time remake are among numerous unannounced Nintendo games reportedly headed to Switch 2 this year, according to noted internet tipster Natethehate. bit.ly/3PxRgnj

A major remake of ‘THE LEGEND OF ZELDA: OCARINA OF TIME’ is reportedly releasing this year. (Source: videogameschronicle.com/news/sources-n…)

@leticiaxmotta E eles ainda correram pra tocar o máximo de músicas que dava. Show foi incrível, mas realmente show solo ia ser muito melhor

Deftones não é banda pra festival não, precisava ser solo, minha única frustração

@pybetim Eh papo de nunca mais ver um jogo desse time

Se anunciarem Fernando Diniz, eu juro que me deixo na BR e espero um carro passar por cima

Fighting Force (1997)

Why JSON is burning your CPU Your API is slow. You blame the database. You blame the network. But the real bottleneck might be the language you are speaking. JSON is not a data format. It is a text string. Every time you send {"id": 12345}, your server pays a hidden 'Parse Tax.' Even with modern SIMD-optimized parsers, text processing faces architectural limits that binary formats do not. Here is the rigorous engineering breakdown: 1./ The CPU Cost (state machine vs. arithmetic) JSON (Text): To read the number 12345, the CPU receives raw bytes. Even the fastest parsers (like simdjson) must implement a State Machine: Scan for structural delimiters (: and ,). Check for escape sequences (\). the conversion: Loop through ASCII characters, subtracting '0', multiplying by powers of 10, and summing. This involves branch mispredictions and memory lookups. Protobuf (Binary): It sends a Varint (for small numbers) or Fixed-Width (for large ones). Fixed-Width (e.g., fixed32) => It is a raw memory copy (memcpy). Zero parsing. Varint => It reads 1 byte at a time, checking the "Most Significant Bit" (MSB) to see if the number continues. The Result => Decoding is effectively a few bitwise shifts and masks. For numeric-heavy workloads, this is mathematically guaranteed to be significantly faster than text parsing. 2./ The Bandwidth Cost (entropy vs. redundancy) JSON: [{"status": "active"}, {"status": "active"}] You are sending the key "status" repeatedly. Counter-argument => "But GZIP compression fixes this!" The Rebuttal => GZIP reduces the Network bytes, but it increases the CPU cost. Your server now has to Serialize JSON -> Compress -> Send. The receiver has to Decompress -> Parse JSON. You are burning CPU to compress redundant text that shouldn't have been there in the first place. Protobuf: It separates the Schema from the Data. The wire message replaces "status" with a Field ID (e.g., 1). [Tag: 1][Value: "active"]. This reduces the payload size before compression is even applied, saving CPU cycles on both ends. 3./ The Robustness Cost (schema-on-read) JSON is "Schema-on-Read." The receiver gets a blob. It hopes the ID is a number. Your code is full of runtime checks (if typeof(id) !== 'number'...) or you use a validation library (like Zod/Pydantic), which adds another layer of CPU overhead at runtime. Protobuf is "Schema-on-Write." It enforces a contract. While it doesn't catch logic errors, it guarantees Type Fidelity at the serialization boundary. You generally don't need expensive runtime validation libraries to check if an Integer is an Integer. In a nutshell - JSON is excellent for Public APIs (debuggable, easy). But for high-throughput Microservices, JSON is a tax. Switching to gRPC/Protobuf isn't magic. It is simply moving the complexity from Runtime (parsing text) to Compile Time (code generation). Happy Learning! Follow @techNmak for more insights.

@somosaopaulinos O único que prestou foi o Enzo

📸 As contratações feitas pelo São Paulo em 2025. Qual a melhor? E a pior?

@somosaopaulinos YOUNG? OS CARAS VAO PREFERIR FICAR COM JANDREI? A pior notícia do SP eh sempre a próxima mesmo

Demissões geram mal-estar, mas São Paulo prepara mais saídas dentro e fora de campo para 2026. Entre os atletas, nomes como Luiz Gustavo, Dinenno, Rigoni, Patryck Lanza e Young devem deixar o clube. A principal agitação no CT, porém, acontece fora de campo. As demissões de funcionários de setores como rouparia, massagem e segurança causaram mal-estar nos bastidores do clube. O clube, porém, planeja mais saídas para o decorrer da semana. No momento, o clima na Barra Funda é de insegurança e de incerteza, e a situação vem criando um grande ruído interno no Tricolor, deixando o ambiente tenso. A diretoria argumenta que a intenção trazer "sangue novo" e oxigenar o quadro de funcionários, com o objetivo de melhorar a estrutura e os processos do time para 2026. 🗞 ESPN | André Hernan 📸 UOL

FORTNITE IS CONSIDERING THESE CHARACTERS FOR SIDEKICKS 🔥 (VIA @FN_Assist)

Same.

@OGabrielSa Sao paulo não vai conseguir ter 11 em campo desse jeito

São Paulo informa sobre Arboleda: “Após relatar dores na região posterior da coxa esquerda, o zagueiro realizou exame de imagem na tarde desta sexta-feira e teve diagnosticada uma lesão muscular. Ele já iniciou o tratamento”

BULLET FOR MY VALENTINE NO BRASIL! Banda substitui Yungblud na abertura do show do Limp Bizkit em São Paulo.

Ratings for Vince Gilligan's last 3 shows 📺

[SEASON 2] confirmed. // #AlienEarthFX

#AlienEarth has been renewed for Season 2 at FX.

Watch the first teaser trailer for #ToyStory5 - in theaters June 19, 2026.