[Opensim-dev] SQLite doen't need Community.CsharpSqlite.dll?

[Spacefriends]

Although nobody should feed the troll, but what the heck is wrong with you Jim ? You only complain about everything. Opensim ist still a 0.8 version and good people do their best and spend their precious (life)time to provide you and us with this great piece of software for free(!) I dunno about your problems but i am running my opensim regions since 5 years now and besides some small drawbacks all is fine. Why don't you contribute better code or, if you can not code just live with what you get (for free). And I think you are mixing things like ... I left OSG because <insert random bs here> and than I left METRO because <insert random blabla here> .. Metro itself still uses 0.7.* and OSG always use the latest version. The people connect their regions (running different opensim versions) to those grids and not the grids itself 'place' orders which version people have to use. I always use the latest OSG versions but connect the regions to metro as well. Metro eg runs a testgrid with always latest 0.8 versions to test out functionality and everybody knows that they have to use the latest viewers and there is the chance for crashes. 

I even met you inworld in metro and OSG some time ago and you where also complaining. I think it was a good idea to have your own grid. So you can live there and complain. Mayby you should revert to 0.4.* and be happy or go back to SL where everything is working out good for you. In any case, I beg you to please stop insulting people in here.

All the best,
Wordfromthe Wise

> Am 08.06.2014 um 15:49 schrieb Jim Williams <sphere1952 at gmail.com>:
> 
> I left OSG first because the grid became unstable for people using the current code as 0.8 nodes started being used.  Has this problem been addressed?
> 
> I left Metro and returned to OSG (rc2) because after jumping into an 0.8 upon returning you became a permanent cloud and had to relog.  Has this problem been addressed?
> 
> I finally left OSG and put up my own grid on the current release because my scripts will not work under 0.8, and I'm not going to waste time trying to write to a moving target.  I figured I could jump to places and then relog to get home.  Now I'm learning that you are planning on releasing crap I won't even be able to jump into.
> 
> What you should do is stop 0.8 dead in its tracks and produce an intermediate release that can survive the 0.8 protocol changes but which does not actually introduce any of them.  This intermediate release should fix enough bugs to induce people to move to it, but introduce no new functionality.  Then, once people have generally moved to a release that won't be badly effected by 0.8 you can try introducing it.  What you are doing is subjecting people to your changes without any regard for their needs or desires.  People cannot ignore your changes simply by not using the new release, therefore you are obligated to make those changes in a manner that does not negatively impact people who are slow to update to your latest and greatest (for whatever reason).
> 
> You have no migration planning at all, and therefore effectively no planning at all.  (And your QA sucks too.)
> 
> (I'm not trying to catch flies, I'm trying to kill cockroaches.  Enough people are playing nice-nice, and the results are not good.  I'd like to 1) see some of the programmers leave, and 2) see the procedures changed so that it isn't the people who want to make new toys who set the development agenda, such that 3) Opensim finally gets some QA.)
> 
> 
> 
>> On Sun, Jun 8, 2014 at 8:40 AM, Shaun T. Erickson <ste at smxy.org> wrote:
>> Jim,
>> 
>> It could, until just a couple days ago, but that's been lessened significantly. Now, it won't let you teleport to it, if you're coming from older code, if the destination is larger than 256x256. That eliminates a huge problem, right there. You get a nice, graceful refusal of the teleport and no crash.
>> 
>> Now, it is still true, that if you wish to teleport from a 0.8, 256x256 region to a region larger than 256x256, you must be using a viewer that supports large regions. I don't think that is unreasonable.
>> 
>> However, if it were possible for the large region to determine whether the incoming viewer is new enough to support it or not, then I would be in favor of it gracefully refusing teleports from viewers that do not. That would close the other vector for crashes due to old code.
>> 
>> -ste
>> 
>> P.S.: As the saying goes, "you catch more flies with honey, than you do with vinegar." Something to keep in mind.
>> 
>>> On 6/8/14, 7:56 AM, Jim Williams wrote:
>>> What I do know is that 0.8 is giving people who do not use it grief.
>> 
>> _______________________________________________
>> Opensim-dev mailing list
>> Opensim-dev at opensimulator.org
>> http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-dev
> 
> 
> 
> -- 
> No essence.  No permanence.  No perfection.  Only action.
> _______________________________________________
> Opensim-dev mailing list
> Opensim-dev at opensimulator.org
> http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://opensimulator.org/pipermail/opensim-dev/attachments/20140608/2ef3fccb/attachment-0001.html>