not to mention that the government is already bound against using things it buys for unlawful uses. Its a totally redundant clause in a contract that OpenAI is touting to confuse people.
so any package could declare some modules as “use server” and they’d be callable, whether the RSC server owner wanted them to or not? That seems less than ideal.
> we implemented logic to prevent the node from going down at the top of a minute when possible since — given the nature of cron — that is when it is likely that scripts will need to be scheduled to run
Why not smear the start time of the jobs across seconds of that minute to avoid any thundering herd problems? How much functionality relies on a script being invoked at exactly the :00 mark? And if the functionality depends on that exact timing, doesn’t it suggest something is fragile and could be redesigned to be more resilient?
This seems like a tautology because what we think of as a good “experience” is something that lets us get our work done quickly. No one ever said a tool had great devex but was hard to get stuff done with.
I’ve worked at companies where they’ve done a “spring cleaning” like this, I guess no one thought to turn it into a branding pitch and call up the media though
The commitment from OpenJDK to continue to support the LTS release for a number of years longer than the non-LTS releases is pretty significant to a lot of companies using Java.