[Can I just point out] That Javascript as a development platform, as it seems to have become, is evil. It's just horrible from an efficiency, performance, security and architectural point of view.
It seems to be the future.
You can point that out, but you'd be wrong. JavaScript hasn't recently "become" anything. The last major revision that all browsers supported was in November 2000.
It is a beautiful, expressive and quite powerful language that is just now starting to shine after years of being misunderstood by people like you.
I don't want Firefox embracing and extending web protocols. The other changes are in line with W3C specs, but this sounds like a cool whizzbang thing that developers might like. I don't want that stuff in there. If you want a drawing API, use Flash, or Java, or something else.
Thankfully, we don't have uninformed luddites like yourself on the development staff
We found that it doesn't really help to enforce a *formatting* style on developers because everyone has their own. The only thing you really should be enforcing is tabs vs spaces (and it should be spaces) because mixing the two can produce some really ugly results.
We have a much better rate of return running tools like JSLint or PMD to catch issues that are syntactically valid but will be sure to cause problems down the line
So you are saying that open source software that isn't written for a paying customer is not good?
No, I'm not saying that. I should have worded that sentence as: A principal or group of principals who care about the future of the software and is active in its development
There must be some end user or group of users who will continue to drive the needs of a given piece of software and help it evolve.
I hate to whine-- well all right, in point of fact I love to whine-- but this poll is going to be a little difficult to do without links to the projects.
I can see that. Its also apparent that you hate to read.
Had you read the summary, you'd know that the poll has already been conducted and that this post is merely announcing the winners
We use them (PMD and FindBugs) for eliminating code that is perfectly valid, yet has bitten us in the past. Two Java examples are unsynchronized access to a static DateFormat object and using the commons IOUtils.copy() instead of IOUtils.copyLarge().
Most tools are easy to add to your build cycle and repay that effort after the first violation
We ended up getting bitten by bugs like unsynchronized access to static DateFormat object so we wrote used a PMD rule to fail our build if anyone does such a thing. We have other rules that curb the use of IOUtils.copy (instead of copyLarge).
I highly recommend using some sort of static analysis as part of your CI process
If you're going mainstream, you had damn sure better get those prices into the mainstream. Japan made be filled with technophiles who are willing to spend big money on the latest tech of the moment. But most of the rest of world isn't.
Average people will not spend $400 on new technology especially with an economic recession looming over us.
I don't see anything clandestine about a software/hardware company providing software/hardware solutions to the Federal government, especially when said information is printed in a nationally recognized newspaper and linked on a major news aggregator.
It seems more like an opportunity to get the Google haters and rumor mongers fired up.
I've often heard it said that open source experience is useless on resumes, because then employers of developers for closed source projects (regrettably the majority of software jobs) will think you are so kind of hippie rebel and they won't trust you keeping their code under wraps.
An excellent sign of a company you don't want to work for. If an interviewer ever said something to that effect, I would thank them for their time and leave.
Do they have current problems with the software they're using? If so, explain how a different piece of software will be able to alleviate those problems. If you're trying to get them to switch software just because its proprietary vs open source, well you should probably just leave them be.
I don't mean to be a wet blanket, but the book has been out for quite some time -- checking Amazon, July of 1999. It is pretty great, and I would recommend it to those who somehow managed to miss it up to this point, but a review almost nine years later? Slow news day much?
I see where you're coming from but I think this book is so fundamental that the article will be worth it if one new person reads the book and takes its advice to heart.
The book is 9 years old and its concepts are still relevant and practical today. That says a lot about a tech book
You seem to be making the mistake of thinking that refactoring means "making ugly software prettier" when a closer meaning is "making bad software better"
While I'm glad someone wrote a book on refactoring methodology, in my experience what we need is a book which describes how to write "simple" code: code that is just as complicated as it needs to be, and no more. And a book which also describes how to simplify overly-complicated code, how to pick simpler techniques, and how to manage programmers who have an "itch" so they go scratch it somewhere else--I think that would be a much more useful book.
It's easy to add complexity. It's hard to simplify.
If you read the book, you'll find that Mr. Fowler agrees with you.
Read the TDD book by Beck. In it, he describes that TDD methodology in terms of making the code simple in terms of doing only what it should and no more.
The primary problem is not legal, but your management.
Improving your software is always a benefit, whether that benefit is visible to the customer or not is an exercise for your management to handle. By improving your code, you make it easier to maintain which in turn allows more NEW features to be added to it with less headaches.
A person with true moral fiber does not act based upon the laws, but acts based upon his code of ethics at all times. For example, it is clear that beating the living tar out of someone that just viciously beat and stole a purse from an old woman, is a very moral act
I heard about this a while ago but in terms of the "green" advantage it gave them. They save a lot of money on gas and reduce their carboon footprint by not idling at red lights waiting to make a left turn.
Slashdot Mirror
[Can I just point out] That Javascript as a development platform, as it seems to have become, is evil. It's just horrible from an efficiency, performance, security and architectural point of view. It seems to be the future.
You can point that out, but you'd be wrong. JavaScript hasn't recently "become" anything. The last major revision that all browsers supported was in November 2000.
It is a beautiful, expressive and quite powerful language that is just now starting to shine after years of being misunderstood by people like you.
I invite everyone to read Douglas Crockford's latest post on the YUI blog entitled: The Only Thing We Have To Fear Is Premature Standardization
He gives some insight into how ES4 got to where it is today and its impact on standards in general
Thread here. The gentleman in question is Tom Harper.
I don't think I'm understanding what this is. What W3C specification exists for a Javascript drawing API?
HTML 5
I don't want Firefox embracing and extending web protocols. The other changes are in line with W3C specs, but this sounds like a cool whizzbang thing that developers might like. I don't want that stuff in there. If you want a drawing API, use Flash, or Java, or something else.
Thankfully, we don't have uninformed luddites like yourself on the development staff
We found that it doesn't really help to enforce a *formatting* style on developers because everyone has their own. The only thing you really should be enforcing is tabs vs spaces (and it should be spaces) because mixing the two can produce some really ugly results.
We have a much better rate of return running tools like JSLint or PMD to catch issues that are syntactically valid but will be sure to cause problems down the line
No, I'm not saying that. I should have worded that sentence as: A principal or group of principals who care about the future of the software and is active in its development
There must be some end user or group of users who will continue to drive the needs of a given piece of software and help it evolve.
Good software has:
Oh the irony of this post in light of how wrong I am.
I apologize and retract my statement
I can see that. Its also apparent that you hate to read.
Had you read the summary, you'd know that the poll has already been conducted and that this post is merely announcing the winners
Add me to the Yes column
We use them (PMD and FindBugs) for eliminating code that is perfectly valid, yet has bitten us in the past. Two Java examples are unsynchronized access to a static DateFormat object and using the commons IOUtils.copy() instead of IOUtils.copyLarge().
Most tools are easy to add to your build cycle and repay that effort after the first violation
Tools like PMD help with this .
We ended up getting bitten by bugs like unsynchronized access to static DateFormat object so we wrote used a PMD rule to fail our build if anyone does such a thing. We have other rules that curb the use of IOUtils.copy (instead of copyLarge).
I highly recommend using some sort of static analysis as part of your CI process
Average people will not spend $400 on new technology especially with an economic recession looming over us.
I thought the true measure of a womans attractiveness was the pointiness of her knees
I don't see anything clandestine about a software/hardware company providing software/hardware solutions to the Federal government, especially when said information is printed in a nationally recognized newspaper and linked on a major news aggregator.
It seems more like an opportunity to get the Google haters and rumor mongers fired up.
An excellent sign of a company you don't want to work for. If an interviewer ever said something to that effect, I would thank them for their time and leave.
More like art for people who waste enough time on the internet to know the current memes and cliches.
Do they have current problems with the software they're using? If so, explain how a different piece of software will be able to alleviate those problems. If you're trying to get them to switch software just because its proprietary vs open source, well you should probably just leave them be.
I see where you're coming from but I think this book is so fundamental that the article will be worth it if one new person reads the book and takes its advice to heart.
The book is 9 years old and its concepts are still relevant and practical today. That says a lot about a tech book
You seem to be making the mistake of thinking that refactoring means "making ugly software prettier" when a closer meaning is "making bad software better"
If you read the book, you'll find that Mr. Fowler agrees with you.
Read the TDD book by Beck. In it, he describes that TDD methodology in terms of making the code simple in terms of doing only what it should and no more.
The primary problem is not legal, but your management.
Improving your software is always a benefit, whether that benefit is visible to the customer or not is an exercise for your management to handle. By improving your code, you make it easier to maintain which in turn allows more NEW features to be added to it with less headaches.
Thats actually not clear at all.
I heard about this a while ago but in terms of the "green" advantage it gave them. They save a lot of money on gas and reduce their carboon footprint by not idling at red lights waiting to make a left turn.
BURN HIM!
Its my understanding that only the FCC can place limits on radio equipment such as antennae. Can someone correct me?