Show HN: Turn a source image into an animated party emoji
github.com
github.com
This could be done with imagemagick in 4 lines of shell script.
for i in $(seq 0 9); do
# Offset by (cos 2pi*i/9, sin 2pi*i/9) and expand the canvas somehow
convert "$1" ... frame-$i.gif
done
convert frame-*.gif -delay 1 -loop 0 final.gif
rm frame-*.gifI'm a fan of stream of consciousness, but that rant kind of just falls into a bunch of whining
I started with Game Maker 5.3, threw together a maze game the same day, proceeded to fiddle around with GM for three years, learning from the manual. Thankfully I was offline so I didn't have the internet's shoulder to cry on
Do they? I didn't see them write anything about GM scaling. They did write about how other people seem to have success with Game Maker, but they have a problem using it because they find some things difficult to understand. But that has nothing at all to how Game Maker scales.
Did people stop using package managers while I wasn't looking? :-)
This could be done in node, which almost everyone already has installed, and whose dependencies aren’t a pain in the ass to get installed and running.
https://ponyfoo.com/articles/npm-meltdown-security-concerns
https://www.bleepingcomputer.com/news/security/52-percent-of...
https://github.com/joaojeronimo/rimrafall
I'd prefer using ImageMagick for something like this, but it's all about tradeoffs and what you're looking to do. There could be memory/security bugs in the future. There are also performance trade-offs if you created a microservice for this function in rmagic/ruby vs node (and you should do both and test them, because you might be surprised which one is actually faster).
I agree it's best to use the right tool for the task, and there are valid reasons for using both in this case. I'd personally probably take the ruby/rmagick/ImageMagick approach myself in a container, but that's not to say that's the best approach.
Meanwhile, bugs that allow malformed input to trustworthy code in JavaScript to subvert or escape the JavaScript interpreter - or the equivalent bugs in Python, Ruby, Perl, etc. - are extremely rare. Of the bugs in 2017 in V8, Node's JavaScript interpreter, every single one of them requires specific malicious Javascript: http://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=v8
It is very easy for a good programmer to accidentally write honest C code that has memory safety bugs that allow an attacker to take over your computer by sending it specially-crafted input. It is very hard for a good programmer to even intentionally write underhanded JS/Python/Ruby/Perl/etc. code that introduces one of these bugs without looking like it's trying to introduce one of them, let alone do so by accident.
Of the security bugs in V8 from 2017 http://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=v8, it looks like exactly one of them could be (and was) tripped by honest code, instead of code trying to subvert the interpreter: https://crbug.com/744584 and if I'm reading it right, it's not even data-dependent. Either the code has the bug or it's not.
Nope. Sorry to disappoint but I refuse to touch node with a barge-pole. Also 90% of the systems I deal with also don't have it installed.
> whose dependencies aren’t a pain in the ass to get installed and running.
pacman -S imagemagick
sudo apt-get install imagemagick
Wow, you're right that was an utter nightmare.
Why won't you touch node? It's a super handy scripting language.
Well, now maybe. I have been able to reliably install stuff with yarn or even npm lately. A year ago though, whenever I saw a node project, I'd try to npm install it and it'd fail 60% of the time.
When you do install something, dear god all the dependencies! So many dependencies! What do all of them do? I have no idea, but they're needed in this boilerplate to get this electron app running.
I've found support in the node community to be pretty non-existent as well. It's easier to find elixir documentation than to get help with node apps. I've been stuck on this electron/vue.js issue forever and have gotten no help, and I've tried Gitter, Stackoverflow, Atom's issue tracker and IRC:
https://github.com/electron/electron/issues/11388
https://stackoverflow.com/questions/48337401/unable-to-test-...