Why is this post titled "The Cascade"? Looks like that's the website title rather than the article title, which is The least amount of CSS for a decent looking site
A long time ago, maybe around 20 years, I did custom levels for RTS games and shooters. Earth 2150, Source engine, Serious Sam, Quake engine, etc. At some point I also did some 3D modeling. Then I participated in a Source mod community project, as part of a team; a Stargate themed mod.
More "recently", I created (an) Ultimate Tic-Tac-Toe (cross-dimension, cross-playing-fields tic tac toe), personal game jam project Energy Consumer (mainly a programming exercise given the limited time), game jam project with a friend Frogventure.
All other dabbling, interest, and ideas have not concluded in any significant development or products, partly due to lack of motivation and connection to people or people's interest.
We leave it to individual tools to decide on exactly what small means. In particular, tools are free to use different definitions in different circumstances.
What does this mean?
What does Linus when he says rustfmtcheck? cargo fmt check? A util I can't find with a simple search? Maybe they have makefile targets or sth for it?
The concerns raised by Linus make sense to me, but should be simple to solve. The small items description already mentions variance, and the need for tools to decide. So shouldn't it be a simple configuration change?
Create and use projects you have an interest or use in for yourself
Reading technical articles
Reading guidance docs (like Microsoft dotnet or SQL Server docs giving introduction to architecture, systems, approaches, behaviors, design decisions, etc)
Working with more experienced people - seeing them work, being instructed, reviewed, commented, guided by them
Experiencing alternative technologies and approaches
Experience in general
Exploring existing projects and their architectures
I don't know how far along you are in Python use. In general, I don't think Python guides you into good practice or architecture. It's too dynamic and varied of a language. You'll need a framework to be guided. Personally, I have a dislike for it for multiple reasons. Others seem to like it. Other languages and ecosystems are more limited, in good ways. (Maybe I'm misinterpreting "todays" Python, I've only peeking experience with Python.)
I would suggest trying out Go or/and then C#. Both are relatively simple to get into, and have more native/mainline frameworks and guidance. C#/Dotnet in general has a lot of guidance, documentation in broad and specific, and tutorials and sample projects.
I don't think 2% of M365 is necessarily bad numbers. Office is prevalent, for all kinds of and even the simplest of office work. Not everyone needs AI or has the technical expertise or awareness of what this offer even means. Some people may not have launched their Office for one or two years but still have a paid license.
There's also a free copilot for GitHub users, which may be necessary as a teaser and testing, and adoption. That may also offset "adoption" by measure of commercial licenses instead of active users.
I didn't like the initial focus on that number of sold licenses in the article. Of course, they expand upon it and draw a broader picture afterwards.
I haven't found anything either. Seems like it was an event and they just now announced it there. So it makes sense that there may not be any project page or documentation yet. Which is unfortunate.
And when you search for it you see articles reporting about this with titles like "it's finally here!". So stupid. Misleading.
In the afternoon, FSF executive director Zoë Kooyman announced an exciting new project: Librephone.
Librephone is a new initiative by the FSF to bring full computing freedom to mobile computing environments. The LibrePhone Project is a partnership with Rob Savoye, a developer who has worked on free software (including the GNU toolchain) since the 1980s. "Since mobile phone computing is now so ubiquitous, we're very excited about LibrePhone and think it has the potential to bring software freedom to many more users all over the world."
No links or references to the project. Seemingly no page on the website, or on the campaigns page [yet].
GNU Guix is a package manager for GNU/Linux systems. It is designed to give users more control over their general-purpose and specialized computing environments, and make these easier to reproduce over time and deploy to one or many devices.
I think it makes sense that publishers are required to update or at least assess games when open security issues come to their attention.
The current state is that you may have 20 games installed and 10 have not been maintained for a long time, and 5 have open security issues that an attacker may use. For example, a game launcher with service installs to program files with admin permission. And suddenly, you have a privilege escalation.
Or a game, when run, pulls in some monitoring, and suddenly exfiltrates data because that service is defunct and was taken over, or hacked.
The necessity is quite clear.
Maybe this will also push us towards more stable software, that changes less, or has less attack or escalation surface. That could significantly reduce maintenance burden - even if it ends up only assessing reported open vulnerabilities not affecting your product (because you don't make use of or open up the vulnerable functionality).
I find this kind of graph a bit misleading/ambiguous. I intuitively want to follow horizontal association between in and out. For example, Recruiter at the bottom splits into three at the bottom.
Not sure if there's a better way to do this. Disconnect in-bar and out-bar with a condensed point/circle to indicate non-conformity?
Concentric AI’s 2025 Data Risk Report found Copilot accessed almost three million confidential records per organization in the first half of this year alone.
Is this about a not-yet-published report?
They don't link to the report they are talking about, but only to the publisher. I can't find a report about Copilot risk.
There's a data risk report, supposedly updated twice a year, but from 2H 2023 (despite the web page being titled 2H 2025), and with no mention of Copilot.
There's also this blog post, which appears to connect their data risk report with Copilot.
The blog post seems a lot more concrete, specific, elaborate, approachable, and actionable than the Techradar post. To me, at least.
