Yes, and English/natural language is not necessarily more concise than programming languages, if you need to describe something precisely.
For example, I was recently trying to get an agent to debug something which was difficult to debug because it ran in an exotic context, where debuggers and logging and printf couldn't easily reach. The agent kept coming up with more and more elaborate and smart-sounding theories and debugging strategies, but nothing worked. I stupidly kept going with this for like 20 minutes, until finally I just went into an IDE, did a simple "comment bisection" where I commented stuff out until I found the line that was breaking, and found and fixed the problem in five minutes. So I solved it by typing code. The code I typed: "//" (in about six places). I could probably have gotten the agent to do the same thing but would have actually literally had to type more to explain to the agent what I wanted. In fact it took me longer to write this comment describing what I did here than it did to just do it.
The barriers are the US demands that nobody should sell semiconductor manufacturing equipment to China.
Otherwise their memory manufacturing companies would be happy to exploit this opportunity.
Actually some Chinese companies already sell cheap DDR5 memory modules, but their production capacity is severely limited by the US blockade, so the cheap memories are available in few places, mainly in Asia.
So the high memory prices are caused by USA both by the AI companies that have bought most of the existing production and by the US government, who has sabotaged the Chinese memory vendors since a couple of years ago, in order to protect the market share of Micron (the US sanctions coincided with the moment when several companies, including Apple, intended to use the cheaper Chinese memories, so preventing this to happen seems a much more likely reason for the "sanctions" than the BS excuse that consumer DDR DIMMs and SSDs are dual-use products that may benefit the military. Even if that were true, the US sanctions did not prevent at all the Chinese from producing anything that would be needed in a small quantity, like for a military application. The sanctions have prevented only the mass production of devices using state-of-the-art lithography, which would have impacted the prices in consumer markets).
Startup costs measured in the billions, with no guarantee of success, and a long payback time horizon in a market that almost everyone thinks is - in one way or another - a bubble.
Oh yeah, the market is also getting intense scrutiny from powerful geopolitical entities that are quite explicit that they don't believe in fair play or consistent, stable rules.
I come into work and work on a 20 year old codebase every day, working on slowly modernizing it while preserving the good parts. In my experience, and I've been experimenting with both a lot, LLM-based tools are far worse at this than they are at starting new greenfield projects.
When it comes to professional development, I've almost never worked on a codebase less than 10 years old, and it was always [either silently or overtly] understood that the software we are writing is a project that's going to effectively live forever. Or at least until the company is no longer recognizable from what it is today. It just seems wild and unbelievable to me, to go to work at a company and know that your code is going to be compiled, sent off to customers, and then nobody is ever going to touch it again. Where the product is so throwaway that you're going to work on it for about a year and then start another greenfield codebase. Yet there are companies that operate that way!
On the specific issue of window corner roundedness, Windows 11 is great IMO. The corners are rounded when the window is floating free, but change to square when it's maximized or snapped to a side of the screen. The perfect design.
I've never really needed that, or I don't understand the need for there to be a difference. I typically tile windows into each corner based on how large I need them. When I need more than 4, I'll manually place them.
What I do notice is the wasted space needed by the entire window border to accommodate rounded corners and how annoying it is to grab a window handle in e.g. Ubuntu w/ GNOME because you're clicking/touching where the corner would be (but isn't, because it's round).
It looks like they were originally on Chakra (the JS engine used by IE9+ and pre-Chromium Edge) but added support for Hermes in 2021 or so and removed support for Chakra last year, so Hermes is now the only option. Edge moved to Chromium in 2019, so this means they actually kept Chakra around for a few years just? for React Native on Windows.
Id be interested in a source for both this and the parent's comment. How do we know which settings pages use which tech? Have people been decompiling them?
For example, I was recently trying to get an agent to debug something which was difficult to debug because it ran in an exotic context, where debuggers and logging and printf couldn't easily reach. The agent kept coming up with more and more elaborate and smart-sounding theories and debugging strategies, but nothing worked. I stupidly kept going with this for like 20 minutes, until finally I just went into an IDE, did a simple "comment bisection" where I commented stuff out until I found the line that was breaking, and found and fixed the problem in five minutes. So I solved it by typing code. The code I typed: "//" (in about six places). I could probably have gotten the agent to do the same thing but would have actually literally had to type more to explain to the agent what I wanted. In fact it took me longer to write this comment describing what I did here than it did to just do it.
reply