thanks!
1,286 karma · joined April 11, 2014
Always happy to see comments at b r a m d b + h n @ g m a i l . c o m
thanks!
In its simplest form, it means you can do this:
public property Foo { get; } = 5;
Your class now has a Foo property that nobody can set, not even methods in the class itself, but that can be publicly read.These become a lot more useful with primary constructors (also a new C# 6 feature):
public class MyImmutableClass(int usersFoo) {
public property Foo { get; } = usersFoo;
}
This will create a constructor on the class that takes the usersFoo argument, and immediately assign the value of that argument to your read-only automatic property. It makes immutable classes a lot easier to create, and guarantees that they'll stay immutable.edit: Permit made it clear that primary contructors have been dropped from the C# 6 spec. You'll just have to assign your readonly properties from regular constructors then :)
Internally, .Net automatic properties are compiled with a backing field and a getter and setter method. In the case of a read-only auto property, they will omit the setter, so there is no public artifact that could be abused.
A bit messy, but an overview with code samples can be found at http://msdn.microsoft.com/en-us/magazine/dn683793.aspx
Either way, the proper course of action would be to return it to the store right away, especially when it refuses touch input.
As an aside, my own Surface displayed a very minor issue with the pen tap location being off by about a millimeter at the top edge of the screen when I first got it. Windows Update fixed it right away. It hasn't shown any issues since then, at all. From what I hear from people I know that also own one, this is more typical than situations with serious problems.
At its core, a rocket isn't more complicated than a car. The challenges are just different. My dearest hope is that eventually rocket components will be as commoditized as car parts, so people can build and maintain their own spacecraft. I want to see rockets held together with duck tape and spit, because that's the point where spaceflight is available to everybody and gravity stops becoming a hurdle.
A quick disclaimer: I have the greatest respect for rocket engineers. They are taking the first steps, the most difficult ones, and I don't believe for a second that they their work is easy. I just believe that eventually, they'll become obsolete to the majority of spacetravel :)
It's true that it's easy for people to interject and annoy, and it happens more and more the bigger your celebrity status. However, unlike the interview example, it's also easy to ignore them. Twitter's reply helped a lot for that. Replying to anybody is optional, you don't even have to read their tweets if you don't want to. It's not perfect by any means, I don't think any platform will ever be. But it isn't bad.
In any case, using some form of video calling is too intrusive. I can type this reply, do something else for 10 minutes, then check back. But then I was always one for text mediums rather than video or audio calls :)
And for the record: I don't train myself to limit my thoughts, I train myself to use a form for expressing them appropriate to the medium I'm doing it in. Expressing something shorter and in steps is not inferior to long-winded explanations. If you must blame something for a fine nuance I failed to grasp, blame the fact that English is not my first language. I doubt I would have caught it in Dutch either, but at least that could be a valid reason.
The advantage of developing a thought in tandem with somebody is that the compromise happens more naturally. You rarely need to 'concede' a point or prove somebody wrong, since you can influence the way the point is made in the first place, pointing out flaws in their reasoning or facts as they happen. Conversely, the other can do that for your reasoning. The result is that, rather than adjust your thinking in a few big steps, you adjust it in minor ways with every sentence. It takes time and practice to get used to this, but it can be very productive and enlightening.
On the other hand, I would never avoid long-form debate either. Both have advantages and disadvantages, just as both have mediums where they work and mediums where they don't. Twitter isn't conducive to classical debate, just as hackernews isn't conducive to the iterative thought development style.
Aside: this conversation would have taken a very different form if we had had it on twitter. The medium defines the form. So I don't mind being verbose here :)
(That's exactly 140 characters for you :) )
If you do get roped into a conversation where you need more tweets to explain, here's a few simple guidelines:
- Don't split sentences over tweets. People will only read one part.
- If you really must, use "(cont.)" on both tweets (end of the first and start of the second), so it's obvious there was another part. I know that reduces your character limit, but it's worth it to be less ambiguous
- Make each continued tweet a reply to its predecessor. You can reply to your own tweets. It facilitates following the conversation on most clients.
- If it's more than 2 tweets, consider using twitlonger. In general, that should be a last resort, though.
Without trying to make it sound high-handed, there's something of an art to smooth twitter conversations. Terseness is the key. I find them rewarding because, when done right, they have an enormous density of information in a short time.
You're not using your education to generate data. Most of the data is made by other people's education and then multiplied many times. Even for cases where you do create information, like in your comment, many magnitudes more data was sent over your line to get it before my eyes. If they wanted to tax new information, they wouldn't do it through a flat fee per GB.
Sales tax is a tax on a monetary exchange. You tax the price you pay for your shoes, you don't tax "$3 per shoe". The point of that is taxing value rather than quantity. How you use the tax money it is irrelevant to how you acquire it.
And last but not least: we're already drowning in 'pointless data'. A lot of the internet's capacity is used to transfer scripts and styles rather than real information. Whether you consider that pointless is a different matter, but it's not up to the government to say what you should consider pointless data and what you shouldn't.
While it does have some applications even with that limitation, it's far from a practical hoverboard, and it's very misleading to be talking about other uses of the technology as if it already exists. They seem to be getting ahead of themselves by extolling their "design focus" when they don't have the product people expect from them yet, and possibly (probably) never will.
"Limited in ways that the public doesn't understand" is undoubtedly correct, but I disagree more on the extent. The author seems to think the president has no real control over the policies he sets, at least in some areas. I believe he does have real control, but he is limited by reality being far more complex than in an ideal world.
He has enacted positive policy changes too. He did pull troops out of Iraq, he did bring gay marriage equality forward by decades. Whatever you think of the man, saying he broke all his promises and essentially acted like a tyrant is unfair. The same can be said of Bush and others before them. On a related note, getting reelected isn't a measure of delusion. It depends on a lot of things, such as quality of the opponent, general approval, party approval, desire for stability, etc. People also reelected Bush, who had some of the same policies as Obama, and whose approval rating was even worse.