Earlier quoted context omitted.
And we haven't even discussed microservices architecture & CI/CD pipelines. Should we included AI powered monitoring?
Let's bake in some blockchain while we're rewriting this to run serverless with rust->wasm on cloudflare workers to make it 5G ready!
Bongo Cat
181–190 of 208 posts
Re: Bongo Cat
#182It's getting increasingly more surreal to see Bongo Cat popping up everywhere when you know the person who did the original art for it. NEVER expected to see it here on Hacker News. Now back to lurking.
Re: Bongo Cat
#183Re: Bongo Cat
#184While the website has barely any text, consider adding a translated option in Catalan. .cat domain is used to highlight the Catalan language[1]. nyan.cat offers a Catalan version because of this. I think this is checked regularly, but I'm not sure. [1] https://en.m.wikipedia.org/wiki/.cat
Re: Bongo Cat
#185It's getting increasingly more surreal to see Bongo Cat popping up everywhere when you know the person who did the original art for it. NEVER expected to see it here on Hacker News. Now back to lurking.
Are you the person who created bongo cat
Re: Bongo Cat
#186The sounds don't seem well balanced. The cow bell is very loud and when I turn down overall volume I can't even hear the bongos. I bet they are normalised rather than balanced for perceived loudness.
How else could it be? https://youtu.be/ALBViu_o-cw
The 1 should be one semitone lower, but it's still decent. Contra Walken, there is in fact too much cowbell if you try to play it simultaneously.
Re: Bongo Cat
#187This is reversed for the Piano and Marimba for some reason which I think should be fixed.
Re: Bongo Cat
#188Earlier quoted context omitted.
I never understood this “suicidal” critique of jQuery. I've never got so tangled up in my own code to feel the urge to switch to a different model. I've seen Backbone.js, Angular, React, etc, all come and go and none ever answered the “why would I want that” question to me. I remember using Prototype.js and MooTools.js and when I saw jQuery's home page I knew instantly the “why” and the answer was an instant and rej…
(TL;DR; It's just a different way of working with less manual code) I never spent much time on webdev in the era where jQuery came into being but as I've understood (and from the jQuery code I've seen since) it solved basic issues in working with manipulating the DOM and gives powerful animation tools,etc. So as you say the upgrade over the browser API DOM manipulation is obvious, clear and direct. I'd say that my ba…
Sure, if you attach behavior code to every interactive element directly, all of which are controlling the same portion of the screen and depending on each other, it's a recipe for a mess.
If, however, you call somewhat generalized functions on those events, with basic DRY strategies in mind, it's all very clear and manageable well into the thousands of lines, with no need of running a gaming engine in JS, creating a templating language that must be transpiled, etc.
edit: >less manual code
jQuery code if often smaller and clearer, I mean check this classic:
jQuery: https://github.com/tastejs/todomvc/blob/gh-pages/examples/jq...
React: https://github.com/tastejs/todomvc/blob/gh-pages/examples/re... https://github.com/tastejs/todomvc/blob/gh-pages/examples/re... https://github.com/tastejs/todomvc/blob/gh-pages/examples/re... https://github.com/tastejs/todomvc/blob/gh-pages/examples/re... https://github.com/tastejs/todomvc/blob/gh-pages/examples/re...
Re: Bongo Cat
#189Earlier quoted context omitted.
I never understood this “suicidal” critique of jQuery. I've never got so tangled up in my own code to feel the urge to switch to a different model. I've seen Backbone.js, Angular, React, etc, all come and go and none ever answered the “why would I want that” question to me. I remember using Prototype.js and MooTools.js and when I saw jQuery's home page I knew instantly the “why” and the answer was an instant and rej…
mooTools was great back in the day (oh man, we're old). And jQuery was a great improvement from that. Prototype was a great initiative, but I think the community was right when it decided to go the jQuery route, and not append new functions to the prototype. Even though prototype never really caught on, working with websites where it was used partially, or scraping data on websites that used it, has caused me plenty…
>But at the time, writing OOP, or even well moduled code in javascript was extremely difficult to do
JavaScript is still the same, you still can and pollute the global window object, use global variables, etc.
It seems these frameworks are mostly about enforcing a code style, best practices when dealing with large teams with very different experience levels. Since I work mostly alone and clients don't care what tech stack I choose, I guess I'm in luck.
Re: Bongo Cat
#190In case you want (like me) to share your best art with you colleagues: let e = $.Event('keyup'); '09090586 '.split('').map((k, i) => {setTimeout(()=>{$.play(InstrumentPerKeyEnum[k],k,e.type==="keydown")}, i * 200); setTimeout(() => {$.play(InstrumentPerKeyEnum[k],k,e.type==="keyup")}, i * 250)});