stassats

Where does it say that?

I guess that's because I added this in 2016 and the article is from 2015.

I don't hate it, it just randomly stops working for me.

I think most binaries go through the linker, and since everyone will have the same linker version from the start it shouldn't be a problem.

They also say >enable the system to better detect code modifications.

So that part doesn't require any central authority and can be handled locally. (But I'm guessing there are more parts)

Since there's no reason to do that only on arm and not on intel macs you would still be able to launch it after jumping over some hurdles.

Just that now the linker automatically signs every binary. So that something like gatekeeper could disable it based on the signature.

That would be my non-"apple is draconian" interpretation, as I don't have an arm mac.

And as to >and what makes Apple Silicon different here

I guess this is a backwards-compatibility breaking change, but Apple Silicon is a new platform so there's nothing to break, all new binaries will have it from the start.

> There isn’t a specific identity requirement for this signature: a simple ad-hoc signature issued locally is sufficient, which includes signatures which are now generated automatically by the linker. This new behavior doesn’t change the long-established policy that our users and developers can run arbitrary code on their Macs

Ok, not really true.

I don't think you need any hardware support for that. And notarization already exists on intel macs, just that it doesn't prevent you from launching non-notarized binaries.

> * And now macOS is adopting the worst of iOS' draconian policies. You won't be able to run non-notarized apps on macOS on Apple Silicon based computers at all.

Where did you get that information and what makes Apple Silicon different here?

You can disconnect the LED cable from the motherboard.

Limiting the action to "Books" seems to not affect other apps as well. The main reason I did not use ⌘C is because it doesn't work when the context menu is displayed (and it gets displayed immediately after selecting text).

I solved the Apple Books problem with an automator script, using the "Copy to Clipboard" action. Then it can be assigned a shortcut in Keyboard preferences. https://imgur.com/a/sG2isap

You can do "taskset --cpu-list 0 make -j"

The not-really-breaking change is not actually related to the version number. There is approximately 0% chance that somebody depends on the presence of that symbol in features. And there have been more actually noticeable compatibility changes with minor version bumps.

I don't want to ruin the language just so that it appeals to some people, it's already fine for me.

But what is the point, really? SBCL will disable type checks with safety=0, LW will enable with safety=3, debug=3. Is the point "read your documentation before relying on things"?

Or is the OP's point that SBCL shouldn't exist because it's "poisoning" and "a bad thing"?

That's the problem with such FUD, can't ignore it or somebody might actually believe it, can't just say "nonsense" since that's not convincing.

It needs (optimize safety debug) and the function needs to be compiled (interpreted code doesn't perform any optimizations based on the types).

That is theoretically true, but what implementation really does that with SAFETY being 3? Claiming that SBCL following the standard is poisoning anything is completely baseless, though.

That's not at all what SBCL is doing. Each type declaration is treated as an assertion, and only then it performs optimization. And there is no undefined behavior at all.

And even without type declarations SBCL is actively deriving types and optimizing things that are proved to have a restricted type.

Spreading misinformation like this is what's poisoning the ecosystem.

That's what the essay is doing. But in my more than 10 years (not 20) of using Lisp I have seen nothing to support the hypothesis, let alone to diagnose a psychiatric condition to a group of people.

Then there is this gem "If you read many posts discussing Lisp (including one in comp.lang.lisp called Common Lisp Sucks)" ... " The problems are soluble (Qi is a proof of that for God's sake), but when you're down everything seems insoluble. Lisp is doomed and we're all going to hell."

Lisp is doomed because nobody likes his pet project or appreciates his insults. This essay is just one big insult, I'd prefer people stop disseminating it.

You are describing any open source library written in someone's spare time.

And this essay is such baloney I don't even know where to start.

I actually like the sliding animation, it's pretty fast and it shows what's going on. I often use it with the three finger swipe, so it'd be pretty weird to suddenly jump to a different space, but even with Cmd-1/2/3 it helps to orient oneself.

Although when reading ebooks I have page animation disabled, I guess because you mostly proceed to the next page, and there's no context switch it's all reading.

But I also prefer having two monitors for multiple contexts, no amount of virtual desktops with or without animation will beat that.

Safari 10 for El Capitan was released yesterday as well.

I've been using h264ify in Chrome on OSX for some time, but lately it started having problems with seeking/rewinding. Have to switch to Safari when I want to rewind. Managed to cobble together a chrome extension that opens the current url in Safari, also pausing the video and using the current playback time (too rough to share).

Part of the issue is that the interrupt number, 5, is hard-wired. So there really was no need to keep it alive.

Because individual instructions doing the same thing are faster. Though it's especially slow because it's microcoded and is left just for backwards compatibility and not trying to be fast. So modern CPUs are good at reordering, predicting branches, etc., for simple instructions and no extra silicon needs to be wasted to duplicate that. And encoding space is limited as well.

Nowadays you can get ECC with intel for quite cheap: http://ark.intel.com/search/advanced/?s=t&MarketSegment=DT&E...

As I understood it, he's usually using this machine as a router at home.

Funny, I've never overslept before when DST was switched, but this time my phone decided that it still should switch from summer to winter time, resulting in me sleeping one more hour.

What's more annoying, my Garmin Edge cycling computer still shows the wrong time, because it determines your time zone based on GPS and there's no way to change the timezone or time manually.

Some web sites (like http://www.wolframalpha.com/input/?i=time+in+Moscow) still don't know that the timezones in Russia have been changed.

There is no need in "#.".