- Even if it's JS, just-js make almost no use of dynamic memory allocations.
- The authors rewrote himself a postgresql driver that support batching request.
- it wraps high performance c++ libraries
Even if the techempower implementation is far more verbose and complex than mainstream JS framework, the amount of work behind just-js and its preformances are just impressive!
I don't understand why when you say "I have covid" people want the proof that you have it and ask you "did you do the test ?".
I personally think I got it twice and never did any test. Just had symptoms I never had before in the 2 waves we had in france, just after meeting persons who also got seek at the same time. This is enough coincidence for me to think I have covid.
I also think that this reasoning may be more accurate that the official not very accurate covid tests.
Doing this reasoning myself also saved me money and the 4h waiting queue to do the test (the last thing I want to do when I have fever).
On the other side, I know people who had symptoms, tested negative (and trusted the test) and still when out to meet (and maybe contaminate) friends or colleagues.
There has been 25 documented cases of COVID reinfection worldwide, so assuming you had it without actually doing tests is likely false. There are many diseases with similar symptoms in the upper respiratory system, and given no more than 25 people on earth have confirmed having it twice, unless you have positive tests Occam’s razor suggests otherwise.
or just run npm test / make test locally without setting up anything. But I feel like writting the tests takes usually more time than setting up CI/CD.
Very interesting, I really think that http APIs are just a user management layer that could be easily abstracted away now that we can do so many things client-side.
How do you handle permissions ? or how do you pervent a clients to erase the database ?
We use Postgres Row Level Security to implement the authorization. You can create your own policies from the dashboard too. You can read more about it here: https://supabase.io/blog/2020/08/05/supabase-auth
Projects using templates and heavy metaprogramming often see most of the compile time spent in template instantiation, not in link time. For this kind of projects I think this would help.
Great that C++ compiler teams are working on reducing C++ compile time. The next great feature I think would be a game changer is caching the result of compilation (templates and binary code). A fine grained cache acting at the level of a line (or a function if it's too hard) would save an incredible amount of time to C++ devs, while also simplifying build systems. This would also stop engineers from losing days trying to speedup their build.
Such a compiler exists, it's called zapcc (was a fork of clang 3.something). Sadly it has been abandoned and never merged even though it was opensourced.
We already had function level compilers back in the early days, Energize C++ and VA for C++ v4, but they were too resource hungry for what companies were willing to pay for and they died.
There is an Energize C++ demo floating around on YouTube.
Or 0 per minute and 25,000 per hour for two days a month. Traffic can be bursty; don't assume that X/month means they're getting exactly X/30 per day..
Is there any doc about how this caching is implemented ? I still don't understand why we need to feed this dependency array to have an up to date version of the count variable.
