When I read I build internal voices of the characters or narrators through the pages as a part of my imagination engaging with the words of the book. With audiobooks this never happens.
4,254 karma · joined December 10, 2021
When I read I build internal voices of the characters or narrators through the pages as a part of my imagination engaging with the words of the book. With audiobooks this never happens.
Not true since it requires you to sign in with Canva account.
For my personal site, it was a 5 minute work, as usual :)
I also wish there could be a general purpose content processing API so I can plug a different format than markdown (such as typst)
It’s now on the whims of Qualcomm, a for-profit company, who might be only interested in the talent and not what that talent has been doing at Modular.
I do feel weird about a major chunk of this article dedicated to ORMs; I guess people think they are still worthwhile, somehow.
> The Licensee may not modify, translate, adapt, alter, decompile, disassemble, decrypt, reverse engineer, change or alter the embedding bits, the font name, legal notices contained in the font software, nor seek to discover the source code of the font data, convert into another font format, create bitmaps, add or subtract any glyphs, symbols or accents, or any other derivative works based on the electronic data in this product.
This is why I haven’t bought it. I like to subset fonts to reduce the size. Any font license that prohibits this just gets ignored by me, no matter how good it is.
Regardless of what people say about Firefox, I've been using it for uBlock Origin and containers for ages, and won't be trading it for whatever performance, battery life, compatibility gains people continue to use Chrome for. Choose whatever is important for you, though.
How large a dataset can it tackle? I work with Parquet files spanning 300million+ records (~800MB files) using DuckDB and it works within seconds.
I might be interested to see benchmarks against Parquet and Vortex. A DuckDB extension would be great as well.
> 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.
These days I use web components for component writing and frameworks to handle routing, state management, bundling, and so on.
This design is already a success IMO.
> 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.
This entire article reeks of bias of someone who hasn’t looked at Java since Java 8.