[
https://issues.apache.org/jira/browse/SOLR-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13415854#comment-13415854
]
Mark Miller commented on SOLR-3619:
-----------------------------------
bq. 100 enterprise search customer
Like I said - that is one segment of the Solr user base - and as a Solr
consultant, I'm sure it's one you are well aware of - we serve many other user
segments. Many of those segments are doing simple db searches! Many will start
prototyping with simple db searches! Many startups and companies are doing
things with simple searches! Mabye the simple stuff will be all they need. Or
perhaps they will adjust some settings and change some fields when they feel
comfortable and try and make the next thing work. This is how the developers I
know develop software? Even the guys you are talking about - those enterprise
developers - they like software that's easy too get started with as well.
You hit the nail on the head - this stuff feels like "enterprise". And that's
too bad - practically, luckily you can do a lot without going through all the
crap you claim that you need to go through - so if people do dive in, they
realize all this example stuff we have around is half non sense and they just
use the configs as starting settings. It's a scary jump you have to make
though. I looked and didn't jump once. New users certainly don't plan out a
schema on day two of playing with Solr. But they should be able to prototype
simple solutions on day 1 of playing with Solr! We do a disservice to confuse
them "for their own good" so that they sit and contemplate on the high levels
of search before they even dare start prototyping a system. Enterprise software
indeed :)
I'll be working against that vision pretty hard. I have a pretty much the
opposite vision. Only in enterprise software do you endeavor to be so difficult
to get started at the expense of the developer "for their own good".
It's not our job to force developers to make "wonderful" search experiences -
it's our job to give them the tools and user experience that gets out of their
way and allows them a lot of power. If we do that, they will figure out the
"wonderful" search experience part - not because we said they have to edit xml
files before they even start thinking about starting a real solr install - but
because we gave them a nice dev friendly system with a lot of power, and
developers know how to do the rest. The ones that don't - your not going to
teach them anything anyway.
I know as a search consultant it can be attractive to say "search is hard!" -
but we should be saying "search is easy to get started with!" - because it is
(though it should be much easier than we currently make it look).
> Rename 'example' dir to 'server' and pull examples into an 'examples'
> directory
> -------------------------------------------------------------------------------
>
> Key: SOLR-3619
> URL: https://issues.apache.org/jira/browse/SOLR-3619
> Project: Solr
> Issue Type: Improvement
> Reporter: Mark Miller
> Fix For: 4.0, 5.0
>
> Attachments: SOLR-3619.patch, server-name-layout.png
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
