SF required application form, where you had to explain why you are worthy to have your git repo hosted by SF. By the time they processed it I already forgot I even applied. I think that was actual reason for them being destroyed by GitHub, that had simple, fully automated signup.
I think that is misinformation caused by circular logic. DDR prices stopped risking, simply because supply reached equilibrium vs demand and willingness of customers to overpay. The Micron stock price also had minor correction.
Suddenly internet is full of articles how it is all caused by TurboQuant release or OpenAI giving up on its huge wafer orders.
Looks very similar like attempts to explain random crypto price changes with any (un)related news.
The term I would use is "corner", as in "silver" and "onions". But there's a couple of distinctions:
- supposedly buying for their own use, rather than reselling
- bought as forward, rather than spot: much of what they've ""bought"" is a commitment to buy memory that has not yet been manufactured
> Will half the memory industry run into the ground because of the oversupply means their current production is unsellable?
They've seen that coming, this is why there isn't a massive expansion to meet the demand rise and instead they're letting "demand destruction" happen. A decision vindicated by the war, as well.
> supposedly buying for their own use, rather than reselling?
Do we know what they're using it for? I mean not reselling would imply the chips go on some OpenAI specific proprietary hardware directly, rather than it being sold back to OEMs to buy more GPUs or other off the shelf accelerators.
> They've seen that coming, this is why there isn't a massive expansion to meet the demand rise and instead they're letting "demand destruction" happen. A decision vindicated by the war, as well.
If you're a memory company, this sounds like making the best of a bad situation. not making more stuff despite demand far outstripping supply, just to prepare for the potential oversupply your customer can cause because they can walk back on their massive order.
If it is the AITA subreddit (or one of many similar ones) it might not be that bad. It is after all dedicated to outrage farming, so there will be many human responses. It is just the original posts that are all baits, and it doesn't really matter if they are made by LLMs or as a creative writing exercise.
Why would you compare Eclipse GlassFish instead to Payara or Wildfly/JBoss?
Anyway, that bickering between JEE application server vendors is what caused Spring to win. It doesn't matter it has update churn that is almost as bad as in JS ecosystem, just the fact you don't have to think about AS helped adoption. Well that and significantly easier testing. And Spring Data with generating queries from method names.
And you can't recruit people with JEE knowledge anyway, they all know only Spring.
Spring won. Why would anyone want to learn the standard aside from it being a standard that few people use? Spring itself is a wildly adopted standard. It is a semi open standard in that anyone can use it freely, but in that it's not supposed to be implemented by others.
The same is true for Micronaught or Quarkus. Learn the frameworks. But they are not a new open standard.
Yes please, though this is largely driven by my personal dislike of Spring Boot. The bloat and magic sucks so much of the joy out of programming to me. That said, I never lived in Spring Boot exclusively. I've heard people say that it's an "all in" kind of thing and once you go all in and learn the thing really well, you start to like it.
I'm saying the spec lost to Spring. There are many historical reasons for the loss, but Spring won.
It looks like the industry is moving away from architectures like EE. The desire now is more like a Go deployment: single, self contained deployable. There are make frameworks that support this goal. Maybe EE is one of them, but it's not essential like it was in the early 2000s.
For the most part, maybe like 99%, the Jakarta APIs are agnostic of what the deployment model is. They are APIs to validate input, service HTTP requests, store data in databases, look up roles, connect to identity providers, etc etc.
People like simple life with as few choices they have to make as possible, right? It's now very simple to start a Java project, when the obvious choice is Spring and everybody uses it.
But is it what everybody really wants? To have a single choice? GlassFish provides a choice for those that don't want to become stuck with the "only" option that everybody uses. Java itself provides a lot of options - Oracle JDK, Azul JDK, Corretto JDK and many others. And that's a good thing. Options in frameworks and application servers are a good thing too. The best option wins. Except, there's rarely the best option for every case. And it's good to have all the other options too, in case the most popular option isn't a good one for you.
I used to work for Red Hat middleware, and I love JBoss. Bickering is not why Spring did so well.
Spring just made things easy. It also had only one implementation, so you couldn’t be confused because a deployment descriptor worked on one platform and not another. Some random blog post on setup always worked when Spring was in use. If you were following a WebLogic cookbook, good luck on Websphere.
In the end, Easy always wins. Make something hard easier to use, the world will beat a path to your doorway.
I know right? Who wants sub-millisecond readiness, sub-second image replication and a measly couple of megs worth of memory alloc per service when everyone can just get themselves a 2 gig springboot heap by default?
FWIW Wasm is hitting kubernetes because that's what customers are explicitly asking for, and the majority of enterprise Wasm-on-k8s afopters are doing so precisely because they want to eradicate Spring bloat and the associated supply chain risks from their engineering orgs.
That whole feature is kind of paragraph 22. No legit/popular site uses it so users don't expect national characters in domain names, so no one actually hosts sites using "xn-" domains.
> To make error is human. To propagate error to all server in automatic way is #devops
I am not sure how AI agent variation of that joke would look like. Every now and then some blog posts lands on HN asking "Where are all new apps created thanks to LLM productivity boost"?. I am more surprised there are no news about some serious fuck-ups that can be traced back to LLM usage in code.
