The struggle is real. A lot of people think cloud lock-in is due to using cloud-specific services like SQS... but its the data. Try and exfil 300TB out of S3 without paying an enormous transfer cost =(
I want to move our infra out of AWS but at the end of the day we have too much data there and it is a non starter.
It's not heavy. The abstrations allow for consistent query compositions from reusable expressions. Demonstrate how you do conditional query building for everyone to witness the way.
Agreed. I am forcing myself to start using my iPad Air more and more but it generally just collects dust. The 10Hz refresh rate has made me want to look at getting a proper one with a fast display - but then I remind myself that it will also probably collect dust most of the time.
From what I understand, these press pools (specifically the White House press pool) began as what the author describes as "stenographers parroting press releases, not watchdogs holding government officials accountable". It seems like the administration is trying to mandate what was once the unstated agreement (that has since changed to some debatable degree).
I am personally unsure of the value of these press pools in the face of modern 'PR'; as far as I can tell, all they do is generate 'clippable' videos.
> I am personally unsure of the value of these press pools in the face of modern 'PR'; as far as I can tell, all they do is generate 'clippable' videos.
Very much the opposite - the press pool generates a massive amount of cross-verified content for distribution to all news agencies. The agencies then clip and edit and nip and tuck the press pool coverage as they see fit.
Obviously the press pool only gets all the talking points they want them to, but also the press pool is literally there following around the president all day, so it's also really hard to hide things from the press pool.
For example, the press pool knew of Obama's smoking or FDR's wheelchair or RFK's... indulgences. As part of the unwritten gentleman's agreement they never broke news on this stuff, but they were also witness to it and recorded it for later.
>I've held my Pentagon press pass for 28 years. For most of that time, when I wasn't overseas in combat zones embedding with troops, I walked the halls, talking to and getting to know officers from all over the globe, at times visiting them in their offices.
Without press credentials, the above becomes impossible.
You seem to be under the impression that these folks sit in waiting areas until a "press conference" is announced, then copy down whatever some talking head says and publishes that and only that.
There may well be some who do so, but that's not journalism, friend.
The question is how choreographed the rest of their ‘access’ is. This author seems to think they were getting ‘real dirt’, but I suspect that the officers they were talking to were actually walking a highly political tightrope in hopes of advancing their own careers.
My suspicions are based on listening to many podcasts with ex-military officer guests, and what they’ve said about serving ‘pentagon tours’, being publicity/public affairs/media officers for their units, and speaking with the press in general.
>My suspicions are based on listening to many podcasts with ex-military officer guests, and what they’ve said about serving ‘pentagon tours’, being publicity/public affairs/media officers for their units, and speaking with the press in general.
Which podcasts? Which ex-military officers?
That's not a "gotcha," I want to listen to those myself.
The Fighter Pilot Podcast is probably the best of them, both in terms of production and content, though recent episodes have drifted away from the ‘core content’ where it really shone. War on the Rocks has had some good ones as well, but not as interesting (in my opinion). There are many other military-focused and leadership-focused podcasts where you can glean something interesting every once in a while, but not really enough that I’d actually recommend following them.
edit: some NASA astronaut interviews contain interesting info about (retired) military astronauts’ careers, which tend to be interesting as well.
And these podcasts prominently feature ex-military officers saying they lied to reporters on a regular basis?
Can you be just slightly more specific? The two podcasts you actually named have ~650 episodes between them. Heaven knows how many are in the podcasts you didn't name.
I never said that I'd heard any officer state that they'd lied to a reporter. I said that I believe that access is/was choreographed (to present a certain narrative to the reporter), and that I don't think the reporters get the 'real dirt' from Pentagon access that they think they do (because most officers doing a desk tour there know they are walking a political tightrope).
There are definitely counter-examples (of officers who do spill real dirt to reporters), such as United States Air Force Colonel James G. Burton, but they are uncommon, don't seem exclusive to Pentagon-pool reporters, and there don't seem to be many these days.
I don't take notes on the podcasts I listen to, so I don't have episode-specific citations for you.
>I never said that I'd heard any officer state that they'd lied to a reporter. I said that I believe that access is/was choreographed (to present a certain narrative to the reporter), and that I don't think the reporters get the 'real dirt' from Pentagon access that they think they do (because most officers doing a desk tour there know they are walking a political tightrope).
>[...]
>I don't take notes on the podcasts I listen to, so I don't have episode-specific citations for you.
Fair enough and thank you for the references.
Like I said, this wasn't some kind of "gotcha" exercise.
Exactly. There was a story a few weeks back about a lot of the CDC top brass basically resigning in protest. I'm just thinking "yeah go ahead and pat yourself on the back with your NYT OpEd about your pyrrhic victory while RFK instills more whackos at the upper levels."
In this particular case, not even the bad guys (regardless of which side you consider them to be on) will take the job:
> No reputable news organization signed the new rule — not mainstream outlets like NPR, The Washington Post, CNN, and The New York Times, nor the conservative Washington Times or the right-wing Newsmax, run by a noted ally of President Trump.
This comes across as a 100% vibe-coded system that could really just be a table or two in a standard SQL database with some care taken with indexing and partitioning (when you reach that point).
What am I missing? What would compel someone to abandon a battle tested system like PSQL for a critical storage engine for this?
You can do an append-only table like this in any SQL database. You can use composite keys to achieve the query+natural sorting abilities over a single field. The effort to replicate this feature in any other environment is so minimal that it the 'vendor lock-in' makes this a non-starter in my eyes.
Hi - its not - more about 20% - for tests and non critical things.
Focusing on your abandonment part etc etc:
- Its not really trying to achieve that, this is simply a more efficient model, with a good storage coupling (for chat).
- What is being achieved here is a cohesive solution for chat specific workloads and optimising for it.
One of the benefits is speed (throughput, latency) - and very cheap calls.
More so - under sql, and for developers who have different demands and mostly changing demands - the effort is quite complicated situation (I speak from my own experience)
The focus here is a simple downmost layer - that allow all the varieties of top layers & requirements to be achieved easily.
In my blog post - i share a variety of these.
Also product is not ready - but thought i share this idea - as i think it can be of benefit to most devs who are starting out with a product.
You technically dont even need progressdb to achieve it - You can do it with a backend based pebble or rocksdb database.
Python is starting to feel a bit like JavaScript circa 2014. Remember grunt, gulp, webpack, coffeescript, babel? Now we've got pyright, mypy, pyrefly, black, ruff, ty, flake8, poetry, uv...
I used to find this kind of tooling explosion exhausting (and back then with JS it truly was), but generally speaking it's a good sign that the community is hungry to push things forward. Choice is good, as long as we keep the Unix spirit alive: small, composable tools that play nicely together and can be interchanged.
Interestingly besides typescript, javascript in 2025 is still super fragmeneted but by a bunch of well-polished tools that all do approximately the same thing. esbuild/vite(rollup)/trubopack(swc), prettier/biome/oxc, npm/bun/pnpm/yarn, bun/node/deno/worker-runtimes
It's just people refusing to use new tools. Prettier is so much slower than any Rust formatter, it's painful. `yarn install` takes forever. Why not switch to Bun? It's 5 minutes.
It's not really that bad. Unless you want to be adventurous you need these tools:
* uv: project management, formatting
* Pyright: type checking
* Pylint: linting (this is probably optional though I would strongly recommend it). Ruff is an option but I don't think it is quite as comprehensive yet.
There are alternatives for those tools but they are pretty clearly the best options at the moment. There's nothing in uv's league, and the only alternatives in Pyright's league is BasedPyright. Hopefully Ty and Pyrefly will be good options in future but I don't think they're ready for production use just yet.
A lot of the tools you list here are composable, mypy checks type hints, black formats code, because of the purpose and design ethos of those two tools they would never think to merge.
So which is it that you want, to just reach for one tool or have tools that have specific design goals and then have to reach for many tools in a full workflow?
FWIW Astral's long term goal appears to be to just reach for one tool, hence why you can now do "uv format".
I think that's the point. Every now and then a language will have a small explosion of new tooling, and all you can really do is wait for it to blow over and see what tools people adopted afterwards, it feels like Python is going through a period like that at the moment.
I want to move our infra out of AWS but at the end of the day we have too much data there and it is a non starter.