Google one isn't a consumer product, just a payment plan, so it seems unlikely that the support is only for "google one". Google Drive is still Google Drive, not Google One.
A Job's Guarantee is a real movement, and a reasonable idea for this reason. Not having a job puts you in a lower social caste - might as well have them doing SOMETHING. Even if it's not especially productive, the small positive affect is better than nothing.
No. Eight hours of soul-crushing boredom every day keeps people in such jobs from doing... anything they want. Like learning stuff that might help them contribute to society in other ways (in a more useful job, maybe).
> Not having a job puts you in a lower social caste
This is a stupid societal expectation that should be fought rather than supported in the way you say.
> It leaves people lots of time to think of better jobs to get.
Thinking is a useful skill if and only if the job they aspire to is philosopher. For everything else (and for philosophers as well, really) you need training, and for that you need time.
On a 8% average, Bezos makes over $8 billion a year (He has been making more than that). Considering there are 2,208 billionaires according to Forbe's, that is mind blowing that he gains more wealth every year than all but about 2000 people alive HAVE.
I suspect that many more employees at Twitter have access to the logs, than have access to a super computer and pasword hashes.
I know I wouldn't trust my password with the number of people that have easy access to logs at other large(ish) tech companies.
I really can't imagine why "we didn't have to" was included in that tweet, at all. What other flaps like this have occurred that exposed my creds or personal data to large numbers of employees, that they didn't have and didn't choose to tell us about?
More employees at virtually every major web company have access to instances (and thus instance memory) than have access to supercomputer clusters, too. Every mainstream popular web application is fed a constant high-volume feed of plaintext passwords, right there in memory (or, in typical TLS termination environments, on the wire) to be read by a persistent attacker.
That's true for nearly every single internet facing service, no? A compromise resulting in point-in-time access to traffic is a bit different than a bug that creates a persisted historical record of every single user who signed in for a period.
Maybe I miss the point behind this comparison? I guess I'd understand more if I thought the number of folks with node access and log access were in the same magnitude at Twitter, or if the TLS stack persisted data over time.
> Last year a contractor deleted the president’s account.
The fact that they undeleted it is strong evidence that he didn't have discretion in how he performed his job, and thus was actually an employee and not a contractor.
Indeed. I deleted my Twitter account recently, there was a message that data is retained for 30 days to facilitate un-deletion. I assume their internal process is the same.
Just use a programmer's calculator or a software calculator (e.g. bc on Unix, RealCalc on Android) for the hex math (and for math in other number bases and conversions between bases too). Or even write one of your own as an exercise and then use it.
Do you even do any of the hex math when writing actual code in assembly?
I understand when you use something along the lines of a disassembler that requires you to actually see the addresses of the values. But even these are sophisticated enough to give you symbolic values instead.
A lot of my hobby programs are emulators or parsers for old file formats (think DOS-era games). Bitfields become important, and they're more convenient to express in hex than in decimal.
There are times where it feels convenient to express things in decimal and times where it seems better to use hex.
>Do you even do any of the hex math when writing actual code in assembly?
There are multiple reasons why it is useful or convenient to deal with data (whether memory addresses, data values, colors, etc.) in hex (including doing math on such hex values).
As I said in another comment in this thread, I have not done a lot of work in assembly language; but have done enough and read enough about it to know that it is useful, and not just a cool or retro thing that developers do.
The fact that two hex digits compactly represent a byte, the fact that one hex digit can represent a nibble/nybble [1], the fact that machine registers on devices attached to computers (such as printers, scanners, any other electro-mechanical equipment with a computer interface) are used to programmatically read and write data to and from those devices, and thereby get their status and manipulate and control them, are some of the reasons why hex and hex math and bit-twiddling in hex and binary is useful and still done.
Depends on what kind of applications you write in assembly (or even C), I guess.
When the choice is to commit crimes or live in hellish poverty, the choice becomes easier. Going to prison just means you get free food and board for a while. Sure, it's awful. But your only shot getting a better life is crime....
Thanks for this, I'll have to take a look at FastText. I've been using word2vec before turning it into a matrix and running it through a CNN. I based it off of Yoon Kim's[0] work. I haven't had much luck though on my 92-class problem. Maybe Fast Text will work better, although I think there are a lot of improvements my model can have still.
