|
I'm sure in the video they put one in the car, I mean if your within 100ft of your car, surely you'd be able to see it?
|
|
|
|
|
Vertically?
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
If you live in Manchester then you'd know if it was above you as you'd be dry.
|
|
|
|
|
We use that as a test for "being indoors" in Wales.
Or at least "dryer"...
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Mycroft Holmes wrote: I could easily keep track of the wife
Just give her an iPhone, and you can track her - Built-in feature.
|
|
|
|
|
She got an iPad mini, hated it so iAnything is no longer an option. All this without me having to do anything more than show her some stuff on my samsung tablet
I don't want to know the details of the tracking capabilities of my phone, I like having a smart phone I really don't want to have to drown it!
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Hmmm interesting... Can it find my money too?
... such stuff as dreams are made on
|
|
|
|
|
@Marc-Cliftonn
From your recent posts about the juniors who are using F# for some kind of driver interaction (but wanted to use Python), I realized that you are lucky that they didn't use this[^]
Maybe I should tell them about that project 😈
What do you get when you cross a joke with a rhetorical question?
The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism.
Do questions with multiple question marks annoy you???
|
|
|
|
|
Python integrated with .NET, natively, ages ago. By natively, I mean no third party software needed.
Do what thou wilt shall be the whole of the Law. - Liber AL vel Legis 1:40, Aleister Crowley
|
|
|
|
|
Message Closed
modified 25-Aug-16 11:01am.
|
|
|
|
|
Message Removed
modified 25-Aug-16 11:01am.
|
|
|
|
|
Message Removed
modified 25-Aug-16 11:01am.
|
|
|
|
|
|
It does! I like the tuple return and deconstruction (although I have been using Python quite a bit recently).
What do you get when you cross a joke with a rhetorical question?
The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism.
Do questions with multiple question marks annoy you???
|
|
|
|
|
Yeah... better tuple comes to C# 7!
|
|
|
|
|
Can't wait to have to maintain poorly written code that misuses all these shiny new "features". Fun times ahead of us all!
“Thinking is the hardest work there is …”
modified 21-Nov-20 21:01pm.
|
|
|
|
|
Don't worry, one can already find poorly written aync, lambda and LINQ code today!
|
|
|
|
|
You can go even further back than that. I still regularly see var abuse.
|
|
|
|
|
There is no such thing as "var abuse".
|
|
|
|
|
I understand your pain!
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X
If you think 'goto' is evil, try writing an Assembly program without JMP. -- TNCaver
When I was six, there were no ones and zeroes - only zeroes. And not all of them worked. -- Ravi Bhavnani
|
|
|
|
|
Initial gut call reactions...
The current out syntax is klunky, but hiding variable declarations like that is even worse.
The out * for "I don't care" is worrying since it will encourage bad behavior by people who're lazy/don't understand what they're doing. Yeah ignoring return variables is a problem now; but I don't think encouraging it is a good idea in the general case. It might make some things like the cluster elephants that are MS Office COM wrappers less painful to use; but the core problem is that the API is a cluster elephant not the language syntax around calling it.
Type pattern matching, the initial trivial cases are rather pointless IMO (and whoever decided it was OK to combine an if and then on a single line should be force fed his keyboard); but making switches easier to use and more flexible is cool.
The new tuple return feature looks awesome.
Deconstructing it into separate variables when there's no innate reason to keep them bound after the call (eg returning a computation result and any errors/warnings reported by the computation) means I can have my cake and eat it too.
I'm not so sure about general type deconstruction. On the one hand it's just syntactic sugar, on the other my gut reaction is that it could probably be abused horribly somehow.
Wild cards in tuple deconstruction trigger the same mixed reaction as with wildcard out parameters and deconstructing normal objects.
Local functions. I missed these many years ago when transitioning from Pascal to C++; now I feel like they're just adding an extra layer of code hiding to no real gain.
Allowing _'s in numerical literals to improve readability. Looks like a nice minor usability gain with no real downside.
Ref returns are probably a good idea overall; but requiring devs who've never had to think in terms of pointer-fun to deal with stuff like this might cause confusion.
Generalized async types. Sounds like a good idea, but since I haven't done any greenfield dev with an opportunity to experiment with async I don't feel comfortable making a judgement call here.
More expression bodies takes the fugliest thing in C#6 and smears it over more of the language like a roomba confronted by a fresh turd[^]. (I was tempted to post my giant vomit meta spewly here.)
Throw expression bodies. Well they're getting close, they need to add throw up and they'll have it nailed. Once again
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
I'm not sure I share your disdain for expression bodies. Used with discipline and restraint, I think they can provide a welcom compression of otherwise wasted space (thus improving readability). I site this source as an example of what I consider appropriate usage.
Can you point to some examples of egregious usages?
|
|
|
|
|
I could start with the first 3 examples in your link (and presumably the rest but I didn't bother to keep reading). They were hideous the first time I saw them and haven't improved with age.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
That's interesting. From my perspective, in those examples I see the "old way" kind of like an old man with a wise brow and pulseless heart, waging all things in the balance of reason, whereas the "new way" seems more like a beautiful maiden, full of fire, with a burning heart and flaming soul.
But perhaps that's just the Topelius in me.
|
|
|
|
|
THWAPP
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|