Comment hinet.net (Score 1) 77
Running your own gateway that does actual logging is an eye-opening experience. There are a phenomenal number of jerks out there...
Schwab
Running your own gateway that does actual logging is an eye-opening experience. There are a phenomenal number of jerks out there...
Schwab
Stack Overflow can't always solve all problems. Many times I have looked for an example of how some piece of Sencha's poorly-documented ExtJs framework works, only to be directed to a Stack Overflow page where someone posted a question looking for the same thing.
I know it can be dull and time-consuming to create examples and documentation, but, really, just linking to the source code does not really explain what a particular class or config option does. If you want programmers to get the most out of your framework, you have to show what can be done with it. If you don't have time to document a feature, why did you bother including it in the first place?
As far as I can tell, I have all of the smartphone benefits without much of the cost.
Or, conversely, maybe it has a chance to thrive if it's being maintained by people who have an idea of what to do with it?
That was supposed to be the whole point of spinning off WebOS in the first place.
Barely two years ago, HP gave WebOS a modest nest egg and spun them off into its own independent entity (which, from the point of view of WebOS, was a good move, given how badly HP has been mismanaged over the last decade). They shared/leased some of HP's organizational infrastructure, but WebOS has been pretty much on its own since then. They definitely had/have a vision, and they've definitely been executing on it.
I'm not sure what value LG's ownership brings to WebOS -- or indeed what value WebOS brings to LG. But at least now the WebOS guys will be able to get employee discounts on nice flat panels
d) Changes. The requirements are often so written in very complex language that noone really understands it, and then they come along with changes every 2 months which require 3 months of recoding because they didn't fully understand what they were asking for to start with.
With federal government projects, and I assume with state projects as well, there are all kinds of specific guidelines and rules that have to be followed. If these aren't stated explicitly in the proposal, they cause cost overruns. For example: Only union employees are allowed to move servers, equipment must be sourced from certain suppliers, certain technologies such as bluetooth aren't allowed in some government locations... The unwritten requirements can go on and on.
By the way, I've been told by doctors for at least 20 years that a magenta tint sometimes helps. This isn't really new art.
Well, the only implementation so far is floating-point. I suspect the fixed-point performance would be a lot better if we ever get that written. It can keep up with real-time on a Raspberry Pi or an old Atom laptop.
Correct me if I am wrong, but the technology we are talking about here is merely splicing some reconstucted sequences into existing human cells.
You don't have to synthesize the entire cell. Only the nuclear and mitochondrial chromosomes matter. If you can replace the ones in a normal cell, what you have after division is the primitive cell reborn. You have to do this to a lot of cells, and grow them for a while, to get one without significant damage.
* Anything but FLAC and Codec2 (because FLAC doesn't compress and Codec2 is voice-only and ultra-low-bandwidth).
With your bare hands?!?