Json + gzip vs messagePack - storage benchmark

ניר — Mon, 18 Aug 2025 09:10:01 +0000

gist here https://gist.github.com/nrbnlulu/ef0c621c1754f51867750c661b1dcb89

Results

Gzip compressed JSON file size: 0.006137 MB
Raw Msgpack file size: 0.213828 MB
Gzip compressed Msgpack file size: 0.006373 MB

--- Comparison in MB ---
Compressing Msgpack with Gzip saves 0.207455 MB.

--- Overall Space Efficiency ---
The most space-efficient format is 'Gzip JSON' with a size of 0.006137 MB.

How to contribute to the Flutter engine [Windows]

ניר — Tue, 29 Apr 2025 05:50:41 +0000

Writing this thing because its a pain setting up the repo + the docs are outdated.

Make sure that you don’t have any flutter executable in your PATH.
Install python3 git depot_tools Visual Studio 2017Windows 10 SDK` (required for non-Googlers only). Make sure to install the “Debugging Tools for Windows” feature.
git clone https://github.com/flutter/flutter.git
cd flutter
git remote rename origin upstream
Fork flutter and change the origin to your fork: git remote add origin git@github.com:\<your fork\>/flutter.git
Add flutter/bin to PATH.

make sure flutter is in your PATH where.exe flutter you'd might need to restart your terminal

Setting up the engine development environment

Add these to your env vars:
- DEPOT_TOOLS_WIN_TOOLCHAIN=0
- GYP_MSVS_OVERRIDE_PATH=C:\Program Files\Microsoft Visual Studio\2022\Community (make sure the path is correct)
cd flutter/engine
cp .\scripts\standard.gclient ../.gclient copy to root folder (before engine)
cd ../ and run gclient sync
Flutter has a tool for building the engine called et. Add it to PATH: C:\Users\temp\Desktop\flutter\engine\src\flutter\bin
cd into flutter/engine and run et build to build the engine. (make sure et is in your PATH)
Go make some ☕️ 🕐
In the mean time, you can configure your VS Code C++ LSP. I suggest that you first disable Dart and Flutter extensions in order to avoid them running commands you don’t want.
What should be done is:
1. Open Code in flutter/engine and make sure you have the ms-vscode.cpptools extension installed.
2. Configure VS Code to use compile_commands.json, which should be in C:\Users\temp\Desktop\flutter\engine\src\out\host_debug.

After several years et build should finish successfully, if not, don't start making changes you'd regret that later.
Implement your patches and create a PR on Flutter. Remember that Flutter's team requires signed commits… ___ ### Running Flutter projects with your custom engine

as per flutter docs on GH you should use et run inside your project (as if it was flutter run ) although for some reason it didn't worked for me, so I instead ran the et tool directly like so
ps dart C:\Users\temp\Desktop\flutter\engine\src\flutter\tools\engine_tool\bin\et.dart run

DEV Community: ניר

Json + gzip vs messagePack - storage benchmark

Results

How to contribute to the Flutter engine [Windows]

Setting up the engine development environment