Actually, having an Aadhar number does not imply that the person is a citizen - this is one of the statements present in the application form itself. So, it is possible for non-citizens to have an Aadhar number.
Collaboration over jupyter notebooks has been available in CoCalc [ https://cocalc.com/ ], formerly the SageMathCloud online notebook, for several years now. I wonder what prompted Google to introduce this.
I guess the promise is (also practically possible) to have electrical _connection_ to all households. It's a different question whether there will be, or can be, steady electricity supply, given how the electricity distribution is currently managed.
Regarding providing free electricity - this can be a good thing as long as the electricity consumption is free up to an amount limited by the size of the house and household. This is very susceptible to abuse.
On one hand there are articles saying young people don't have enough savings, and on the other hand there are these articles ruing that the older generation don't spend more.
Maybe we need to check which kind of industries are sponsoring the respective articles.
I would suggest going for an NUC (at least core i3). These are small, has enough computational power for the tasks you want to do, runs OK with Linux, and can run VM if you want to from time to time. You can likely reuse the SSD from the Thinkpad if it is of the right kind.
Personally, I purchased an NUC with i3 that is only marginally slower than a 2013 Dell XPS 13 with core i7 (noticable only in compile times of software). I used the SSD from the Dell laptop via an adapter, and run Linux on it.
I don't know where they get those statistics? Do they include the daily wage working families? I have several near my own home (in a city) and none of them are able to open bank accounts.
This may have been a good idea, but it is terribly implemented. Especially, notes of denomination 500 should not have been banned with immediate effect.
In general many poor people, even in cities, do not have bank accounts and face lot of issues when opening such accounts. Sometimes bank require a "reference" from an existing customer to open an account. Sometimes many such poor families (say 20 families - think of it as a big landed area with 20 small houses) live together at a single address, paying rent for a single room, and the banks will refuse to open so many accounts under a single address. Their are several such smaller issues that crop up when trying to open an account that are not well known and that only the people in a particular city or locality face.
These people cannot deposit their savings since they don't have a bank account to begin with. And they definitely have savings in Rs 500 denomination since 500 is nowadays often used in the markets. Essentially, this ban has hit hard the common people. The very rich are hiring others to do the transactions and exchange of money. The lower middle class and poorer sections are left wanting for cash. Hence, good idea, but bad implementation.
If I am not mistaken, the chipsets on the Intel NUC models are laptop chipsets. I have the Skylake Core i3 version and that supports up to 32G of LPDDR4 RAM (dual channel). Since the thin laptops typically have only one RAM slot, it makes sense why they are limited to only 16G.
With this in mind, my understanding is that it is perhaps a limitation of the current Intel chips for single RAM slots, combined with the reluctance of the laptop manufacturer to include dual channel memory in their (thin) laptops.
This tool looks interesting from the screenshots in the website. I wonder if some things that diff doesn't do well are handled separately by this tool.
Or, I do not know how to make diff do it well - for example, show added similar "paragraph" in better context. If I have a for loop and add an identical for loop after current one, diff will typically show the new one inserted in between the first part of the existing for loop and the last line of the existing for loop. The perforce diff client seems to get this right and shows the new for loop inserted after the current one.
Aside from that, what I miss in some GUI diff clients is the way vimdiff works. By default, vimdiff collapses the similar areas and shows only the diff parts noncollapsed. This is very useful when I am looking at a diff of a large file and the diff portions are far apart. It helps get a quick overview of the differences in the entire file.
One of the sources of this problem is the relentless experimenting that has been ongoing since about 2007-2008. First, there was pmount and hal introduced to take care this automounting, and as soon as this was in a working state, it got replaced by devicekit. Soon after, devicekit was abandoned in favor of a combination of udev, consolekit, policykit. Then then policykit got replaced by polkit. And then systemd was introduced and consolekit got abandoned. And each time the documentation gets worse (except for systemd, since the authors try to justify their choices).
Overall, it has been a sequence of constant rewriting, and I don't see an end to it. People who have been using rolling distributions like Gentoo and administer their own machines are the most affected. If one is not using the whole systemd to major DE (KDE, Gnome, XFCE, etc) stack, it is arduous to set up a mounting system which always works. Usually, vfat external disks tend to be immediately writable on mount. Move over to exfat, mtp, ext[234], or another other native filesystem and it is an exercise in exasperation to get them to mount as read-write as an unprivileged user, or even mount at all as an unprivileged user (see https://bugzilla.kernel.org/show_bug.cgi?id=15875).
The only decent program that I have found that works quite reliably is udevil.
The only D-Bus tool that is nice in the command line is qdbus, and that stems from Qt. I wonder why the original D-Bus writers could not write a decent enough command line tool for it.
Indeed, printf is shorter. I use it in a similar fashion in my own script [1], which can be made to behave like hr() (haven't tried shells other than bash):
btex - interactively compile LaTeX to PDF or PS or DVI, highlighting warnings and errors ( https://github.com/ppurka/btex )
searchforfile - search for files interactively with results "as-you-type" ( https://github.com/ppurka/searchforfile )
displaymessage - wrapper around a bunch of gui dialogs ( https://github.com/ppurka/displaymessage )
A couple more in my GitHub account.