>So instead of having only two options, or a third invisible option, there is only one real option and the demon cannot be wrong or it cannot be right.
This third neither right nor wrong option reminds me of 'Mu' found in eastern philosophy and highlighted in Hofstadter's GEB and it forms another crucial part of self-reference and recursion as mentioned earlier in your comment.
Is there a chance ty or a similar implementation will make it into Go core? What do you think about Go designers being generally averse to the idea of parametric polymorphism?
> Is there a chance ty or a similar implementation will make it into Go core?
I hope not! It was purely an experiment. There are significant draw backs, particularly with respect to performance.
One could reasonably argue that writing parametric functions with reflection should be hard, so as to discourage users from resorting to it too easily.
> What do you think about Go designers being generally averse to the idea of parametric polymorphism?
I think the jury is still out. Russ Cox laid out the essential trade offs given to them: 1) slow programmers 2) slow programs or 3) slow compiler. There's a lot of wiggle room in there (what do you mean by "slow"?), but my sense is that they're still looking for a trade off they're happy with.
In my experience with the Go community, there isn't a ton of internal complaining about the lack of generics. It's certainly brought up now and then, but it doesn't seem to put people off too much. Now, obviously this could just be confirmation bias, but if the Go community keeps growing despite the lack of generics, it may be difficult to justify generics in the future. (i.e., People will live with the first trade off.)
My expectation is that they'll end up giving us something that'll make it easier to work around the lack of generics, but I don't know about getting actually full-on generics. Honestly, I don't want them - they make it way too easy to make overly complex code.... much like class inheritance. I've been developing for 14 years and can count on one hand the number of times I needed something like a tree or graph. Certainly, if you're working on scientific or mathematic projects, you may use them every day of the week, but if so, maybe Go isn't the right language for you, and honestly, it doesn't have to be everything to everyone.
I'm skeptical that trees and graphs are the only thing generics are good for, but, I've published research with open source software written in Go.[1] I've also done it for Haskell.[2] I just try not to pigeonhole languages and learn as much as I can about different paradigms. In my experience, they all have something useful to offer beyond trees and graphs.
“One must lie low, no matter how much it went against the grain, and try to understand that this great organization remained, so to speak, in a state of delicate balance, and that if someone took it upon himself to alter the dispositions of things around him, he ran the risk of losing his footing and falling to destruction, while the organization would simply right itself by some compensating reaction in another part of its machinery – since everything interlocked – and remain unchanged, unless, indeed, which was very probable, it became still more rigid, more vigilant, severer, and more ruthless.”
Depends on your definition of frontend tests. TDD alleviates these workflow problems for javascript (the actual code of the application). But using automated tests for the UI layout is gonna be a bad time. As @davemo mentioned, this post seems primarily directed at a designer's workflow with CSS and less about javascript development.
My advice would be to spin up a free EC2 instance, put a small "dog fancy" type blog/website up with a few articles about poodles, and then use something like openVPN to tunnel your traffic via tcp, port 443 through this.
It looks like you're just doing your wordpress thing, fancying your dogs. Just watch how much data you tunnel this way. 500 gig in a month might raise some eyebrows.
Also remember to use your regular un-vpn'd connection to visit ILoveAhmadinejad.com on a fairly regular basis so not all your traffic goes to this mysterious blog.
If using OpenVPN, there is one precaution one must take - make sure your firewall prevents traffic escaping when your VPN connection fails. Shorewall lets you set up such an arrangement fairly easily. Many US poker players have been burnt this way when using overseas VPN services to play poker as operators are able to catch their real location during brief moments of VPN failure.
With SSH tunnel, if your connection fails, no traffic will escape regardless.
There's a world of difference between "citizen spotted using SSH" and "citizen spotted using Tor".
In the first case you are just one in a huge number of people using SSH to avoid sniffers. With Tor the authorities know you're doing something you'd rather not be seen doing. It's a much, much bigger red flag.
I'd rather "the authorities" would stop spying on me whatever I'm doing, and I believe everyone should actively send up as many red flags as possible to confuse the bastards.
I don't accept the authority of any random gang of thugs over me, from whatever part of the world, period.
"There are two novels that can change a bookish fourteen-year old's life: The Lord of the Rings and Atlas Shrugged. One is a childish fantasy that often engenders a lifelong obsession with its unbelievable heroes, leading to an emotionally stunted, socially crippled adulthood, unable to deal with the real world. The other, of course, involves orcs." - John Rogers
Yeah, but there could be a new parenthetical, "likelihood of an alien living in another universe, multiplied by all the effects of Fermi's Paradox itself, and multiplied by the likelihood of that alien's ability to traverse universes."
I think that would be a very small extra factor, especially if you also add the likelihood of that alien's interest in traveling to specifically this part of this universe.
And of course, we have no reasonable basis for estimating any of those numbers. We have a sample size of one universe and we don't even know the rate of occurrence of life in that one. Still, it can be fun to speculate.
Last week it announced the 'Guidelines and general information for setting up of international gateways for Internet'.
Another quote:
There is a view in the industry that 40-bit key length is too weak for most commercial applications and can be easily broken.
Surprisingly, Singhal [secretary, Internet Service Providers' Association of India] is not very worked up over this. He clarifies that it is just an initial step. "It is not a hard and fast rule that higher bit encryption is not allowed. If encryption over 40 bits is used then the key will have to be given to the government. The DoT seems to have taken the worldwide standard. As and when they receive complaints that it can be easily broken, they will consider going for stronger encryption.
> “Those DVCS kids, they got just what they deserved, won’t it be great when we can get back to a real VCS like Perforce”.
This entire article is based on the false dichotomy that either we use get along with github as it is or go back to svn.
Given the number of projects which directly pull code from github and execute it on production machines, it is not unreasonable to expect basic security from a hosting provider. I don't see why github should be given a second chance.
It also conflates DVCS (specifically, git) with the attack at Github. The security incident at Github had zero to do with DVCS in any way, shape, or form. Were Github to have been SVNHub, built on Rails, and lacking mass assignment controls, the same attack could have occurred.
https://github.com/shabda/tweet-signer
At it's core it's just a spec, so feel free to write your own tools! Suggestions for improving the spec welcome. Please use Github issues