-
This is a disappointing article on an interesting topic.
Dismissing logic is clearly a mistake but honestly none of the topics are looked with any depth or insight.
What would be good would be an article which looked at the good parts of each method and then compared, contrasted and imagined ways to unify them, barriers to unifying them and so forth.
Especially, artificial neural networks apparently are quite good at recognizing particular static patterns after they’ve been laboriously trained to do so - deep learning seems to be mostly a refinement of this. What’s obviously needed is a way to combine this ability with some higher degree of logic - allow search for patterns modified by various logical constraints. (I know efforts to do this exist but they are definitely in their infancy).
-
-
Doesn “backdoor” imply something nefarious? This is bug that causes local privilege escalation.
-
I think this can be classified as a “backdoor API” because it’s clear that the
systemsetuptool uses it to escalate its privileges in a way that was intended by the developers. They attempted to hide it by making it require root with the patch that is referenced, but the API part was still part of the system design. In fact the time/work it took to fix also leads me to believe that this wasn’t a bug but rather functionality never meant to be seen by unprivileged eyes. I think its another side effect of trying to make the command line tools more user friendly, or non-power user friendly rather.EDIT: The privilege escalation on all users is a bug, but the Admin use case I would argue is still a backdoor.
-
-
Agree and disagree. Does your readme say “here’s a thing. maybe it works.”? That’s ok.
Does it say “my new whizbang framework kicks the pants off everything else because it’s been meticulously hand crafted for awesome!”? And it’s still shitty? That’s not ok.
-
I thought I’d post my standard readme, btw. :) I’m particularly proud of the “except for the parts that aren’t” wording.
Experimental Code
This source-code repository is published here in the hope that it will be useful or at least interesting, but is very likely to be in an unfinished state, and not necessarily a consistent one, either.
The sole representation is that (except for the parts that aren’t), this code is authored by me - Irene Knapp.
If the repository contains information about its own licensing, that information is normative; otherwise, all rights are reserved and it is provided for information only.
If you do something that requires me to write a better disclaimer, I will be very irate.
-
-
-
-
Here’s a thing, maybe it works: https://github.com/choongng/objc-tidy
I posted it earlier but in my exuberant rebasing I accidentally deleted the source (now fixed). The thing that would make me happiest is if someone put this functionality into clang-format but in the mean time if you have an Objective C codebase the combination of the two can help tidy things up.
-
-
No interest because chiclet keyboard. =( I am endlessly disappointed that Apple managed to infect the entire laptop market with this nonsense.
-
I’m honestly curious what the issue people have with chiclet keyboards is. I own a Lenovo x220 with “traditional” style keyboard, and having tried the newer Lenovo chiclet style keyboards (on the x240), the chiclet keys don’t feel worse and I type just as well (or poorly, depending on your perspective :-) ) on them. Of course, the newer Lenovo keyboards have problems (layout, removed useful keys), but in my experience the chiclet keys aren’t to blame.
(There are of course, bad chiclet-style keyboards, like the Apple ones that have virtually no travel)
-
The perpendicular key edge means I make typos far more frequently when I hit a key slightly off-center. I find them basically unusable for extended typing.
To be clear, I don’t care that chiclet keyboards exist—I just won’t buy laptops that have them. I am pretty upset that every new laptop has a chiclet keyboard, though.
-
-
-
-
-
I think that it should be irrelevant how many status codes are used, so long as they are documented and used consistently.
I’ve spent the last few months working with an API that sometimes returns a 4xx or 5xx and other times a 200 with a verbose error in JSON for the same error, completely defeating the purpose of status codes.
Because they’ve been unwilling to embrace the existing http status codes they’ve effectively coded another set of status codes in JSON in addition to the existing ones.
-
I have started compiling all my go programs with netgo, which is the native resolver, instead of using the glibc resolver. As a result, I have far fewer issues with memory spiraling out of control and random crashes. As a bonus, I get an actual static binary (unless using something else that pulls in cgo).
-
IIRC the only reason the native resolver is not used by default is because the OSX firewall triggers if an app tried to do its own DNS resolution. There have been some attempts to make netgo the default at least on Linux due to issues like this but it’s never gained traction.
-
-
I submitted this mostly to highlight/discuss two lines.
As always, it’s a good idea to wait a few days to see if the update causes any problems
As always, the iOS update includes a slew of security fixes
There are a slew of security fixes. But you shouldn’t apply them yet. As always.
-
There are a slew of security fixes. But you shouldn’t apply them yet.
It’s a shame that security updates and releases are often bundled. It should be possible to say, ‘give me those security updates, but I’ll defer the minor release for a few days’. Case in point, I had to update to 10.10.3 for a slew of security updates [1], but it also introduces graphics artefacts on my Mac Mini Late 2012.
-
It seems like Apple would do well to offer a faster, slimmer update path that doesn’t always require the Big Giant Update. I was thinking about this recently as more states are debating their future with DST, does an iOS update to tzdata require a similar Big Giant Update?
For all its faults, Android is pretty good about updating core apps frequently through the normal app update process (but of course that doesn’t cover OS security updates).
-
-
it is a sweetener that gets users to want to apply the updates.
Or it is a bitterant that makes users not want to apply the updates. I know multiple people who hate when the interface they’ve laboriously learned to deal with changes on them for no good reason, and so they avoid applying updates because they don’t know how badly it will break their workflows.
-
+1 in the sense, that’s exactly why I keep clicking ‘remind me tomorrow’ for an update Apple has been reminding me of since last year.
+1 For the word bitterant. I didn’t know how to parse that first. “Bitter” + “Ant”. Hmm, I don’t know this meme. “Bitter” + “Rant”. Hmm. Don’t know that either. Must be out of touch with the cool kids. Then I saw it in conjunction with sweetener …
-
-
-
-
-
Slightly OT: Are there any large/general-purpose eInk displays/devices?
I really wish there was one big enough for papers/math books that wasn’t super expensive. I love reading on my Kindle but I basically can’t use it for anything work related.
There is Sony Digital Paper [1] but last I checked it was prohibitively expensive for a tablet (>$1100)
[1] http://pro.sony.com/bbsc/ssr/show-digitalpaper/resource.solutions.bbsccms-assets-show-digitalpaper-digitalpaper.shtml
I keep wondering whether the new high-ppi displays on kindle/kobo could be juuuuust decent enough for most papers…have yet to try them out though