Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
cronjobber
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
10 ms
·
31.
▲
by
cronjobber
9y ago
That would be fun, what with the ultimate dispute resolution procedure against a sovereign Google being the lobbing of heavy ordnance at Kinakuta Googleplex until they cease and desist :)
32.
▲
by
cronjobber
9y ago
I don't think they expect to ever collect a fine at all; they can reasonably expect this law to eventually fail review with one or both of Germany's own supreme court and the EU. The law only needs to hold up and silence dissent
33.
▲
by
cronjobber
9y ago
> giving you the benefit of the doubt and assuming that you weren't just throwing rocks at lisp and smalltalk Nope, I don't believe you ever gave me the benefit of the doubt—your undoubted assumption that I was just throwing ro
34.
▲
by
cronjobber
9y ago
I can't find talk about "high risk" in what I wrote. I can't seem to find where I'm "proposing not learning any new concepts at all." You seem to enjoy arguing against figments of your own imagination. I
35.
▲
by
cronjobber
9y ago
https://en.wikipedia.org/wiki/Rational_ignorance https://en.wikipedia.org/wiki/Opportunity_cost https://en.wikipedia.org/wiki/The_Market_for_Lemons
36.
▲
by
cronjobber
9y ago
> Most folks actually object to going back to novice status A good part of that reluctance is entirely rational. There are many dozens of programming languages that might be worth learning based on what communities of current users say
37.
▲
by
cronjobber
9y ago
The book "Functional Programming" by Field and Harrison (1988) was already very much into referential transparency as the panacea for all our programming woes:-)
38.
▲
by
cronjobber
9y ago
> But who are the people here that keep defending it? In recent times, people have become afraid of being perceived as anti-science . See it all the time.
39.
▲
The Presence of One’s Own Smartphone Reduces Available Cognitive Capacity
(journals.uchicago.edu)
707 points
by
cronjobber
9y ago
|
376 comments
40.
▲
by
cronjobber
9y ago
Does this apply to seizing domains?
41.
▲
by
cronjobber
9y ago
"Portable" is a red herring. C used to be a great language for writing non-portable code. That's what the optimization hounds are destroying.
42.
▲
by
cronjobber
9y ago
The rationale is that you can use them along with those other versions of UUID that contain nonrandom data. Assume Bob uses one such not-entirely-random UUID variety and actually makes use of the embedded information. Charlie uses random
43.
▲
by
cronjobber
9y ago
The Emacs incantation you wanted is something along the lines of (modify-syntax-entry ?\{ "(} " lisp-mode-syntax-table) (modify-syntax-entry ?\} "){ " lisp-mode-syntax-table)
44.
▲
by
cronjobber
9y ago
You're right that this is worse for user privacy, which is exactly why there's hope the new rules could kindle an American conversation on online privacy. If that ends up giving the US strict rules for everybody, that should inclu
45.
▲
by
cronjobber
9y ago
This has a lot of potential. This fist stage is a blow to the Google data monopoly. I obviously don't know if there's a second stage, but there might be, if this spreads awareness that private coroporations store everything they d
46.
▲
by
cronjobber
9y ago
> you don't generally mutate strings If strings in Emacs are mutated so rarely that making them immutable would cause almost no breakage, it logically follows that strings in Emacs are mutated so rarely that using them from Cloj
47.
▲
by
cronjobber
9y ago
> How would you write in prolog that you want it to serve a website? Here's one approach: http://www.swi-prolog.org/pldoc/man?section=pwp Scroll down for examples. You might disagree, but I think the fit betwee
48.
▲
by
cronjobber
9y ago
Quite confused. Two examples: > It turns out there is very little code that would break if Emacs strings became immutable Which means that very little Clojure code would break if they just went ahead and used Emacs strings. > Common L
49.
▲
by
cronjobber
9y ago
> Research on Types and Soundness smothers research on programming languages Perhaps, but you could turn it around, too. Statically typed languages had time to catch up because innovation into "more powerful/better language m
50.
▲
The threat of increasing reliance on closed, foreign code
(osnews.com)
1 points
by
cronjobber
9y ago
|
0 comments
51.
▲
by
cronjobber
9y ago
> (thanks to Google for the kind gift) Why am I spontaneously thinking "Trojan Horse?"
52.
▲
The curious rise of the ‘white left’ as a Chinese internet insult
(opendemocracy.net)
28 points
by
cronjobber
9y ago
|
5 comments
53.
▲
Male circumcision is a weapon in the sperm wars
(newscientist.com)
2 points
by
cronjobber
9y ago
|
0 comments
54.
▲
by
cronjobber
9y ago
TIL, and it's even a first page search result. > I’m beautiful. I’m having a plastic surgeon install rotary blades, 30 mm cannons and AMG-114 Hellfire missiles on my body. From now on I want you guys to call me “Apache” and respect
55.
▲
by
cronjobber
9y ago
Is the "solution" of pushing everybody onto a handful of centralized platforms entirely dictated by the nature of the problem?
56.
▲
by
cronjobber
9y ago
The FSF has always made clear that they don't have any problem with people selling Free Software; it's about freedom, not low low price. (What infuriates me about this story is that it reminds me of how far companies like Google h
57.
▲
by
cronjobber
9y ago
If that's your biggest question, then what did you think "weird attempt at levity" referred to?
58.
▲
by
cronjobber
9y ago
> “But then they went ahead and took the data anyway.” The only question remaining for me is why Googlers still enjoy the respect of their peers. It was fine in 2000, nobody knew how it would turn out. Today, we need to start disrespecti
59.
▲
by
cronjobber
9y ago
It seems doable, e.g. have a few neurons observe that the "other" ant's movements seem to obey our own motor neuron's commands. The consequence wouldn't be that ants are conscious, it would be to question why "
60.
▲
by
cronjobber
10y ago
I've written CL macros. I've noticed that for me, the probability of long-term use seems proportional to the size of a macro's implementation. The more work a macro does, the less likely I'm to revert to "straightfo
More ›