Diclo. is an unimaginable useful drug. It has some properties that make it almost irreplaceable for certain types of pain that are broadly experienced in the population.
Rheumatic pain is usually hard to treat and many patients end up with a whole mix of pain drugs and many many times diclo makes the whole mix work.
You have every right to profit according to German law. You have to be compensated appropriately for your employer to be allowed to use what you hold the copyright for. Usually this is ensured by your monthly salary. However, if what you did and hold the copyright for becomes a surprise success you have to be compensated appropriately in addition to your salary. In practical terms, if your code makes a billion bucks and you only get a regular average salary you could sue the employer and would probably win.
Couldn’t this be solved easier by using a simple version field? If the remote version != client version then request is rejected with an http 409 response...
Purely due to aesthetic reasons. I am not using the terminal for any complex stuff and this allows me to use the terminal which looks the best to my eyes. If my requirements change I may go back to iTerm but for now: something simple and nice looking is okay.
I am using Hyper 2 since the beta and I really like it. It has replaced iTerm for me. Performance may still be an issue for some people. For example, printing to stdout seems slower on Hyper than on, let's say iTerm. To me it is noticeable but still feels nearly instant.
I always wonder if slowing down the phone is a good solution. By slowing down the CPU the CPU needs less energy. But at the same time the user has to wait much longer in order to finish what he was trying to do. Thus the screen is on for a longer period of time. Isn't the screen one of the main energy consumers in an iPhone?
Launching apps on my iPhone 6 (which needs a new battery) takes for ages (even when compared to my older but less used iPhone 5S). I can't imagine that the extended "screen lit"-time does not have a big impact as well.
Also: I am one of the few users who would be totally fine with the iPhone shutting down at 20% or so (if I have the full performance as I used to) because my iPhone is rarely going near 20%. At work I can charge. At home I can charge. When I am on the go I usually am not using the phone that much... However playing hearthstone when I am in bed, loading the phone, everything takes much longer as well which makes playing games less fun...
Couldn't Apple fix this by only using data from 100% successful unlock attempts, meaning: If you unlock your phone without having to enter your passcode the data is used to train the model. If you had to enter the passcode - for any reason - the data is not used to train the model.
This would certainly make some edge cases (for example if you didn't use your phone for a while => changed facial features) less "magic" because you would always have to enter the passcode - but a simple "retrain" should then solve the problem... am I correct?
It makes it easier for Apple and others to adopt swift on a large scale. It will probably mean new swift only frameworks will be developed by Apple after swift 5.
In mid April I will move to a 200sq ft apartment. Very small. I am a bit anxious if my plans work out. Up until now I had about 3.5x that space for me alone. The apartment ist directly at the central station of the city which allows me to get to work super fast and the central station is not too far away from the inner city... walking distance. Let's see how this goes.
Collisions are very very rare. In over 10 years of Objective-C development I have maybe seen it once. Also: clang got much better at detecting collisions at compile time (where possible).
That said: Swift extensions are safer because private categories cannot collide.
Rheumatic pain is usually hard to treat and many patients end up with a whole mix of pain drugs and many many times diclo makes the whole mix work.