rdsubhas

There is no craziness here. It's a "Value rotation". Sell high, buy low, repeat. Capture a higher rate of return.

OpenAI just completed separating it's non-profit and for-profit restructuring: https://www.cnbc.com/2025/10/28/open-ai-for-profit-microsoft...

This probably means the for-profit structure will be going public in 2026, and there is probably a last private round happening.

Only time will tell if it ends like: "to avoid someone else shooting us, let's shoot ourselves".

Dedicated consortiums like CNCF, USB Implementers Forum, Alliance for Open Media, IETF, etc are more qualified at moving a standard forward, than ISO or government bodies.

The proportion of the utilities involved are a fraction of 1.4T.

A few more steps (<< post-covid << covid << zero interest-rate << ...) to understand that there is no reliable baseline for this use case.

This subset is not perfect, but good enough.

yes, and that my friend is how mini-shell-ansible usually begins :)

I used cgroups, lxc, chroots, self-extracting executables. I built rugged, portable applications for UNICEF laptops and camps before docker was a thing.

And I think this whole point about "virtualization", "security", making the most use of hardware, reducing costs, and so on, while true, it's an "Enterprise pitch" targeted at heads of tech and security. Nice side effects, but I couldn't care less.

There are real, fundamental benefits to containers for a solo developer running a solo app on a solo server.

Why? My application needs 2 or 3 other folders to write or read files into, maybe 2 or 3 other runtime executables (jvm, node, convert, think of the dozens of OSS CLI tools, not compile-time libraries), maybe apt-get install or download a few other dependencies.

Now I, as a indie developer, can "mkdir" a few files from a shell script. But that "mkdir" will work the first time. It will fail the second time saying "directory already exists". I can "apt-get install" a few things, but upgrading and versioning is a different story altogether. It's a matter of time before I realize I need atleast some barebones ansible or state management. I can tell you many times how I've reinvented "smallish" ansible in shell scripts before docker.

Now if I'm in an enterprise, I need to communicate this entire State of my app – to the sysadmin teams. Forget security and virtualization and all that. I need to explain every single part of the state, versions of java and tomcat, the directories, and all those are moving targets.

Containers reduce state management. A LOT. I can always "mkdir". I can always "apt-get install". It's an ephemeral image. I don't need to write half-broken shell scripts or use ansible or create mini-shell-ansible.

If you use a Dockerfile with docker-compose, you've solved 95% of state management. The only 5% left is to docker-compose the right source.

Skip the enterprisey parts. A normal field engineer or solo developer, like me, who's deploying a service on the field, even on my raspberry pi, would still use containers. It boils down to one word: "State management" which most people completely underestimate as "scripting". Containers grant a large control on state management to me, the developer, and simplify it by making it ephemeral. That's a big thing.

Problem: Trailing commas, key-quoting-rules, etc are a problem when generating JSON from scripts/templates - which is a key practical necessity for a Configuration language. Of course, you may already disagree here and say you don't have this problem, but it's a sufficient problem for everyone that there are many attempts to solve it. If you don't have this problem, feel free to ignore.

MAML: Takes JSON, makes trailing commas & key-quoting optional. One may not like it, but it does indeed solve the scripting problem, and it's a nice and novel idea. Thereby it's a "Superset" of JSON. All JSON is valid MAML, but all MAML is not valid JSON.

JSONNet: Also a good attempt, directly solving the scripting problem with built-in functions and so on. But can be overwhelming.

Other approach: A strict "Subset" of JSON. Every value MUST end with a comma, whether it's first or last. Every key MUST be quoted. Comments MUST be a valid JSON key-value called ".comment" that will be ignored at parsing but otherwise part of the JSON. JSON5 seems to be more suitable for this.

Backup works for a few outliers. But when everyone needs that backup at the same time, it's not a backup anymore.

From what we know...

- baseload electricity generation is not economical or practical (reactive) as a pure backup.

- a few grid-level mega-storage prototype projects, but nowhere near the scale of powering modern cities for a couple of off-weather days, or events where people congregate.

The hope is that – a combination of "couple of hours" of grid-level battery, and use that time to bring up a baseload. But the economics of that is abysmal (high capex/opex for what's essentially "hoping as an investor" for a few off-days so that this thing gets used after all). Those micro-nuclear-plants seem to still have a place.

As of now, grid as a backup is still only wishful thinking. Except for those who are already off-grid and changed their lifestyles to accomodate a few no-power days as a compromise.

The G now stands for GenAI.

To be fair, this is a daily life story for any senior engineer working with other engineers.

QUIC. HTTP/3. WebP. And more in this comment thread.

There were many discussions about this in HN too, and the general conclusion was Google wanted to force more Google searches, and the large general users of Chrome were fine with it.

> Any web request in my rails app could theoretically add new functions to any other class

Java Spring applications pretty much do the same thing (reflections, proxy beans, aop, JSON/Date serializers/deserializers, ORMs, etc are all compiled and changed dynamically upon route hits).

These things are theoretically possible (and happen) in any JIT language (node, java). Only statically compiled languages seems to be immune to this.

In most countries in the world, 24 hour time is just not human (user) friendly.

Programmer-friendly for debugging? Sorry No. I don't mind the extra T in between and I'd actually like to see the timezone or zulu in logs when debugging.

A counter view would be: it's half-human-half-computer inclined, but not objectively good for either.

Interest rate was hiked rapidly from 1% (in May 2022) to 4% (in Dec 3 2022).

Oct 2022 recorded the lowest for S&P 500 since COVID (till now).

COVID assistance was over. Vaccination reached a critical majority. On Sep 2022, Biden declared "COVID-19 pandemic was over" [1].

Businesses got a reality check.

1: https://en.wikipedia.org/wiki/COVID-19_pandemic_in_the_Unite...

I read the definition of "rely on" here as production outage, not operations.

For example: Say you use gmail and excel at work. If Gmail is down, your Windows PC crashed, or Excel does not own, the product (machines, websites, etc) do not stop working straight away. The specific term is unattended production hot path.

The 75% is already reasonably high when most production/industrial stuff runs on Linux or embedded derivatives. This shows the level of unattended production hot path on US tech.

An equally relevant question is, how is the support and maintenance story.

Or 23 years if the currency depreciates 2% each year.

Or 16 years at 5% inflation.

Wasn't the angular resolution solved by having spinning lidars?

They wanted to reduce congestion. Not eliminate traffic.

At that time. One can conclude the policy worked at it's time.

20 years later, today is a different day. One could say congestion is there today, but they can't say how much further congestion has been avoided.

Municipality can decide to reduce (not eliminate) it again today.

It is the laffer curve, in 3d (time).

Living in Germany, one of the things about DNS-level adblocking is: It SILENTLY obstructs a lot of the payback, reward and coupon programs.

For example, the biggest country-wide payback program is payback.de, and their most of their coupon multiplier links here – https://www.payback.de/coupons/info – will be clickable, but silently not work after you purchase.

Adblocking is good, but I prefer when it's controlled and I can just open an incognito window or disable it temporarily when I need them, for whatever reason.

Their network map promiscuously shows ZERO servers in Germany. They have in every other major EU country. I guess they have it this way to not follow this.

A &lt; Glass $gt; component that's an empty container everywhere else, except on iOS it a glass.

I had asked: In which cloud do you see CUDs being 70% cheaper for standard machines?

And the article has the standard machine spec, and the page shows clearly your information is blatantly wrong.

Fitting a different content into your own pre-set wrong mental model is not worth engaging over.

Yes, that's what the article is about.

And yes, the comment is confidently wrong as said in that page.

The article is about – saving 30% by switching from Spot to 70% more expensive VMs. It's the opposite of what you're talking about here.

> Switching to committed use nodes that can give customers up to a 70% discount?

This information is wrong. In which cloud do you see CUDs being 70% cheaper for standard machines?

Can you link any cloud provider's page that says – use "standard machines" for a higher discount than spot machines, it can be a productive conversation.

Yes. Prestop sleep is the magic SLO solution for high quality rolling deployments.

IMHO, there are two things that kubernetes could improve on:

1. Pods should be removed from Endoints _before_ initiating the shutdown sequence. Like the termination grace, there should be an option for termination delay. 2. PDB should allow an option for recreation _before_ eviction.

Give it to Apache Software Foundation please, with a good grant.

From the article:

> The contracts "represent non-essential spending on third party consultants" for services Pentagon employees can perform

Compared to every other developed democracy in the planet, the US is politically unstable with its two party democracy.

Trump is just a product of this right-vs-left volatile maximalism, represented as woke-vs-maga, which is fully on-track to get worse. Try guessing who will be the next woke maximalist and maga maximalist candidate, and what Executive Orders it leads to, which the US is pretty much ruled by at this stage.

Good luck with flip-flopping maga and woke Executive law as a country.