I've had best results with opencode. Running locally w/ 64GB RAM and Radeon 9070XT (16GB). NVidia should be easier (CUDA), I'm on Linux full time now but used to use WSL2 all the time and had all this working in it.
7,261 karma · joined May 7, 2013
meet.hn/city/gb-Cardiff
I've had best results with opencode. Running locally w/ 64GB RAM and Radeon 9070XT (16GB). NVidia should be easier (CUDA), I'm on Linux full time now but used to use WSL2 all the time and had all this working in it.
However, one thing in AI is that while the usage goes up extremely quickly, it tends to go down just as fast. I know a lot of companies that are in the process of switching from Cursor to Claude Code, so in 6-12 months I'm not entirely sure of the data quality/quantity.
Also I think it is telling that they are calling them SpaceX not X. The X brand is absolutely toxic, especially in enterprise.
If you're in the higher tax brackets this means a £200/month lease (say) ends up more like £90/month.
And because of the "new" £3kish subsidy the govt put in, the car finance companies seem to basically apply that as a big discount to the lease value (or it seems that way?). So you could get a brand new ~£30k EV with no upfront payment and a 2-3 year term for <£100/month including maintenance. Mine even came with a free car charger install at home.
So it's far better to sell EV below cost (Chinese or not) to get more sold than have to a pay £15k for an ICE car.
The Chinese manufacturers are arguably at double advantage here as they have more BEV to sell so it's far easier for them meet the targets, and they can 'sell' the excess to the Western manufacturers (and further subsidise their EVs!).
I'm not personally against it, I got a brand new EV on a lease recently for close to free after all the tax advantages, and it's not like the Western manufacturers didn't have time to prepare...?
You can keep the KV cache on GPU which means it's pretty damn fast and you should be able to hold a reasonable context window size (on your GPU).
I've had really impressive results locally with this.
I'd strongly recommend cloning llama.cpp locally btw (in wsl2) and asking a frontier model in eg Claude code to set it up for you and tweak it. In my experience the apps that sit on top of llama.cpp don't expose all the options and flags and one wrong flag can mean terrible performance (eg context windows not being cached). If you compile it from source with a coding agent it can look up the actual code when things go wrong.
You should be able to get at least 20-40tok/s on that machine on Gemma 4 which is very usable, probabaly faster on qwen3.6 since it's only 3b active params.
- Bitbucket workers are hopelessly out of date (self hosted). We've had to put so many random workarounds in especially for Docker, as they don't keep them up to date enough
- I have had a bug in JIRA for years where I can't reorder a new ticket unless I refresh the page
- Every new feature they introduce into JIRA/Bitbucket over the past couple of years just doesn't work.
- I tried their AI stuff on the free trial, didn't work at all, tried to cancel, can't cancel the free trial online and had to write a load of support tickets (of which the support ticket contact form bugged out multiple times).
Anyone have any insight into why things have got so so dysfunctional? Tech debt? Talent leaving? Both? Even 'bad' enterprise software tends to be able to keep the most basic features running, but Atlassian is a whole new category. If you check their 'community' it is just hundreds/thousands of bugs with workarounds.
But regardless I agree, I'm just saying that these kind of patterns _are_ needed in any moderately complex system, and taking the view that "it's great not to even have it" in the core framework is really strange to me. Esp given every machine I have these days has >10 CPU threads and it won't be long before 100+ is normal.
I use it all day every day with Claude Code. I sometimes wonder past code if this has had the biggest impact on my day to day productivity, either having to make do with semi-bad looking reports or have a designer design them (which is slow).
Sort of feel sorry for Figma in a way though, given all the "partnerships" (highlighting their MCPs) and case studies they've done with Anthropic and then they release this. I note there isn't a testimonial from them this time.
I'm surprised how poorly Figma have used "AI" in general - given they were the "gold standard" in taking emerging technologies (WASM etc) and making an incredible product. The Figma Make thing was incredibly underwhelming, I managed to extract the system prompt out and it's basically just Gemini 3 Pro with a design prompt. Perhaps the original team has left?
They are extremely exposed imo. While all the UI/UX designers will continue using it for the forseeable, I strongly suspect a lot of their (A/M)RR was coming from extra seats for PMs, developers, etc to view and export and do commenting on the files - not core designer usage. I think a lot of this just won't happen on Figma as much.
What if you need to call multiple external APIs at once with complex json? Sure you can call them one after another, but if each take (say) 2s to return (not uncommon IME), then you are in real trouble with only one thread - even if it is just for one "request".
I guess I'm spoilt in .NET with Task.WhenAll which makes it trivial to do this kind of stuff.
Like you are not going to agree a eg 3 year supply deal with $SUPPLYCO at a significantly lower price than what you could get on the spot market for it (or what you could hedge out on futures).
Obviously there is some investment needed but if you take a look at the capex cost of the north Scottish grid upgrades PLUS the HVDCs it's pretty terrifying.
The idea is that the financing will be "paid off" after 35 years so it doesn't require a "guaranteed" price after that (it reduces finance costs significantly when HMG is underwriting the main payback period. I expect the remaining 25 years will be extraordinarily profitable for EDF. Even if there is more maintenance costs they will have no finance costs. And finance is the main cost of HPC (60-70% goes to interest payments on the debt).
I don't really agree with this 'declining grid' narrative the renewable lobby has pushed. Yes there is upgrades to be done, etc etc. But peak UK electricity demand is down from ~65GW to ~45GW (which may change, but doesn't look to be).
Nearly all of the cost on the grid is to do with renewables, not 'general upgrades'. We would not be building 10GW of HVDC from scotland to england. We wouldn't be doing a drastic 275kV -> 400kV rerating and duplication in the middle of nowhere scotland otherwise.
And there's no reason we couldn't have used other reactor designs, apart from lack of financing so only EDF gambled everything on the EPR for HPC (again) and failed to deliver on time/on budget (again).
>Hinkley Point C has a contracted price of £133/MWh. I imagine there's some risk-sharing and inflation in the contract so this will probably go up. Compare this to £65/MWh for new solar and £72/MWh for new onshore wind [3]. Plus of course that wind and solar projects don't take 20 years to come online.
In 2012 prices HPC was £89/MWh. AR7 is delivering (in 2012 prices) offshore wind for ~£65/MWh.
But regardless these aren't comparable at all, for the reasons I set out above. That £65/MWh often doesn't include grid upgrades (which aren't required to nearly the same scale for nuclear, as they tend to be nearish existing population/demand centres and have existing grid infra). AND you still need (expensive) backup for that wind. We are building (right now!) new gas peaking plants that are allowed by law to only operate 10 days per year. The cost per MWh if you include that capex is horrendous.
>Lastly, the only way the per MWh costs can even get that low is by giving Hinkley Point C a 60 year lifespan to amortize the cost over a sufficiently large timespan. It's likely that as the plant ages, operational costs will significantly increase beyond what's projected.
Not true, HPCs 'agreement' is for 35 years. After that they just get the market price, so it is not based on the 60 year lifespan per se.
And it's a relatively small amount of mass to ship - perhaps 500 tonnes of yellowcake for a reactors' yearly requirement.
https://www.gov.uk/government/publications/electricity-gener... https://www.gov.uk/government/publications/energy-profits-le...
And the reason Spain is so well insulated is because they have limited gas interconnection so they have a 'captive supplier' in Algerian gas. Algerian gas can basically only go to Spain, Morocco or the domestic Algerian market. They have some limited LNG export capacity (which is growing and will significantly change the price Spain pays longer term).
But it was incredibly dumb to build many GW of offshore wind in Scotland when the grid was already over capacity.
If you switched to 'people get paid what they bid' it's almost certain the market would just converge back to this anyway - but with a lot more gaming and guesswork (wind guessing the gas marginal price to try and get the highest price).
My guess is that £20bn/year is a fair cost overall in subsidy payments. This is clearly not offset by natural gas fuel savings even with elevated prices.
The UK IMO made a couple of critical mistakes. Firstly, far too much offshore wind is in Scotland when it should have been closer to population centres in England. A few factors for this but the issue is planning is devolved to Scotland (so they have every incentive to approve as many) but energy subsidies are set by Westminster. By the time UK central government realised this it was too late (or they didn't want to rock the cart for political reasons post/during Scottish independence referendum).
We're now having to pay £20-30bn+ to get Scottish wind generation down to England where it is needed (primarily through new 5 (!) 2GW HVDCs from Scotland to England). It would have been far far better just to... build those wind farms closer to England. This would have still required grid upgrades but far cheaper ones (bringing it 100-200km to population centres instead of all the way from Scotland, plus you still need to do the ones in England on top of that for the most part to get it from the HVDC landing sites to the population centres).
The second major issue is there is definitely massive diminishing returns from adding more renewables at this point. There's too many renewables on the grid a lot of the time, even if transmission was perfect - supply is outstripping demand. Instead of building more and more generation the subsidies should be redirected towards storage projects.
But overall, for the same £20bn a year you could have probably built 5 Hinckley Point C sized 3.2GW nuclear plants concurrently (assuming £4bn a year capex for 10 years). In 20 years you'd have probably 30GW of nuclear built, which should cover nearly all electricity demand in the UK in that time, with very limited transmission costs (existing nuclear plants have good grid connections and you build them close to them). And importantly, you would basically eliminate _any_ dependence on gas from the UK grid. Clearly nuclear has risks in project delivery, but at least it's reliable once built.
So it's really a non issue (XGS-PON is even better as more data per frame means heavy upstream 'clears' the frames quicker), IME consumer routers add more jitter themselves even with ethernet on the LAN side (and WiFi is a lot worse).
Obviously you're not going to lay fibre to the last 1% of population in the US (for the most part).
The Swiss use point to point fibre (there are a few small pockets of this elsewhere). But in reality it is very hard to saturate. XGSPON has 10G/10G shared between the node. GPON has 2.4gbit down/1.2gbit up shared across the node.
In reality point to point is not really a benefit in 99.99% of scenarios, residential internet use cannot saturate 10G/10G for long, even with many 'heavy' internet users (most users can't really get more than >1gig internally over WiFi to start with).
And if it is a problem there is now 50G-PON which can run side by side, so you just add more bandwidth that way.