You either allow a single origin, or allow them all with “*”.
You either allow a single origin, or allow them all with “*”.
Got it, but if you expect people to switch from JS to Rust , you’re going to be disappointed. That’s like asking people who just got their driving license to hop into a fighter jet just because it’s faster. JS is a simple language. Its widespread adoption is not due only to it being ubiquitous, but also because it’s pretty easy to learn. Rust, on the contrary, not so much.
Isn’t DOM manipulation notoriously tedious with WASM? That seems quite a showstopper for most client-side js I’d say.
Exactly, it was pretty useful until ~2015 imho. Then JS got better, and coffeescript did not follow these evolutions.
Except that
On a side note, while Safari is not Chrome, Chrome’s rendering engine is a fork of Webkit, the one inside Safari.
The best tool is the one you have and are familiar with. That being said, it also depends on the task at hand. There’s no silver bullet, and anyone telling you this or that language is THE best without context is a fool.
That’s from Curb Your Enthusiasm I suppose.
You mean coreJS, not standard JS, right? But yes, it’s a sad story.
Useful tool that helped more than once finding the performance bottlenecks in my code.