anyoneamous

Twist the rug into a mobius strip - then all problems can be considered swept under the rug (from an appropriate reference frame)

You say "police state", I say "government subsidized backups".

(e) Thousands of person-years wasted bickering over how real climate change is and what the magnitude will really be, when it ought to be obvious that renewable energy sources are preferable to non-renewable ones.

Over long journeys, those 3 nanograms really add up.

Are there really significant use-cases which require both a higher performance processor and GPIO pins? I imagine at this point there is value in splitting the product line to tailor towards "mini Arm server", and "IoT/robotics" users separately.

I love that Google are willing to such a big swing at Microsoft in the text of this announcement - I just wish AWS wasn't so badly shackled busy it's marketing and PR people these days.

Well, I'm off to learn about Apache Tomcat so I can be ready for 2025.

This seems like an opportune moment to remind/notify any fellow UK dark-dwellers that the NHS recommends taking vitamin D supplements here in the winter.

Scrolled the homepage until I saw "...earn a new digital currency" - then immediately closed the tab. Dead on arrival.

"Everybody" meaning "the normie plebs who work for a living".

Is it just a big power play that keeps rolling in the expectation of bottomless/infinite talenent and pepetual inflow/attrition?

This has always been my interpretation. The "everybody is replaceable" mindset comes from Amazon retail warehouses, and bled into the rest of the company.

The manager wasn't the one doing the forcing - the overall stack-ranking system was, and the manager was just employing the required level of doublethink to convince themselves the employee was both suitable for firing and also worth trying to retain.

I would think for companies default should be:

- Pay the tax we think you owe, or go directly to jail

- if you can prove later that you overpaid, we will give you a rebate on taxes over the next N years

- if the government is consistently getting your tax estimate wrong (in your view), then perhaps your tax-avoidance games aren't such a good idea after all

Regarding the linked page about containers: a major gripe of mine is when people make content which includes "don't do this part in production!" - but then never bother to explain what the production equivalent is. If it's out of scope for your guide then fine, but at least provide some keywords and links.

It feels like one of these days, if they keep trying, they'll manage get it past the experts/lawyers

I felt exactly the same way about Brexit; it was clear that if we voted Remain that Nigel Farage would still be there - alongside Maxwell's Demon - to shove us towards the door at the next opportune moment.

Seems like this is one of the hardest problems in modern politics - populists only have to win once, due to us having a complex system of preferential arrangements and one-way door decisions.

I am torn between wanting to read something which seems genuinely interesting and not wanting to waste time on a crackpot wall of text.

Whenever content related to Wolfram comes up there are mixed opinions about his genius - I wonder how much more impactful he could have been if he had a smooth-talking PR person filtering and shaping his output into a more digestible form.

As a HPC guy, I really like the idea of one or two of these racks serving as the cluster front end, providing the login nodes, controllers, etc. You would still need generic servers for the main bulk of the compute for density and cost reasons, but it would basically make the back-end part of the cluster into an interchangeable blob of cores, allowing us to focus on the interesting bits of running a service.

3 years ain't what it used to be - A100s were launched over 3 years ago and lots of people are still happy when they can get hold of some on AWS. People buying H100s now will very likely still be getting good value out of them in 2027.

We might be the world champions of pilfering stuff, but we really dropped the ball when it comes to teaching the rest of the world about the finer points of "finders keepers".

Respect can be earned through repeated professional and trustworthy behaviour - what you are talking about is fear.

I was an AWS employee too and found that people building services basically lived in a completely different world, hardly ever actuallyusing AWS - so I'm not surprised.

Solutions Architect Associate is the way to go - definitely the broadest coverage and most approachable. Won't get you a job by itself but I would find it a bit odd if I was hiring someone who works with AWS already and doesn't have this.

I had to stop reading after a couple of sections as I was worried the whole thing was a set-up to a "giving a FUQ" punchline.

Is it that folks are forced because the company's locked in or stuck on that platform?

Bingo.

Any other company and I might be excited, but Meta can get in the bin.

More than just office space, it is about the tax kick-backs that Amazon (and presumably their peers) have extracted from cities where their major offices are built. The cities offered the tax cuts or rebates to the company on the expectation that wealthy tech commuters would be forthcoming. Much like how Amazon has its cake and eats it via advertising revenue from its marketplace sellers, these companies have found a secondary revenue stream from their employees.

I read that as "Tolkien ring" - which would also be appropriate, since "...and in the darkness bind them" is a good summary of cloud vendor lock-in.

Straight to jail.

IME quite a few of those auto-generated docs (mostly the examples) have slight incorrectness, where the code snippet is a mangled mix of Python and TS.

Also, the tooling you need to drive CDK is all TS-based, which means I now need to think about NPM and Node versions occasionally, which are not relevant in any other part of my workflow.

Admittedly as someone in scientific computing I am unusually far from the JS/TS ecosystem - but all I can tell you is that it feels second tier as a user.

I see a roughly even split of people using CFn, Terraform and (Python) CDK.

AWS shot themselves in the foot by making the Python version of CDK second-tier after Typescript; IaC is still done by DevOps people far more often than application people, and DevOps people use Python.

Another gripe is the number of services and new features which launch without CFn support, which also blocks CDK support; when Terraform supports a new platform feature before the vendors own tools do, that's a sign the product teams are being driven by the wrong metrics.