116 karma · joined May 10, 2015
This deliver a poor experience when implementing History API compare to Safari and Google on iOS that work as expected.
“This product can expose you to chemicals including Nickel (Metallic), which is known to the State of California to cause cancer, and Bisphenol A (BPA), which is known to the State of California to cause birth defects or other reproductive harm. For more information go to www.P65Warnings.ca.gov“
https://inclusive-components.design/
IE11 is meant for supporting legacy sites and Microsoft doesn’t recommend consumers to use it. It make sense to work on Grid and Flexbox for new sites.
Now I would rather wait for V language which seem to solve many limitations found in other languages.
What are the amazing option do you suggests with batteries include in the language would be ideal.
I wonder which part is performance unmatched?
My opinion would be Crystal language for its simplicity and higher throughput but unmatched performance is behind Rust and C.
https://www.litespeedtech.com/products/litespeed-web-server/...
The article is translated from Japanese, not from Chinese since Qiita is for the Japanese community.
It has a JSON pull parser to minimize memory usage which is useful for memory constraint environment but at the expense of less performant. If that could be split up with fork Crystal processes, I believe it's feasible.
You knew each languages solve different problems in AI or space age.
There is even a issue reques to bring HTTP/2 feature implement in HTTP/1 for better performance.
In fact, Metal is powered in all iOS SDK too.