Jorropo
@jorropo.net
I break code, both mine and not mine. Mainly in Go. 🇫🇷
IPv6 maximalist
IPv6 maximalist
I contributed a piece of opensource code that is a true gamechanger for an industrial machine.
Operating it used to mean constant supervision and manual interventions every 5 minute.
Let's see if I the company is willing to sponsor my work and support opensource developers.
Operating it used to mean constant supervision and manual interventions every 5 minute.
Let's see if I the company is willing to sponsor my work and support opensource developers.
November 3, 2025 at 12:54 PM
I contributed a piece of opensource code that is a true gamechanger for an industrial machine.
Operating it used to mean constant supervision and manual interventions every 5 minute.
Let's see if I the company is willing to sponsor my work and support opensource developers.
Operating it used to mean constant supervision and manual interventions every 5 minute.
Let's see if I the company is willing to sponsor my work and support opensource developers.
Reposted by Jorropo
Ooh, the SIMD WIP stdlib API for #golang is ready for people to poke!
From Cherry from a few minutes ago:
> As of today, we've landed a preliminary version with a reasonable API coverage. You're welcome to check out the dev.simd branch and try it with your use cases.
github.com/golang/go/is...
🚀
From Cherry from a few minutes ago:
> As of today, we've landed a preliminary version with a reasonable API coverage. You're welcome to check out the dev.simd branch and try it with your use cases.
github.com/golang/go/is...
🚀
proposal: simd: architecture-specific SIMD intrinsics under a GOEXPERIMENT · Issue #73787 · golang/go
Update (08/20/2025): A preliminary implementation of AMD64 low-level SIMD package is being developed on the dev.simd branch. You're welcome to check it out and try it with your use cases. Feedback ...
github.com
August 20, 2025 at 10:29 PM
Ooh, the SIMD WIP stdlib API for #golang is ready for people to poke!
From Cherry from a few minutes ago:
> As of today, we've landed a preliminary version with a reasonable API coverage. You're welcome to check out the dev.simd branch and try it with your use cases.
github.com/golang/go/is...
🚀
From Cherry from a few minutes ago:
> As of today, we've landed a preliminary version with a reasonable API coverage. You're welcome to check out the dev.simd branch and try it with your use cases.
github.com/golang/go/is...
🚀
Working in hardware gives a whole new literal meaning to FIXME comments:
> FIXME: this will blow up if 5V_EN and 50V_EN are concurrently HIGH, consider adding an interlock
> FIXME: this will blow up if 5V_EN and 50V_EN are concurrently HIGH, consider adding an interlock
August 8, 2025 at 7:48 PM
Working in hardware gives a whole new literal meaning to FIXME comments:
> FIXME: this will blow up if 5V_EN and 50V_EN are concurrently HIGH, consider adding an interlock
> FIXME: this will blow up if 5V_EN and 50V_EN are concurrently HIGH, consider adding an interlock
When will a general purpose ISA add a programmable logic instruction ?
One 4LUT per output bit, inputs indexed from 2×64bits source operand bits = 352 config bytes, with PTL 131456 transistors (11 transistors delay).
Would replace many instructions in algorithms where each bit has different logic.
One 4LUT per output bit, inputs indexed from 2×64bits source operand bits = 352 config bytes, with PTL 131456 transistors (11 transistors delay).
Would replace many instructions in algorithms where each bit has different logic.
July 29, 2025 at 8:39 AM
When will a general purpose ISA add a programmable logic instruction ?
One 4LUT per output bit, inputs indexed from 2×64bits source operand bits = 352 config bytes, with PTL 131456 transistors (11 transistors delay).
Would replace many instructions in algorithms where each bit has different logic.
One 4LUT per output bit, inputs indexed from 2×64bits source operand bits = 352 config bytes, with PTL 131456 transistors (11 transistors delay).
Would replace many instructions in algorithms where each bit has different logic.
THIS SOFTWARE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. EXPRESS OR IMPLIED
July 21, 2025 at 2:20 AM
THIS SOFTWARE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. EXPRESS OR IMPLIED
New debugging tech: have you tried turning on the AC ?
I was debugging a random once a day crash in the go runtime,
turns out my ram was at >100°C. Disabling XMP for now.
Shame ECC isn't standard on consumer hardware.
I was debugging a random once a day crash in the go runtime,
turns out my ram was at >100°C. Disabling XMP for now.
Shame ECC isn't standard on consumer hardware.
June 27, 2025 at 1:48 AM
New debugging tech: have you tried turning on the AC ?
I was debugging a random once a day crash in the go runtime,
turns out my ram was at >100°C. Disabling XMP for now.
Shame ECC isn't standard on consumer hardware.
I was debugging a random once a day crash in the go runtime,
turns out my ram was at >100°C. Disabling XMP for now.
Shame ECC isn't standard on consumer hardware.
It is 2025 and I had to send A LETTER.
Disgusting.
Disgusting.
June 25, 2025 at 8:13 PM
It is 2025 and I had to send A LETTER.
Disgusting.
Disgusting.
After nine months of inactivity my 3D printer started failing all prints while I need to make parts for a manufacturing machine.
I post a photo on a random discord and within minutes I get an expert telling me exactly what is wrong and how to fix it.
Maker communities are truly a magic place.
I post a photo on a random discord and within minutes I get an expert telling me exactly what is wrong and how to fix it.
Maker communities are truly a magic place.
June 14, 2025 at 1:03 AM
After nine months of inactivity my 3D printer started failing all prints while I need to make parts for a manufacturing machine.
I post a photo on a random discord and within minutes I get an expert telling me exactly what is wrong and how to fix it.
Maker communities are truly a magic place.
I post a photo on a random discord and within minutes I get an expert telling me exactly what is wrong and how to fix it.
Maker communities are truly a magic place.
Today the toolchain broke, so I've hexedit-ed the binary to fix a bug.
« Everything is open source if you know assembly. » might not be as wrong as it looks.
« Everything is open source if you know assembly. » might not be as wrong as it looks.
April 18, 2025 at 10:49 PM
Today the toolchain broke, so I've hexedit-ed the binary to fix a bug.
« Everything is open source if you know assembly. » might not be as wrong as it looks.
« Everything is open source if you know assembly. » might not be as wrong as it looks.
What they don't tell you about software engineering is that on 11 April 2025 at 04H07 UTC+2 you will spend 40 minutes stare at the screen thinking, read thousands of words across multiple issues to catch back up, do a couple greps to check how things were done just to review a 1 LINE CODE CHANGE.
April 11, 2025 at 2:51 AM
What they don't tell you about software engineering is that on 11 April 2025 at 04H07 UTC+2 you will spend 40 minutes stare at the screen thinking, read thousands of words across multiple issues to catch back up, do a couple greps to check how things were done just to review a 1 LINE CODE CHANGE.
- Nobody: Are you felling good today ?
- Me: 😒
- Nobody: Why ?
- Me:
- Me: 😒
- Nobody: Why ?
- Me:
March 29, 2025 at 9:01 AM
- Nobody: Are you felling good today ?
- Me: 😒
- Nobody: Why ?
- Me:
- Me: 😒
- Nobody: Why ?
- Me:
Reposted by Jorropo
Google plans to move all Android development to its internal branch and then publish relevant updates to the Android Open Source Project when they're ready. AOSP isn't going anywhere, but updates will come less frequently.
Exclusive: Google will develop the Android OS fully in private, and here's why
Google has confirmed it will move development of the Android OS to behind closed doors. Here's why it's doing it.
www.androidauthority.com
March 26, 2025 at 5:31 PM
Google plans to move all Android development to its internal branch and then publish relevant updates to the Android Open Source Project when they're ready. AOSP isn't going anywhere, but updates will come less frequently.
My life:
- Lurk in an open source project.
- Spend a couple hours coding a feature wanted for months.
- 😎
- Turn out you need to spend 10 more minutes fixing an edge case.
- It now only works for you because you're the only Arch user and Debian ships a 20-month-old version of libuv.
- Lurk in an open source project.
- Spend a couple hours coding a feature wanted for months.
- 😎
- Turn out you need to spend 10 more minutes fixing an edge case.
- It now only works for you because you're the only Arch user and Debian ships a 20-month-old version of libuv.
March 23, 2025 at 1:38 AM
My life:
- Lurk in an open source project.
- Spend a couple hours coding a feature wanted for months.
- 😎
- Turn out you need to spend 10 more minutes fixing an edge case.
- It now only works for you because you're the only Arch user and Debian ships a 20-month-old version of libuv.
- Lurk in an open source project.
- Spend a couple hours coding a feature wanted for months.
- 😎
- Turn out you need to spend 10 more minutes fixing an edge case.
- It now only works for you because you're the only Arch user and Debian ships a 20-month-old version of libuv.
Reposted by Jorropo
@thepudds.bsky.social is my hero
So far, up to 15x faster escape analysis for the Go compiler when compiling the TS checker package.
End to end that's an 8x faster compiler of the checker package for us, bringing it down from 50 seconds to 6 seconds.
github.com/golang/go/is...
So far, up to 15x faster escape analysis for the Go compiler when compiling the TS checker package.
End to end that's an 8x faster compiler of the checker package for us, bringing it down from 50 seconds to 6 seconds.
github.com/golang/go/is...
cmd/compile: slow escape analysis in large package in the typescript compiler · Issue #72815 · golang/go
Go version go version go1.24.1 linux/amd64 Output of go env in your module/workspace: AR='ar' CC='gcc' CGO_CFLAGS='-O2 -g' CGO_CPPFLAGS='' CGO_CXXFLAGS='-O2 -g' CGO_ENABLED='1' CGO_FFLAGS='-O2 -g' ...
github.com
March 18, 2025 at 8:00 PM
@thepudds.bsky.social is my hero
So far, up to 15x faster escape analysis for the Go compiler when compiling the TS checker package.
End to end that's an 8x faster compiler of the checker package for us, bringing it down from 50 seconds to 6 seconds.
github.com/golang/go/is...
So far, up to 15x faster escape analysis for the Go compiler when compiling the TS checker package.
End to end that's an 8x faster compiler of the checker package for us, bringing it down from 50 seconds to 6 seconds.
github.com/golang/go/is...
Reposted by Jorropo
TypeScript team: rewrites compiler in Go.
Go community: what do you mean your new compiler takes more than a minute to compile? Unacceptable. Dishonorable even. We are so sorry for this sub par experience. Not how we do things around here.
Two days later: WIP 5x speedup.
HN: why pick Go anyway?
Go community: what do you mean your new compiler takes more than a minute to compile? Unacceptable. Dishonorable even. We are so sorry for this sub par experience. Not how we do things around here.
Two days later: WIP 5x speedup.
HN: why pick Go anyway?
cmd/compile: slow escape analysis in large package in the typescript compiler · Issue #72815 · golang/go
Go version go version go1.24.1 linux/amd64 Output of go env in your module/workspace: AR='ar' CC='gcc' CGO_CFLAGS='-O2 -g' CGO_CPPFLAGS='' CGO_CXXFLAGS='-O2 -g' CGO_ENABLED='1' CGO_FFLAGS='-O2 -g' ...
github.com
March 13, 2025 at 12:53 AM
TypeScript team: rewrites compiler in Go.
Go community: what do you mean your new compiler takes more than a minute to compile? Unacceptable. Dishonorable even. We are so sorry for this sub par experience. Not how we do things around here.
Two days later: WIP 5x speedup.
HN: why pick Go anyway?
Go community: what do you mean your new compiler takes more than a minute to compile? Unacceptable. Dishonorable even. We are so sorry for this sub par experience. Not how we do things around here.
Two days later: WIP 5x speedup.
HN: why pick Go anyway?
Awesome work by @thepudds.bsky.social github.com/golang/go/is...
Compiling the typescript compiler went from 70s to 30s !
Compiling the typescript compiler went from 70s to 30s !
cmd/compile: slow escape analysis in large package in the typescript compiler · Issue #72815 · golang/go
Go version go version go1.24.1 linux/amd64 Output of go env in your module/workspace: AR='ar' CC='gcc' CGO_CFLAGS='-O2 -g' CGO_CPPFLAGS='' CGO_CXXFLAGS='-O2 -g' CGO_ENABLED='1' CGO_FFLAGS='-O2 -g' ...
github.com
March 13, 2025 at 10:44 AM
Awesome work by @thepudds.bsky.social github.com/golang/go/is...
Compiling the typescript compiler went from 70s to 30s !
Compiling the typescript compiler went from 70s to 30s !
Reposted by Jorropo
Today we're thrilled to announce our effort to port the TypeScript compiler and language service to native code, gaining a 10x speed boost in build times and editor responsiveness!
devblogs.microsoft.com/typescript/t...
devblogs.microsoft.com/typescript/t...
A 10x Faster TypeScript - TypeScript
Embarking on a native port of the existing TypeScript compiler and toolset to achieve a 10x performance speed-up.
devblogs.microsoft.com
March 11, 2025 at 2:36 PM
Today we're thrilled to announce our effort to port the TypeScript compiler and language service to native code, gaining a 10x speed boost in build times and editor responsiveness!
devblogs.microsoft.com/typescript/t...
devblogs.microsoft.com/typescript/t...
The most surprising thing in the typescript-go story is the number of C# devs feeling betrayed by Microsoft.
March 12, 2025 at 2:40 PM
The most surprising thing in the typescript-go story is the number of C# devs feeling betrayed by Microsoft.
Useless go fact:
Untyped expressions are not limited to the const realm.
Using << and >> operators on an untyped LHS with a variable RHS produce an untyped variable expression.
Untyped expressions are not limited to the const realm.
Using << and >> operators on an untyped LHS with a variable RHS produce an untyped variable expression.
March 12, 2025 at 12:28 PM
Useless go fact:
Untyped expressions are not limited to the const realm.
Using << and >> operators on an untyped LHS with a variable RHS produce an untyped variable expression.
Untyped expressions are not limited to the const realm.
Using << and >> operators on an untyped LHS with a variable RHS produce an untyped variable expression.
The ESP32 backdoor conclusion from an offensive PoV:
If you are running code in ring0* you can read, write and execute arbitrary code.
*note that the Core used in the first ESP32 lacks an MMU like the vast majority of MCUs.
If you are running code in ring0* you can read, write and execute arbitrary code.
*note that the Core used in the first ESP32 lacks an MMU like the vast majority of MCUs.
March 11, 2025 at 8:15 AM
The ESP32 backdoor conclusion from an offensive PoV:
If you are running code in ring0* you can read, write and execute arbitrary code.
*note that the Core used in the first ESP32 lacks an MMU like the vast majority of MCUs.
If you are running code in ring0* you can read, write and execute arbitrary code.
*note that the Core used in the first ESP32 lacks an MMU like the vast majority of MCUs.
Tomorrow's side quest, figure out why the first function compiles better than the second one:
func good(x, y uint) uint { return min(x, y) }
func good(x, y uint) uint { return min(y, x) }
func good(x, y uint) uint { return min(x, y) }
func good(x, y uint) uint { return min(y, x) }
March 10, 2025 at 7:43 PM
Tomorrow's side quest, figure out why the first function compiles better than the second one:
func good(x, y uint) uint { return min(x, y) }
func good(x, y uint) uint { return min(y, x) }
func good(x, y uint) uint { return min(x, y) }
func good(x, y uint) uint { return min(y, x) }
Today's mood:
- 12h00 I guess I am writing Java
- 15h00 Fuck Java why am I doing this ?
- 12h00 I guess I am writing Java
- 15h00 Fuck Java why am I doing this ?
January 14, 2025 at 5:40 PM
Today's mood:
- 12h00 I guess I am writing Java
- 15h00 Fuck Java why am I doing this ?
- 12h00 I guess I am writing Java
- 15h00 Fuck Java why am I doing this ?
So much fun waiting to be had, I just noticed the go compiler lacks RISCV64 C & B support even tho GORISCV64=rva2020u64 & rva2020u64 respectively allows us to use them.
January 1, 2025 at 12:16 AM
So much fun waiting to be had, I just noticed the go compiler lacks RISCV64 C & B support even tho GORISCV64=rva2020u64 & rva2020u64 respectively allows us to use them.
Wake up babe new Agile manifesto just dropped !
agvxov.github.io/fdd/fdd_mani...
agvxov.github.io/fdd/fdd_mani...
December 27, 2024 at 11:23 AM
Wake up babe new Agile manifesto just dropped !
agvxov.github.io/fdd/fdd_mani...
agvxov.github.io/fdd/fdd_mani...
Ok hear me out, Factorio asynchronously autosave while playing by forking to create a COW of the memory space.
What if we did the same thing for Go tests ? The scheduler would fork on each scheduling decision and run all paths, this allows to prove some concurrent is always correct via bruteforce.
What if we did the same thing for Go tests ? The scheduler would fork on each scheduling decision and run all paths, this allows to prove some concurrent is always correct via bruteforce.
December 25, 2024 at 12:14 PM
Ok hear me out, Factorio asynchronously autosave while playing by forking to create a COW of the memory space.
What if we did the same thing for Go tests ? The scheduler would fork on each scheduling decision and run all paths, this allows to prove some concurrent is always correct via bruteforce.
What if we did the same thing for Go tests ? The scheduler would fork on each scheduling decision and run all paths, this allows to prove some concurrent is always correct via bruteforce.