Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
Avro >> mail # user >> Design decision question about the Avro Java API


Copy link to this message
-
Re: Design decision question about the Avro Java API
On Wed, Feb 27, 2013 at 10:42 AM, Francis Galiegue <[EMAIL PROTECTED]> wrote:
> On Wed, Feb 27, 2013 at 7:34 PM, Tatu Saloranta <[EMAIL PROTECTED]> wrote:
> [...]
>>>
>>> Well, to have user code be aware that it can fail, for one ;)
>>
>> Unchecked exceptions are no uncatchable exceptions, so you can catch
>> them as well as checked ones can't you?
>>
>
> Sure, but this is not good practice for one, and it can lead to very
> nasty surprises when it fails -- in production, otherwise it's not
> funny ;)
>
> I catch it right now, but I'd rather my IDE tells me that "hey, it can
> fail here, deal with that" -- and I do.

I do not have strong opinion myself on check vs unchecked exceptions,
but just so know, many Java developers are religiously AGAINST use of
checked exceptions, and consider their use a bad practice.
At best it can be said that this is a controversial question. Feel
free to google to see what I mean.

So it is good to be careful when claiming (as a fact) that doing
something is a bad practice.
It might just be your personal preference.

-+ Tatu +-
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB