1,253 karma · joined April 30, 2019
[ my public key: https://keybase.io/lmedel; my proof: https://keybase.io/lmedel/sigs/HFr8jtOYsBp9NKivqd9SXHvFeEjntcdyd4h9-MYksN4 ]
The earliest jaw-dropping water effect I saw (and somewhat understood at 14) was the awesome credits scene from the Iguana's Earthquake demo[0].
The code[1] contains the following explanation (ancient DOS chars fixed with chatGPT)
; // UpdateTable : performs one integration step on U[CT]
; Differential equation is: u = a²( u + u )
; tt xx yy
;
; Where a² = tension * gravity / surface_density.
;
; Approximating second derivatives by central differences:
;
; [ u(t+1)-2u(t)+u(t-1) ] / Δt² = a² (u(x+1)+u(x-1)+u(y+1)+u(y-1)-4u) / h²
;
; (where Δt = time step, h=Δx=Δy = mesh resolution)
;
; From where u(t+1) may be calculated as:
; ┌ 1 ┐
; u(t+1) = a²Δt²/h² │ 1 0 1 │u - u(t-1) + (2-4a²Δt²/h²)u
; └ 1 ┘
;
; When a²Δt²/h² = ½ last term vanishes, giving:
; ┌ 1 ┐
; u(t+1) = ½ │ 1 0 1 │u - u(t-1)
; └ 1 ┘
;
; This needs only 4 ADD/SUB and one SAR operation per mesh point!
[0] https://www.pouet.net/prod.php?which=364Maybe the OP's "not that important" was an unfortunate way to put it.
I think the answers you ask for are in Ordinatio Sacerdotalis[0]
[0] https://www.vatican.va/content/john-paul-ii/en/apost_letters...
What I mean is that having so much info at the toe of our tips, comments like "you should put a link about what this thing is" are needless.
FYI, you can download the source code [1].
[0] https://news.ycombinator.com/item?id=31311461 [1] http://ftp.lanet.lv/ftp/mirror/x2ftp/msdos/programming/iguan...
I wonder how hard would it be to go back to visual designers like we had with Delphi or VB6. There were flexible layout container components which helped a lot when adapting forms to varying screen resolutions.
About the "when do I say 'I know enough'"...well, never. I just follow my curiosity and it's infinite ramifications. I loss/gain interests about very diverse topics in a somewhat short amount of time.
$ git-down -d bootstrap-dist https://github.com/twbs/bootstrap.git:master dist
is *way* better than $ git clone --depth 1 https://github.com/twbs/boostrap.git
$ cd bootstrap
$ mv ./dist ~/stuff/boostrap-latest
because: "C'mon, you don't have the time to be doing all that."And then we wonder how the fuck we end with malware in our systems.
My first contact with Linux was with Debian 2.1. Exactly with this distro CDs https://archive.org/details/linux-actual-06-2/LinuxActual_01...
To be honest, it was a miserable experience to install it on your main computer without anything else available to look for help in case of problems. It was also hard to really try it due to lack of drivers for current (at that moment) ADSL modems.
But here I am a crapload of years later, still loving it :-)
But good luck selling that to some regulated companies where basic risk assessment is a must. Tell a financial institution you'll _never_ fuck their money transfer pipeline, because you don't do code reviews, you "deliver value" even on Fridays and your methodology avoids all sort of errors or malicious modifications.
IMHO, trunk based development removes some safety. Software development is a complex task and we all risk to break things even on a good day. You're not smarter by removing safety from the process.
But more and more people use "billions" (not billardo, which is our own term for it). The same people that say "diez kas" (for 10k) instead of "diez mil" like they're saving words for doing that (hint: no).
If you're interested, I also implemented a few effects like lens[0] and Jare's fire[1] along with some other amusements[2]
[0] https://toys.luismedel.com/lens/index.html
[0] https://www.joelonsoftware.com/2002/01/06/fire-and-motion/
> [...] Now everyone can click on a button
IMHO the code that the button runs after the click is the problem, not the availability of a button.
If the author wanted to "force you" in any way, he wouldn't offer a publicly reachable download link, nor the source, nor a permissive license.
It's OK to have economic expectations related to a software you wrote.
...served by a simple Kubernetes cluster, I suppose? Back to the roots!
/s