Actually, that makes me think, what will happen, if suddenly there is a flood of reports, too many for them to deal with? Let's say all GrapheneOS users installed that app to get reported and then some more bots/fakes are set up to do that too.
While most people who use an unbackdoored OS aren't frauds, presumably it's correct at a slightly higher rate than assuming someone is a fraud because they use the internet.
I migrated from Angular 4 to 18 (including ngrx and material) and didn't find it especially problematic.
Migrating mostly was little effort and consisted of automatic migration and walking through the provided checklist (mostly to ensure I didn't miss anything important), but I don't have any comparison in the JS SPA ecosystem.
Vue 2 to Vue 3 has been equally painful for atleast one app I know about. Compare that to last three versions of Astro (with web components) and it has been a breeze.
> I migrated from Angular 4 to 18 (including ngrx and material) and didn't find it especially problematic.
The pain varies from project to project. Mine has been touched by a generation of developers of different levels of proficiency. A more disciplined project would’ve been easier to migrate in retrospective.
I think Angular ecosystem really missed the train with schematics (even ngrx!). Schematics could tackle a lot of toil if implemented exhaustively but apart from Angular and Material, nobody else seems to implement them effectively for brownfield projects.
> I’m a lot better at CSS than I was when I started using Tailwind.
> I got curious about what writing more semantic HTML would feel like.
This is so relatable. In the beginning of my career, I used to add so many dependencies for things I did not know. But these days, I mostly work on removing dependencies because I'm a lot better at using the web platform. I treat the web platform and browser primitives as materials to build what I want rather than a blank canvas to paint things from scratch.
That recent?!? Most criticism of Perl comes from people listening to second-hand rants of someone who hasn't looked at Perl since 2001.
Yes, the article could be improved by the Make magazine advice on submissions that you should write a 3 paragraph summary of your article and then submit that instead. This could have been shaved down to the 4 paras at the end (Prologue) to make the author's point more succinctly.
This is fantastic. I’ve been building an Excel-like but columnar spreadsheet app using DuckDB and had to reinvent the “client” through classic HTTP layer.
reply