And the so called 'male-chosen' professions generally have higher risk of serious health consequences, injuries or death.

It's true that men tend to hold more of the physically dangerous professions, but the ones well known for being high paying, like software engineering or finance, generally don't fit that model.

If we talk about gender equality why take into consideration only part of the picture not a whole? Is it fair?

I thought I was kind of "unlucky" to have a guy swing at me in the first place ... lucky that I'd had some kind of preparation at all!

I'm a wuss I should never have been doing security ever ...

"But if this is the case you should not trust any website with your password anwhere ever".

That is why you should use unique password for each site.

Yes, with unique passwords for each services, you narrow the attack surface to compromise other accounts. But you still have to trust the operator to store and process this one - unique - password on this one service/website. It does not make any difference for the argument, if one or many accounts are potentially compromised. And you have to trust your password-manager software, since it is next to impossible to remember all the different passwords for all the different services you use.

This is absurd and impossible to remember, you should instead have at least 3 levels of password strenght, one high strenght for base services that are used to retrieve other accounts like facebook and e-mail, other for important services, and another for crap.

You're not expected to remember them all, you're expected to either wrote them down or use a password manager. That way you only really need to remember one very strong password.

Except that my 3 level system failed ages ago. Originally I had one, then with more sites coming - several with bogus or recless implementation - it was extended to the aforementioned 3 tier one just to get f*cked up by 'knowing it better' god complex but stupid enforcers requesting or forbidding (!! how stupid is that!) characters. Not to mention leaks forcing me to introduce new ones, having eventually 5 layers with variations on each level because of the highly arbitrary rules of enforcers blocking my well thought of secure passwords.

All led to the situation that I have an encoded file on my computer with passwords (most just referrals/reminders/instructions not the actual password characters).

How stupid is that! Writing down passwords!

Even into secured files, still, increased level of risk. A method with doubtful protection when someone is targeted for his/her secrets personally. Stupid but that is reality. Made necessary by recless developers.

The whole password infrastructure is dead as means of protection. It does not work against serious attackers, only agains random wanderers. And more and more against rightful users!

And the most was done to ruin it by those enforced the users to solve the problem on the user side that in fact lying in the system side.

Passwords will not fullfill their task if: - allowing parties without permission to enter - locking out righful parties Very strict enforcers corrupt the system through the second point. Narrowmindedly focusing on not letting in unwanted elements cause the whole system to case working as intended, locking out and disallowing users to use it, defying the very purpose of existence.

Encouraging users not to use passwords that ever used by someone is just an extremely very radical level of enforcing and again trying to make users fix the inadequacy of the system developers.....

This is not solving systematic problems just conserving a bad habit plus making a bad situation even worse.

Use a password manager. It's so ridiculously easy to setup and makes it so much easier to log into sites.

This is quite old and probably been posted here: http://yosefk.com/blog/my-history-with-forth-stack-machines....

But this in my opinion explains well both why people are seduced by forth and why forth is not widely used.

EDIT: also gives opinion why Chuck Moore can be successful using forth.

Text-to-speech in kindle was really nice feature in my opinion.

I doubt it's a solenoid. Solenoid can be used for galvanic separation in AC circuits not DC. Maybe you mean relay?

It is a Solenoid, it's exactly what I have: http://theroadchoseme.com/diy-jeep-wrangler-jk-isolated-dual...

Could you explain why? I have quite a bit of experience with Z80 and x86 (16bit) assembly. I remember that I've tried to learn 6502 many years ago but lost interest after a while. I remember that 6502 didn't feel superior to me then, quite opposite.

It's extremely simple. It's too simple for modern use, given that it doesn't have 16 or 32 bit instructions and lack mul/div etc., and doesn't have a decent sized stack, but for a small system like the C64 the simplicity was great - it was easy to learn, and for things like demo programming it's easy enough that you can quickly learn to remember how many cycles each instruction + addressing mode takes.

And the name is already taken: https://en.wikipedia.org/wiki/Inferno_(operating_system)

React was also taken before Facebook used it. It's not an issue in my eyes. Inferno was used to emphasise performance and power.

Newsletter is not connecting your subscribers together - add that and you have good old mailing list. One of my friends created such a mailing list for our circle of friends some time ago but it didn't win with the Facebook.

But they did not use any backdoor. Etchalon is right - if they had to access file system how should they do that if it was encrypted? And you were in control of the situation - next time change the password to temporary one before handing it over. And if you are really paranoid decrypt and encrypt the drive afterwards to have new encryption keys ;-)

EDIT: spelling.