AWS is getting their money regardless. The front end doesn’t matter, if the data/infrastructure is hosted on the backend with aws, they get paid for usage and the data (like the spice) must flow. I suppose by circumventing the website’s frontend you hurt that site’s bottom line by making them incur costs from AWS while not being able to monetize your visit. Which is at least something.
- 0 Posts
- 4 Comments
Joined 2 years ago
Cake day: June 22nd, 2023
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
sacredfire@programming.devto Programming@programming.dev•CLion Is Now Free for Non-Commercial Use4·1 month agoI’ve heard it’s one of the best (if you’re looking for a full IDE experience). I haven’t tried it yet but I am on the lookout to hear about what tools people like to use for c/c++ development. Do you have one that you prefer?
sacredfire@programming.devto Programming@programming.dev•Courses for SIMPLE, website-orientated, javascript development1·2 months agoThe Odin Project has a whole section dedicated to only front end js. But that might be a bit of overkill but they will cover everything you requested.
If you’re mainly interested in how communication between the front end and the backend works using JavaScript, I would look into rest APIs and the browser’s fetch API specifically.
One of the things that first made me fall in love with the cli was how fast doing things like this was. GUIs are hard, and can crash or use up resources for all sorts of different reasons wholly unrelated to the primary task you are trying to accomplish. Once I got over the learning curve of using the cli (and to be fair I’m still in the process of getting truly comfortable with it) I was able to do things so much faster and with less frustration.
Of course, I also don’t want to neglect that it’s not just a matter of the command line but just how good Linux is in this regard. Windows has a command line too and I hate using that thing.