Kissaki

In Brief:

• Two motions regarding "artificial intelligence" and Large Language Models (LLMs) were voted on among Codeberg e. V. members and passed.
• We are promising to not use any of your data to train LLM and explain what the planned Terms of Use change mean for 'vibe-coded' projects.
• We believe that LLMs endanger the free/libre software ecosystem as a whole.

The blog/news post then goes extensively into where Codeberg understands itself to be in the development landscape, and their voting results. They present their interpretation of the current software development and hardware landscape under the influence of LLMs, and the consequences they take. And how it changes not only development in general, but FOSS collaboration and projects specifically.

To us, it seems ridiculous to see projects with a single developer and virtually no users consuming as much or even more resources than some of the largest community projects on Codeberg, which operate frugal with CI/CD and storage resources. We do not believe it is reasonable for Codeberg to invest our precious donation money into hosting of large ghost projects.

After loading a project, Cursor attempts to find git binaries at various locations including the current workspace. By creating a repository with a planted malicious git.exe in the root, the IDE will execute it with no user interaction and no prompting of the user. This occurs repeatedly on a cadence.

Andrew Kelley quit his job in 2018 to build a programming language. Eight years later, Zig powers Ghostty, TigerBeetle and Uber's cross-compilation. It's top 5 most admired on Stack Overflow. There's just one thing missing: 1.0. Andrew Kelley explains why.

Vitaly talked to Andrew about:

• Why Zig has no 1.0 after a decade, and why that's deliberate
• Why Zig left GitHub
• Why Zig banned AI from Zig
• What makes Zig better than C (and why every other C replacement failed)
• Andrew’s take on Open Source

It's a long interview, but I found it very interesting and worth it.

ColorSym is a free, open-source color-identification system that pairs every color with a unique, memorable symbol. When color alone isn't enough to tell things apart, the symbol does the job, so the roughly 1 in 12 men and 1 in 200 women with color vision deficiency can read your components, charts, or UI with confidence.

• https://github.com/luisfrancisco/colorsym
• https://colorsym.com/

When using Central Package Management (Directory.Packages.props holds package versions), package version declarations can remain after package references have been removed. The package versions are unused and misleading.

dotnet nuget why can be used to get a dependency tree across projects to answer how a package comes into the dependency tree. However, the extensive tree list result for a list of version declarations is not viable to simply determine what 'is in use' and what isn't.

I am sharing my Nushell snippet which answers the question of what is declared but not referenced:

# List Directory.Packages.props version declarations that are in no csproj
def "dotnet unused-dirpackprops" [] {
  let defs = open Directory.Packages.props | from xml | get content | where tag == ItemGroup | get content.attributes.Include | flatten | sort --ignore-case --natural
  let refs = ls **/*.csproj | get name | each { open | from xml | get content | select content | flatten | flatten | where tag == PackageReference | get attributes.Include } | flatten | uniq | sort --ignore-case --natural
  $defs | difference $refs
}

❯ dotnet unused-dirpackprops
╭───┬─────────────────────────────────────────╮
│ 0 │ coverlet.collector                      │
│ 1 │ System.Net.Http                         │
│ 2 │ System.ServiceProcess.ServiceController │
╰───┴─────────────────────────────────────────╯

Gaps: In this simple form, only covers the standard csproj package references. Package references included during build through other target or prop files are not covered (probably irrelevant for most users).

They go over how the web and frameworks decided against horizontal, apart from deliberate emphasis, they go over some desktop layout attempts, failures and successes (more of the same vs navigation), a chapter about (paper) documents as the source, and endless panes now using horizontal.

From the description:

Almost every screen we use is a landscape rectangle, wider than it is tall. And on almost all of them, the content moves vertically. Always down.

This video walks through a wrong question. If mobile scrolls down, why doesn't the desktop scroll sideways?

The question turns out to be wrong.

Chapters

• [00:00] Introduction
• [01:23] The Web Could, and Doesn't
• [03:18] The Microsoft Bet - Windows 8 "Metro"/"Modern" failure
• [06:18] What Makes a Difference - Layouts where horizontal works
• [09:14] Horizontal Scrolling as Emphasis
• [10:24] When Horizontal Axis Means Something
• [12:13] The Document Model
• [14:06] The Potential of a Glass Plane

References

• Tim Berners-Lee, Information Management: A Proposal, CERN, March 1989 : http://w3.org/History/1989/proposal.html
• Tim Berners-Lee, HTML Tags, late 1991: http://w3.org/History/19921103-hypert...
• Jeremy Keith, A Brief History of Markup, A List Apart, 4 May 2010: http://alistapart.com/article/a-brief...
• MDN Web Docs, overflow: http://developer.mozilla.org/en-US/do...
• Chen Hui Jing, The horizontal overflow problem: http://chenhuijing.com/blog/the-horiz...
• Beware Horizontal Scrolling and Mimicking Swipe on Desktop: https://www.nngroup.com/articles/hori...
• Responsive Web Design: https://alistapart.com/article/respon...
• Building Windows 8: • Building Windows 8
• Niri Wayland Compositor: https://github.com/niri-wm/niri
• macOS Spaces: https://support.apple.com/en-gb/guide...
• Myspace shows off redesign, promises invites soon https://www.nbcnews.com/tech/tech-new...