There is a significant amount of complaining about Python 2.x not getting a new version update beyond the current version 2.7. The Python language maintainers are moving on with new 3.x versions. Though, end-of-life for Python 2.7 has also been extended by 5 years.
In a recent post, Martin Faassen calls for a Python version 2.8. He argues that a 2.8 version is needed as an incremental upgrade path to 3.x, and that it should introduce language chances that are breaking backwards compatibility to older Python 2.x code.
Forking Python, taking the 2.x series in a new direction, will introduce new possible problems and headaches that haven't been envisioned by Martin. It would also divert core developer attention from what is really important, namely driving Python 3.x forward.
Instead, Python developers should face facts. Python 3 is the future. Make the necessary investment, upgrade your active code base to Python 3.
Creating a new software product is much like a creating a painting.
You can talk about what you're going to paint, and you may be able to convey in words the experience you want people to have from your painting. But, no matter how well you perform, the narrative is not your painting.
You can visually sketch the motif of your painting. You can even show people an early rough version of your painting. But, they will still not get anything close to the experience of the finished painting.
It's not until you have the finished painting that people will get the full experience.
However, as all artists and software developers know, a painting is never finished.
How Spotify Engineering builds a product:
(This image has been shared endlessly on Twitter the last couple of weeks.)
Here's the video from the event:
Here are some hints:
- No clutter
- "Ease of use"
- Low barrier to entry
- Renders on "all" devices
- "Few" screens (specialised app)
- Simple, unobtrusive color scheme
- Pages render fast (no lag)
That which is most satisfying is that which is earned. Anything received free of charge is seldom valued. You can't get something for (from) nothing. The price is too high.
~ Dave Kekich
This in no. 38 in Kekich Credos. They are all well worth reading.
It's an often repeated mantra among "product people" that:
When building something new, simple and proven technology wins.
The peculiar thing is, there is no amount of empirical evidence that would make it possible to disprove the logic of this mantra.
After all, we're talking about "proven technology", and if something new consistently worked better that would also be considered "proven technology".
It's a self-fulfilling prophecy.
Here's a better way of stating what I believe Mathias is conveying in his post:
If you need to get something done in a hurry, use the tools you already know.
However, if you have the time and the interest, there is no need to shy away from learning and working with new exciting technologies.
Who knows, you may end up proving a new technology.
I had no problems navigating through the menus or making selections, thanks to the touch-friendly interface.
Finally, Microsoft seems to be landing on their feet, with a solid product for tablets that people actually use.
And, given that this is a previously untapped revenue stream for Microsoft, it matters less that Apple is getting a 30% cut of Office 365 subscriptions sold as in-app purchase through the Microsoft iOS apps.