The trade off has changed over time as memory access has become a bigger and bigger bottleneck. But caring about this is still "premature optimisation".
The claim of 20x program performance difference is overblown. Compilers can often remove virtual function calls, JITs can also do it at runtime. Virtual function calls in a tight loop are slow but most of your program isn't in a tight loop and few programs have compute as a bottleneck.
Measure your program, find the tight loops in your program and optimise that small part of your program.
* $200-400 million for equivalent onshore wind (they don't mention offshore wind which is more cost effective over it's lifetime)
* $1.5 billion for the SMR
Assuming solar and wind stay the same price for the next decade (which they definitely won't) that's a 4-5x construction price difference. The article didn't mention lifetime, decommissioning or running costs, which is likely a significant difference too.
If you have any unauthenticated routes that you don't want arbitrary websites calling.
> using JWT in a typical SPA <-> API scenario.
Is this typical? It's a pretty horrible setup.
Cookies have a lot of great features that 'store a JWT in LocalStorage' just doesn't have.
Sure, but the needle has moved. The thing that took you two weeks to write in 1987 isn't even considered anything useful by today's standards. The parsing needs to happen in real time, it needs to provide machine learning assisted auto complete, it needs a web UI and UI needs to show you an animated graphic of the scene you're describing, etc.
> All teams will henceforth expose their data and functionality through service interfaces.
> Teams must communicate with each other through these interfaces.
I read that as interfaces to the team, instead of interfaces to software the team is responsible for.
Something like Mechanical Turk(https://www.mturk.com/) but for internal team communication. I'm not sure if that was what was meant but that sounds interesting.
Amber Electric in Australia has this same model of passing the wholesale prices on to customers.
But they have a cap.
"We pass through the 30 minute wholesale prices directly, and this is typically significantly cheaper than the Government’s Default Market Offer, but to give you peace of mind we guarantee you will never pay more than the Default Market Offer (or VMO in VIC) over a year or we’ll refund the difference."
https://help.amberelectric.com.au/hc/en-us/articles/36003745...
I think this is only possible because there is lots of regulation on electricity providers in Australia.
> These companies are profitable, but only because the process relies on a supply of cheap fossil fuels. If solar panels supplied the energy, the extra costs and space for the energy supply would again cancel out the savings in terms of space and costs.
Given that solar has become so cheap that new solar is able to compete with existing fossil fuel power this conclusion seems outdated. Solar can be placed in many places where it's not possible to plant in to the ground and it also doesn't account for power from other renewable energy sources that aren't available to plants in a field ie. Wind and Hydro
> Don't force me to pay for your little communist ideas and then force me with my own money to pay more for the privilege to use my own car.
Parking and roads are massively subsidized by government taxes/council rates and are built in to the cost of all city real estate. Everybody is paying for your 'free parking' don't pretend that we're not.
> Trains and busses are fundamentally less convenient and useful than cars
This is only true for very low density areas which means low prosperity and opportunity. In any major city it's physically impossible to transport the majority of people to their work places in cars and impossible to store those cars for the work day.
Studies have shown that people are happy to use what ever transport is available as long as it's fast, frequent and cheap. For a high density city with lots of economic opportunities the only way to do it is with trains.
> Need to make enough parking available for a building.
In an apartment building I used to live in 1/3 of the building was parking. That means that each apartment was 1/3 more expensive than it needed to be. Even though I didn't have a car I still had to pay for the cost of the construction and maintenance of the 7 level car park. Everybody pays the car tax.
"consumerist capitalism is an environmental disaster" isn't a hard argument to make and people eventually realize most environmentalism is just stacking the deck chairs on the titanic.
This seems completely ridiculous. If it was profitable to do then companies would be doing it directly at the source of emissions more much efficiently.
This is what we do in Australia.
Government supported places in courses have a price cap, loans are CPI indexed and paying back the loan is scaled to your pre-tax income. If you earn more then you're required to pay back your loan faster. If you earn less than $40K, you're not required to pay back any of the loan.
>A good way to start would be to split up libraries. Instead of creating one big library that does everything you could ever possibly need, just create many libraries. Your god-like library could still exist, but solely as a wrapper.
This isn't it. It's literally what is creating the problem.
Small libraries mean duplication, a lack of shared abstractions and dependency hell.
The reason garbage collection was such a huge win is that before that every C library shipped with it's own completely different way of managing memory, that's a nightmare.
We need bigger libraries providing better abstractions that are reused through out and written to allow composition and dead code elimination('tree shaking' for the JS crowd) to work well. So you can opt in to functionality you need and opt out of functionality you don't need.
Communities working on big libraries can actually do good release planning, backwards compatibility and timely deprecations. React is a example of a library that does a really good job of this. All the smaller libraries in the JS ecosystem are the cause of the pain in modern JS development.