The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
I sure prefer the ISO 8601 date format (reason 1: sorts correctly, reason 2: is not confused with hh:mm:ss, reason 3: is not confused with other date formats) - but I never saw it as having antyning to do with the meter. Time isn't measured in meters.
Sure, you do not measure beer in meters either, but 1 cubic meter of beer is 2000 half liters, so there is a connection. (And then you of course have derived units like square liter - the amount of floor space covered when you tip over two full half-liter glasses of beer.)
Sure, 8601 first became popular in countries also using metric units, but that doesn't imply that everything we do is 'metric'.
Fifty is "half threescore" ("halvtreds"), sixty is "threescore" (treds) etc.
See what comes of going metric! In the USA, half three-score is only thirty. I guess we've some catching up to do.
Consider yourself lucky you're not French - they only managed to figure out up to sixty, then they went to sixty-ten instead of seventy (&etc.). Actually, upon consideration, it explains a lot about how they do things.
The logic behind "half threescore" etc. is that it is halfway from twoscore to threescore.
Even though Norwegian doesn't count by scores(*), for small numbers we use a similar logic: One and half is frequently referred to as "halvannen", i.e. "halfway to the second". Somewhat depending on dialect, "halvtredje", "halfway to the third" or even "halvfjerde", "halfway to the fourth", can be heard, although only "halvannen" is the only one active used in all Norwegian dialects.
(*) Score, or Norwegian "snes", is somewhat archaic, but for some reason eggs may still be counted by scores. I have asked a number of young people whether they still know/use the term "snes", and half of them say "som ett snes egg, mener du?" ("like in a score of eggs, you mean?"). But then, several of the younger ones know the term, but believe it is another word for dozen.
Working from home, at times when I wake up late, I would need to communicate to everyone that I'll be logging in late. But when I open the messenger & look to convey, addressing my boss, I see 3 people from my own team have already posted the same, conveying it to me. (On the same public channel) WTH!
My boss being a 'legacy' one quickly concludes things are going totally out of control. Rather than wondering at this miraculous co-incidence of 4 people running late at the same time from the same team.
I'd be left with no option but to be late without any hints & sneak into work later lol.
Starting to think people post kid pics in their profiles because that was the last time they were cute - Jeremy.
In this high tech world, might I suggest an alarm clock?
No you may not. I have despised alarm clocks since I was in my early teens and had to wake up at 5:00 a.m. Sunday mornings to deliver newspapers. The wonderful thing about flex-time is that if I need to sleep in another 15 minutes or so, I just do it. I'm usually in the office by 7:00 or so anyway.
Of course some of that is due to my greyhound[^], who likes to be fed promptly at 6:00 a.m.
I have had 'legacy' bosses that would have had more of a reaction than you could ever dream of for this. They probably would have had you waiting outside in full battle gear within five minutes, then tell you to turn right and keep walking straight ahead until you reach the starting point again. Time: 4 hours max, so keep moving, ladies.
So we got an call from a client complaining that he couldn't open a CSV file we generated.
Excel gave the error that the file format was incorrect for the SYLK file type.
Apparently, Excel treats a file as SYLK (whatever that is) when it starts with "ID": "SYLK: File format is not valid" error message when you open file[^]
We changed the column from "ID" to "Id" and all works as expected.
First you get a message telling you that the file format and extension do not match; the file is corrupt or unsafe; don't open it unless you trust the source.
When you click "Yes" to open it anyway, you get another message telling you that Excel decided it was an SYLK file, but couldn't load it; either the file has errors, or it's not an SLYK file; click "OK" to try opening it in a different format.
When you click "OK" in that message, the file opens as expected.
Interestingly, if you save the file from Excel, you don't get any warnings, and it doesn't insert the apostrophe listed in the "Workaround" section from that KB article. Probably because that would break the file for applications which don't try to second-guess the file type based on the content.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
The wheels are loose everywhere today and the things we took for granted are no longer.
Those kids with the far away look in their eyes are now at the controls. There is no other way to explain what we are seeing today in terms of things that should never be in software.
I was working on a PIC project, I had a '.s' extension on an assembler source file, and it would fail to build, after much ado (me beating my head against a wall) I changed it to '.S' and it worked like a champ, aaarrrggg!!!
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
I have a MacMini. I've developed native iOS apps.
I have developed numerous native Android apps.
Figured I'd give Xamarin a try.
I have Visual Studio 2017.
Couple of weeks ago I tried to connect to my Mac via the "helpful" Studio agent.
Nope. Doesn't work. I can ssh to my Mac so all is supposed to work.
The (stupid, stupid, stupid) answer is that you have to install Studio on the Mac too.
So I installed it.
The installation is so stupid, it asks you to provide your password numerous times so you have to babysit it.
It worked and now I can connect -- except, wait for it...that causes another problem.
When I build my iOS app on Studio on my Win10 box I get the error:
The root assembly CrossOS.iOS.exe conflicts with another assembly CrossOS.iOS.exe
It's so stupid.
I look it up and it seems that the answer is that I need to uninstall Visual Studio from the Mac and install Xamarin Studio which is almost the same thing, but I guess not.
Why would Microsoft not give a warning about this? Why not provide a little guidance before I do all this?
It's Obvious No One Is Doing This
Why haven't more people experienced this? Because no one really cares about Microsoft and/or Xamarin.
There are like 4 of us out here trying this.
EDIT (Subtitle - The Reason I Rant)
Well, I decided to try one more thing right after I posted this.
I went back to Studio 2017 on my Win10 box and created a new project that targeted Windows Creator edition and this time it built perfectly.
I then pressed the run button on Visual Studio on my Win10 box and it deployed it to my MacMini and ran the app on the iOS emulator running on the Mac.
I can't believe it.
Lotsa magic in there though.
I'm sure my rant is what made it work.
I was doing it at my previous work.
Every now and then Xamarin will have build issues and it was particularly painful with the Mac. Frankly I suspect it's the Max development constraints at work here, not Xamarin which is the issue.
But most of the time it worked out well. Particularly when you consider what you are doing (multi target phone OSes)
Particularly when you consider what you are doing (multi target phone OSes)
I do agree with that. It is amazing that they have gotten all this to work at all.
It's just annoying when things partially and/or intermittently work.
And, I must admit it was very cool to get that default app running on all three platforms (win10, ios, android).
Wow. Once it works (if it does) it almost makes you forget the pain. Almost.
Because no one really cares about Microsoft and/or Xamarin.
Thats true, kindof. Why invest time in something that they are going to drop again? By the time they get the problems sorted out, they already plan to get rid of it. I think it's easier to get rid of them.