Sr. Software Engineer 🤓 I create stuff for the web
Paris, France
Joined February 2019
- Tweets861
- Following279
- Followers1K
- Likes2.3K
Pinned Tweet
I built a 3D cinema for Infinite Slop.
You walk in, pick a seat and watch the stream on the big screen with everyone else in the room. Multiplayer, spatial audio, free, no account.
Just opened: slop.theater/
Powered by @levelsio's infiniteslop.ai
Hey @levelsio
I built a 3D cinema for Infinite Slop: you can walk in, sit down, and watch your stream on the big screen. It’s multiplayer, and the audio is spatialized.
Would you be okay with me shipping it? You’d just need to allowlist my VPS IP address, and a couple of hours after that, it’ll be live! 🍿
My DMs are open.
Okay I built it!
🍰 Infinite Slop
levels.io/infinite-slop
An infinite and interactive AI generated live stream of slop that goes on forever and ever
Anything that you write in the chat is generated next and AI will try to connect it to the previous video so there's an actual sequence and story line
Idea by @marcantoinefon and @rehan_shei's original stream so I made it
It'd be very expensive to run this so @fal very generously sponsors this
They also fine-tuned the model that makes this possible for the first time, making Minimax H3 50x faster and as "Max" and it can now generate videos faster than you can watch them, very cool!
Let me know what you think!!!! 😊
Making progress on Click the Cloud, with a little help from Fable 5.1 ☁️🌱
You can now plant seeds, make it rain, and grow flowers!
Next up: automating rain and planting, so you can slowly turn your tiny patch of land into a magnificent lake 🌧️💧
Built with @threejs
Working on a chill incremental game where you click a cloud to make it rain, collect water, and slowly turn it into an absolute rain machine ☁️🌧️
Going for some cozy, ASMR-like vibes. This is the prototype, I'll post each major updates.
Built with @threejs
I'm building Reddit Place, but in 3D.
You'll be able to paint on 1,000,000+ pixels, and even on yourself, with thousands of people around you.
It runs entirely in the browser using @threejs.
Launching in a couple of weeks.
I've used @cursor_ai (90% with Grok 4.6).
#threejs #indiegame
I already love the new model() function from #angular!
Here's a quick demo using model() + computedAsync from ngxtension by @Nartc1410 and @Enea_Jahollari + no RxJS
Demo: stackblitz.com/edit/stackbli…
Here's a version with no external deps.
Important note: RxJS is great. Please use it if you wanna have a highly scalable and event driven app (which you very likely want)
stackblitz.com/edit/stackbli…
I love RxJS and I love Signals.
It's WONDERFUL that they both exist in Angular and it SHOULD continue like so.
You need to create data and other data that derive from them while keeping them all in sync ? Use Signals.
You need to manage events like a click on a button, a http request, a window resize or any custom events ? Use Rxjs.
Signals are simple and powerful.
RxJS is complex but super powerful.
The combinaison of these two solutions is what makes an #angular application truly resilient.
A rebrand + a total rework of the learning journey in Angular 🥰
Today, we are excited to announce Angular.dev – the future home for Angular developers.
goo.gle/angular-dot-dev
Here's how to use Signal's effects in #Angular to update the title of your app.
In this example, the 'increment' function updates the 'count' Signal which triggers the 'setTitle' effect because 'count' is used inside of it.
Pretty cool trick if you ask me!
We all know about 'let index = index' on #Angular's *ngFor. But did you know there are plenty of other variables?
- odd
- even
- first
- last
Pretty useful on some cases!
One of the first thing I do when I start an #Angular application?
I modify the 'generate component' schematic.
This way, my teams will simply need to type 'ng g c my-comp', and it will create a component:
- with inline template
- with inline style
- standalone
- flat (no wrapping folders)
- with onPush CD strategy
This boosts productivity and introduces consistency across the entire codebase!
Did you know you can emit an Observable from an Output in #Angular ?
Here, I've created a SearchComponent that emits a 'searched' Observable every time the search field's value changes.
On the consumer side, all I have to do is listen to this observable and react accordingly, for example by updating a Signal.
By doing this, you'll implement the debounce/filter/etc operators only one time in the reusable component and not every time in every consumers.
Where should you provide your Angular's Injectables?
Most of the time, Injectables are Singletons, meaning there's only one instance of them, and every element that injects them actually uses their same state.
However, you can scope your Injectables in several ways:
👉 If you need a global state
Use providedIn: 'root' for an Injectable available everywhere within the app, typically if you need the same state in multiple places.
👉 If you need a different state for each component
Use the 'providers' property of a component for a state available only at the component level and its child components.
👉 If you need a state available at the level of a route and its sub-routes
Use the 'providers' property of the route located in the routing file. By doing this, the injectable is scoped to that specific location, so if MyFeatureComponent or MyFeatureGuard injects the injectable, they will use the same instance.
#Angular
