Re: Ah, customers.
There's a sweet spot there -- a non-technical boss can be a nightmare, but technical bosses frequently try to micro-manage every step of the process because they're convinced they could do it better.
1977 publicly visible posts • joined 13 Aug 2007
Indeed, transferring all the rights to a copyrighted work is actually fairly involved and has to be done quite deliberately -- even paying someone for something doesn't make it a work for hire and transfer copyright, unless there's a contract in place stating it does.
I'm genuinely curious if you know of an example of a lawsuit that went this way. It's not a scenario I've heard of before.
Personally I prefer BSD because while I like having my source code open, I also like to keep the possibility of later monetizing my projects. With a BSD license I could add proprietary features and charge for them, without having to release them for freeloaders to use.
I'd think the overhead of FUSE would outweigh that, in the ZFS case, but I've never benchmarked it -- maybe FUSE is more efficient than I would think.
FreeBSD's stack is highly consistent and stable, but you're right, my experience is it's not quite as fast. This may partly be interface-dependent, though -- FreeBSD's driver support is not as comprehensive as Linux's.
As a sysadmin I really like FreeBSD, everything is straightforward and easy to maintain. It has a nice, clean init system, multiple good options for handling package updates, and I've never had a failed upgrade between releases. (RedHat, on the other hand, requires you to reinstall to upgrade.)
Ken White (aka Popehat) has also written at length (and often amusingly) about this topic.
It's actually extremely hard to win a defamation case in the US. Truth is an absolute defense. Also, the statement has to be such that a reasonable person would conclude it was true -- which means satire and general puffery are protected.
To give you an idea of how hard it is to win, the guy that Elon Musk publicly called a pedophile sued him for defamation and lost.
LE's checks are mostly just about whether the person requesting the certificate also controls the server (and thus the DNS.) It's not great, but it's equivalent to other budget certs I've gotten. I think in the early days I had to submit a photo of my driver's license, but realistically what's that going to prove? That I could come up with a plausible-looking image of a driver's license?
"Who owns it" is what EV certs were supposed to prove, but it turns out that it's hard to determine if the "Foobar, Inc." asking for the cert is the well-known "Foobar, Inc." or some other corporation that happens to have the same name in a different state.
It's become a ritual at every major wildfire for water bombers to start trying to fight the fire, only to be grounded because some asshole is flying a drone. This doesn't seem like the right solution, but I'm not sure what is. "Letting the fire burn people's houses down while drone operators get viral videos of it" doesn't seem acceptable either.
I'm almost to the point of getting one. A typical long distance trip for us is around 250 miles round trip, which comes close to fitting inside the practical range of current cars. One issue that's holding me back is the charging infrastructure -- while there *are* charging stations along the highways here, using them still requires a lot more pre-planning than I'd prefer. I might find it fun, but my wife would find it frustrating and stressful.
I wouldn't overthink the cycle issue. There are companies using Teslas for livery service, and one of them recently published their maintenance logs. The upshot is you *might* need to think about a battery replacement at about 300,000 miles -- at which point most ICE cars would be junk anyway.
At home charging speed isn't nearly as important. Generally you're charging the car at night, so there's at LEAST 8 hours of downtime. My daily commute can be taken care of with just Level 1 charging, although I switched to Level 2 because it was less of a strain on the house's electrical system. (16A from a 240V/30A circuit causes quite a bit less conductor heating than 12A from a 120V/15A circuit.)
Here in SoCal it's less of a problem than you'd think, because the distribution system was designed to cope with daytime A/C loads. Charging at night, when those loads are lessened, is heavily incentivized. My nighttime rate can be as low as a third of what I pay during peak hours.
I think in current DC fast charging schemes the car's electronics are mostly bypassed, and power is delivered directly at the pack's charging voltage.
Even Level 2 charging doesn't generally use transformers, at least not ones operating at 50/60 Hz. It uses switching type power supplies like you'll find in a modern PC.
Most of the danger can be avoided if you make sure the connection can never be made or broken "hot." This is how all EV charge connectors (even lowly 240 volt Level 2) work; there's a low voltage pilot connection that makes after the high-voltage one, and breaks before it, and signals the charger to cut the flow.
There'd also be a stronger magnetic field from a 1000 amp cable, but a back of the envelope calculation suggests it's still three orders of magnitude too small to erase a credit card. ;)
The closest we came in that era was the Handspring Treo series of PalmOS phones. They were nicely integrated, not just a phone taped to a PalmOS device -- for example, SMS and phone calls were handled by PalmOS apps, and PalmOS apps could use cellular data. But the market for such things at the time was not that big, and their hardware was a bit flimsy.
Very cool, but not really related to consciousness. ;)
I think part of the problem is no one can agree on what consciousness *is*, exactly, or how to test for it. Until we can answer whether a chimpanzee has consciousness, or a raven, trying to create it in an AI is pointless -- we won't know it when we see it. As was noted above, we've essentially defined it as something unique to humans, which makes it a bit tautological.
It's very rare for directors of a company to go to jail for the company's bad actions. Among other things, it usually requires proving they authorized the bad behavior *and* knew it was illegal; you won't find many company memos with "yes, do the illegal thing -- Your CEO" written on them, so proving any one person meets those criteria is hard.
As a long-time ChromeOS app developer, I'm of the opinion that Google fully intends to axe the ChromeOS platform and replace it with Android. This explains why the web store is so understaffed, why the Chrome API has stagnated, and why they removed Chrome App support from desktops.
Even black-and-white printers can reach that price level if the usage is heavy enough. Printers have a certain rated monthly output. I work for a large academic department and we average somewhere around 400,000 pages a year. We have two large Ricoh high-speed printer/copier/scanner units that according to my inventory sheets cost about $8,500 each. They're each around 4' long and just fit through a normal doorway; they weigh over 400 pounds.
I've often said that a lot of what people think of as "government waste" or "red tape" is actually the result of rules put in place to prevent any appearance of fraud or self-dealing. Corporations just accept that a certain amount of money and equipment will walk out the door, and write it off, but that's not acceptable when taxpayer money is involved.
I thought Firefox OS looked interesting, and was gearing up to develop apps for it when they killed the platform.
Part of the problem was Google's anti-competitive terms; manufacturers could not offer phones with a non-Android OS if they wanted access to the Google Play Store, so anyone who decided to make a Firefox phone would have been locking themselves out of the much bigger Android market.
A fragmented app infrastructure plagued WinCE from the start, and meant that Pocket PC devices were mostly relegated to specific single-function jobs, like scanning packages. In many cases apps had to have a separate build for the specific CPU and screen format of every device, or they wouldn't run; there was very little commonality between different manufacturers' products. The platform persisted mainly because PalmOS was only suitable for low-power tasks (intentionally, since the first Palms ran off alkaline batteries.)
Yes, well. They're also the generation that gets told they should work their way through college instead of taking out loans (by people who did so when tuition was lower, or even zero, and the minimum wage had kept up with inflation), should buy a house (when house prices have shot up massively compared to income), should get a job by reading the classifieds and then work their way up (by people who did that when it was still possible), should shut up about wanting health care (by people who get free Medicare), etc.
I don't actually know any Millennials who thought they deserved a house at 21. Most I know are pushing 40 and assuming they'll be stuck renting forever.
Me, I'm GenX. We don't get insulted much because everyone forgets we exit.
Some places in the US have taken to passing ordinances to protect agricultural operations from that kind of attack.
More recently some of these laws have been used by legal marijuana grow-ops to shut down people complaining about the smell of weed, which I suspect was not the intent. ;)
Not sure I understand your point. Alcohol's actually got fewer BTU's per unit volume than gasoline. It also needs a higher concentration in air to burn. It's less susceptible to detonation in engines, though, which means the engine can have higher compression and make more power for its size.
The main hazard with alcohol is it burns with a clear, invisible flame. On the other hand, since it's water-soluble, it's easier to put out a puddle of alcohol than a puddle of gasoline; you can just dilute it with water until it won't burn anymore.