In India Flutter is quite popular. But I also doubt there will be professional 1M flutter devs our there. However if we include students and hobbyists, then definitely there could be a 1M Flutter devs out there.
A lot of people here are comparing Flutter with programming languages like Python, PHP, etc. It shows how under appreciated UI development is and the amount of complexity UI developers need to handle. Also UI framework developers are always at the mercy of someone else when it comes to their destiny, unlike programming language creators which "almost" control it fully. Apple, Google, MS all keep changing their OS and browser behaviours all the time and cross platform devs need to adapt to those things continuously.
My experience has been exactly opposite. Ability to do Vacuums is good. MySQL doesn’t free up space taken by deleted rows. The only option to free up the space is to mysqldump the db and load it again. Not practical in most of the situations.
VACUUM rarely reclaims space from the OS’ perspective, if that’s what you meant. It can in certain circumstances, but they’re rare. VACUUM FULL is the equivalent to OPTIMIZE TABLE – both lock the table to do a full rewrite, and optimally binpack it to the extent that is posssible.
EDIT: my mistake, OPTIMIZE TABLE is an online DDL. I’ve been burned in the past from foreign key constraint metadata locks essentially turning it into a blocking operation.
That helps a lot thanks. Will summarize it quickly for those who come later: MySQL (InnoDB really) and Postgres both use MVCC, so they write a new row on update. InnoDB however also additionally writes a record marking the old row for deletion.
To do a cleanup, InnoDB uses the records it kept to delete old data, while Postgres must do a scan. So InnoDB pays a record-keeping price as part of the update that makes it easier to clear data, while Postgres decides to pay this price of occasional scanning.
I don't know how VACUUM works, I couldn't tell you about the differences.
The OPTIMIZE works almost exclusively with online DDL statements. There's only a brief table lock held during table metadata operations, but I haven't found that to be a problem in practice. (https://dev.mysql.com/doc/refman/8.4/en/optimize-table.html#...)
Does is support any kind of caching for server side rendering? Without caching running JS framework based SSR is slow and hard to scale in my experience.
Other than this. We don't like to use cache, because a framework needing cache is a sign of a patch to cover a problem. We are fast by nature, we invite you to try it and you will see that the server takes 4-5ms to render.
However, an important part for the 1.0 routing is to do a lot of optimizations that we already have in mind.
Currently Brisa on version 0.1 does not provide caching for SSR. Would you be able to provide an example of what are you looking to have as cache? We will be looking at optimisations for the v1. Thanks for the feedback!
Basically I would like to cache the server rendered pages for not logged in users. When you have thousands of active users such kind of cache helps a lot. Though this can be solved by SSG if the framework supports it.
This is one thing I like about Go. Backwards compatibility. It’s same for Java also except when Oracle got greedy and removed JAXB and related stuff in JDK 9 in the hope of selling those long term support contracts!
Battery as Service - to Quote the article - With the launch of the Windsor EV, MG has also introduced a Battery-as-a-Service (BaaS) ownership rental program. Through this, this electric crossover will become more accessible and customers will only pay for its usage as the upfront cost eliminates here. The Windsor EV will be available at Rs 3.5 per km (approx. 4 cents per km), which is 40 percent of the fuel costs of an ICE.
I studied astrology independently for 3-4 years and concluded that while it can lead to astonishingly accurate predictions at times, the current literature is far from reliable or accurate. It needs to be studied scientifically to gain credibility. Currently, conclusions are often drawn from small sample sizes (sometimes just 1-2 charts), and it’s presented more as an art than a science.
I was drawn to astrology because, in India, it’s deeply embedded in the culture. Personal predictions and predictions about my family members that came true piqued my interest. For example, an astrologer told my father when I was in 10th grade that I would never complete my graduation, which was revealed to me only after I dropped out of college. Despite being a top student with scholarships, this prediction came true, sparking my curiosity.
There are many similar stories, particularly related to Agastya Nadi Jyotish. For instance, in my Agastya Nadi prediction, 10-12 sentences described my wife. Individually, each sentence was generic, like "she will be a middle child" or "she will not be tall," but the probability of all being correct is quite low. Except for one detail (she was predicted to have a master’s degree, but she only has a bachelor’s), all were accurate. Such experiences can lead one to believe in astrology.
However, I’ve also noticed that people who believe in astrology tend to remember the accurate predictions and forget or dismiss the inaccurate ones. For example, many people for whom I’ve done chart readings (as a hobbyist, for free) often recall the predictions that came true when they meet me after many years.
Paytm: Here the issue was that they were not meeting RBI (Reserve Bank of India) compliance for their banking license. So RBI revoked their banking license which prohibits them to process UPI transactions by themselves. So this causes a massive exodus of UPI users from PayTM app. Later PayTM partnered with some other bank and resumed those services again.
reply