Python console progressbar "???"

1%^M142/6456


Hence, 142 / 6456 < 0.02.

Good old Python (???) progressbar .. broke the mold, eh? Don't want to know ;)

No swap on AWS

Using Linux on AWS? As of now, there's no swap file then by default coming out of the images.

See the below two links for advices

How can I check if swap is active from the command line?
Why don't EC2 ubuntu images have swap?

A brief highlight roughly from those is this helpful command, to confirm your suspicion:

cat /proc/meminfo | grep -i swap

This will likely provide you with big fat zeroes as below:

SwapCached: 0 kB
SwapTotal: 0 kB
SwapFree: 0 kB

How cool is that (without a warning at the very least)...

Watch out when doing memory intensive processing (which is a less than good sign :) but happens), for any reason.

Love hate / Ubuntu & Android

When having to transfer files like

mkdir FromPhone/DCIM; sudo mv /media/motog/Internal\ shared\ storage/DCIM/Camera FromPhone/DCIM/

After apt installing this'n'that and mounting with
sudo jmtpfs /media/motog/

Hm... not feeling like a plug & play Windows user that much anymore :)

Too bad I'll never remember/work out in retrospect if it's just my faulty ("universal") laptop charger transferring a noise that normally makes my touchscreen crazy - and yes, it may have failed file transfers too - which was playing tricks with me.

Because anyhow, it just works now.

Empty sets, really?

There is just absolutely no point in empty sets.

Sorry.

Some things I like about >>>this

Beginner's Python stuff it may be, still there are some very important concepts wrapped in this ...

>>> import this
The Zen of Python, by Tim Peters
Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!

(... and some things I'd be too happy to debate or discuss, such as "hard to explain" is very subjective - a picture sometimes speaks a thousand words, and what if it's a sound, sculpture; prior education, a shared interest to come at help, you name it, rules are not really rules, but guidelines for the here, now and us, but let's not get lost in the details, rather get things right ... good thing.)

The irony ("life always finds a way")

Fixding. So typocal :) Though I guess it's just appreciable self-irony.

Anyway, you can't escape fate - "if they cut off one head, two more shall take it's place".

Out of memory again? Cut me some ...

The recent purchase of a new 5 yo laptop has made things fluent again work-wise.

But then, when getting to do some feasibly picked exploratory data processing, R started running out of memory, seemed unreasonable at first.

The bad boy seems to be the Slack client version installed via the Ubuntu Aptitude. There's an interesting-looking article (which I am yet to read in its full glory) about some likely difficulties faced when relying on web UI's on the desktop, saying:

Work is underway to fix the underlying factors affecting client memory consumption, but in the meantime we’ve built a tiny new Slack client to help address this issue.

... which is still giving me some daunting moments when installing the old client.

However, I am already on 6.2.3, the latest Ubuntu 64-bit beta version :S and the change log does mention some mem. footprint improvements. Hopefully those "tiny client" improvements weren't those and are to come soon ...