Take More Screenshots

1

CleanShot X

#Screenshot Annotation #Screenshots #Image Annotation 74 social mentions

2

Luau

When I started making a game [0] last year, first thing I did was write a little Unity script that takes a screenshot of the opening scene, counts current lines of code using CLOC [1] (for fun, not as a true measure of anything), and occasionally renders it all out to an image file. With that I'm able to create some pretty fun time lapses of progress. I've been doing this at an arbitrary milestone, whenever my Luau [2] LOC surpasses C++ by another factor. This post reminded me I'm overdue for another now that Luau > 3x C++ LOC. I find it rewarding to look back at my progress. I'll share in case it's interesting for you too [3]. [0] https://store.steampowered.com/app/2168330/Helmscape/ [1] https://github.com/AlDanial/cloc [3] https://twitter.com/kineticpoet/status/1619508466212831232.

#Web App #Green Tech #Tech 27 social mentions

3

ScreenCloud.net

I've been using https://screencloud.net/ for the past few years. Custom file naming rules, you can upload to your own FTP server, then it will automatically copy a link to the file. Works perfectly for sharing and archiving screenshots.

#Digital Signage #Marketing Platform #Office & Productivity 2 social mentions

4

Artifactory

And all of those have packages that could technically disappear, or you could have network issues and so on (when I build my container images, I sometimes even have apt fail, even though very rarely). I think a safe bet is to run your own package proxy, like Sonatype Nexus: https://www.sonatype.com/products/nexus-repository (there's also JFrog Artifactory in this space, probably others too: https://jfrog.com/artifactory/) This can improve build speeds because you refer to your own server for getting packages, the proxy will also pull packages that it doesn't have automatically, there are no rate limits to deal with (e.g. DockerHub pull limits vs the image being pulled once and stored in Nexus, unless changed) and you can also pretty easily see just how much stuff you're relying on. The next step is to also use this server for publishing your own packages, which is suddenly easier - you can manage your own accounts, with nobody to tell you what you can/can't upload and how: you literally have all of the storage on the server at your disposal, redeploy as often as you want. The only real downside to this is that you are indeed self-hosting it: you need updates, storage and all that. Well, maybe there's also the issue that using custom repositories downright sucks in some stacks - while npm supports something like --registry, I distinctly recall Ruby being a total pain in this regard in a container context (something about Bundler configuration, since it doesn't seem to support a command line parameter): https://help.sonatype.com/repomanager3/nexus-repository-administration/formats/rubygems-repositories.

#Git #Code Collaboration #Software Development 20 social mentions