What are the hot 2016 frameworks for making simple animations for iOS now? I'm quite familar with XCode and SWIFT but I suppose this is not my only choice - Xamarin?

Michael Pauli

Well I think most of the enhancements looks promising - especialy null propagation and primary constructors. Both makes code shorter and more clear. Exception filtering looks kind of short-hand of "if (e is MyException) {...}. Why not remove the break-need in the end of switch-case's. I don't see why break is needed - should break out when the next case begins - or? That is what I can think of.

Michael Pauli

Yaa thanx' that was my conclusion too. Thinking about it it is a little strange that the components inside a normal laptop cant stand the "rain". After all resistors, capasitors etc. are all sealed so what can water possible do to them? If one was folding origami animals I could understand - but the laptop is rock solid to my knowledge - but it stops working after just one trip to the bottom of the pool!

Michael Pauli

Thank you. At first glance both links seems like phones only. No laptops and no lightweight tablets as far as I can see. That makes programming while floating around on my inflateable beach toy or madress both difficult and expensive in case of wetting it. That was what I was mostly getting at in the first place. You have to have a certain technique to get up without splashing water all over the Lenovo keyboard - this is really difficult! I know it sounds a little silly picturing this, but it's a real pain i the butt in a 100 degree fahrenheit environment.

Michael Pauli

Why is it that it is so difficult to get a waterproof tablet/phone that one can use while in the pool? I travel a lot around equator and enjoy being in the pool most of the time working online og talking into the phone. I have washed away 3 cellphones now.

Michael Pauli

Totally agree and totally nice thing to bring your appliance to the restroom and tabbing around the web while emptying yourself. That way both things come together into new a userfriendly experience: press that thing into the bowl while online!

Michael Pauli

Being afraid of SQL is a strange exaggeration in my opinion. The only wierd SQL stuff is all the inner and outer etc. joins. They are hard to understand. I feel better working with smaller blocks of code one selection at a time and the narrowing in of the data set. Linq helps us doing that. And after all developers loves Linq mostly.

Michael Pauli

What about an Al-Queda-version instead?: If security is so insecure to begin with why not remove it all together? Therefore a name should be enough. Also passwords are so difficult to remember - right? On attempts to login on other peoples behalf a finger are chubbed off at the local police station and on following attempts another finger. On the 10'th attempt no more fingers are left and he/she can't login anymore. Set and done! Top security and as a result - over time - no more security are compromised.

Michael Pauli

The 1.5 -> 1 is a little strange. Except for that you can use

double MagicFormula(double x)
{
var d = Math.Log10(x);
var f = Math.Pow(10.0, d);
var res = Math.Round(x / f, 0) * f;
var res2 = Math.Round(res, 0);
return res2;
}

Michael Pauli

What about the hacker then? There must be a constitutional founded legislation enabling even hacker-scumbacks to login now and then. Or otherwise you could just as well disable the checkmark to begin with if the current loged in user has a TRUE marking for Session.User.IsHacker <--- you know that one?

Michael Pauli

...and if I may add: You sellsman. You buy bananas to children. You feed family - yaa? Buy gas to car - yess? Sellsman go sell. Programs good!

Michael Pauli

In stores in my country you often see signs saying: "Discount: Save -25%" and "A discount of -25% are withdrawn at checkout". I always avoid such arithmetic discounts and insist on going for only 100% checkouts when in the grocery store and elsewhere. I feel that 125% is sligthly over the top ;P

Michael Pauli

In my opinion it smells like being in a public restroom in a underground railway station - a harsh, yellow and greasy environment. The only advantage of bacon is that it can transform a piece of non-transparent paper into a transparent one just by rubbing it all over. You just have to rub my meat hard baby! ;P

Michael Pauli

Yaa sure - I agree but some technicians here would like to have this filebased and not put in a database for some more or less obscure reasons. So they get what they want. I have less than a week left on this assignment ... if you get my point ;-) Kind regards,

Michael Pauli

Hi Dave! Thank you for your opinion. I must say I tend to go your way here, but to avoid any problems of a more political nature I go for the file sys. solution. I my career I've never done a thing like that and I find it hard to write - even though it's simplistic by nature. To begin with we go for 500 directories each holding 500 sub dirs. each holding 500 sub dirs. That is 500³ = 125,000,000. I'm having a server for this so it's not on my locale dev. pc. :-) My feeling is that we would be better off having an Oracle db or likewise for it. But the decision is made :-( Thanx' again. Kind regards,

Michael Pauli

Hi Jörgen, I totally agree about your comment, but my customer want to use a filesystem and not a Oracle db etc. I really don't understand why, but it is something about maintenance and backup I'm told. Kind regards,

Michael Pauli

(hope this forum is right then :-) Hi all, I'm about to begin a small project in which I must be able to store and lookup up to 20. mio. files - in the best possible way. Needless to say fast. For this I have been around - http://en.wikipedia.org/wiki/NTFS#Limitations http://www.ntfs.com/ntfs\_vs\_fat.htm And now my question: Dealing with a production load in the area around 60.000 files (=pictures) per day each around 300 kb in size, what would be the best ratio of what number of files in what number of directorys to make the search-time best? Obviously I do not put all the files in one directory, but in a number of dir's. So what would be the best economy for such a thing? Seems to be hard to find information about on the web. Thanx' in advance, Kind regards,

Michael Pauli

I'll move it. Sorry for the inconvenience. Kind regards,

Michael Pauli

Thank you for your answer. Thing is that we must use a file system for it and not a db. Second I'm not sure that a recursive principle would be first thing to go for for us due to the large number of files. Kind regards,

Michael Pauli

Hi, I'm about to begin a small project in which I must be able to store and lookup up to 20. mio. files - in the best possible way. Needless to say fast. For this I have been around - http://en.wikipedia.org/wiki/NTFS#Limitations http://www.ntfs.com/ntfs\_vs\_fat.htm And now my question: Dealing with a production load in the area around 60.000 files (=pictures) per day each around 300 kb in size, what would be the best ratio of what number of files in what number of directorys to make the search-time best? Obviously I do not put all the files in one directory, but in a number of dir's. So what would be the best economy for such a thing? Seems to be hard to find information about on the web. Thanx' in advance, Kind regards,

Michael Pauli