Nyandalized

You would find that banking and it's related fields are indeed very profitable.

I'd argue that "the cloud" makes traditional computing more efficient. Since their motto is "pay for what you use", it automatically aligns with motives for the most efficient use.

Not to mention that the usage of computers has reduced the need for much more power hungry methods. We can now efficiently calculate much stronger, lighter, easier to manufacture parts and building patterns.

There is no need to drive/ride/walk to a place to hear the message, radio broadcasting is much more effective, even though it itself consumes power.

I'm not quite sure what you're trying to say. Are you discounting their efforts? Their motives?

You're not responsible for everyone else, or if you were, they'd not need to be for themselves.

Why are you not making them yourselves? If it's because of economics, it clearly indicates unsustainable growth. The only thing immigration would support is below-livable wages.

Computers are part of automation, just like chainsaws. It's not a new phenomena. It's been sweeping through all industries the whole time.

The thing is, efficiency unveils new possibilities, and possibilities induce demand, consumption. We are much more efficient than 10 years ago, but also consume at a much faster pace.

"Big JS app"'s aren't that big if done correctly. The entirety of Angular8 fits into ~170KB, less than some thumbnails.

You can write bad apps in any language and environment, similarly a site/app is not bad just because it's done in Y.

I believe the government already has the right and power to control what people eat. People form the government, and people (ideally) choose the people to hold that power.

In part I, too have the right to control what people eat through voting.

I don't think people will stop consuming meat if you ask them nicely. You have to make decisions that will hurt the meat industry and make it infeasible.

This would likely best be achieved through slowly dropping tax incentives, and transferring them over to alternatives so that people have something equally economical to today's meat.

Connectivity is not always available, and errors retrieving it may mean you have to re-enter everything. Being able to "navigate" the site without the dinosaur is a tremendous boon for end users. You wouldn't be able to send anything without a connection, but you could buffer it for an opportune moment.

Sites like HN and Stackoverflow have a vastly different audience than most bread-and-butter sites, and tackle different kind of issues.

There is a free version of MySQL called MariaDB. PostgreSQL is a very viable alternative.

It has different philosophy, and needs a little getting used to, so it's not as easy as simply lift-and-shift

PHP serves most of all web traffic: https://w3techs.com/technologies/overview/programming_langua...

Everything has an absolute complexity. You can't get rid of it, just move it around.

Page refreshes can be a delta increment, it doesn't have to download everything again

>You can't physically swap out a processor while the system is booted and you can't swap a virtual processor either.

I think you can do that on multisocket systems:

https://www.kernel.org/doc/html/v4.14/core-api/cpu_hotplug.h...

Looking at the pricing at: https://www.backblaze.com/b2/b2-transactions-price.html

It seems that calling b2_delete_key is free. It's just not conveniently abstracted. Listing the items however if you don't already have a catalog is $4/M items

Why would you prevent sharing it when you're already double dipping by introducing a datacap?

When you do something, the cpu works at _full_ speed for a given duration, which is shown as %/time used. If you make a processor half as fast, all CPU tasks will be performed two times slower.

Not all abstractions cost anything, they're simply useful. In addition IDEs, compilers and other parts of the toolchain pump up the output quality significantly compared to what would otherwise be available at a given time.

Programming doesen't exist in a vacuum. It has real business constraints, and you simply cannot make a perfect program. You must make the right compromises in order to be succesfull.

Optimization is an easy trap to step in. You can take it up in other layers aswell, optimizing your choices about the choices to optimize | Ad infinitum.

At some undefined point you may realize that you are trying to solve an undecideable problem. You can spend an infinite amount of time, and not get an answer.

You cannot build an algorithm to determine the amount of time that an arbitrary problem can be solved in, or if it's solvable in the first place. You must make a choice based on imperfect knowledge.

Legacy code often ends up as such, because it was immediately available and immediately utilized. It worked then, and piled on functionality.

You don't see good looking legacy, because it didn't survive.

I think it's somewhat paradoxical: The software that gets delivered, produces value gets to live. The market prefers just-good-enough software

You can definitely go the other way to overthink a problem, even as high to induce the halting problem. Absolute optimization is mathematically impossible, and an imperfect choice has to be made at some point.

You definitely can, and that is being done at the moment. I'm reasoning that you could be doing so much more with much less effort and cost if you didn't have as stringent requirements. We should progress in all fronts, and not simply pile everything on one.

Most web tasks are completely I/O bound anyway, the significance in making the few business logic decisions is minimal.

Not a lot of people know there are some great utilities for emulating low/intermittent bandwidth and slow CPU on chrome

With the help of transport compression like gzip, the total size can still be reduced by almost the same amount even if you don't minimize it.

There are lots of other problems piled on web development that is strictly not their fault. The aging network infrastructure hasn't seen updates in sometimes decades, despite billions and billions of tax money poured into it.

You really should be able to get more than 3mbit/s in 2019. Pictures should be allowed to be more than a handful kilobytes in size.

Datacaps are a ginormous moneygrab with no basis on technology. Abolishing corrupt corporate brotherhoods would do much more good than inventing yet another band-aid compression/surveillance point to the mix.

Anything that becomes 19 seconds to become interactive on a flagship phone should be classified as faulty. It's not just unethical for people, but the environment. It's badly written code that is basically turning your cpu into a space heater.

I'd argue that there is a certain amount of complexity that cannot be avoided, and is likely already addressed in the current platform. You can try and shift the problem to different parts of the application, but that is at best a distraction.

There are certain tasks that you simply have to do yourself (understand the problem), and apply the solution accordingly as fast as you can.

A house is built upon a thousand bricks.

I'd argue that "CRUD" apps are all there is in development. Everything complicated broken down comes to creating, retrieving, modifying and/or saving data.

After understanding the more exciting challenges, they become easy, mundane "crud" aswell. Gaining knowledge and insight is easy and fun; the value comes from effective application of that knowledge, which is tough.

It requires real endurance to bring something from start to finish in the real world, not all of it is fun. It is unavoidable.