jingo
Joined 13 years ago
Joined 13 years ago
I took this angle early on and have never had second thoughts. As they say, "It just works."
Glad you are seeing the benefits.
However, I think "WiFi" is a strong marketing signal. Even if it does not work as well as Ethernet at transferring data, it appears to work well to sell products and services.
"I really don't know how this tech is going to work..."
It may not have to work. Consumers of computing devices have developed a high tolerance for stuff that is either ridiculously slow or does not work. Many do not know any different: when none of the devices people use have an Ethernet port, they will never know the speeds they are missing. The choice of using Ethernet has been removed.
I use my own cache, not shared with anyone. Do I really need to worry about snooping?
I also use CurveDNS with the authoritative server that serves my version of the root.zone.
Practicing my CurveDNS skills for that day when more authoritative servers are using curvedns. Not sure that day will ever come.
I interpreted this to mean encrypting each DNS packet.
Maybe I misread the statement?
DNSSEC of course does not protect the contents of the packet.
Instead, DNSSEC more or less is just another CA system (or an adjunct to the existing one), running over UDP.
About the price of a domainname? (Note I did not use the word "cost". I create dommainnames all the time at the price of $0.)
Given the choice between a domainname and an IPv4 adddress, I would take the IPv4 address.
Also, given the choice between a single, routable IPv4 addresses and a block of IPv6 addresses, I would still choose the IPv4 address.
IPv4 is "simplicity" in comparison to the complexity of IPv6. IPv6 has features I do not need.
Whenever I am granted the choice, I always choose simplicity over complexity.
Most of the time the additonal complexity is not needed and can only cause problems in the long run.
This is only the opinion of one "consumer". Certainly the "market" may have another opinion.
Microsoft? Amazon?
Does it make a difference?
If my company starts selling cloud hosting and then I announce my company will be hosting its internal applications in "the cloud" (i.e., in my own data centers), what are the security implications for my company?
Are they the same if some other company asks me to host their applications in my data centers?
Is this article a PR piece (or "submarine" as PG calls it)?
What do you think?
"Oracle or Microsoft"
Would any self-respecting programmer follow along with such idiocy if they were not paid to do so?
I humbly request some illustrative examples. Note I agree with you. Examples can be powerful (and, unfortunately, polarizing). Whatever you can share would be appreciated.
Perhaps he is not suggesting that popular ideas likely to be are wrong.
Instead maybe he is saying that to think and develop ideas like Knuth's one needs a certain amount of irreverance for what is popular.
(Undue?) reverance is rampant in the software industry, in my opinion. Would Knuth agree?
Not sure what I missed. It must have some other redeeming qualities besides this one. :)
Learning to master nc and tcpclient before curl* had the same effect. I guess I am missing all the fun.
*There are so many features, so much rarely used code, I'm not sure one could ever hope to fully understand all the implications.