The benefit of this approach is that the compiler should be able to see more opportunities for optimization and also result in fewer bugs.
1,054 karma · joined September 20, 2012
The benefit of this approach is that the compiler should be able to see more opportunities for optimization and also result in fewer bugs.
As soon as you run into edge-cases with authentication, compression, binary formats etc you'd have to use WCF. I think many use WCF "just in case" they need those features
It's kinda the same thing except telling the compiler what to do you instruct it what's safe to do, and it can make smart decisions from that. If the compiler/environment detects any ambiguity or risk it might even query the programmer to declare his intent
For example: if I'm calling an IO method that returns a value it should be able to figure that out and orchestrate the code to run asynchronously and await for the value when it's referenced. If I have several asynchronous calls methods in a method it should be able to optimize it so they all run in parallel as optimized as possible.
It might need some added declarative syntax on methods but I'd rather prefer that and make the compiler smarter, instead of offloading that complexity on the programmer per default. Sure you should be able to explicitly control asynchronicity if needed but in most cases that doesn't seem optimal nor necessary
Adding async/await all over your code adds to the "crud" that makes code more verbose and harder to read and understand
It would have been better if they kept and maintained a streamlined alternative. Forcing everyone to deal with the complexities of WCF isn't developer friendly.
This is a common anti-pattern in frameworks where they grow until they are a kitchen sink monster instead of splitting of into different frameworks streamlined for different purposes.
I think most people are afraid of the slippery slope and censorship if taken too far. Making Reddit "too political correct" would transform the current culture into something else. Many (or a loud minority) currently doesn't seem to trust Reddit to not do that. What makes things worse is people assume this is a "Monetization of a service"-story they've seen played out many times before with catastrophic results.
In the end I guess it comes down to the execution and agenda.
"I take care of my kids, I take them to school!" he says proudly
"That's what's you suppose to do you dumb M---F!"
What do would you rather use, an UI that's super easy to learn but cumbersome to use, or an UI that required learniing a few basic gestures and then being much more efficient and ergonomic to use?
Also having the same interface for Phone/tablet/desktop is a dangerous idea if pushed to far, jack of all trades, master of none. Of course they should share some common ground but they risk sacrificing an tailored experience for each on the altar of standardization.
They haven't made any greater strides in addressing thumb ergonomics on larger screens. Sure at least the buttons are at the bottom again but to make it truly next generational they should have utilized more gestures.
My guess is they don't dare make Win 10 "too different" for risk alienating developers from other platforms and "mainstream users". That might be the safe choice but it doesn't make for greatness. It feels more like design by committee.
There was certainly room for improvement, the old interface was a little too stark, but they're changing course instead of refining.
I also call bullshit on "people are circles" argument. The "old" metro was more about full bleed pictures which IMO is more timeles, the circles thing is just being influenced by a current design trend and makes WP less unique. Each to their own I guess.
I just say though it's very seldom that a huge class/method is justified. Usually there are plenty self-enclosed logic or reusable methods that can be broken out either to utility libraries or a separate class.
My rule of thumb is that you should be able to look at a method/class and understand what it does, and that diminishes quickly over a certain size.
Sure some logic might be in other classes but that's another layer of abstraction
I think it's a faulty generalization either way, companies should be run by competent passionate people.
Also it seems Apple has missed the mark one some fairly common use cases, like having sleep & don't disturb modes, or being able to dismiss multiple notifications.
I was thinking about watches and realized one mode I'd like is that only show notifications when prompted (like a force push). Then you could make notifications pull rather than push UX wise and don't have to be interrupted. Good for dinners etc
1) It's almost impossible to start charging for something that was free
2) It's almost impossible to go from one time payment to subscription model.
If you want either model you better start out with them or you're going to have a vengeful mob after you. I've seen this repeated time after time with catastrophic results. I was actually surprised that Adobe got away with it.
Having a friend as an anchor and fixed point for discussions and sharing experiences can make it much more rewarding. Unfortunately it's pretty rare to have a friend with as much freedom as oneself at the same point in time.
Also I must say that if you travel and stay for 3+ months in a place you face a different problem: You've gone past some kind of threshold and started to create a new life with friends, favorite places and habits.
Leaving can then feel a little bit like you're leaving shards of yourself behind, and the physical disconnection of all those new relationships can be quite sad too.
* up to a point
I found it a bit rambling without clear premise or pay off. He sounds like someone who talks about programming from the outside while never having been deeply immersed in it himself.
Clarity of writing follows clarity of thought.
One aspect that's really underplayed I think they could go with as a complement is diary and life tracking. It could be very interesting to have as an experience where you could relive where you've been and done.
I think reducing friction and increasing productivity is really important, it's not as sexy as some of these other features but it makes real difference in big projects.
I'm getting a little worried about the async-await and task methodology. It's true that they've made a lot of that kind of programming much much easier, but it also means that orchestration is cluttering our code. It seems that now that we've elevated the level of abstraction it should be possible to get rid of it (more or less) by being more declarative in our intent and structures. We're programming on at least one layer below what we should.
Unfortunately I think that might require so large fundamental changes that you need a new language. Many might say, what about F#? While F# is great for certain more algorithm oriented solutions for me it never seemed to quite fit the paradigm of certain applications and enterprise systems.
I think in the end there's a skeleton of a next generation language embedded in what c# has become. If we removed some of the crud and used LINQ style syntax as template perhaps we could take parallelism, asynchronicity and productivity to the next level
I was really hoping for better integration of tests and pre/post conditions
Even better was if you had a startup mentor that approved expenses.
An easy example are checking if a file exists under Windows 8, it's partly a product of the currently deficient API's but the fastest way to check if a file exists is to try to get it and catch the exception, and you'd want to return bool from a FileExists method