ARM Windows laptops are a pretty different scenario now than when the Surface came out. They have pretty seamless x86/64 emulation built in similar to when Apple started their Mac transition to ARM. In contrast the OG ARM Surface didn't run any existing Windows software.
Most people could pick up a modern Windows ARM laptop and everything they do would work just fine, just potentially with less heat and longer battery life than their older Windows laptop.
The primary annoyances would be Windows itself and its ad and engagement driven UI reminding you about Copilot and Edge every chance it gets.
I wouldn't call it "seamless"; a lot of Windows applications don't work. An example is some software packages common in the construction industry which want to install all kinds of ancient x86-only thing likes old ODBC drivers. So that wipes out one of the compelling reasons to have a Windows laptop. Quickbooks (Enterprise Desktop) is another example of one; not supported on ARM, although with some hacking you can get it to sort of work.
They've discovered that it's more efficient if the money flows directly from the private enterprise to the politicians without going through tax revenue.
There will be no single moment when that happens. It will be a stack of years and years of innovations and improvements each of which take time to roll out into mass production, start expensive, and get cheaper.
Then, write your "breakthrough" article when they get to mass production. (Ok, you can write the article when they demo it as the consumer show six months before availability, if you really can't help. They won't ship it in six months, they will ship in a year, maybe that's fine.
I'm a software engineer, I'm not going to lecture anyone about optimistic release dates.)
Write another one when they find a way to make it affordable to the average consumer.
I m asking : don't write it when it's a proof of concept in the lab, or when you just started the workforce that's going to contemplate thinking about thinking of a plan to build a pilot plant for the alpha version of the prototype. I'm sick and tired of those.
Same thing if your "breakthrough" is in curing cancer or making fusion. Please stop using this word. It does not mean what you think it does.
Well except that there were incidents of cars getting stuck in floods with passengers before they paused the service.
A closer analogy would be ""Chicago O'Hare pauses flight departures due to a winter storm after 3 planes slide off the runway due to ice"
Absolutely I think there will be a disconnect between when people think they should be able to drive somewhere (ie to work in a no-visibility blizzard) and when ideal self-driving cars would allow themselves to operate. Maybe society will adjust to be more flexible to natural conditions, or maybe people will get frustrated and drive themselves into the poor conditions as always.
We don't like LLMs throwing giant walls of code in PRs at repos and expecting devs to read and respond to all of them.
That's kind of similar to written content being posted and linked. There's an expectation that you are asking someone to take time to read it, and with LLMs now the cost to generate things to be read is a lot lower but our attention and capacity to read them remains the same.
> We don't like LLMs throwing giant walls of code in PRs at repos and expecting devs to read and respond to all of them.
One giant PR versus dozens of smaller ones, what's the difference? LLMs are going to send it your way whether you like it or not. No one is going to argue that usage of LLMs is going to lead to less code that has to be reviewed than normal, are they? It's by design since you're able to produce more code now, remember?
> There's an expectation that you are asking someone to take time to read it, and with LLMs now the cost to generate things to be read is a lot lower but our attention and capacity to read them remains the same.
I could understand this argument if this had been a 500 word blog post expanded out to 50K words, but it's not. And who's to say the author didn't write most of it and just had an LLM do a little polishing?
I don’t like humans throwing accusations that something was written by an LLM if they don’t like it. The constant insinuations that us machines are the ones with poor taste is fookin’ tiresome.
They're all over the place in Mexico City. It'll be interesting as these EVs start to show up along the northern and southern borders traveling within the US.
The sad reality is how politically influential it will be for Americans to take a Chinese EV from the airport to a hotel in Cancun and say, "Why don't we have this in the US?"
Well currently commenting on PRs isn't working. I'd say we notice this kind of issue once every few weeks or so. It's not the end of the world but also not great for a service that we pay for and which used to be more reliable.
They aren't going to let you advertise them as Steam-branded hardware without an agreement, but there are multiple handhelds that have done so to be branded officially Steam Compatible.
In this case, the issues under dispute are the cases where the trademark was used outside of the GPL-covered code.
Specifically the port author using the Notepad++ name and logo on their website, in addition to the photo and bio of the original Notepad++ author, in a way that could mislead others to think that this was part of the original Notepad++ project.
Hosting a copy of the GPL'd Linux code, represented as such, and making a website claiming to represent Linux or the Linux Foundation with Linus's face and name on it are different things.
Most people could pick up a modern Windows ARM laptop and everything they do would work just fine, just potentially with less heat and longer battery life than their older Windows laptop.
The primary annoyances would be Windows itself and its ad and engagement driven UI reminding you about Copilot and Edge every chance it gets.
reply