Also the fact that they have millions to bribe (or in friendlier terms "donate") their way out of anything, and have a network of very powerful friends and allies does not help at all.
Regulation should have started when the likes of Microsoft and Google started to become omnipotent and the big players in the Valley were not as powerful and influential as they are today. Now it's probably way too late.
If/when the AI bubble bursts, and the worlds economies crash, we might have a chance then.
Please, for the love of all things almighty, re-invest in your core IDEs. That's what you're known for, and that's what professional developers want.
I don't want a glorified text editor that does a few cheap tricks, and is 'AI first'. I know I'm going to piss off a few people here rubbishing VS Code, however people are blown away when I show them how much more powerful PyCharm is when debugging complex code.
Its embarrassing that there are many popular, numerously starred, issues across JetBrains' YouTrack that have been open for nearly a decade, that are already well integrated features in other, free, IDEs.
However all is not lost - you have a great suite of products that need much more tender love and care. They'll see you through.
You already have AI in the AI Assistant plugin. Make your core fleet of IDEs worth the investment, for new and existing JetBrains customers alike. AI, agentic or not, will only get programmers so far before it's time to toss the kids toys then break out the real tools that require human intuition, domain knowledge, and reasoning.
To pick up on one of the points in the article:
> Combining them in a single tool results in a disjointed experience, so the Fleet team chose to stop competing with IDEs and code editors and instead build a product focused on agentic workflows. This led to a pivot to a new product: an agentic development environment.
You don't need to develop an entire IDE/environment for this. Develop plugins/enhance the existing AI Assistant plugin for these workflows that integrate with your existing IDEs, 'the real tools' I was talking about above.
I feel like this new "agentic development environment" is making the Fleet mistake all over again, when you could be value-adding to your already great suite of IDEs directly by way of plugins, and also continue to refactor and improve your IDEs along the way.
A key part of secure systems is availability...
It really looks like vibe-coding.
It would require half of one distribution center of a major retailer.
That also meets the specifications of a clean room, and is actively maintained as one?
If OpenAI bought 40% of the annual capacity of finished memory, with the goal of using it in their server farms ASAP, that's one thing.
But unfinished wafers that still need to be protected to finish the manufacturing process, that OpenAI itself does not have any capability to do?
That to me looks like a preemptive strike against competitors, which also affects any other industry that requires RAM, in an attempt to develop a monopolistic position.
I can't see how this isn't a massive national security issue for any country that needs devices requiring RAM for new systems and maintenance of existing ones (pretty much all of them...) to manage critical infrastructure, national defence, public and social services, and so on.
It used to be pretty easy to just ban people from playing, now we're 100% reliant on their ability to do it. So we have anti-cheat which roots our computer, and still doesn't 100% solve the problem.
Make the anti-cheat follow one of the key tenets of cybersecurity: never trust user input.
Should work reasonably well for first-person shooters.
You're ranked based on the game's inner metrics, calculated on the server, rather than player-visible ones:
- time from observation to target contact with crosshairs (inc. standard deviation, standard error)
- % of time successfully striking specific hit boxes
and so on (depending on the game).
These rankings don't affect your public rankings but do affect who you're match-made with, or games that don't have private server options. Eventually you'll only be match-made with other cheaters, or players so good they give cheaters a genuine run for their money.
For games that do have private server options it could be configurable to:
- flag the player to admins as 'suspicious' for investigation
- Start ignoring hits that would've otherwise been successful for statistical outlier behaviours (where the statistical analysis indicates a significant disparity between observed and known-human-like reaction times and behaviours).
Even if cheats were used on the server, their
Probably:
- a couple of tower servers, running Linux or FreeBSD, backed up by a UPS and an auto-run generator with 24 hours worth of diesel (depending on where you are, and the local areas propensity for natural disasters - maybe 72 hours),
- Caddy for a reverse proxy, Apache for the web server, PostgreSQL for the database;
- behind a router with sensible security settings, that also can load-balance between the two servers (for availability rather than scaling);
- on static WAN IPs,
- with dual redundant (different ISPs/network provider) WAN connections,
- a regular and strictly followed patch and hardware maintenance cycle,
- located in an area resistant to wildfire, civil unrest, and riverine or coastal flooding.
I'd say that'd get you close to five 9s (no more than ~5 minutes downtime per year), though I'd pretty much guarantee five 9s (maybe even six 9s - no more than 32 seconds downtime per year) if the two machines were physically separated from each other by a few hundred kilometres, each with their own supporting infrastructure above, sans the load balancing (see below), through two separate network routes.
Load balancing would become human-driven in this 'physically separate' example (cheaper, less complex): if your-site-1.com fails, simply re-point your browser to your-site-2.com which routes to the other redundant server on a different network.
The hard part now will be picking network providers that don't use the same pipes/cables, i.e. they both use Cloudflare, or AWS...
Keep the WAN IPs written down in case DNS fails.
PostgreSQL can do master-master replication, but it's a pain to set up I understand.
> We are continuing to work towards restoring other services. > Posted 12 minutes ago. Nov 18, 2025 - 13:13 UTC
Now I'm really suspicious that they were attacked...
Edit: it was related
https://www.laprovence.com/article/region/83645099971988/pan...
Edit2: They edited the article stating it wasn't related.
Windows Recall.
VS Code forcing Copilot.
Windows forcing Copilot.
Office forcing Copilot.
Azure forcing Copilot.
GitHub forcing Copilot.
Outlook forcing Copilot.
Edge forcing Copilot.
You folks are insane.
Even though I don't use it, and have disabled as much Copilot functionality as Microsoft will let me.
I can't wait for this AI bubble to burst.