
Pierre
7.9K posts

Pierre
@martpie_
Web // Frontend // UX. Some open-source. Stupid and arrogant French in my spare time. Also building @museeks
Zurich, Switzerland Katılım Nisan 2012
175 Takip Edilen532 Takipçiler
Sabitlenmiş Tweet

Next.js 13.1 is released.
This is officially The End of next-transpile-modules. 🎉🎅
Congrats to the @vercel and @nextjs teams!
github.com/martpie/next-t…
English

… == null
Is perfectly fine, often desirable
Artem Zakharchenko@kettanaito
I can tell your seniority based on your opinion on the "==" operator alone.
English

@gethackteam Well now even if Redux Toolkit make things more bearable, putting more things in URL params + react-query cache is just easier to think about.
If one really need global state just use Zustand or Jotai and move on.
We had to have the terrible things to get the nice things.
English

Current Vite+ adoption.
There's also a TONS of issues we need to address, we'll churn through them asap.
I can hand out repo triage permission if you show enthusiasm and help out.
github.com/voidzero-dev/v…

English

@kettanaito I write that as someone who has migrated all my apps to Native Webviews, and fairly happy with the changes, but there is a cost to it engineers need to understand.
English

@kettanaito External drag-and-drop fails on Windows unless you disable menu accelerators.
libwekit-gtk dependencies are distro-specific and may not be available.
File associations is a nightmare between macOS and Linux/Windows.
If you are a business and want peace of mind, go Electron.
English

I’d go so far as to say migrations themselves are unnecessary. At least beyond their changeset. Once applied, they should be removed and the latest schema should be snapshotted. There’s no reason any application should run hundreds of “old” migrations in sequence.
Freek Van der Herten@freekmurze
I never write down migrations. Down migrations are the least tested code in any Laravel app. They're written once and never run. And when you do need to roll back, you don't know beforehand what you need to do with the data would already be stored in the updated schema.
English

@larroumecj Super intéressant, serait il possible dans le groupement par décile d’avoir une plus détaillée plus on monte? Par exemple top 10% -> 1%, top 1% -> 0.1% etc?
Français

Je vous propose un graphique qui je crois n'avait encore jamais été fait : les flux monétaires complets Français => sphère publique => Français.
En effet, la sphère publique est une grande machine à redistribuer.
On prend aux Français de plein de manières différentes (TVA, IR, amendes, etc.), ça passe par des administrations diverses complexes et ça retombe dans le poche d'autres Français de façons diverses (transferts, services publiques, infrastructures, etc.)
Ce graph retrace les flux, et permet de voir les transferts par niveau de richesse et par génération.
Cela m'a forcé à faire des trucs rigolos, comme décomposer qui paye vraiment l'impôt sur les sociétés.
J'arrive à la conclusion que seulement 15% de l'IS est payé par les plus riches des actionnaires, et qu'en proportion de leurs revenus, les plus pauvres payent plus pour l'IS. Pourquoi ? Parce qu'une partie du coût de l'IS est portée sur des salaires plus faibles et des prix à la consommation plus élevés.
Ce n'est forcément pas parfait, et je prends tous vos commentaires et corrections. Je pense néanmoins que les ordres de grandeur sont corrects.
Vous trouverez les versions détaillées et interactives ici : #depenses" target="_blank" rel="nofollow noopener">francetdb.com/#depenses
(Par ailleurs j'ai ajouté partout sur le site les sources et les formules)




Français

@adamsilverhq I’d like to get your alternative for a desktop app I’m building: museeks.io
For some actions, like « add to queue », « add to playlist », etc, what would you recommend as an alternative for a quick, non-invasive « green check » showing the users the action was done
English

Github’s Design System now bans toast messages.
In case you don’t know, toast messages are little messages shown on top of the UI to give feedback about an action that you’ve just taken.
Banning toast messages is an excellent decision because they have bad UX and are terrible for accessibility.
Here’s a few reasons why:
(1) They disappear automatically after a few seconds (at best this is stressful, at worst you’ll miss it)
(2) They obscure the content underneath which is frustrating and slows users down.
(3) They’re hard to spot because they’re small and shown at the edge of the screen.
And there are plenty of other issues which I’ll link to below if you’re keen.
Let’s hope Github bans tooltips next.

English

@Timofey_Khmelev @mmartin_joo I mean, this is true of any API? If you remove a field or an endpoint, you need to make sure all callsites are removed from your front end.
English

@mmartin_joo yeah, we try to abandon it in our project. Deploying changes is a nightmare - your front and back have to be in sync all the time.
English

@ZachWarunek Always check for a dirty repo at the end of your CI.
Here how I do it: #L61" target="_blank" rel="nofollow noopener">github.com/martpie/museek…
English

@thatgayfella @chinlee @jamesbaratheon @AlexNoonan6 VSCode is free, as in « free ».
code.visualstudio.com/license

Nederlands

Pierre retweetledi

Museeks 0.20.0 is here!
- Now built on top of Tauri (rust backend, 20x smaller binaries, less cpu/memory usage)
- Updated header
- New library management
- New dark theme
- Compact track view
- Scroll restoration
- Edit more track information
github.com/martpie/museek…
English


















