274 karma · joined June 23, 2014
Also, Prolog does not have a "standard library". What predicates are implemented varies greatly by implementation, and if you want to write portable code then you have to stick as closely as possible to the ISO standard.
I still believe there is a niche where a product like this would be very much at home, but Livescribe's smartpens in particular were undone by a combination of bad internal decisions combined with a market that changed from underneath them. Who knows, maybe the Nuwa Pen will be able to target that niche market more successfully. I could certainly find a use for one, given the right combination of price/features.
Thanks for walking me through it, and for the handy example with exiftool. I like that you're doing this with command-line tools because you can see what's going on more easily. I think it's more accessible than requiring a Java + Gradle build environment.
> 1) field of view + rough estimation of lens data can be computable directly from perspective cues
> 2) this can be narrowed down to specific objectives
Really! That is so cool, I wasn't aware that kind of thing was possible. I never write down the lenses I've used (because lazy) so extracting that kind of metadata from the image would be an interesting exercise.
I get the impression whatever it is requires metadata from a digital camera, which isn't present in my photos because I like to shoot film and scan it. My first thought was, "Wow, how is it going to analyse the subject matter and classify all my scans in 'seceonds'?" My second thought was, "Ah, it won't." The author is clear that this tool is based solely on their own workflows, which is fair enough, but I'd at least like to know what those workflows are.
On a related note, writing accents is usually a bad idea. I remember reading Asimov's "Foundation" when I was a teenager in Australia. One of the characters is a lord and speaks like this: "Ah, Hahdin. You ah looking foah us, no doubt?" Because of course everyone in the future is American and everyone who's not American speaks with a comical (and completely unreadable) accent. Trying to read that dialogue makes me feel like I'm having a stroke.
Even if a collection is processed, because of the volume of information in a given collection archivists typically don't typically describe every document. In a library you can catalogue every book, but that's not possible in an archive. And in an artist's papers, how can you know which document will be important to someone? How can you know what's artistically significant? The time it would take to research the background of every document (Was this script ever made? Is it interesting to anyone?) would be prohibitive.
Add into the mix that archives are chronically underfunded and archivists underpaid. This is coming from the unpaid intern who was asked to process a $33,000 acquisition last year. Fun times.
It was a different time...
[1]: https://www.ala.org/tools/ethics [2]: https://www.ifla.org/publications/ifla-code-of-ethics-for-li...
Full disclosure: they said I broke it. My side of things is that it's stayed on my desk or in a bag most of the time. It never got subjected to rough handling, and this has never happened with any other laptop I've owned. I think it was an issue with build quality if even gentle handling can break it.
The whole experience was very disappointing. I'd really hoped that supporting a smaller company like this would mean I'd get more personal support, but that wasn't the case with Star Labs. This isn't a reflection on the Byte mini PC, of course, but just be cautious about dealing with companies if their products break easily and they don't offer good customer support.
I heard they're moving in the direction of supporting multiple users, which will be fantastic. Then you really can use it as a proper webmail client for a small email server.
The same link but for Jessie says "Package not available in this suite.": https://packages.debian.org/jessie/nginx
But if it is a personal dislike and other people are fans, I can't object. It wouldn't be the first time I disliked an Apple initiative that turned out to be very successful.
They also made the mistake of showing a link that includes the word "Typography", which has an underline so broken up and interrupted that it's distracting (which devindotcom also pointed out). It's linked, then it's not, then it's linked, then it's not!
So yeah, I have to give them credit for a good idea and a clever implementation, but it just doesn't work out in the end.
I'd be curious to hear more about the scam, if you have a source on hand.
I get the sense that the generational shift moved towards Python in the late 90s and 2000s. Then of course Python has been running in circles for so long with Python 3 that the focus is now shifting to newer scripting languages. Does anyone know what the next thing might be? I do hear a lot of talk about Go, but I don't know enough about it to say. I'd be curious to know where people think we might be headed.