If it's for the future, why not use something even newer than Deno, because clearly newer === better?
But on a more serious note, what could they possibly stand to gain to use Deno instead of NodeJS at this point? The languages are mostly the same, the tooling slightly different. Sounds like it'd add a lot of changes just for the sake of changing things. Not to mention newer stuff usually are less tested and higher chance of not working.
Speaking about newer, has Deno received any sort of security audits? Tauri is pretty focused on security, so one could assume that'd be a requirement before even considering Deno.
My guess is that there's only so much change you can foist on people at once. If the point of Tauri is that JavaScript devs can leverage their existing knowledge and skills then meeting them where they (or most of them) are seems like a reasonable strategy.
Which you don't even have to use. I don't. I just use `cargo build` and `cargo build --release` which works exactly the same way as the CLI. Add `entr` and you get the "live-reload" feature for free too.
I really liked reading this. I never used TenFourFox (no Mac user at all) but occasionally came across its blog posts because it is in the planet.mozilla.org RSS feed.
I really liked how the motivation and problems for a (hobbyist) OSS project of this scale are written out.
This made it an interesting read for me - I'd say for actually almost anybody somewhat related to unpaid FOSS.
On a second note it is a shame that there are no harder governmental restrictions that hardware has to be supported by its software for a certain time. So much (forced!) waste on resources because the manufacturer wants to sell its next-generation... There are a lot of phones - still good enough hardware - but you cannot get updates for it after 3 years...
The complement book "Started with MicroPython" at https://www.raspberrypi.org/products/micropython-pico/ looks like a nice present for kids. Would be great if it was available in other languages (for example, german).
Anybody knows if translations of the book are planned?
It crashes sometimes (about twice a week for me), but it's Preview Nightly what I use. I would suggest you uninstall and reinstall (from Google Play). Maybe it helps.
A site of mine is also hosted as their PAAS at Luxembourg, but was luckily not effected. Probably my site was on another storage unit ("on one of our ZFS storage units").
PS
I also always thought that the snapshots were backups.
> We have over 250 tests passing, most of which are autogenerated from running the same layout in Chrome. This ensures web-compatibility and overall correctness.
So if it outputs like Chrome, then it is web-compatible? While I understand this from a practical point of view, this is also clearly a result of render engine mono-culture.
Let's see how innovation goes within a 5-10 year time frame if everything is bound to Google Chrome.
Author of stretch here! I would love to add tests for other browsers as well, and it should be pretty easy as we are just relying on webdriver. Targeting chrome was done as a first step as I had previously set up webdriver tests with it so that was just easiest :) The goal is for general web compatibility and not just chrome-compatibility though.
