minimaul

At the moment, the closest thing AMD has to efficiency cores is Zen 4c - and it's really not an eco core in the traditional sense.

https://www.techpowerup.com/310057/amd-zen-4c-not-an-e-core-...

The power draw on these compared to AMD feels absolutely bizarre - in an age where we're supposed to be trying to conserve resources, it feels ridiculously wasteful to burst up to 430W [1] for minor gains. That's over 200W more than the approximately equivalent AMD chip (the 7950X), for practically no performance over it.

1. https://www.anandtech.com/show/21084/intel-core-i9-14900k-co...

Ah, I’m installing from an image of the CD I had as a child ;) probably explains the differences!

https://packages.debian.org/search?keywords=Cockpit&searchon... says 188 to 287, for versions I’ve used.

My experience of running Red Alert 2 on modern Windows is pretty horrific, and it looks like it’s shared by a lot of people: https://www.pcgamingwiki.com/wiki/Command_%26_Conquer:_Red_A...

More generally, I usually have more success running older games under Wine than on Windows 10 or 11 - DXVK helps a lot with early directx9 games in particular, in my experience.

I've not noticed any dependencies on NetworkManager when using Cockpit for VMs on Debian? My servers configure their networking using Debian's usual ifupdown, and NetworkManager isn't even installed!

It's a very useful tool to manage libvirt + KVM remotely without trawling through poorly documented XML, it's accessible from any platform - even an iPad, and it requires next to no setup (basically install the package and add a cert and you're done).

I consider these big pluses, I use Cockpit on Debian on my servers that run VMs rather than something like Proxmox, because 1. it's much less invasive, 2. the machines tend to run other things too, like docker containers.

Have been using it for this since ~2019.

The stats views are useful too, but I wouldn't install it for that on it's own.

edit: and honestly, there's not another good (maintained!) option that fits the niche of 'let me create libvirt VMs from a web browser on a single machine without taking over my whole system'.

Much better now :)

Thanks for taking that onboard and resolving it.

Or, perhaps, there are more nuanced reasons?

I had a pair of Sony WH-1000XM3. The earpads collapsed quite badly after about a year of constant use at work, and the inside of the (very shallow!) ear cups starting pressing on my ears, which ended up being painful to wear for more than a few hours.

I contacted Sony, expecting to be able to buy replacement earpads like basically every major headphone manufacturer on earth supplies (yes, even Apple and Bose), and they informed me that earpads are not user serviceable and that I would have to send the headphones into their service centre for a paid for repair. The repair would have ended up costing more than a new pair of the same headphones from Amazon. I'm not replacing my headphones annually, it's ridiculous (both from a cost and a waste PoV).

I looked online and found replacement pads available from third parties, and tried a set of Dekoni pads, which noticeably changed the sound signature of the headphones and caused ANC problems.

So I started looking for a replacement, discounted Sony's line completely, and ended up buying AirPods Max from Amazon when they were decently discounted in a Prime sale, and... they're fine. ANC is competent, sound quality is reasonable, unlike the WH-1000XM3 when I want to move them between Apple devices I don't have to do the re-pairing mess or stop bluetooth from autoconnecting on my other devices, earcups are lovely and deep, and the pads are user replaceable.

They're honestly not a bad product, they're just a bit too expensive without a discount.

The swipe ads for digitalocean on this are tremendously obnoxious as they break back and forward swiping on Safari on iPhone.

That’s not okay, don’t do this.

But hey, it’s a way to guarantee that you’ll annoy people enough to not use it.

Adjusting front wing angle is standard practice during stops - they’ll certainly do it when they change tyre compound (eg from softer to harder tyres), and they do it quite often otherwise.

They have specialised tools to do it too!

And, each group is probably an order of magnitude smaller than the one before it - nearly everyone just uses their ISP's router.

A small number of people use routers you can buy from Amazon, or in a store.

A really tiny number of people use more professional equipment at home.

The problem is, most IT professionals fall into one of the smaller two groups, so they get more friction than others, and that leads to them having more reluctance to roll out v6 at work, etc.

I think there's largely three groups that home users fall into here:

1. people who just use the router their ISP provides

2. people who go and buy off the shelf consumer routers/wifi - eg Netgear, Linksys, TP-Link

3. the kinds of people who run home labs and use small/medium business targeted routers/wifi like pfSense, VyOS, Unifi, Mikrotik, or even things like Juniper SRXes etc.

The first group will get a 'blessed' and hopefully well tested IPv6 configuration when their ISP rolls it out, and I'd expect minimal problems there. Certainly haven't noticed anything big in the UK with some of our biggest ISPs rolling out v6.

The third group will inevitably have teething troubles, but v6 works okay on those kinds of platforms once you know how to configure it, from my experience.

The second group is where a lot of the pain will sit, imo. I've found consumer routers have really bad IPv6 implementations (things like broken prefix delegation, broken firewalling that can't be changed, IPv6 negotiation not working over PPPoE, weird RA settings, etc). The firmware on these kinds of devices is usually not great, and things like hardware acceleration engines in router CPUs are also frequently missing acceleration paths for v6 for things they already accelerate for v4. It will get fixed eventually, but it's going to be a pain point for a lot of years to come.

I seem to think that the primary UK mirror (http://ftp.uk.debian.org/) was problematic for v6 for a while? But these days the https://deb.debian.org/ mirror is really heavily pushed, and that one seems to work just fine.

edit: but this was quite a few years ago, from grepping my IRC logs, somewhere around 2016!

It's a little tricky - the more unique v6 allocations we have, the more complex routing gets, and the more resources it needs.

Having a ton of people/businesses with their own announced and unaggregatable /48s would add a lot of entries to routing tables.

The other common mistake is blocking ICMPv6 completely. This creates a really broken IPv6 stack!

edit: I've been running dual-stack with Windows, macOS, iOS & Linux for at least a decade now - I think it's closer to 20 years than 10! I've never seen it be like the parent post for my personal use, but I have seen it broken like that in places I've worked with incorrectly configured routers/firewalls.

edit 2: this isn't a good idea for v4 either, but it's less broken than v6!

However, Steam offers more eyeballs, and in particular, more eyeballs that actually buy games.

The extra 18% doesn't feel as unreasonable when you get to make a lot more sales.

I can confidently say I’ve never had these issues using firstname@firstnamelastname.co.uk and firstname@firstnamelastname.com…

Are you using an unusual vanity domain TLD?

Geekbench scores do not compare between versions - you have a v4 score for the MNT Reform and a v6 score for the M1.

I feel like the screen is far too high res for the GPU performance available - I’d love to be proven wrong, but I think this device will basically live on FSR2.

Honestly I agree with this.

When I was more junior, or not doing programming as a full time job, I was more motivated to work on personal projects. Now I am more senior and programming/managing people full time, I can't get motivated to work on code-related projects in my downtime. It sucks :/

BizHawk is basically a wrapper for other emulators, though. Essentially a fancy frontend.

Ah, I was thinking more about lock in as more of a hard technical lock in (where he talks about setting up new build systems, CI, etc) rather than a soft lock in created via a lack of education & understanding, but I can see how that can happen if people just use tools without understanding what they do. That's a fair point!

The section on Lock In effects makes little sense to me - if you look at popular .NET IDEs for instance, they mostly produce .sln and .csproj files - which is the defacto .NET standard, and works with the standard command line tooling. They're portable between IDEs, and you still produce .cs files with raw source code that you can open in any text editor.

It's similar with PHP via something like PHPStorm, Python via something like PyCharm - there's no real lock-in beyond personal habits in IDEs I've used.

More generally, in this space... using a text editor (with or without plugins) and using an IDE are both valid approaches. I do not believe either are fundamentally better than the other. Try both approaches and choose for yourself - it's all about finding what suits you as an individual and makes you more productive. You may even find that your choice differs depending on what software stack or language you're working with - mine does.

"Hot takes" aiming to belittle or degrade people that choose the opposite to you are unhelpful at best and discourage people from trying both options for themselves. No one is a worse developer because they like working with a simple UI with minimal distractions and separate tools for separate tasks, and no one is a worse developer because they like more integrated tooling with code suggestions, refactoring tools, integrated debuggers, etc.

At small ISP scales, the cost of CGNAT isn't too high.

Larger ISPs tend to be longer lived and often have large pools of v4 allocations that they didn't pay market rates for, so are happy to sweat long term.

Reasonably practical - this is similar conceptually to what a lot of v6 mobile networks do with eg 464xlat et al.

It’s cheaper to do v6 & CGNAT v4 at scale than just CGNAT v4 or buying v4 addresses.

Buying v4 addresses isn’t sustainable and drives the prices up long term.

CGNAT v4 at scale requires hefty and expensive translation boxes that have to keep growing with traffic volume.

Native v6 immediately takes the majority of your traffic - most of the big CDNs & content providers like Netflix support v6 already.

Half of the big four ISPs in the UK provide IPv6 now (eg BT, Sky).

Full dual stack or something like v4 CGNAT + native v6 is practical and works well where available.

Big CDNs and content providers typically support v6 - eg Apple does, Netflix does, Google does, the big CDNs like Cloudfront, Fastly, Cloudflare do.

Apple requires app store apps to function on IPv6 only networks since 2016.

The holdbacks are smaller ISPs, ISPs with big legacy v4 allocations, and businesses.

I see more pushback from MSPs etc on IPv6 (and practices like disabling it completely) than any other sector.

edit: for an ISP that enables IPv6, the majority of their traffic will pretty much immediately be over it, as a result of the big CDNs and content providers supporting it. This reduces load on compatibility mechanisms like CGNAT, which is nice too.

The most common use case is where ARM provide fully functional CPU core IP that you can put into your own SoC - in AWS Graviton's case that seems to be the ARM Neoverse line of cores.

You can also get architecture licenses where you can implement your own CPU core (from scratch, or by making tweaks to an ARM design) - Apple has one of these, but Apple is a special case in that they were one of the original partners when ARM was originally founded in 1990.

RISC-V on the other hand is an architecture that is open for anyone to implement, but the RISC-V foundation doesn't sell you a core design - you need to create your own, or find a partner to sell you one. It's also much newer, so there's less of an ecosystem around it compared to ARM.

Quite right - you can't infer performance from pricing.

We did some assessments of how well our applications ran on ARM and x86 based AWS instances, and quite simply it costs us less to serve the same quantities of end user traffic using Amazon's ARM instances compared to the x86 ones.