Am I the only one who read this article and thought a designer with no sense of programming skills is talking, over an actual programmer?
A designer should know that a design come to life with HTML/CSS + some artistic skills
Dear Python, Why Are You So Ugly?
71–73 of 73 posts
Re: Dear Python, Why Are You So Ugly?
#72The astounding number of devs asking "who cares?" sums up one of my biggest pet peeves. Would you buy a car that had a modern engine but a chassis and interior from 1983? Maybe if you wanted to save a few bucks - but your friends would still tease you for owning an old clunker. True, Python is a beautiful language that's stayed modern in the face of the evolving web, and I've come across many Python sites that do loo…
PHP has had an 'alpha' version of a new site design available for a while now, but its buried in the 'My PHP.net' section of their site.
You can get to it here: http://php.net/?beta=1
Re: Dear Python, Why Are You So Ugly?
#73Here's an anecdote: In my experience, finding something in Python docs takes a total of five seconds, including passing through the "Google gateway". Finding something in Rails reference has been downright impossible. This is a function of Ruby itself, a very magical language, magic that fails to communicate in auto-generated documentation. How does this work? Good luck finding out, but you'll feel very clever three…
As a ruby developer I may not be that well qualified to ask about this but can you give me an example where you've had this difficulty? It would be good to know in case there's some low-hanging fruit in documentation that would make new ruby/rails developers lives easier. I tend to have a very easy time finding the documentation I need, in both ruby and rails. Sometimes that means a google search, but if I want more…
My last exposure was months ago, sorry. =(
Reading the source is certainly not an alien notion to me coming from Python. I just find Ruby code very difficult to follow when you actually need to understand the implementation.
One of Ruby's greatest strengths, the ease with which you can define a DSL, is its biggest weakness in practice (in my opinion, of course.) In Rails for example, there is a DSL for everything, the Ruby language is used in non-obvious ways to get the desired DSL syntax.
All this makes it very difficult to read other people's code. For the same reason, reading the documentation is difficult. You don't know what function you should be looking for in the first place.