HN user

ErikCorry

1,077 karma
Posts7
Comments385
View on HN

I like the coins idea. I don't subscribe because I know I'll forget about it and it will turn into a recurring charge on my credit card. But I would buy $10 of coins, knowing the paywall just comes back if I don't buy more, and if I lose interest it won't keep costing me anything.

When I see the "$1 introductory offer" I just think they are trying to trick me.

Larry should be remembered for the development of "patch" more than perl. Without the concept of fuzzily applying patches to modified source files you can't have "git rebase" or "git merge".

The syntax problems are just surface. There are some real problems underneath:

Poor performance of the single implementation.

A single implementation.

Leaky ref counted GC, but 'luckily' the syntax for references is so clunky that nobody does anything complicated enough that it really matters.

Bolted on object oriented features that never got the love they needed at a time when oo languages were sweeping the world.

Most of the wizards decamping to a new language (Perl6) that was 'developed' for years without an actual implementation to keep them grounded.

The C++ GC is not for V8 code, it's for the users of the V8 API eg. Chrome (Blink). It's not being used for big internal systems like the compilers or GC.

V8 has its first module in Rust and I'm sure more are coming, but it's not necessarily an easy integration.

JS is a GCed language. Are there good examples of Rust interacting well with a GCed language runtime where it is able to free unreachable cross domain pointer cycles? Like a JS object that has a reference to a Rust object, which itself has a reference to a JS object. Add more steps and hopefully you can see that collecting such cycles is a hard problem. This is the problem the C++ GC solves.

By the way you can't always break cycles with weak pointers. The browser standards have semantics you have to adhere to.

I guess I'm using 'Nimby' in the wider sense to include all the red tape that slows down or blocks every building project in the UK. A project doesn't have to be individually targeted by Nimbies to be slowed down, they have enough regulatory quicksand to stop building wholesale. Then when you get through that, they can target your individual project.

And Nimby is politics, so I don't see a distinction between Nimby and 'purely politics'.

It's easy to blame project mismanagement, when it was always well known that undersea cables are much more expensive and difficult than the on-land cables that the Nimbies scuppered.

And it's unsurprising that windfarms in Scotland keep getting planned when the operator can collect these payments while switching off their turbines to reduce wear and tear.

Are you sure?

Despite campaigning for more data center development two years ago, not much has come to fruition in Scotland. In December of 2021, Oracle closed the Sun Microsystems data center in Linlithgow, Scotland. DataVita has opened a new data center in Glasgow in its parent company’s office development, as well as expanding its Fortis data center in August 2022. No major construction projects have been announced since the campaign began. https://www.datacenterdynamics.com/en/news/scotland-continue...

Why would you open a datacenter in Scotland when the UK rules mean the electricity price is the same throughout the UK, regardless of supply and demand? This is precisely the issue that OP highlights - the UK electricity auction is at a national level, but transmission is limited and the actual supply and demand is not evenly distributed, causing huge curtailment payments to have to be made.

It's not a real free market, though, if you ignore transmission. Since transmission is a scarce resource it needs to be part of the market to send the signal to build more of it (or more battery storage, or better located production). The national auctions obscure the actual resource shortage and therefore the market can't work.

You mess with the markets at your peril. If you pay people to produce electricity that can't be consumed then you will waste a lot of money.

If the transmission capacity is limited you need to expose that signal to the market, not attempt to hide it.

We choose to be transparent when we fix stuff, even if it makes us look a bit silly :-) . We are certainly installing more logging and tracking of this sort of thing!

In general I think the GC should auto-adapt as much as possible. It's a bit of an admission of defeat for the GC author if the users have to spend a lot of time tuning the parameters. What we are doing here is removing the tuning that was no longer correct, and allowing V8 more latitude to pick its own young gen size.

The problem is they are treating it as a free market issue with hourly auctions, but the 'free market' system ignores transmission. So the windmills can sell cheap electricity in the auctions that can't be delivered to anybody who needs it. Then after the auction you have to pay the windmill operators to switch off the excess production.

The OP linked site lists one of the solutions as "Make energy cheaper where supply is strong." This sounds obvious, but UK (and German) politicians don't want to do it, so we continue to get this dysfunctional system.

The Norwegian grid is divided up into different regional grids and they each have different electricity prices. Those who build interconnects between the areas can get some of the price difference. It's very different from the UK market, which pretends to have a single area, runs auctions to determine the price and then has to make post-auction adjustments (in the billions) to fix the fact that electricity can't be transmitted across the grid.

See https://app.electricitymaps.com/map/live/fifteen_minutes