Kissaki

joined 2 years ago
MODERATOR OF
[–] Kissaki@programming.dev 3 points 2 weeks ago

NFC Release 15, with an increase from 0.5 cm to 2 cm.

[–] Kissaki@programming.dev 2 points 2 weeks ago

I didn't add a star at the end for the word search, so at least for that example, the sarcastic ones were all 'amazingly' and consequently not counted, and the 'amazing' at the end seems literal. I haven't looked at any other cases, though.

[–] Kissaki@programming.dev 6 points 2 weeks ago

A Python-specific question is better suited to the !python@programming.dev community instead of the general programming one.

[–] Kissaki@programming.dev 2 points 2 weeks ago (1 children)

Glad you're so appreciative and worked through it! I gladly share, discuss, and respond.

I'll have to read up on palette filters. :) I do semi-regularly use ffmpeg, but palette filters are not something I have heard or used before.

I assume in this case it's a downsampling into fewer colors, evading the issues of almost-same-colors?

Especially given the last square/check pattern makes me thing of codecs splitting into square blocks and then encoding those. It could make sense that this division leads to different results for one reason or another, which then produces a check pattern without it being there before.

[–] Kissaki@programming.dev 10 points 2 weeks ago (2 children)

For comparison, "amazing" occurs six times.

[–] Kissaki@programming.dev 5 points 2 weeks ago

Only one of them barely reaching 200. For the size of the Linux kernel I find these numbers surprisingly low.

[–] Kissaki@programming.dev 2 points 2 weeks ago

I don't see a sharp drop as a sign of corporate oversight at all.

Stuff may be tackled en-batch. Or individuals can care. Or it can be an organic team decision or effort.

[–] Kissaki@programming.dev 2 points 2 weeks ago* (last edited 2 weeks ago) (3 children)

1, 2, 4, 5, 6 all look fine resized in the post and full size

3 looks fine full size but has slight visual artifacts resized in the post (check/square pattern)

I can barely see it on my monitor. So on worse monitors it may not even be visible. #272a31 vs #262b31

animated webp may also be an option

[–] Kissaki@programming.dev 1 points 2 weeks ago

[ADDED] This week’s flight comes with a delightful blast from the past and will play the Windows Vista boot sound instead of the Windows 11 boot sound. We’re working on a fix.

[–] Kissaki@programming.dev 6 points 2 weeks ago* (last edited 2 weeks ago)

"can not last" and "use when available" are two very different things.

I doubt people felt they wouldn't "last" - as in survive - an hour without internet.

[–] Kissaki@programming.dev 2 points 3 weeks ago (5 children)

The screenshot is from my desktop with wide enough screen on Lemmy web (programming.dev).

The issue is one of scaling.

When I open the image without being resized into the website layout, it has the following visual pattern:

When I zoom out to 50% it looks (almost?) fine

Did you scale the source with ffmpeg? Do you have a visual pattern in your console background? The simplest solution would be to have a solid color as background. The second best to render a small enough size that it does not get resized in the browser.

At 1920x1038, it's very big right now. I'm surprised the font is big enough to be readable. I assume you scaled it up or have a high dpi display resulting in this.

[–] Kissaki@programming.dev 3 points 3 weeks ago

You speak of consent, but then ignore the lack of consent. I don't get it.

 

A little wrapper for Hugging Face Transformers in C#. This is not a comprehensive 1:1 mapping of the whole HuggingFace transformers package, because the API is enormous.

If you need a specific feature, toggle or pipeline API clone this repo and make adjustments.

This project was created using CSnakes and will fetch Python, PyTorch, and Hugging Face Transformers automatically, so you don't need to install them manually.

Demonstration (Video) from MS Build conference

 

CSnakes is a .NET Source Generator and Runtime that you can use to embed Python code and libraries into your .NET Solution without the need for REST, HTTP, or Microservices.

Video Demonstration at MS Build Conference

 

Blog post text follow-up to the build conference video announcement posted here two days ago.

We are super excited to introduce a new feature that was released as part of .NET 10 Preview 4 that makes getting started with C# easier than ever. You can now run a C# file directly using dotnet run app.cs. This means you no longer need to create a project file or scaffold a whole application to run a quick script, test a snippet, or experiment with an idea. It’s simple, intuitive, and designed to streamline the C# development experience, especially for those just getting started.

In upcoming .NET 10 previews we’re aiming to improve the experience of working with file-based apps in VS Code, with enhnanced IntelliSense for the new file-based directives, improved performance, and support for debugging. At the command line we’re exploring support for file-based apps with multiple files, and ways to make running file-based apps faster.

 

Our 17.14 release of VisualStudio.Extensibility includes the following features:

  • Text classification support
  • Updates to the ShowPromptAsync API

This release also includes a previously mentioned change regarding .NET runtime management requirements. VisualStudio.Extensibility extensions are executed on a separate .NET runtime host, unlike VSSDK extensions which run in the same process as devenv.exe, using the .NET Framework runtime. Since VisualStudio.Extensibility extensions operate on .NET, we must adhere to the runtime servicing lifetime of .NET. Consequently, the VisualStudio.Extensibility platform will be regularly updated to advance to newer versions of .NET LTS. For more information on how this affects you as an extension developer or consumer, please refer to our documentation here.

Note: VS 17.14 was released 14 days ago. This VS blog post highlights and elaborates on this topic.

 

How do you experience good and bad reviews and feedback on your games? Are you ecstatic or proud when reading positive reviews? Is it difficult to read reviews listing a lot of negative points?

How does it depend on the proportion of your contributions to the project?


I've occasionally wondered about team titles, how individual developers feel when reviews turn out majority or overwhelmingly negative. For very small teams and individual devs, I've often wondered how they feel when receiving "negative" feedback, especially reviews pointing out many flaws.

Today, I posted a Steam review with a long list of things the title is lacking. Personally, I would have never released a title in that state, and for money. I feel bad about pointing out many flaws on indie titles. But I also see no way around it. It's only honest to list what I see and notice. For a review, honesty is key, and allows others to see these things that are not visible from a store page or game trailer.

I'm interested to hear your thoughts and experiences.

 

The comment does well in providing context and arguments.

Lets go back to the closest thing we have for requirements for this editor..Default CLI Editor - Feature Exploration!. This discussion was based on the current state of windows and was not concerned with UNIX.

Being a simple text editor, it should not hallucinate, it should not add text one did not type, it should not change the text that was typed. If the user typed a tab character, it was because the user wanted a tab character. If you want four spaces then type four spaces.

edit should by default work like the original namesake and not hallucinate or add characters that were not typed or make assumptions.

Where do you draw the line on "smart" features? Tab should not add indent spaces? Encoding or newline mechanisms? Determining EOF newline?

 

Almost four years after our reporting on the games industry's unseen crunch at outsourcing studios in SE Asia, Chris received an email that demanded we return to this story once again.

Reporting on a specific outsourcing studio with abuse, with occasional references to the broader industry and its dependence on outsourcing studios.

 

This release fixes some issues related to the Windows MSI installer and the Nushell winget package. macOS and Linux users are not affected.

 

I found the announcement (quoted in the article) interesting and worth sharing, even without knowing or seeing the game.

Excerpts (I recommend reading the full thing):

My primary inspirations were the Japanese living doll myth and my experiences urban exploring in Germany (many backgrounds were crafted from photos I had taken).

The final act obviously deals with a difficult topic, sexual assault. I wanted the ending to be shocking, that was intentional, but never to cause harm. Instead, I thought I had crafted things in a way that would act as a jumping off point for some difficult discussions.

Secondly, the girl was never meant to look underage. In retrospect, I should have been more careful to ensure there was no ambiguity. Because she’s a doll (not human), I didn’t consider the possibility of misinterpretation as thoroughly as I should have.

This was also written long before the #MeToo movement, and I was a lot less educated on all the nuances of topics like these at the time.

If I had written it now, in my mid-30s, in 2025, it would be very different. Still, some choices I stand behind:


Do you have experience representing difficult topics in art? Weighing or deciding on respectful or acceptable representations, on the degree of deliberately shocking or uncomfortable representation?

Or do you remember scenes in games or otherwise in art that you found uncomfortable or shocking? In a good (well-represented or tactful) way or a bad way?

 

The VS extension

GitHub Copilot app modernization - Upgrade for .NET is a public preview AI-powered experience that helps you bring your .NET applications to the latest version quicker and more confidently than ever before. Powered by GitHub Copilot and Agent Mode, it serves as an intelligent upgrade companion that understands your code, determines the right upgrade path, and applies changes step-by-step with minimal manual effort.

This public preview focuses on Core-to-Core upgrades, such as: .NET Core 3.x, 5, 6, or 7 → .NET 8 or .NET 9

If your solution is currently on .NET Framework (e.g., .NET Framework 4.8):

  • Use the existing .NET Upgrade Assistant to upgrade from .NET Framework to .NET Core (.NET versions 3.x, 5, 6, etc.).
  • Once on .NET Core, you can use GitHub Copilot app modernization - upgrade for .NET for the rest of the upgrade process.
view more: ‹ prev next ›