Jump to content

Void Singer

Resident
  • Posts

    7,967
  • Joined

  • Last visited

Posts posted by Void Singer

  1. 1.)    Did your Mummy love you?
    Some days...

    2.)    Did you Mummy spank you?
    No, but she did beat me. generally with anything handy, including my father.

    3.)    Did your Mummy tell you that your dingle-dongle would drop off if you played with it?
    I suspect she meant to, but was too traumatized. I discovered the truth of it on my own when I learned she kept her own replacement in the back of her dresser. After that I wasn't worried that my own must have fallen off some time before I can remember, because I knew that replacements were sold and I wouldn't need to bother with long hours of watering with the shower in hopes that it would grow back.

  2. I agree, very useful in some scenarios, for instance it's the method I proposed for on demand reading of landmark data way back on the original forums to work around the llMapDestination touch limit. It's usually overkill for anything that you can sensibly pre read or event chain, of course, so most of the basic stuff dealt with in the forums doesn't need it. I tend to avoid it generally because of the lowered security implied, but it's nice to have when you need it.

  3. short answer, essentially yes.

    long answer, OOP is more practice than feature, but in theory Event Driven Programming tends towards Object Oriented... it can be violated in practice, but tends to work better if you don't. LSL's basic lacks (no pass by ref internally, limited privatization of functions) can lead to large violations in black box design, depending on the level you look at it.

  4. laguhable, and to think SL original conspiracy nut is onboard with it is entirely picture perfect.

    I don't need any propaganda, I can read it just fine... and it does nothing for "the little guys", what it does do is give anyone with the money to throw at it the arbitrary ability to attack any and all businesses that host user based content.... without even the limited protections of DMCA. The more money you can throw at it, the more efficient the process becomes, and there is absolutely no accountability.

    and the proposal isn't to just blacklist domains (although that's bad enough by itself), but mandates blocking specific content, regardless of source, which therefore necessitates both path tracking and in process monitoring.... the bill for which isn't going to be footed by the government, or even the companies that have to implement it (turning every service provider into a paranoid police force), it'll be footed by the little guys. and guess what? it isn't even going to slow the flood of illegal content, because even if those systems were in place overnight, the whole thing can't be maintaianed faster than it's worked around.... and it still doesn't target the people actually dealing in stolen content.

    it doesn't take a rocket scientist to understand that, but chances are that your average congress critter with barely enough savvy to open an email account probably doesn't get that.

    and for the record, if I ordered said toxic chemicals and they were sent by the proper means, you're damn right I would be screaming, only it wouldn't be censorship, it'd be theft, if they didn't deliver.

    a big pipe hooked up to some trucks? I begin to see where public education is failing miserably...

  5. Oh I dunno, maybe because it's a stupid scorched earth tactic that does nothing to actually pursue the pirates but rather targets businesses, and destroys any posibility of of privacy and allows requires the interception and checking of in route packets. furthermore it has zero accountability, no proscribed methods to be in compliance, and no methods to contest violation. Additionally it provides no means of support to add the network resources and technology required to even attempt compliance.

    it was drafted as an MPAA/RIAA wet dream by people who have no idea of how the internet works, nor it's structure, physical or logical.... and to top it off it isn't even effectively designed to do what it proposes.

    IMHO it is quite possibly the most idiotic thing to hit the house floor.... ever.

  6. another factor is that if script time is high, causing script throttling, that effect is deadly for vehicles, and some physics applications. but if memory is high enough it can still cause paging. paging sucks the life out of a whole region.

    there's lots of room to play in the current model though, and 10MiB isn't that uncommon, nor is it usually that much of a negative impact... anything over that is patently absurd IMO, and a target of under 2MiB is preferable, and easly achievable for most users (that 32 mono scripts at full capacity). anyone that even mentions something about THAT low level  of usage out of the blue should probably be smacked with a clue stick.

  7. but it really is unexpected... because the system is set up with no memory of previous actions (so no file that says hey there was something here but we yanked it).... and servers are about as bright as goldfish...only slightly more useful (unless you were going to make sushi with it)

    but yeah I get what you are saying... the message should be close to standard 404... we don't have that, it may have been moved, deleted, or the address is wrong.

    and now for some funny...

    server_attention_span[1].png

    (kinda reminds me of "10 Second Tom" from 50 First Dates)

  8. depends on your goal... as a general practice, yeah if you're repeating the same code (or it's code that can be used in other projects) you should turn it into a function...

    in LSL there are some stiff speed and size penalties to encapsulating code in functions though, especially with the lack of pass-by-reference. for instance, projectile scripts can often react faster with inlined code than they can with function code, even if there are several instances of the same code. the tradeoff is that it becomes a bit more of a pain to maintain (must be sure to update all instances), and can lead to subtle unexpected behaviors where two paths using the same code may trigger before the next step of either.

    the performance gains may be worth it for some things, and may not for others... I tend to write the functionalized versions first, and then if I need the extra performance insert into it's call spots, and test for those subtle errors.

  9. hmmmm

    Void Singer, Black Knight, I like the sounds of that lol....

    as for Lindens.... we could take a step back a bit further before feudalism, and borrow from the Roman Empire... all Lindena would be Praetors (those protesting a policy could call the CEO Praetor Maximus rather than Emperor)

×
×
  • Create New...