I doubt games will ever bother with direct support now that Proton works so well. Devs aren't going to release open-source versions of their game engines, and they aren't going to provide and support compiled versions for a dozen different popular distros. The glibc problem makes it really difficult to release binaries for Linux, and many of the containerized packages have performance hits or require external configuration due to their security model. It is just so much simpler to target Windows and make sure it runs in Proton/Wine.

I could honestly believe that they thought the "no generative AI" rule was about using it in the final product. The IGA clarifying that the rule means that you can't use genAI during the course of the whole game's *development* is insane since any developer using GitHub Copilot instantly disqualifies the game. I would bet that most of the entrants should technically be disqualified, but you'll never see anybody cop to using Copilot.

No, it definitely is a gray area. You right-click and see "Ask an AI Chatbot" in the menu? Some people here count that as not being opt-in and invasive because they can see the option, even if it doesn't do anything until you set it up or click the button to remove it. Hell, some people here on Slashdot will bitch and moan if the browser so much as pops up a hint asking if you want to enable some LLM feature. Even ASKING if you want to opt-in is too much for some people.

Some people think that they should not even be aware that a feature exists unless you search for it in the settings menu and enable it. That is "opt-in" for them. And for others, they don't view the browser exposing a feature stub or informing the user about a new feature as "opt-in" if you still need to take action to both enable and use the feature.

It sounds like this "kill-switch" is to placate the first group of people who don't even want to know the feature exists. It will most likely remove all of the dormant feature stubs entirely and the browser won't tell them about the features at all. I think that is perfectly okay.

It's pretty amateurish to introduce memory vulnerabilities with the "unsafe" keyword when there are perfectly memory safe ways to add memory vulnerabilities to your code (https://github.com/Speykious/cve-rs)

We shouldn't be giving kids iPads and Chromebooks in school. Every year there seems to be a new article about how kids have trouble getting jobs because they don't know how to even use Word on a Windows laptop. The basic corporate standard. We need to bring back the computer labs. Teach kids what they -actually- need to know.

I clicked on that and uBlock flagged it as badware. I looked into it and apparently it was bought by "LimeWire" earlier in the year and is uploading your files to the cloud. I would use one of the forks or alternatives like PairDrop instead of that.

It still upsets me that Swype is still the best keyboard, and that it can't really be used on modern Android anymore. No other keyboard I've found has embraced the extremely useful shortcuts that keyboard had. Did a word get completely mangled and you want to retype it? Tap the word and then double-tap the Swype symbol and it would select the whole word and let you try again. It is such a pain to do that on basically everybody other keyboard on Android. Copy/paste having shortcuts was also extremely useful (so you didn't have to attempt to long press on an input field), and having shortcuts around punctuation like 's and ? made it much easier to use proper English. It's just sad.

How is that relative? It literally won't do anything unless you trigger it to generate the preview. If you've chosen to generate a preview of a link, you've chosen to visit that link, and that is entirely on you.

It's not even that. It's a simple web page FizzBuzz test (print the numbers 1-100 on a web page when you click a button and do FizzBuzz-like things). We give them a day to do it and tell them that we will review what they write in the technical interview. People create elaborate solutions to impress, but I've noticed certain... trends in how they design it. And after the review, when we ask them to make it so the FizzBuzz factors are user editable on the web page, things always end up falling apart.

We provide a technical test in our interview process and we got all sorts of neat submissions but it always falls apart when we ask them to make changes live. I personally don't care much about somebody using an LLM if they can demonstrate that they are skilled enough without using one, and if they can demonstrate that they won't trust a result. In fact, at this point we ask about AI usage and have applicants ask it questions that we know will give wrong answers just to see if they can identify the problem and figure out how to resolve it.

Well, you can choose to just not install it. It doesn't ship with the browser and you have to enable it and download the AI model explicitly. But, you can go to "Tools > Extensions and Themes > On-device AI" and delete any AI model that you may have installed if you don't like it.

I mean, it doesn't even get installed until you choose to install it, and it can be removed at any time. I don't think having AI extensions that aren't shipped with the browser and need to be explicitly enabled don't really qualify as "bloat". This should just be an article about how their smart tab grouping feature is broken.

They make it clear when you install the add-on. It explains your highlighted text will be collected and sent and it requires you to opt-in before it can be used.

I would agree with that. It's anecdotal but I've noticed when using Copilot at my job that it usually gets me a "mostly" proper solution. But even getting you mostly to a solution can save you an hour or more of digging through documentation. "Hey Copilot, I have an Excel workbook in a memory stream. Load it up with the Open XML library, open up the Summary spreadsheet, and copy out the contents of cell D:3." AI bots are pretty good at crawling through lots of information and summarizing it; I've been finding them quite good at identifying which classes and functions you need to use in unfamiliar libraries. But, in the end, you still need a developer with enough skill to understand the provided solution and know where the solution was deficient, since, as I said, it usually just gets you part-way there.

They claim about 20% more battery life over the Pixel 8 when the screen is on. The 8 was pretty good already so I'm hopeful, but we'll just have to wait for reviews of the device.