1,623 karma · joined October 30, 2014
I am with you that if I'm doing something lightweight I don't use any of the new fancy JS frameworks, I just write vanilla JS.
Edit. Corrected currency to the Pound.
I hope you and your SO can find some common ground in the present to built off of.
I have noticed this pattern in my marriage, friend groups and vocation. That there are parts of the past that I cannot recreate or experience again but rather than try to recreate them I should move forward and learn to enjoy and improve what I currently have.
"2. Testable. The business rules can be tested without the UI, Database, Web Server, or any other external element."
If that doesn't scream functional, then I don't know what does. :)
I prefer Gary's explanation of it because he jumps right into the meat of the problem and shows code that models this architecture. The video doesn't require you to know Ruby to understand what he is saying, just as long as you know some basic testing phrases; Mocking, Stubbing, Etc, you should be able to follow along.
But I agree with your general sentiment that currently C/C++ is the only choice for certain domains. But there is nothing theoretically stopping us from creating safer system languages. (See Rust and Swift, much less so Swift. But Apple is working towards that goal with the option to disable reference counting in a future version which will give much more predictable performance.)
My argument is that we need to stop pretending that C/C++ is not worth improving. Every time someone criticizes a gotcha of C/C++ HN gets very defensive. We need to kill our gods if we want better ones and I personally think we need better system programming languages because it is far too easy to write bad C/C++ code.
What I'm really trying to say is that as an industry we need to stop proping up C as if it's some golden god. Was it a good compromise for it's time? Of course but we can and should do better because it's clear that writing 'good' C code might be beyond the realm of man.
But realistically I think your right. People will gladly handout passwords to people who sound authoritative. It's amazing to me how many DEFCON talks begin with: "So we just pretended to be X and asked for their password and got it."
Let's say that you have 'sustainability', fill in that word however you want, in mind when building your business. But a company who's primary concern is growth will most likely surge ahead of you, possibly squeezing them out of the market. That company can't just retrofit those 'sustainability' practices as by this time they are expected to continue their revenue and company culture is extremely difficult to change.
Edit: Illogical because while you may be making money now, your actions will cause you to loose your assets in the long term.
For scaling a lambda it might make sense to run your lambdas on EC2 using this: https://github.com/lambci/docker-lambda. (But at that point you loose the 'NoOps' benefit of lambda and I can't imagine you'd get similar performance to just running a Node Server or the like.)
Edit: I'm guessing 86,400 seconds in a day and ~30.5 days in a month. If so you're using lambda wrong. You should not keep a lambda running forever rather treat each lambda as a short living function that responds to an API request and avoid calling async operations during the execution of it.
But while most of our tooling for Software Engineering is pretty archaic. I think there is a tooling revolution going on now, especially with new languages: autoformatters, graduation typing, memory ownership checkers, etc. I feel like as an industry we are slowly starting to take tooling seriously.