Awesome article. SDF(or mSDF) isn't the future. It's already "good enough" classic. > This works, but performance tanks hard, as we solve every > bezier curve segment per pixel This is "the future" or even present as…
https://component-party.dev/compare/svelte4-vs-svelte5 best format to compare to my mind
It seems you are mixing two things: inner string representation and read/write encoding. Java has never used UTF-16 as default for the second.
Dart compiler does it, as I know.
You can import/export to Google Authenticator only and you must have two phones. You cannot backup QR codes because screenshot is forbidden for security reason. You cannot migrate to another application.
> It doesn't support map/tables/dictionaries. This is actually huge. It's actually easy to implement. Just define custom scalar type: scalar JSON type MyObject { myField: JSON }…
Awesome article. SDF(or mSDF) isn't the future. It's already "good enough" classic. > This works, but performance tanks hard, as we solve every > bezier curve segment per pixel This is "the future" or even present as…
https://component-party.dev/compare/svelte4-vs-svelte5 best format to compare to my mind
It seems you are mixing two things: inner string representation and read/write encoding. Java has never used UTF-16 as default for the second.
Dart compiler does it, as I know.
You can import/export to Google Authenticator only and you must have two phones. You cannot backup QR codes because screenshot is forbidden for security reason. You cannot migrate to another application.
> It doesn't support map/tables/dictionaries. This is actually huge. It's actually easy to implement. Just define custom scalar type: scalar JSON type MyObject { myField: JSON }…