There really is no answer to this except that the more tries you make, the higher your chances one of them might have some people interested in it.
6,291 karma · joined May 11, 2011
There really is no answer to this except that the more tries you make, the higher your chances one of them might have some people interested in it.
It's hard to describe but the stories seemed to be not more than sketches without richness or detail, and many of the potentially interesting ideas were never fully explored.
To be fair, there was something strangely appealing about it, and by the end I found I quite liked it even with its flaws - probably because there were some really imaginative concepts underneath (the Foundation I suppose).
Also, Apple is not enthused about anything that might limit the ways in which a device is used. The whole point is that everything they do is focused on finding more and infinite ways to make a device used. Constraining use is deeply against the DNA of everything they are actually aiming at. There seems to be a real, deeply ingrained unwillingness to implement things that might reduce unfettered usage.
Truly this is politics. In politics, you say what people want to hear but do whatever you want. That's what Apple does - positions the iPad as kid and family friendly but just does what it wants.
I know it's not the same market circumstances but this feels alot like the decision to stop development of ie6 after Microsoft beat Netscape.
Is it necessary to pay to get someone to design it to make something look good, or do I just have naturally really bad skills at making things look attractive and convey a clear message?
What's the secret?
They'll clean up, grandma, aunty and the school mothers will continue posting and they never even knew there was an issue.
People will soon forget.
"What do I do in componentWillReceiveProps?" It's a good question. Looking through the code I see alot of cases in which I am mapping new props to state, sometimes transforming received network data that is stored in redux, sometimes making a barrier to redirect to a different page if for example some condition has changed.
Perhaps these things are relics from before I really came to understand Redux - maybe in most cases I can just directly use props rather than having an intermediate setting of state.
You asked "Curious, what do you use it for?" in regard to componentWillReceiveProps
https://news.ycombinator.com/item?id=16695064
I use componentWillReceiveProps for just about everything - I had thought it was a fundamental part of the Redux flow. i.e. Redux updates, new props flow through the hierarchy, I pick that up in componentWillReceiveProps and make changes based on new props.
Is this not correct?
For example load something from network, which goes into redux, redux triggers a props update, so then I do something because for example now redux state has changed to say "loaded === true"
Is this not the correct function to handle changes in props?
and its going as soon as V17? Too early.
I love Redux but I find myself using it less than I want to because so much stuff has to be put in place any time I want to store some stuff.
I'd try not to spend it.
I made good money when young and as a result did not appreciate how hard it is to get. So I spent it, assuming (reasonably, but incorrectly I think), more would come.
I wish I'd hung onto it.
I feel like something has gone wrong with software development that the task of making software requires so much meta programming.
I think Voicery does itself a disservice by featuring a "pick the human voice versus pick our machine voice" demo quiz on their website. I got 100%, and it led me to emotionally response "they have failed", but in fact the voice sounded great.
A more useful demo would have been to hear a range of different voices and be able to put my own text in and hear it read back.
But it is not the point that a machine voice can be determined versus a human voice. The important question is "does the machine voice sound good enough".
Instead, their marketing approach has forced me to make a comparison in which my conclusion was that they tech "lost" in some sort of contest.
One day, I walked into my work area and this new machine was set up and on the screen was this: http://amiga.lychesis.net/amiga/AvrilHarrison/AH_KingTut.png I was a pivotal moment.
My mind was blown and although I could not afford it I immediately ordered one.
In hindsight a more successful strategy for Amiga might have been to build it as a games console as its primary market position.
The real challenge is to work out when your product isn't being snapped up by users not because it CAN'T be awesomely useful and demanded and valuable, but because your marketing has not effectively sold it to them yet.
Nothing here at all for Flutter, just words.