jayflux

It’s not windy 24/7, there are many days of low wind. You still need to take that into account, which luckily the govt are.

https://storelectric.com/dunkelflaute-energy-storage/

https://assets.publishing.service.gov.uk/media/677bc80399c93...

You are still going to need an energy source that you can “switch on” and balance the grid at times of low wind/solar.

You know it’s not sunny all the time, you don’t need me to tell you that, but it’s not windy all the time either. Batteries are a good investment but they can only hold hours worth of capacity right now not days.

So you have 2 options. Either invest in long term storage, or have enough nuclear around that can kick in when other generators don’t have much, or ideally both, which the UK is doing.

Both Hinkley and Sizewell are the right choice. They’re an upfront cost but once running are cheap.

https://storelectric.com/dunkelflaute-energy-storage/

You’re right a lot of this will be domestic lighting changing.

That said, UK manufacturing decline also correlates with this as that’s very energy intensive. Also don’t rule out fridges, old 90s fridges were very energy intensive compared to today.

> Improved efficiency is also supporting reduced use in the industrial sector – as has a general decline in GB industry and associated intensive electricity use

https://energy.drax.com/intelligence/2024-the-year-electrici...

> This is part of a larger trend. Demand has been falling by 5 TWh per year since 2005. Improving efficiency (lighting, televisions, fridges, etc.), fewer homes using electric heating, and deindustrialisation all play a part

https://reports.electricinsights.co.uk/?p=2065

He’s very popular in clacton and his odds to win are like 90%, I doubt anyone in his team are genuinely worried about losing.

> David who was at the BBC at the time suggested they use yellow balls instead

Apparently he didn’t explicitly say they should be yellow, he just said the white didn’t work, the ITF chose yellow after research and studies.

Ironically, Wimbledon was the last venue to switch to the colour, despite David influencing the decision to change it.

> In 1972 the ITF introduced yellow tennis balls into the rules of tennis, as research had shown these balls to be more visible to television viewers. Meanwhile Wimbledon continued to use the traditional white ball, but eventually adopted yellow balls in 1986.

https://en.wikipedia.org/wiki/Tennis_ball#

https://pressurebox.com/blogs/news/why-are-tennis-balls-yell...

> In 2022 is was £1.89 a litre and spent most of the year over £1.60 a litre

Why are you choosing the 2022 energy crises as your baseline? Not only your choice was arbitary but you managed to choose the year fuel was at its highest as a reaction to the war in Ukraine.

That price was not representative or typical, it was a spike. You can see it here.

https://www.ons.gov.uk/economy/inflationandpriceindices/time...

This was an intentional design decision. We wanted to make sure all the temporal types could be serialize/deserializable, but as you mentioned, you couldn't implicitly go back to the object you started with as JSON.parse doesn't support that.

Instead the onus is on the developer to re-create the correct object they need on the other side. I don't believe this is problematic because if you know you're sending a Date, DateTime, MonthDay, YearMonth type from one side, then you know what type to rebuild from the ISO string on the other. Having it be automatic could be an issue if you receive unexpected values and are now dealing with the wrong types.

There is an example here in the docs of a reviver being used for Temporal.Instant https://tc39.es/proposal-temporal/docs/instant.html#toJSON

What we’re seeing today with Windows is more representative of the times we’re living in rather than because of who’s the CEO.

I don’t doubt for a second Ballmer would also be jumping onto the AI hype train if he was still running the show.

Pretty much every citation added to wikipedia is passed on to web archive now, either by the editor or automatically later on.

For news articles especially the recommendation now is to use the archive snapshot and not the url of the page.

It’s not a perfect solution, but it tries to solve the link rot issue.

I’m sorry I struggle to understand your comment, but I’ll have a go.

> Saying “nuclear can handle the easy part” doesn’t help.

That’s literally how baseload works, look at France’s energy mix for an example, they have nuclear handle the bulk of their demand (at least the very minimum it will ever be) and renewables + transfers handle the rest, if renewables goes up they export it or lower their nuclear output (yes, their nuclear output can be modulated).

> You still need 20GW of extra capacity to cope

The goal isn’t to replace the entire energy mix with Nuclear, the goal is to add enough nuclear in the mix so that we don’t need gas being generating all year round (gas sets the price in the merit order so we don’t want it on 24/7). If you added just 6GW of nuclear you’d be achieving that on some days.

That’s quite an odd statement to make.

The UK certainly does have continuous demand, our overall energy demand has rarely fallen below 25GW in the past couple of years. Right now gas makes up for much of that, the goal here is to replace gas with nuclear, using gas as baseload generation isn’t wise long term.

Source: https://grid.iamkate.com/

That’s simply not true, or at least not today.

First of, the UK are investing in battery storage, there’s already a rollout of grid-level battery systems across the country*.

None of them hold capacity for longer than 2 hours before they need to start discharging. In fact, the record breaking duration is 6 hours. This is great as a short buffer, but it’s not “storage”.

To put this in perspective, last year the UK went 2 weeks without any significant wind, so a 2 hour buffer is nothing. This is why Hydrogen is still being kept as an option for long term storage.

https://stateraenergy.co.uk/projects/thurrock-storage

https://rhomotion.com/news/longest-duration-battery-energy-s...

The past year has been huge for conformance for us, not only we caught up with the top engines but we surpassed them when working on Temporal and having all tests pass for that.

We hope to wind down some of the conformance priority now and focus on performance, we need to work on a new GC, refactor some parts of the engine, and improve various areas.

The idea of a JIT has been raised and we’re not against it, but it’s not on our plans right now (because of the above), that being said there is an open discussion.

Hi all, wow was not expecting this to be trending right now.

I’m the creator of Boa, you can catch my talk about it at JS Conf EU 2019 https://www.youtube.com/watch?v=_uD2pijcSi4

That said, today Boa has a whole team of maintainers who I’m sure will answer some questions here.

Yes the name does invoke the sense it’s a Python project but I liked it and stuck with it, I saw a Boa snake at a zoo once and knew I wanted to name my next project after it, I was also inspired by Mozilla at the time who named their projects after animals.

Speaking of Mozilla, Boa’s existence came to be because at the time I was working on Servo and wanted to include an all-rust JS engine, one didn’t really exist so I set about making one as a learning exercise, after around 2 years more joined me on that journey and today Boa is around 8 years old. It is not browser grade (although at 94.12% it is more compliant than some browser engines) but that doesn’t matter, plenty of Rust projects have found good use for it as they find it easy to embed and use, so we’re happy.

One recent example is Biome who use it for their plugin infrastructure. https://github.com/biomejs/biome/pull/7300

Another recent thing which we’re very proud is seeing our implementation of Temporal be used in V8 and other engines, so we’re also helping the wider ecosystem and raising all ships! (More here: https://boajs.dev/blog/2025/09/24/temporal-release)

We do hope to improve performance over the next year or so, hopefully that answers some of the Qs here.

Transmission is a real problem and just like Nuclear, we haven’t improved it in the past 30 years.

So both eastern green link projects (offering more capacity) are due to be finished in 2029, “ok” I think.. “but surely we’re doing some work onshore to improve the existing network in the meantime..”

> Due to ongoing project work for increased power flow from North to South across two Transmission Owner (TO) regions and the interaction of the outage plans, increased capacity across the boundary will be limited and intermittent till 2029

So basically no transmission, onshore or offshore is going to be improved until 2029, but we’re still green lighting wind farms in Scotland. I’m amazed someone has the foresight to increase generation but not transmission until now, how were these green lit in the past knowing full well this bottleneck existed.

Maybe it’s controversial, but id argue for stopping more generation until transmission or storage is sorted or curtailment is going to be even higher in the next few years.

> Even if you’ve been doing JavaScript for a while, you might be surprised to learn that setTimeout(0) is not really setTimeout(0). Instead, it could run 4 milliseconds later:

Is this still the case? Even with this change? https://chromestatus.com/feature/4889002157015040

VS Code has had multi monitor support for a while now https://code.visualstudio.com/docs/configure/custom-layout#_...

One aspect I haven’t seen anyone mention contributing to the decline is GitHub (part of your “improved tooling”)

These days you can go to the repo and there’s usually already an issue open with the problem and a workaround. Or if someone has a question on how to use the tool/software they ask there.

Before GH boomed it was often SO doing this job.

I really think you’re trying to use the wrong tool for the job here. Joplin isn’t designed for your notes to be modified outside of the ecosystem, the notes themselves are markdown so you can export or transfer them, but you can’t simultaneously edit them outside of Joplin. For that you’re better off with a folder of markdown files which you can push to Git.

Joplin is essentially an open source version of Evernote and a great alternative for people who enjoyed that style of application.

I don’t think that’s the case anymore. I just popped on to newegg and scrolled through their “best seller” motherboards, none of them have PS/2 ports. They’ve started to die off on enthusiast motherboards for the past few years.

Its funny because I'm younger than you by a couple of years and I can remember the big parallel ports on keyboards before PS/2 became popular! PS/2 still feels modern to me in comparison

> The direct answer to your question is that the idea of "responsive" web design gradually took over when smartphones became popular. People liked the idea of not needing to create a separate mobile version of their frontend, and instead simply adjusting the styling and structure of the page in response to the size of the viewport.

Table-based layout was already falling out of favour before this happened. Even when you had fixed sites that were predominantly desktop, divs and spans (coupled with CSS) made life a lot easier to put things where you wanted them and lay out a site faster. It was also cleaner when reading the markup.

From what I remember, the move away from tables happened around the same time external CSS took off and you could partition your site with reusable styling instead of framesets or tables.

Responsive design then sped up the process a few years later.

In a speed running context, those saying “the streamers just need to save their best content and ditch the rest”.

I think this works if we’re assuming all those world record holders are still active, I can imagine many have gone on to other things or haven’t logged into their account in years.

So it will certainly need to be a community effort to try and preserve some historic runs done over the years. I don’t even know if footage can be archived if not owned by the original streamer

From https://www.carscoops.com/2025/02/tesla-recalls-380000-cars-...

> Tesla is rolling out an over-the-air software update for 376,241 EVs.

The media love headlines like this as people often envisage 100s of thousands of Tesla owners needing to send their car in. But in reality most of these “recalls” are a software update.

It’s a bit of an anachronism to keep using that word (in this context) and if people knew the reality the story wouldn’t be half as interesting as it sounds.

As someone who's bought and owned a Founder's Edition card (2080 TI) that's not true. They exist there's just very few of them and supply is limited. I don't think NVidia have much incentive to increase supply as most people buy the 3rd party ones instead anyway.

It's like saying the PS5 doesn't exist because you couldn't get hold of one when they first came out.

> For R&D and quick tests it is a very useful language feature to have IMO

Right, but unless you have an ftp server or quick ssh access and PHP isn’t doing any code caching that feature isn’t an advantage, how many developers are in that situation? Is this something you do?

If you’re running locally PHP spawns its own server which other runtimes have. If you’re running this on a server you’re most likely going to have app/code caching (apc Or opcache) switched on so you’ll need to restart the server anyway, in which case it’s not more advantageous than uploading a js file and restarting node.

> Easy to deploy: Upload files, done

I know people love to say this, but does anyone realistically make websites or web apps that way? No, not really. Even with PHP there are frameworks, there is a package manager, there is version control, and there are deployment systems.

Pretending that PHP developers are uploading a .php file to a shared hosting server (like in 2002) to suit the narrative feels disingenuous to me as it doesn’t align with what I see PHP developers doing at all.