wtbob

256 ms·

2071.
by wtbob 13y ago
Frankly, I dislike this kind of thing. My passwords are typically 32-character random strings, stored via a secure mechanism; having to re-enter them means retrieving them from the secure password store and re-entering them. My computer is
2072.
by wtbob 13y ago
> This puts the burden of checking email validity on every user, even perfectly capable valid users. ? Whenever I hit a form which wants me to retype my address, I just triple-click to select the entire address, then middle-click to pas
2073.
by wtbob 13y ago
> It's significantly harder to style, which means it's hard to work password reset into it. Couldn't that have been fixed with a new parameter in the Authentication header? > It doesn't easily admit to "logout" I think it easily a
2074.
by wtbob 13y ago
> My 4yo daughter can set the foreground and background colors in emacs You, sir, win! More seriously, has she learnt how to read and type? Or does she like playing with letters on the screen?
2075.
by wtbob 13y ago
> So if you're sharing a package with dependencies, you'd have to first check in your dependencies and not rely on go get to manage them. That's what I was describing. The developer of the dependent code pulls in the dependency with go
2076.
by wtbob 13y ago
My suspicion is that it's due to a number of factors. Economic equality (real or perceived) is probably one thing; cultural homogeneity is probably another; if I infer correctly from the article that Icelanders see dealing with crime as a
2077.
by wtbob 13y ago
> Then there's hyperlinks. If not like HTML anchor tags were the hypertext is independent to the destination, but still some method to follow links in e-mails as a lot of online registration requires email activation that way. Well, the
2078.
by wtbob 13y ago
> But this is all moot as the article is about XMPP, WebDav and RSS. The SMTP headline is nothing more than clickbait. Not really. SMTP derives most of its utility from federation, and XMPP could have done the same. Of course, this is
2079.
by wtbob 13y ago
Easy: shake hands, always. Hugging is for close family. I suspect that if someone I were in business with tried to hug me, we'd not be in business for very much longer.
2080.
by wtbob 13y ago
Well, Limbo existed in 1995, but it got nowhere…
2081.
by wtbob 13y ago
> But a new clone of the project since dependencies have moved yields a new product where the libraries have "moved" since a previous clone. No, because a project's tree contains the source code of all dependencies. Why do folks keep o
2082.
by wtbob 13y ago
> "The developer should have done X!", well, then why doesn't Go just do it by default It _does_ do it by default; the problem in this case appears to be (although I could be wrong) that the developer went out of his way to do the wrong
2083.
by wtbob 13y ago
> How would you guarantee that known version? Using the normal import above would not do this Because that's the source code sitting in your src tree. That's actually exactly what 'go get' will do: pull the source code of the current v
2084.
by wtbob 13y ago
Importing from HEAD _is_ the Go convention (so far as I can tell from others' code); it's also Go convention (again, in my experience) to have each system in its own source tree specified in GOPATH, with all remote dependencies installed lo
2085.
by wtbob 13y ago
> Erm, yes it did. The civilized world (Java, Ruby, Python, Clojure, Scala, Haskell, OCaml) has version numbers in their dependency management. Go has localised dependencies: you package your code with exactly the versions you need. &#6
2086.
by wtbob 13y ago
I've only been writing Go for a short while, but my experience so far is that 'go get' only pulls down updated versions of dependencies if you tell it to, with -u. The developer should have set up a proper Go tree for his project, prepended