all_these_years
Joined 14 years ago
Joined 14 years ago
$ gem install sha3
$ irb
> require 'sha3'
> s = SHA3::Digest::SHA224.new
> s.update("\x00")
> s.update("\x00" * 4294967295)
[ Segmentation fault... ]
Tested with Ruby 3.1.2Gem's code (including C native extension): https://github.com/johanns/sha3
It looks like the only remaining issue is the licensing model, which would need to consider the legislation on where the software is acquired or executed.
EULAs will probably be rewritten, lawyers will profit.
Anyway, I think that an hourly rate, strangely, has some good things from the employee's point of view, if you have some value to offer and the job market is healthy. You feel that your commitment is to your work, and that to leave is not such a big deal, less attachment to 'the position', more responsibility to your craft.
I can offer my situation as an example: I work as a senior lead dev in Rails in a hourly basis (US East Coast). Interesting job with a lot of autonomy, possibilities to learn (there is a complex mix of technologies here). I know it is not easy to find someone with my skills set and I know they are more than happy with my performance. The job is hourly just because that was the initial deal, a 'contract to hire'.
They've just offered me a fixed salary and benefits, but with a lower pay from what I am doing hourly (even if my hours are cap to 8h/day). You know, business side tries to push down. So I am seriously considering to start sending resumes and just leave if I can't continue hourly, just because of the pay cut.
So I think all depends. Flexibility in the hours, if it's possible, is a good thing, but fixed salary has also some advantages (if the salary is attractive): health insurance, benefits, paid vacations,... and you may get a higher degree of identification with the company.
So again, it all depends.