4,157 karma · joined May 28, 2011
Email: <myusername>@gmail.com
If anything the hardware is the hard part to copy and open source drivers could do nothing but benefit them and ensure wide platform compatibility and longevity, and yet so many companies like this insist on closing things up and forcing hackers to reverse engineer everything. It's bizarre logic to me.
Update: and now I've read through the github issue, oh my I've missed quite some drama.
$ docker rmi amazon/aws-cli
<snip>
$ cd /tmp
$ python3 -m venv venv
<snip>
$ . venv/bin/activate
$ pip install awscliv2
<snip>
$ ssh -i mykey.pem ec2-user@i-masked -o ProxyCommand='awsv2 ec2-instance-connect open-tunnel --instance-id i-masked'
Unable to find image 'amazon/aws-cli:latest' locally
latest: Pulling from amazon/aws-cli
6ebddf7084e9: Pull complete
eb7d160dbc3b: Pull complete
af71d24e41d0: Pull complete
cf26adf9ea98: Pull complete
2491adb1df28: Pull complete
Digest: sha256:a8c8edb4641672d9ef61873594aa02d1c493341ca30f96e257fdc4d3da17ef9c
Status: Downloaded newer image for amazon/aws-cli:latest
A newer release of "Amazon Linux" is available.
<snip>
And now I am logged into the machine. You can clearly see that it downloaded an AWS docker image. Exit from ssh, back to local terminal, and now there is an image on my machine: $ docker images | grep aws-cli
amazon/aws-cli latest 817d1061df76 3 hours ago 384MBSo I don't know if I agree that aws ec2-instance-connect doesn't use docker. And also, I don't necessarily have a problem that it does, it just surprised me a bit.
On the other hand, on my first try I couldn't get "instance-connect" to work and it turned out I needed a different package "awscliv2" which I had no idea existed.. I've been using "awscli" for the longest time and didn't know there was an alternative and more up to date package available. What a mess.
Also, when running the new one apparently it does a bunch of weird docker magic in the background instead of just being a normal Python program so not sure what to think but I guess it works. If anyone knows a leaner solution to opening an instance-connect tunnel I'd love to know.
There is also the issue that often they were published before adding a LICENSE file was a thing. I've found myself in the position before of having to email professors in some random university to ask them if I can get permission to redistribute such a routine while packaging a library that depended on it. In one case I asked them if it would be possible to update their code with a license (which was just a zip file on netlib) and the answer was, "no, but you have my email". So I found myself having to write something like "distributed with permission from the author, private correspondence, pinky swear" in my copyright file. some of this code is so old the authors aren't around and it would get "lost" in terms of being able to get permissions to use it, I mean it's a potential crisis to be honest, if people really cared to check. (Until the copyrights expire I guess, which is what, 70 years after the author's death or some such?)
Anyway, I wonder if a potential solution is to autotranslate some of these libraries using LLMs? Maybe AI will save us in the end. Of course you can't trust LLMs so you still need to understand the code well enough to verify any such translation.
I tried to work on a Mercurial-based project (not firefox) but eventually gave up and just used git to track my changes and then prepare, very carefully, specific big merged commits to contribute back. It was easier, because I could never figure out how to clean up properly if I made a mistake -- so this way, I could just wipe the local copy and start over instead. But it was annoying, and I was glad to stop using it.
Completely bewildered by every thread about mercurial full of people proclaiming its advantages and "simpler mental model". Simpler than a DAG with pointers? Sure.
If I remember correctly you even needed to install some kind of external plugin just to do simple rebasing / branch cleanup. Now's the part where you tell me I'm doing it wrong, shouldn't be rebasing etc etc, but I'm just saying, it didn't work for me; and the constant claims that it's somehow objectively "better" but misunderstood get really boring.
https://github.com/audacity/audacity/blob/6c2e8a2377542d6722...
Value of this comment aside, it kind of makes me chuckle how casually it (and other comments in this thread) just drops the word "artificial" from neural networks here, specifically when comparing with neurology. The irony is funny. Like, somehow we've forgotten why we call them that in the first place, exactly when talking about the thing that inspired the approach.
I don't know much about k8s, but this reaction reminds me very much of how I felt when I first learned CMake. "Wait we're replacing all this crap with.. this crap?"
In other words it performs well for certain applications specifically because it allows you to bring in domain knowledge in the form of the process model and known uncertainties. Whereas deep learning models try to generalize the model and learn implicit structure from data.
Although, I wonder, if you're cooking it like this anyway, does it matter if it's raw?
the machine learning stuff is cool, but it's important not to discount the apparently pretty manual labour still involved in the virtual unwrapping:
> Early in the summer, a small team of annotators (the “segmentation team”) joined our effort. They began mapping the 3D structure of the scroll using tools initially built by EduceLab and improved by our community. By July we had segmented and “virtually flattened” hundreds of cm2 of papyrus.
So, it sounds like it was about a month or two of work, for a single scroll. Although, it probably could be partially or fully automated too, with some effort. Already they developed some tools to help, and I guess it's the kind of task that gets easier after you do it the first time.
Plenty of fiction uses "future seeing" as an interesting plot device, (Dune for instance, and currently the Foundation tv series), so we clearly find the concept intriguing, but it is relegated to fiction of course, so likely we generally find it preposterous, and perhaps it's all just biblical references after all.
But it seems that there was a time that people could get away with prophecy as a real claim. It's hard to put your mind sometimes into a pre-scientific mindset, but obviously enough people found these claims compelling. (I realize there is some survivorship bias going on here.). How did they get away with it, I wonder? Just make it vague enough and far enough into the future to be unverifiable? Just make it scary enough that people don't want to take the risk that you are wrong?
When you think about it, it's amazing that some of these stories made it so far and that people even today still believe them. I mean this from a kind of anthropological point of view I guess. Makes you wonder what we commonly believe today that will seem silly 1000 years from now.
It should be noted that there are methods for training the network to encourage these prunable neurons, eg sparsity penalties.