technically, yes. but at the end of the day, in the real world, that app would work fine on ~all but ~1 desktop compositor
wayland doesn't require SSDs, because it's not just meant for desktop computing. in the context of desktop computing, it's been a standard for decades now to have a title bar on a window, so it does make sense that apps would assume they can get one without having their own drawing code or relying on a third-party library!
I don't have a personal Microsoft account, and have no desire to create one more account, but am required by my organisation to use 1 Windows-only software for 2 hours every week. As such, I run that in a Windows VM on my computer, and this doesn't seem like it'd be worth the effort of making a MS account
imo, that's why flat earth stuff usually doesn't make sense at its core. how do you explain that all those governments from around the world that hate each other all collectively agreed to lie to you
well, the point of flatpak is to have bundled dependencies so they run predictably no matter the distro
if one of your software's dependency gets updated, and your software isn't, you may run into issues - like a function from the library you're using getting removed, or its behaviour changing slightly. and some distros may also apply patches to some of their library that breaks stuff too!often, with complex libraries, even when you check the version number, you may have behavioural differences between distros depending on the compile flags used (i.e. some features being disabled, etc.)so, while in theory portable builds work, for them to be practical, they most often are statically linked (all the dependencies get built into the executable - no relying on system libraries). and that comes with a huge size penalty, even when compared to flatpaks, as those do have some shared dependencies between flatpaks! you can for example request to depend on a specific version of the freedesktop SDK, which will provide you with a bunch of standard linux tools, and that'll only get installed once for every package you have that uses it
for my use case, that'd be good enough, i don't want my school/building admins to snoop on the websites i visit, and don't want to fear academic repercussions for torrenting and such
though if you think your government is out to get you, then tunneling to another country is probably best!
"AI" today mostly refers to LLMs, and whichever LLM you're using, you'll likely face the same issues (wrong answers creeping in, tending towards mediocrity in its answers, etc.) - those seem to be things you have to live with if you want to use LLMs. if you know you can't deal with it, another rebrand won't help anything
i asked it to transcribe "zenquistificationed" (made up word) in IPA, it gave me /ˌzɛŋˌkwɪstɪfɪˈkeɪʃənd/, which i agree with, that's likely how a native english speaker would read that word.
i then asked it to transcribe that into japaense katakana, it gave me "ゼンクィスティフィカションエッド" (zenkwisuthifikashon'eddo), which is not a great transcription at all - based on its earlier IPA transcription, カション (kashon') should be ケーシュン (kēshun'), and the エッド (eddo) part at the end should just, not be there imo, or be shortened to just ド (do)
it is absolutely capable to come up with it’s own logical stuff
interesting, in my experience, it's only been good at repeating things, and failing on unexpected inputs - it's able to answer pretty accurately if a small number is even or odd, but not if it's a large number, which indicates it's not reasoning but parroting answers to me
do you have example prompts where it showed clear logical reasoning?
we need to have trusted sources, and provide sources for pictures and video the same way we've been sourcing claims
it doesn't matter if there's "a picture" of something, it only matters if it's "a picture taken by [specialist] published by [specialist institution]"