martpie

Joined 8 years ago

Karma
566
Submissions
67
Member since
Oct 9
Used to be @KeitIG.

JS developer, maker of Museeks. Stupid and arrogant french in my spare time.

View on Hacker News

Recent submissions

Comment · 8 months ago
Look very nice, I may end up using for https://museeks.io, gapless playback has been on the roadmap for a while, but WebAudio APIs have always been super cryptic, a higher-level API is very much welcome.
Comment · 1 year ago
I mean, I hate business as much as any other engineer, but what’s the point of software without a business? (excl. the beauty of open source)
Comment · 1 year ago
TBH, all of what’s in this release came from previous 1.1.x patches.

It seems they just drafted a new release to communicate the groups of change from the previous releases.

Comment · 2 years ago
That the whole industry embraced. Not bad for a piece of trash.
Comment · 2 years ago
Well, it definitely becomes harder when you cannot (officially) access any of the WP infra, including themes and plugins.
Comment · 2 years ago
That is exactly what Meta acknowledged, and this is not a product that is going to be released to the public anyway.
Comment · 2 years ago
As a non-native English speaker, I may be one the few finding this addition really useful to correct syntax and spelling mistakes.

I am not 100% sure to understand the hostility towards such a feature, that seems accessible only via a user-action.

Comment · 2 years ago
To me, the best feature is Relay Fragments (I think Apollo has fragments too?), as each component describes the data they need: no need to do a big top-level request then pass down the data to the responsible components, everything is in one file.

It makes UI changes much much easier to deal with.

Comment · 2 years ago
Lots of valid points about the increase in complexity for React over the years, and that one should pick another more modern tech stack (Svelte, Solid, html, whatever), and I used to be thinking like that

But since maybe 1-2 years, I am back and betting on React for most of my serious projects (for the ecosystem, the ease of hiring, etc), but the most important point is the following:

React backwards compatibility is really good, and will stay so for a good reason: a LOT of Meta’s UI code is using old features (classes syntax etc), and Meta cannot afford to break those. If there are breaking changes, they must be “codemodable” (so, usable by everyone).

Meaning in terms of stability, I know my codebase today will still work fine in years ( or upgrade-able with minimal efforts). Of course there will be new shiny features, but I or my team will not have to rewrite old code all the time following tedious migration guides.

disclaimer: I am kind of biased as I work at Meta, but far from React.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton