I do not understand why you feel entitled to the domain. If I was entitled to the domain of every side project I had, I would be a multimillionaire in domain assets.
Middle class does not translate across the atlantic. Middle in the UK might be what an American calls upper. Upper class in the UK is reserved for royalty.
Also, classical middle class is shrinking. Middle class didn't use to mean people who would become poor after a few months without paychecks. There are people who consider themselves middle class, but whose wealth is actually negative.
Participants were instructed to maintain their current
dietary habits and physical activity levels for the
duration of the study.
My understanding is that creatine increases the amount of available energy for muscles to use (hence increases sports performance, training performance, and recovery) - not increase muscle growth alone. That said - it is an interesting study which helps decompose the effect, this shows that creatine likely provides no other additional benefits.
I will context virtually all. I have never had this come up. I suppose it depends on what products you're looking at, but buying pure creatine is easy.
Creatine does tend to get added to pre-workouts chocked full with caffeine, but stimulant free pre-workouts exist and you can always buy it in bulk seperately either in pill or powdered form.
Even writing articles on this stuff feels like insecurity. Just let the AI fad come and go; the real engineers will take what works and everyone else will fail. The tide goes in - the tide goes out.
I laugh at the vibe coding nonsense now -- yeah, a million people making tiny variations of the same crappy web games is not revelatory -- but it truly does feel like there are extremes that are just as harmful.
On the one side are the super enthusiasts who grossly oversell to try to seem innovative and "with it", hoping they can claim some land in the great new AI development world.
On the other side are the head-in-sand types who keep railing about how useless AI is, it's a stochastic parrot, only super juniors find it useful and it holds no value for the Super Novel Work that they engage in, etc. You see this sort of commentary on here all the time.
Right now it's somewhere in the middle. I find the tools extremely helpful in my day to day, and they've completely changed how I work, and the tools are growing more valuable with each passing week.
I've not run into anyone who says AI is useless. I'm highly critical of AI as an "everything machine", won't let it code for me and believe AGI is a pipe dream... and I still have incorporated it into my workflow as a rubber duck, idea soundboard and documentation search engine.
On the other hand I've run into way too many people (dozens in person, hundreds online) who are overselling AI, most with a direct financial interest as their motivation.
It's not true that the sides are at all balanced unless you create an extreme "anti-AI" side that doesn't exist.
> I've not run into anyone who says AI is useless.
There's a front page post on HN at least once a week about how AI is useless. And in the threads that aren't about AI being useless, at least one person who will comment that they are.
There are magnitudes more delusional or in-denial people underselling AI in hopes that they can create a reality and that the status quo remains unchanged (and they're probably sure that everyone impressed by AI assists all are really shills, bots, etc. It's a pretty classic cope mechanism). Magnitudes. Every discussion about AI on this very site, which presumably includes a higher than normal proportion of early adopters, yields the highly up-ranked "Sure it's useful for crappy developers, but not for me The Excellent Developer and my Extremely Novel Needs". Many, many devs on here last experienced AI development assists in the era of the first release of CoPilot, and carry all of those initial assessments forward unchanged.
These people absolutely dwarf the tiny number of social media agitators that ply the "AI has replaced devs! I am the 100X vibe coding CEO" type nonsense.
I think the problem is largely the enormous wealth extraction from the working class (this includes any working person, including high-tech and finance workers) to the old asset-owning class. Property prices (and rents) and income taxes are setup in such a way to effectively drain you of any potential wealth accrual. You simply cannot reach escape velocity in almost any job.
If you are a high-earning knowledge worker - you will be taxed to the pips, pay some of the highest OECD childcare costs, pay >= 35% of your paycheck in rent alone. The median house to median earnings ratio in even second cities like Manchester, Leeds and Newcastle are comparable to San Francisco. The older generation living an index linked lifestyle are completely immune to seeing these effects.
I've lived in the US too - there is a huge cultural difference in how house prices are treated. Even home owners bemoan high house prices, because they increase their property taxes. This is a huge cultural blind spot in the UK. And a similar system would be enormously helpful (but not exhaustive) in terms of incentives.
By house to earnings ratio beating SF, it seems you mean it's easier to buy there than SF (Manchester 7.1 to SF 10.5 from first Google results). That seems expected as SF is known to be expensive.
I encourage all to look up what a gene drive is - find replace all mentions of 'mosquito' with 'human'. This makes a nuclear bomb look positively provincial - all it would take is one disgruntled post-doc. Only by the grace of god...
I just looked it up. The process involves modifying a fertilized egg or embryo to create a founder organism. The gene drive is designed to be inherited by more than 50% of the organism’s offspring and propagate through the population over successive generations. Because humans have fewer offspring and longer generation times compared to insects, it would take many generations and potentially hundreds of years for a gene drive introduced in a single human to spread widely through the population.
I apologies for my other reply - which was flagged - perhaps I was rude. You are wrong because there are ways to introduce a gene drive through pathogens - e.g. you introduce a self-generating CRISPR payload through a pathogen vector for which it is possible to completely saturate gen 0. Source: I worked in a leading biology lab, with biologists actually performing this research.
If you can get a pathogen vector to infect all of humanity you already have just about everything you need to cause massive damage; the gene drive doesn't make this situation appreciably worse.
We are comparing guns and bullets. The fact that you can genetically engineer a pathogen vector to deliver a gene drive is not well known to the public.
But mosquitoes are super annoying, and the probably don't even know how to make nuclear bombs. I mean, lots of humans are annoying too, but not all of them. Every single mosquito is annoying, and they can't stop us, so, uhh.. let's do it.
Did you know that most people outside the US do not intuitively understand the arbitrary US delineations for North, South, West, Midwest? And yet, "they expect everyone to know they are talking specifically about..."
Apache Iceberg builds an additional layer on top of Parquet files that let's you do ACID transactions, rollbacks, and schema evolution.
A Parquet file is a static file that has the whole data associated with a table. You can't insert, update, delete, etc. It's just it. It works ok if you have small tables, but it becomes unwieldy if you need to do whole-table replacements each time your data changes.
Apache Iceberg fixes this problem by adding a metadata layer on top of smaller Parquet files (at a 300,000 ft overview).
I knot you’re not OP, but and while this explanation is good, it doesn’t make sense to frame all this as a “problem” for parquet. It’s just a file format, it isn’t intended to have this sort of scope.
The problem is that the "parquet is beautiful" is extended all the time to pointless things - pq doesn't support appending updates so let's merge thousands of files together to simulate a real table - totally good and fine.
Well… when Parquet came out, it was the first necessary evolutionary step required to solve the lack of the metadata problem in CSV extracts.
So, it is CSV++ so to speak, or CSV + metadata + compact data storage in a singular file, but not a database table gone astray to wander the world on its own as a file.
They probably detect this. Thats why the problem is solved after one to ten minutes according to the article. There's probably nothing they can do which wouldn't stress the disks more.
Probably sometimes, at least if we trust the article:
> In our experience, the documentation is accurate: sometimes volumes pass in and out of their provisioned performance in small time windows:
What AWS consider "small degradation" is sometimes "100% down" for their users though, look at any previous "AWS is down/having problems" HN comment threads and you'll see there tends to be a huge mismatch between what AWS considers "not working" and what users of AWS considers "not working".
Doesn't surprise me people want better tooling than what AWS themselves offer.
Author here - it's not that we're detecting failure better than they are (though certainly, we might be able to do it as fast as anyone else) - it's what you do afterwards that matters.
Being able to fail over to another database instance backed by a different volume in a different zone allows for a minimization of impact. This is well inline with AWS best practices, it's just arduous to do quickly and at-scale.
It's not just failure detection. A write to EBS is at least two additonal network hops. The first one is to get to the machine for the initial write, and the second is for that write to be propagated to another machine for durability. Multiply this by the number of IOPS required to complete a database transaction.
No offence to anyone who has drank the kool-aid with AWS, but honestly they're making a product *not* foundational infrastructure.
This might feel like a jarring point.
When you think of foundational infrastructure in the real world you think bridges and plumbing and the costs of building such things; which is stupidly high.
Yet when those things get grossly privatised they end up like Lagos, Nigeria[0].
Because there is a difference between delivering something that works most of the time, and something that works all of the time -- Major point being: one of them is obscenely profitable, and the other one might not even break even, which is why governments usually take on the cost of foundational infrastructure: They never expect to even break-even.
I think the more interesting part here (besides the fact that AWS SLA's sneakily screw you over and make it hard to guarantee static stability) is the remediation aspect.
This is a consistent letdown across most AWS products; they build the undifferentiated 90% of a thing, but some PM refuses to admit their product isn't complete, so instead of having optional features flags or cdk samples or something to help with that last 10%, they bury it deep in the docs and try not to draw attention to it. Then when you open a support case they tell you to pound sand, or maybe suggest rearchitecting to avoid their foot-gun they didn't tell you about.
reply