The most impressive thing is that we can actually measure this minute effect
According to Wikipedia, it's 8.74×10^10 m/s^2. If you integrate that over fourty years, that's 17000 km, or 55 ms light-speed delay, which should not be too difficult to detect.
--jch
--jch
Since it's not clear from your post, the Surface (even the RT version) can do all of that.
Since it's not clear from your post, the Surface (especially the crippled RT version) cannot do most of that.
I don't think any of the current editors support syntax highlighting for it
[...]
There is not yet a LaTeX compiler available for RT
[...]
you need a dongle
See?
On the other hand, sometimes more productivity makes it worthwhile.
Thanks for your concern, but I'm quite productive on my cheap netbook — the battery lasts over 8 hours, and the keyboard is good enough for a sustained 65wpm. The only reason I'd consider a tablet is the weight: the netbook weighs 1.1kg, which is 400g more than a lightweight tablet. But I wouldn't consider anything as crippled as the Surface.
- too expensive
Compared to what?
Compared to a laptop.
The netbook I currently use on trips cost €220. Since it's fully encrypted, it means that having it stolen or leaving it on the train is a fairly minor annoyance (I've had one stolen already).
Since I have a nice laptop at home and a nice desktop at work, I'd gladly replace it with a tablet, as long as I can encrypt the flash, view PDFs, run LaTeX, and plug in a projector. But not at that price.
it's nice to see GNU Emacs finally bothering to catch up to these ten-year-old XEmacs features.
I've always wondered why FSF Emacs couldn't implement a package system...
They might be waiting for the tech savvy slashdot folks to lead the way...
$ host -t aaaa lwn.net
lwn.net has no AAAA record
$ host -t aaaa arstechnica.com
arstechnica.com has no AAAA record
$ host -t aaaa tomshardware.com
tomshardware.com has no AAAA record
$ host -t aaaa phoronix.com
phoronix.com has no AAAA record
$ host -t aaaa smallnetbuilder.com
smallnetbuilder.com has no AAAA record
Stil, I'm not sure it's a good idea to make all devices directly accessible over the internet, it's kind of like begging for a wormpocalypse.
You're expected to have a stateful firewall at the very same place where you have a NAT right now. This is described in RFC 4864.
Imidacloprid is better known as Bayer's Gaucho, at least in Europe.
The real power is (and has always been) with the European Council
Hear, hear.
While the Commission is no more democratically elected than the Council, at least they are serious about transparency. The Council holds a disproportionate amount of power, and they are completely opaque.
could you create an encryption method that generates a new encryption key for every new message.
Yes, modern cryptosystems do that. It's called an Initialisation Vector.
I deeply desire to have a Symbolics machine of my own some day—or at least a version of OpenGenera that boots properly.
You won't have one properly licensed, since the courts were unable to agree who owns the copyrights to Genera. On the other hand, that means you cannot be sued by the copyright holders, since nobody is quite sure who the copyright holders are.
You'll need:
Setting it up requires a little bit of work (you'll need to set up a local NFS server and to tweak your X server's modifier mappings), but I warmly recommend it -- it's complete enough to do some real work in Emacs, and the full sources and documentation are there for your greater enjoyment.
have written most of OpenNTPD.
And you admit it?
I am sick and tired of wasting energy on each and every unfounded accusation someone posts somewhere.
Please show me where the OpenNTPD code computes the dispersion and root delay that it sends to clients, and I will retract my claim.
I don't know if the NTP protocol does [have a leap second provision].
Yes it does -- that's what the LI (Leap Indicator) field is for.
OpenNTPD just ignored the leap second
OpenNTPD has clearly been written by someone who doesn't understand NTP. For example, it advertises incorrect root delay and disperson values, which can cause clients to fail to achieve a majority vote, or to pick the wrong peer to synchronise against. (Earlier versions were even worse, they advertised themselves as being at stratum 0, which could cause synchronisation loops; this has thankfully been fixed, but it doesn't inspire much confidence in the authors' competence.)
I've also found OpenNTP to fail to regulate the local clock on dodgy hardware (it would oscillate wildly, with an amplitude of 3 seconds or so), in situations where the reference ntpd coped just fine.
Folks, do yourself and everyone a favour -- run the reference NTP, run chrony, heck, run some SNTP client, but please avoid OpenNTPD.
Even the name Belarus means "White Russia".
No, it means White Ruthenia . (Rus' as opposed to Rossiya.)
--jch
Today is a good day for information-gathering. Read someone else's mail file.
