But as with any code, compilers have bugs too and sometimes they can be quite surprising.
65,359 karma · joined June 19, 2010
Previous lives:
gnu hacker (e.g. co-founder of Cygnus back in '89) Pharma developer (Talima) Distributed solar thermal systems (Terrajoule) MIT AI Lab/PARC/MCC/Rodin consumer tabletop AR (CastAR) Etc...
remove-everything-up-through-last-dash-gumby@brachiate.org
But as with any code, compilers have bugs too and sometimes they can be quite surprising.
Lisp casually waves from the bleachers, then goes back to high speed coding with metasyntactic macros and reflection (and so much more).
I remember we had a chunky dial that required a lot of force (for me as a little kid) to turn from channel to channel. It had a bunch of channels (a dozen?) but I think there were only two channels broadcasting. (My Dad bought a B&W TV for us to watch the moon landings)
If you purchase an edible “power bar” anywhere (not just America) you can be sure it has and can provide no power. It might have a little energy stored as a carbohydrate though.
The rest of the time don’t ever pull the plug out by the cord, even though NEMA requires some appliances to use a power cord with a special bar in it to defend against such mistreatment.
And they don’t feel safe including a patch without a license to use it. Not an unreasonable position to take.
The wording is explicit (italics mine):
> You hereby grant to the Company and to recipients of software distributed by the Company a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to…
My not super-close reading is that this is actually reasonable (but note: I wrote the original GNU blanket assignment back around 1989 or 1990 so you may consider my perspective bogus).
This agreement says that you confirm that you have the right to license your contribution (that what you wrote isn’t actually your employer’s), and that they can use it without restriction, even if there’s something patented in the submission. It doesn’t stop you from using the code for something else. But you can’t come back later and say “hey, yank out these lines of code which I sent you long ago”. It's not even an assignment -- you retain ownership.
If I were doing this, personally, I might add something to the effect of “btw if the company tries to change the license in a way incompatible with the AGPL 3.0 or later versions this license I have you becomes void” but that could implicitly be in there (if explicit, I missed it in my quick read).
Yes, Multics Emacs was the one used by secretaries (except at AI & LCS where they used TECO EMACS on ITS). In both cases most of the extending by non-programmers was done with macros (`c-X (` which is still that command today).
Multics Emacs had an excellent design and you could in fact write some very simple functions with a copy-and-modify rote approach (nothing wrong with that!). But beyond that I never met one whom one could describe as knowing Lisp. In fact most would have been intimidated if you'd told them that they could improve the editor by "programming".
This "programming is impossibly hard for a person like me" attitude was a bad cultural property of the 1970s, thankfully now somewhat in the past. But that change depended on direct work on the problem by people like Seymour Papert and Cynthia Solomon in the LOGO lab (part of the AI lab).
Excel is a great (in volume and reach) example of this: many people write very complex and sophisticated programs in Excel and still don't believe they can program. Now Python is embedded in Excel some people can be tricked into writing real programs. And, presumably, tricked into running sophisticated malware!
I seem to remember reading as a kid that this happened first in some Victorian bet (I would have read this in one of my dad’s kid’s books from the 1930s).
This was also a plot device in a Larry Niven short story (one of the Draco’s Tavern stories).
People who want to are welcome to -- you be you.
People who don't want to should not be pressured to do so.
The context of the Johnson–Reed Act is more complex than you make it and significantly restricted people you would call “white”, not just other “undesirables”.
Most of the violence of the early 20th century was political (especially, but not only, during WWI, which is the example you chose) and seemingly had more to do with age demographics than racial (a similar problem arose a millennium earlier, driving the invention of crusades). The biggest period was after the Johnson-Reed act, as part of a broader increase in crime.
Yes there was an enormous amount of racial violence, but most of it was directed against black citizens, none of whom were recent immigrants.
I have followed this history because without the 1965 Immigration act I would not have been permitted to come to the US and attend school. And I come from a country with twice the immigration rate of the US, but little violence.
Could you expand on this? I can’t think of a scenario where that is the case.
> Social security's payout formula should factor in the number offspring.
Ha, how will you track it? I have no offspring in this country (USA) bc they decided things are better elsewhere. But they were born here.
Germany just does it directly: when your kids are little you have to support them (assuming you can); when you are old and decrepit your kids have some responsibility for your wellbeing.
So what -- are those people somehow special?
Some rethinking is required -- in the USA Social Security was put in place when the typical recipient was expected to receive a payout for...less than three years.
I have friends in the "reduce the birth rate" community, and they are at least as thoughless if not more than the "birth rate too low" crowd. In the former case their "diagnosis" is inevitably that the wrong people are having too many kids though they hate it when you point that out.
A higher birth rate in sub saharan africa is hardly a crisis: every person in the US emits 5X the CO2 of a person in Africa. Dropping population in the rich, polluting countries can be a step in the right direction.
(Personally I'm pretty indifferent to either position. As Herb Stein famously put it: "if something cannot go on forever it will stop". Sure, the latency in this case is quite high but people deal with worse all the time.)
The title is even ambiguous: the same title would work for a story about how BofA breaks its internal rules to prevent dangerous workloads
Though perhaps you shouldn't be manipulating anything and instead concentrating on navigation while the car isn't moving straight? Hmm, perhaps those controls should be disabled when the wheel is (say) 15% from straight?
I do mainly use voice to control my watch, which means in practice it's pretty much a read-only device (which is just fine for me).
> Think times when you can't call the person but need to send them a quick message, eg noisy festival or loud bar.
Aren't these precisely cases where speech doesn't work? Too noisy to hear you; too noisy for you to hear the message.
Your points are good regardless of the fertility rate.
The problem is that, at the end of the day, that's just a feature, not a benefit.
It reminds my of the ongoing push for speech interfaces. Supposedly they are "more natural" but in reality, even when you have a screen, the keyboard is still significantly better (even if it's virtual like on a phone)
Forgivable, as it’s a concept car, so just give people an idea.
He definitely is. He was also a really nice person (I only knew him for a few years, before his stroke)