If you switch IPs you can usually get a message or two through during these outages. This has been a consistent issue with Gemini for the past few months, but has increased in frequency and duration of outages, especially since 3.5.
Early on this outage it was just the 3.5 pro models affected, then flash started having issues, and now flash-lite is not being responsive.
Slightly related, but has anyone else using the gemini cli noticed that over the past few months, usage of the Gemini 3 pro models frequently times out or hangs? Antigravity cli has been better about this but the quotas are just so low with the 5-hour window bs.
On the other hand, seperating concerns by process boundaries leads to more secure, composable and stable code. By not reinventing the wheel, you avoid a whole class of problems. Of course a stable API or library might be better, but convenience always wins out.
The difference is apple doesn’t let you modify your device to use other services. Their contractual obligation goes beyond the service itself. That’s why EPIC won this case.
The reason I brought up roomba wasn't to talk about Lidar or vision necessarily. It's more a story about how the first-mover in a technological space became entrenched in what works and became resistant to investing in newer technologies. The result was rival companies taking away marketshare from a market roomba once defined. Roomba has since incorporated lidar and other innovations after being stagnant for a decade, but its too late - their competitors now dominate the market.
To complete the analogy, Tesla is invested in vision-only technologies, while its competitors are making gains with Lidar and other tech that Tesla refuses to acknowledge. It's very reminscent of Roomba in the mid 2010s.
A fun anecdote - a lot of people may remember Roomba from forever back with their automated little vacuums. Roomba's market share declined significantly because they failed to adopt Lidar technology as quickly as their competitors, instead they depended on the bumper for as long as possible. This put them at a disadvantage in navigation and efficiency as their competitors started using Lidar. Combined with aggressive pricing from rivals, expiry of its patented roller in 2022, a weird insistence to not combine vacuum and mopping into one device, Roomba (or iRobot now) is a just little fish in the sea it made.
Ignoring 95% of a uniform market to target the 5% of users who all have niche and conflicting preferences is a ridiculous strategy for stability, growth, and profitability.
Only the first letter being case-sensitive is a major strike against readability, one of four major pillars. While I’m sure the Nim developers are probably used to it by now, it just seems like a bad design decision Nim is probably burdened with as the result of legacy/interoperabilty.
Even just reading your foobar example
at a glance took a moment for me.
And case insensitivity is also generally frowned upon. To have a language with both sensitivity and insensitivity is the worst of all worlds with none of the benefits.
If you want to understand why at a deeper level I would recommend reading readability or the case insensitivity sections in any programming languages book. Personally, I enjoy Programming Languages, Principles and Practice (Louden & Lambert)
EDIT: Yes, I get it, it doesn't affect YOU. But it doesn't mean it doesn't affect other people. Non-english languages and/or speakers are an easy example. It also eliminates a whole class of human error, and maybe that only affects non-experienced juniors, but they exist too. There are other issues with symbols being case insensitive and string values being case sensitive. If you want a practical example a classic one is HttpsFtpConn vs. HttpSftpConn
I agree that sometimes linters can enforce code styles that are more of hassle to deal with than offer any real concrete gain to new developers. But I disagree that only senior developers should use linters. Especially if you are learning a new language, it can introduce you to common conventions in that language, writing cleaner and more idiomatic code, and helps form good habits off the jump instead of building bad habits you will eventually have to change in a professional setting. Sure it can be overzealous at times, but I think on the whole it is a net positive.
I agree with you, and I think you have misunderstood the nuance of the parent comment. He is not letting google "off the hook", but rather being tongue-in-cheek/slightly satirical when he says that the reality is too troubling for google. Which I believe is exactly what you mean when you call it "anti-social-history, not pro-material-reality ".
The idea that “attention is all you need” here is a handwavy explanation that doesn’t hold up against basic scrutiny. Why would Google do something this embarrassing? What could they possibly stand to gain? Google has plenty of attention as it is. They have far more to lose. Not everything has to be a conspiracy.
Code generally does not enter the YouTube code base without a lot of review namely (1) performance tests and (2) code reviews from multiple teams. Lines like this almost certainly get flagged/increased scrutiny. It would be very hard to imagine multiple people didn’t know about this and assign the blame to a single person.
Yea, I don't imagine native stream parallelism will help when CPUs are already loaded. Presumably you're using Spring or Rx, in which case you probably can leverage reactive streams and/or Managed Blockers, but thats really just taking advantage of async patterns and not necessarily parallelism. The only case I could envision having a concrete benefit is if you used your own fork-join pool leveraging virtual threads instead of the global fork-join pool to prevent platform threads from hogging CPU, and then used reactive streams that leveraged the virtual threads. Although this would (theoretically) raise responsiveness, it would almost certainly come at the cost of throughput. All that is to say, parallelism generally only provides as much value as you have idle CPU cores.