I might give Backpack Battles a try. It doesn’t look like my usual style, but I heard there’s some good strategy under the surface, and I like that it’s made with Godot.
I might give Backpack Battles a try. It doesn’t look like my usual style, but I heard there’s some good strategy under the surface, and I like that it’s made with Godot.
After decades of license strangleholds by the likes of MPEG LA and Microsoft, it’s refreshing to see open codecs adopted in mainstream hardware and APIs. Hooray for progress!
I’m curious how long the current gen OLED consoles will be in use before they develop screen burn-in.
Or by people formerly paying for their internet service with money that should have been going toward food or heat.
Losing the $30 monthly discount could force families to choose between broadband and other necessities,
Exactly.
It’s also important to note that some ISPs created a low-cost service plan specifically for ACP. (It’s reasonable to assume this was possible in part because ACP handled income verification and eliminated the costs of individual billing and credit card payments.) That plan will likely disappear if ACP goes away, leaving poor people stuck paying a bill much higher than the program ever paid.
That’s as I expected; Thanks for confirming.
Unfortunately, that leaves out the kind of integration I was asking about (and the kind implied in this post), through existing Qt & KDE shared libraries and such.
CopperSpice might still be interesting for stand-alone projects written in C++, though, and I appreciate that you’re here engaging with the community.
I think you’re talking about migration from Qt to CopperSpipce, though, yes? I’m talking about integration with existing desktop environments. Making use of the themes that are already installed. Communicating with existing libraries via the existing interfaces. Are there any hitches to be aware of on that front?
And language bindings, for those of us who are trying to get away from writing in C++?
It’s an interesting project, but as a fork, I would be concerned about its compatibility with standard Qt & KDE libraries, widgets, and styles. Can you comment on that?
Also, what language bindings does it offer?
Linux has quite a few schedulers. The performance of this new one is almost certainly a result of different algorithms used, not an effect of refactoring the existing ones, nor the language it’s written in.
I don’t think I’ll dig in to the code just now, but if it turns out to have much practical value, perhaps we’ll eventually see an article about the design.
Seems like a weird headline. AFAIK, the language it’s written in has nothing to do with the performance.
Yes, exactly. So a standard compiler can be used, making language bindings much cleaner, while the runtime functionality and library compatibility are preserved.
And then there’s DQt, which uses DLang’s compile-time function execution instead of the meta-object compiler.
Qt is a wonderful GUI toolkit, but new language bindings are notoriously difficult, since it depends not only on C++ (which itself is tricky to bind into other languages) but also the Qt meta-object compiler. Even so, some interesting projects have emerged on that front. For example:
This (header-only) library can be used to create an application using Qt, without the need of the moc (MetaObject Compiler). It uses a different set of macro than Qt and templated constexpr code to generate the QMetaObject at compile-time. It is entirely binary compatible with Qt.
DQt:
DQt contains experimental bindings for using a subset of Qt with the D Programming Language. Qt is a library for writing cross-platform graphical user interfaces. Currently bindings exist for the Qt modules core, gui, widgets and webenginewidgets.
[…continuing…]
composable
, default_overload
, deprecated
, and protected
attributes
are supported in the IDL compiler.libwine.so
library is removed. It was no longer used, and deprecated
since Wine 6.0. Winelib ELF applications that were built with Wine 5.0 or
older will need a rebuild to run on Wine 9.0..seh
directives for exception
handling is required on all platforms except i386.The Wine team is proud to announce that the stable release Wine 9.0 is now available.
This release represents a year of development effort and over 7,000 individual changes. It contains a large number of improvements that are listed below. The main highlights are the new WoW64 architecture and the experimental Wayland driver.
The source is available at
Binary packages for various distributions will be available from
You will find documentation on
Wine is available thanks to the work of many people. See the file AUTHORS for the complete list.
--enable-archs=i386,x86_64
option to configure. This is expected to work
for most applications, but there are still some limitations, in particular:
ARB_buffer_storage
extension
support.There is an experimental Wayland graphics driver. It’s still a work in progress, but already implements many features, such as basic window management, multiple monitors, high-DPI scaling, relative motion events, and Vulkan support.
The Wayland driver is not yet enabled by default. It can be enabled through
the HKCU\Software\Wine\Drivers
registry key by running:
wine reg.exe add HKCU\\Software\\Wine\\Drivers /v Graphics /d x11,wayland
and then making sure that the DISPLAY
environment variable is unset.
HKLM\Software\Microsoft\Wow64\x86
registry key. The FEX emulator
implements this interface when built as PE.D3DXFillTextureTX
and D3DXFillCubeTextureTX
are implemented.ARB_fragment_program_shadow
.D3DXLoadMeshHierarchyFromX
and related functions support user data loading
via ID3DXLoadUserData
.bew-ID
, blo-BJ
, csw-CA
,
ie-EE
, mic-CA
, prg-PL
, skr-PK
, tyv-RU
, vmw-MZ
, xnr-IN
, and
za-CN
.zh-Hans
, are also supported on macOS.systeminfo
application prints various data from the Windows Management
Instrumentation database.klist
application lists Kerberos tickets.taskkill
application supports terminating child processes.start
application supports a /machine
option to select the
architecture to use when running hybrid x86/ARM executables.tasklist
application is implemented.findstr
application provides basic functionality.[…continued in a reply, due to Lemmy’s character limit…]
It would be nice to see the current trend of ever-increasing software bloat turn around in favor of better efficiency. Reducing our power consumption and replacing our hardware less frequently would definitely help the environment.
Your current approach of talking raw SMTP is likely to be more hassle than is worthwhile, and since the days of permissive SMTP servers are long gone, might not work at all.
Since you appear to be using an Debian-based Linux distro, I suggest this approach:
apt install dma
/usr/sbin/sendmail
command (which comes with dma or exim) to send messages from your scripting language of choice.If you prefer to receive messages as SMS, note that most major mobile carriers maintain an email-to-sms gateway for this purpose. Some web searches will probably lead you to the one for your carrier. They usually accept email at an address like 123456789@sms-gateway.example.com
Next step: Submit your first patch. :)
mileage may vary if you’re looking at cutting edge games, as driver updates can significantly boost performance in that case.
If you’re playing games in Steam, Flatpak, or any other tool that provides its own runtime, the graphics driver updates that tend to affect performance (e.g. Mesa) don’t come from your base distro.
(Unless maybe you have an Nvidia GPU and a distro that packages its proprietary drivers? I’m not sure in that case, since I quit Nvidia years ago.)
Any reason why I shouldn’t just go with Debian + KDE and install Steam?
No reason to avoid Debian unless you have hardware so very new that it requires the very latest kernel to operate.
If you go with Debian Stable, you can enable Backports for a fairly recent kernel, currently 6.5.10. You could go with Testing or even Unstable if you’re addicted to upgrading as often as possible, but chances are you won’t need to.
I’m gaming on Debian Stable with Steam in a flatpak. It works great, and is blissfully low maintenance.
At some point, you’ll probably run into people claiming that Debian is bad for gaming performance because of “outdated” packages. In most cases, those people don’t know what they’re talking about. I suggest ignoring them unless they identify a specific performance issue that actually affects you.
Joke’s on them. Google locked me out of my account when I refused to give them my phone number.
It’s also ironic in light of his history of loudly bashing linux and linux game development.
I can’t think of anything good to say about Tim Sweeney.