So, why do you waste money on the phone?
It provides a convenient phone number to provide to people who require one but to whom you don't want to talk, e.g. charitable organizations that will pester you to increase your donation. Turn the ringer off, give it an answering machine or similar service, and let people leave messages which you pick up later.
(It may also work better for speakerphone calls than a mobile phone.)
The fiction of net metering is that you will not be paid the same amount for the electricity you generate as for the electricity you consume.
On of the purposes of "Smart Meters" is to permit differential pricing on electricity produced vs. consumed; it's not just to provide a temporal demand market. There are already tariffs in place in California where PG&E only has to buy as much electricity as you consume for a net 0 energy usage, rather than being required to purchase everything you generate over what you consume.
The idea of a large grid only works if someone pays to maintain that grid, and that pricing comes in as a differential.
Everyone can't do what Tesla is doing because not everyone is going to have the storage capacity to make it economical; Tesla can just rota the batteries it manufactures in service to the manufacturing plant itself, as part of "burn in testing", so that it'll get local off-grid storage as a side effect of the manufacturing process itself.
I suppose that "every rechargeable battery manufacturer can do what Tesla does" would be a fair statement, but that's a tiny subset of "everyone"
Of course! It's all rainbows, sunshine, lollipops and unicorns up here so there's nothing interesting to report.
Yup. And honored by a "mainly Canadian economics blog", no less.
Almost everything everyone complains about regarding Facebook is related to its choice of NoSQL as an underlying implementation technology:
- You don't get to see all of your friends posts
- Everyone who follows you isn't guaranteed to see all of your posts
- The computational overhead of making ACID guarantees is available
- Posts show up out of order
- A comment on an old post by someone brings the whole thing back as if it's a new post
It follows that the other things that people complain about Facebook over are sure to follow into the NHS implementation, if they are taking that lead to its logical conclusion - meaning advertising replacing desirable content in the medical record.
Get rid of your dictator and adopt a representative democracy and it will be over. Indeed, nobody could have thought it would go on this long.
If you look at a screenshot of blivet-gui, you'll see it doesn't use the same UI as anaconda.
"Rejects empirical data" is another way of saying "taking it on faith", i.e. the Austrian school is a religion by another name.
Oh I feel your pain. I've had to put up with those damned mathematical religionists taking it on faith that not all primes are odd, when time after time my experiment taking a random sample of one thousand of the first billion primes has kept showing them all to be odd.
And I've had to put up with those damned geographers claiming they've seen triangles with three right angles when it's been mathematically proven that the sum of the angles in a triangle is 180 degrees! "Empirical evidence" indeed!
If I'd say I'm underwhelmed, it would be a big understatement.
Every major device announcement that Apple made in the recent years was always driven by one thing: It had a purpose. It provided something that was lacking in the world. Not a totally new invention in many cases, but a solution. Smartphones existed before the iPhone, but it is clear that the smartphone market history can be divided into "before the iPhone" and "after the iPhone" - just look at pictures of smartphones from those two periods.
iWatch? I know it was rumoured for two years or so, but in all that time I couldn't see which problem it solves and what meaning to life it has, and I still can't. It seems the Jobs spirit has left, because this is clearly a device that was made in response to the rumours about it, not because someone knew what he was doing.
Great, they've invented "MedBook"... what you see when you look at it is a fraction of the available data at any one time because it has "arrived" at the node where you are viewing it from yet.
What do I have to do so that my drug allergies and blood type are "sponsored postings" so that when my doctor looks at them, he doesn't kill me due to all of the auto-play video advertisements for Cialis being there instead of the information I want to be there?
HTML5 is, indeed, a programming language -- at least when paired with CSS3. You can implement Rule 110 in nothing but HTML5 + CSS3, and Rule 110 is known to be Turing-complete. Ergo, HTML5 + CSS3 is capable of any computable process, and is a full programming language.
It's a horrible programming language, but hey, when has that gotten in the way of widespread acceptance?
We have trolleybuses here in Vancouver, too. Vancouver isn't as hilly as San Francisco, but it's far from flat. Our electricity is relatively cheap and comes from dams. So no carbon footprint.
The new diesel buses are all hybrids.
...laura
They no longer provide MBTF metrics for consumer (Deskstar) class drives but the uncorrectable error rate on Ultrastars is an order of magnitude higher than the others, which is a common distinction between consumer and enterprise-grade drives.
He gets tax breaks to entice bringing lots of jobs to THAT state instead of some OTHER state.
That's the problem there, can you spot it?
Another possibility is that the "well-reasoned logical argument" wasn't actually well-reasoned. For example, I've seen a perversion of the Austrian School axiom
And, of course, an axiom is just a starting point; if the axioms are inconsistent with each other, or with reality, the conclusions drawn from the axioms could be bogus, no matter how air-tight the reasoning.
Unfortunately, Mukt completely mis-reported this and Slashdot picked up their errors for the summary, which is making for a lot of confusion.
tl;dr:
1. blivet-gui isn't supposed to (and in fact cannot) 'replace' gparted in any reasonable sense of that term.
2. blivet-gui is a new application, but its backend is the Fedora installer's storage management code, which is a very old codebase. There is no new storage management backend being written here.
3. Lennart and systemd have nothing at all to do with this.
4. It wouldn't really be practical to 'contribute' this to gparted, as it would involve completely ripping and replacing gparted's backend and then very rapidly proposing significant changes to the GUI, and hence would be a project takeover by any other name.
5. blivet uses standard underlying tools for performing operations, it's just a logic/configuration layer for them.
1: what the original announcement says is that blivet-gui uses a gparted-like UI to make it instantly familiar for gparted users. It doesn't say anything at all about it 'replacing' gparted. That's a pure invention (likely based on a misunderstanding) in the Mukt article. See the original announcement at https://lists.fedoraproject.or... to verify this, if you like. There's no sense in which blivet-gui really *could* "replace" gparted, if you think about it. gparted is an independent project; Red Hat doesn't own or maintain it, so Red Hat can't stop it existing or being maintained. gparted isn't a significant component for either RHEL or Fedora: it's just a leaf package, an app like any other. It's not like anaconda uses gparted as its partitioning tool, or anything like that. So talking about blivet-gui 'replacing' gparted doesn't make any sense, not upstream, not downstream. So long as upstream gparted devs see a need to keep developing gparted, gparted will continue to exist upstream, and so long as a Fedora packager wants gparted to be in Fedora, it'll be in Fedora, whether or not blivet-gui or any *other* storage management GUI app is also in Fedora. We have lots of space in the repos.
2: the backend for blivet-gui is blivet: https://git.fedorahosted.org/g... (packaged in Fedora as python-blivet). This codebase is simply the storage management backend of anaconda (the Fedora installer) split out into its own repository. The split happened back in 2012: http://www.redhat.com/archives... . The intent was to allow for exactly this kind of code re-use. So there really isn't some kind of new NIH effort going on here: the storage management code is not new, all that's new is the light wrapper around blivet to produce a standalone GUI app rather than using it as a part of the anaconda installer. The underlying codebase has existed basically as long as anaconda has existed, which is rather longer than gparted has existed. anaconda dates back to 1999 (https://fedoraproject.org/wiki/History_of_Red_Hat_Linux ), gparted AFAICT dates back to 2004 (http://gparted.org/news.php?item=180 ).
3: Doesn't really need expanding on, but no, there is absolutely zero link to Lennart, systemd, or any other systemd developers.
4: so the reason to do blivet-gui at all, and the reason anaconda doesn't just call gparted for "partitioning" like ubiquity does, is it doesn't cover anywhere near the functionality we actually need for the Fedora (and, more to the point, RHEL) installer. gparted really is a *partitioning* tool, and there's a reason I keep referring to blivet as "storage management". It handles things that aren't just partitions. The most obvious examples are mdraid, LVM, and btrfs (insofar as btrfs acts as a volume management and redundancy system, not just as a simple filesystem like ext), but blivet has all sorts of other interesting capabilities too, primarily of interest to an enterprise audience (iSCSI, FCoE, blah blah buzzwords buzzwords). We've been interested for a while in the idea of having anaconda's GUI for actively changing disk layout be a separate process, and just having a GUI for assigning mount points within anaconda itself (or something along those lines), and this is a step towards that, as well as probably just being a useful tool for people. We can't use gparted for this purpose, because it's just not capable enough. It's really only a GUI wrapper for libparted. blivet sits on top of libparted...and also on top of btrfs-progs, cyrptsetup, device-mapper, lvm2, and mdadm (among others). It's inherently more capable and more complex. This is why we can't just "contribute" this work to gparted - they're really fairly different beasts, you can't just "contribute" blivet to gparted in much the same way you couldn't just "contribute", oh, say, the backend of emacs to the frontend of nano. It'd be a ground-up rewrite by stealth, effectively. the gparted you got out would be nothing like the gparted you started with. (to discount the humdrum technical fact that they're not written in the same language, of course.)
5: even if you consider blivet as if it wasn't one of the longest standing storage management codebases around and thus accuse it of NIH, it doesn't really work, as it just sits on top of perfectly standard tools. blivet *uses* libparted (via the pyparted wrapper). it uses e2fsprogs to create ext partitions, mdadm to create mdraid arrays, dosfstools to create FAT partitons, btrfs-progs to handle btrfs devices, lvm2 to handle LVM. it's really a logic and configuration layer on top of those tools.
The following statement is not true. The previous statement is true.
