I think we're talking about two different things now. On the one hand, businesses being required to keep records communications for some number of months/years before deleting them. On the other, deletion of evidence after you become aware that you might be in court soon. Obviously the latter applies to everyone, not just businesses.
I recently got a $16 a month AT&T line just so I could find my phone when I lose it tho. I leave the ringer off and it is good for 25 outgoing calls.
Wow. Using a local provider I get a basic phone line for $20 per month, no limits. Though like yours about 90% of incoming calls are telemarketers who don't even leave a message.
And the smallest sticks are too damn small already. A friend got one of those Micro SD or something and I was surprised he hadn't already lost it in the carpet. Maybe good for having a normal-sized watch with GB of memory, but otherwise too easy to lose.
More exciting stories on the way: Student has to wait until end of class to use restroom. Student denied hall pass. Student drops ice cream on floor at lunch.
There is nothing wrong with running wires into petrol tanks for sensors. [...] Currents, voltages are limited. Components are overrated by a set amount. [...] So what if you use fiber optics to provide the power.
If the wires short with something outside the tank (even far away), that power is now going inside the tank where it could cause sparks. With fiber optics it's virtually impossible to cause a spark via light. I'm assuming the fiber would carry very weak light, on the level a solar calculator uses, not on the level of CD burner.
Empty sectors on a disk are like empty blocks of memory: a complete waste. Just as every available byte should be used for read-cache (which can be instantly dumped if the memory is needed), every free byte on disk should be used to store previous versions so I can revert to any previous point in time.
Except that what you describe isn't a cache since it's the only copy of the information (older versions of files). Not very useful if you can't rely on it. "No problem, I'll just get the previous version. Oh drat, the free space it was stored in was recently overwritten by the web browser's cache." or "Oh drat, I copied everything to a new drive yesterday so there's no history available." Using free disk space for true caches is useful, like like thumbnails of one's photo library or a huge web browser cache.
In India there is a popular belief that if an AirConditioner is turned off one must wait for three minutes before turning it on. One technician hand waved about the compressor might be at some odd point in the cycle and suddenly making it run would "break" the shaft. Did not believe him. But in the last trip I find that all the A/C are connected to the grid through "voltage stabilizers" that have a delay timer to prevent the machine from being turned on too soon!
A brown-out time delay protects the compressor in two ways. If the voltage drops and the motors draw too much current(amperes) it shuts the contactor off. If the control voltage is interrupted momentarily, it shuts the contactor off. When the compressor is running, high pressure exists at the exhaust port. If it is shut down and restarted before the pressure equalizes with the intake port, the motor will not be able to overpower the pressure imbalance and overheat. The time delay will stall the restart for three or four minutes; sufficient time for the pressures to equalize.
Maybe there is a legitimate purpose for this delay after uninstalling SP1? My best guess would be their Genuine disAdvantage thing is suspicious of closely-spaced registration events or something.
What I did find interesting was the description of MP3 as a perfect copy. Niquist aside MP3 is a lossy format.
If you're alluding to the fact that a CD isn't a perfect copy of the original recording, it's not just the sampling rate that's an issue, it's also the limited resolution (16-bit). For a perfect copy, you need infinite sampling rate and sample resolution. Bringing human hearing in, we can use a finite sample rate because human hearing has an upper frequency limit, and we can use a finite sample resolution because humans cannot hear sounds quieter than some level.
Macros for integral constants (yes, even in C), since enum does the job and obeys scope (yes, C has different scopes, not just C++).
The third point - is there a good technical reason for that? I use defines (with very good names) a lot in my code. Who cares if it is LIBNAME_VALUE or LIBNAME_ENUM.VALUE?
Not if you have prefixed names like that. I guess I was thinking of headers specific to a program that don't use prefixed names, where enum is preferable.
And yeah, I meant to write this for the last item:
Fundamentally, things that ARE highly modular and can be understood and used in isolation. I want to combine modules and have a minimum of complexity increase due to this combination.
Here are some pet peeves of mine involving dealing with other people's code. I don't think many of these are subjective either.
Header files you can't #include without getting errors because you didn't #include something it requires (but stupidly doesn't #include itself).
Lots of global variables that are read and written by several modules.
Header files lacking comments about what functions do.
Use of non-standard names for types with a fixed number of bits, instead of those from stdint.h/inttypes.h. So they have u16 or int16 instead of int16_t. Or really stupid stuff like uint instead of unsigned int (or just unsigned, which is equivalent).
Lack of const-correctness. Something like void print_string( char* str ); Huh, does it modify the string? No, then why does it take a pointer to non-const?
Unnecessary non-portability. Don't use #include unless #include isn't sufficient.
Internal things put in header files. If it's only used in the module, keep it in the module's source file only! Same goes for not making internal functions static, opening the possibility of clashes.
Files indented with two spaces instead of a tab, or even just one space. Fortunately this can be worked around with tools.
Unnecessarily space-taking comments about a function's visible behavior. Things with lines of stars around everything, etc.
Lack of structure tags, preventing forward declaration. Don't do typedef struct {... } foo_t; do struct foo_t { }; and a typedef if necessary.
Macros for integral constants (yes, even in C), since enum does the job and obeys scope (yes, C has different scopes, not just C++).
Fundamentally, things that aren't highly modular and can be understood and used in isolation. I want to combine modules and have a minimum of complexity increase due to this combination.
It works for me very well. Importantly, it does not disable disk's power control. Instead, it auto restarts the disk whenever needed.
Wow, so Linux can use the drive the same way Windows can! I can't understand why this story is presented as if the drive is defective or can't work in Linux; it just has a feature that needs a small update in Linux to support properly.
Regardless, isn't there some requirement that the one distributing the product (Verizon in this case) ensure that there is a written offer for the source code?
Yes, that was my exact point. I guess I didn't deliver it clearly. This Netflix issue serves as a good CONTRAST to companies practicing net NON-neutrality.
In simple terms, there are a huge number of people that will consume your good if it doesn't cost them anything (or next to nothing), but as soon as you raise the price a little bit, the number of people willing to buy the good drops substantially. This is called the price elasticity of demand.
And, if they actually succeeded in stopping all piracy, people wanting free movies might turn to other producers who welcome it. So it's sort of like Microsoft, where piracy helps them by reducing use of non-Microsoft operating systems.
This gives a good contrast with net non-neutrality. In this case, the envelopes (apparently) cost more to process than the postal service planned on. That's understandable since it's a fairly new thing to be shipping such mass quantities, so the postal service hasn't yet made a new category to cover it. So this isn't the postal service attempting to charge a customer more simply because the customer is making more money than another customer shipping the exact same envelope. Contrast this with net non-neutrality where the carrier wants to charge more to the more popular company per bit simply because that company has deeper pockets or is more profitable than some other company also transporting bits through the carrier.
Slashdot Mirror
Who is this Source you keep referring to? Is it the name of a group or person or something? I'm confused.
I think we're talking about two different things now. On the one hand, businesses being required to keep records communications for some number of months/years before deleting them. On the other, deletion of evidence after you become aware that you might be in court soon. Obviously the latter applies to everyone, not just businesses.
Wow. Using a local provider I get a basic phone line for $20 per month, no limits. Though like yours about 90% of incoming calls are telemarketers who don't even leave a message.
And the smallest sticks are too damn small already. A friend got one of those Micro SD or something and I was surprised he hadn't already lost it in the carpet. Maybe good for having a normal-sized watch with GB of memory, but otherwise too easy to lose.
Why is this tagged privacy? This applies to businesses, not people.
More exciting stories on the way: Student has to wait until end of class to use restroom. Student denied hall pass. Student drops ice cream on floor at lunch.
If the wires short with something outside the tank (even far away), that power is now going inside the tank where it could cause sparks. With fiber optics it's virtually impossible to cause a spark via light. I'm assuming the fiber would carry very weak light, on the level a solar calculator uses, not on the level of CD burner.
Except that what you describe isn't a cache since it's the only copy of the information (older versions of files). Not very useful if you can't rely on it. "No problem, I'll just get the previous version. Oh drat, the free space it was stored in was recently overwritten by the web browser's cache." or "Oh drat, I copied everything to a new drive yesterday so there's no history available." Using free disk space for true caches is useful, like like thumbnails of one's photo library or a huge web browser cache.
Let me guess, your last name is mylastname? Unique, definitely, but unfortunate I'd say.
From a page about condensers:
Maybe there is a legitimate purpose for this delay after uninstalling SP1? My best guess would be their Genuine disAdvantage thing is suspicious of closely-spaced registration events or something.
It's not funny! I'm a Mac user and the first time I encountered a multi-button mouse, I couldn't figure out how to click.
... 2007 hasn't ended yet!
(I hate these "top X of this year" before the year has even ended, though at least this one is less than a month early)
But if you go backwards, it's only four letters! We're all doomed!
If you're alluding to the fact that a CD isn't a perfect copy of the original recording, it's not just the sampling rate that's an issue, it's also the limited resolution (16-bit). For a perfect copy, you need infinite sampling rate and sample resolution. Bringing human hearing in, we can use a finite sample rate because human hearing has an upper frequency limit, and we can use a finite sample resolution because humans cannot hear sounds quieter than some level.
Applying similar logic, would you say that people should keep using Windows rather than abandoning it and switching to Linux or Mac OS?
Is C a necessity? In C++, that's an absolute breeze:
namespace library_sublibrary
{
const int foo = 1234;
}
int bar = library_sublibrary::foo;
Too long?
namespace ls = library_sublibrary;
int bar = ls::foo;
Still too long?
using library_sublibrary::foo;
int bar = foo;
Want to bring all the names into scope, not just foo?
using namespace library_sublibrary;
Not if you have prefixed names like that. I guess I was thinking of headers specific to a program that don't use prefixed names, where enum is preferable.
And yeah, I meant to write this for the last item:
Here are some pet peeves of mine involving dealing with other people's code. I don't think many of these are subjective either.
Wow, so Linux can use the drive the same way Windows can! I can't understand why this story is presented as if the drive is defective or can't work in Linux; it just has a feature that needs a small update in Linux to support properly.
Regardless, isn't there some requirement that the one distributing the product (Verizon in this case) ensure that there is a written offer for the source code?
Yes, that was my exact point. I guess I didn't deliver it clearly. This Netflix issue serves as a good CONTRAST to companies practicing net NON-neutrality.
Good thing it's not at the beginning, otherwise it wouldn't have shown up.
And, if they actually succeeded in stopping all piracy, people wanting free movies might turn to other producers who welcome it. So it's sort of like Microsoft, where piracy helps them by reducing use of non-Microsoft operating systems.
This gives a good contrast with net non-neutrality. In this case, the envelopes (apparently) cost more to process than the postal service planned on. That's understandable since it's a fairly new thing to be shipping such mass quantities, so the postal service hasn't yet made a new category to cover it. So this isn't the postal service attempting to charge a customer more simply because the customer is making more money than another customer shipping the exact same envelope. Contrast this with net non-neutrality where the carrier wants to charge more to the more popular company per bit simply because that company has deeper pockets or is more profitable than some other company also transporting bits through the carrier.
Oh come on, everyone's running that new shiny Vista by now. Who would be running an older, less-capable OS like XP?
Er, wait, maybe it's the other way around...