Post AT5cOT53fH6NiReOSe by codewiz@mstdn.io
(DIR) More posts by codewiz@mstdn.io
(DIR) Post #AT3B0wsO9Cyw64MhSy by globalc@chaos.social
2023-02-24T11:29:08Z
0 likes, 1 repeats
You should know ~2000 Kanji - how to input these with a normal keyboard?An attempt to explain how Japanese input works:https://blog.fluxcoil.net/posts/2023/02/japanese-keyboard-input/
(DIR) Post #AT3B0xZzX5rOHIlWQi by laubblaeser@ruhr.social
2023-02-24T13:33:13Z
0 likes, 0 repeats
@globalc > The Latin alphabet which is widely used has just 23 characters, so normal keyboards simply map one letter to each key.Maybe I'm severely mistaken but last time I checked, the modern version of the Latin alphabet currently consists of 26 characters (which I can also all find on my keyboard). Why did you mention 23? This was only the case before J/V/W were added, so maybe a bit outdated.
(DIR) Post #AT3B0ybnhqtxTCcTtA by globalc@chaos.social
2023-02-24T20:51:31Z
0 likes, 0 repeats
@laubblaeser Right. I had 26 in mind too, looked at a reference which was old and seen 23 there. Thanks for the hint!
(DIR) Post #AT3B0zAtbMyTE32Vai by codewiz@mstdn.io
2023-02-25T21:20:59Z
0 likes, 0 repeats
Hey @globalc, do you use ibus or fcitx5? With mozc or kkc? On GNOME or KDE?@laubblaeser #japanese #linux
(DIR) Post #AT3Bxjn6RRY6bCvRmS by globalc@chaos.social
2023-02-25T21:31:41Z
0 likes, 0 repeats
@codewiz fcitx5/mozc/sway right now.Gnome is better integrated with ibus I would think (if it plays a role at all), as our devs are mostly working on ibus and Gnome is our default.Technically, also ibus/mozc or ibus/kkc would work now for me on sway.
(DIR) Post #AT3LGnNIEzZ6ns11ma by codewiz@mstdn.io
2023-02-25T23:15:58Z
0 likes, 0 repeats
@globalc I'm trying fcitx5 + mozc in Plasma Wayland on Fedora 38......and couldn't get it to work with KDE apps. Though it works in Gnome apps 🙃
(DIR) Post #AT3TGjngKUb5LoqGo4 by globalc@chaos.social
2023-02-26T00:45:43Z
0 likes, 0 repeats
@codewiz I recognized that I did not use so many bells and whistles from KDE.. and I do not miss upgrade to new major KDE versions and seeing things breaking which worked before. Sway has the functionality I need, does it fast, and is not in the way. :)Granted, getting sway with the input methods to run initially was not easy either, see my rants on Mastodon. But now all works nicely.
(DIR) Post #AT3kMpzbuxNVVxurSK by codewiz@mstdn.io
2023-02-26T03:57:18Z
0 likes, 0 repeats
@globalc The #KDE folks have been working hard to offset the reputation of releasing buggy software.#Plasma 5.37.0 was a particularly smooth release, the first one in which I didn't notice any regressions.There are a few of course, but they're being tracked and worked on aggressively:https://pointieststick.com/2023/02/24/this-week-in-kde-even-better-multi-monitor/#15-minute-bugs-resolved
(DIR) Post #AT3psdSiXayxgnVpNA by dropbear42@fosstodon.org
2023-02-26T04:59:04Z
0 likes, 0 repeats
@codewiz @globalc >#Plasma 5.37.0Ooooh! Is the Future a nice & kind place? 😜
(DIR) Post #AT4L61ByinvZd8Xncm by nanook@friendica.eskimo.com
2023-02-25T23:22:13Z
0 likes, 0 repeats
Actually there are approximately 50,000 Kanji characters, only about 3000 of them are in common use. One means is to use Linux's input method, it's been a few years but there was a way you could input the romanization and it would come up with the appropriate kanji character.
(DIR) Post #AT5HTJvR26StjRccS0 by globalc@chaos.social
2023-02-26T06:45:36Z
0 likes, 0 repeats
@dropbear42 Does it count as positive if I say "it can only get better"?Joke aside, Plasma is nice, and still my first recommendation for example for my parents or others coming from Mac. I like it much more than Gno'we can remove this one button here'me. :)(All my own opinion, not my employers)@codewiz
(DIR) Post #AT5HTKTSzZgfQzXnUm by dropbear42@fosstodon.org
2023-02-26T09:21:17Z
0 likes, 0 repeats
@globalc @codewiz Hiya. Some stuff, fwiw:1. My cheeky reply was to Bernie, re their typo.2. "Plasma is nice" --> yep, prolly why i've been a KDE4 to Plasma5 user since early 2014. 3. You'll never catch me offering unsolicited praise to GNOME 😜 I require my DE to be adaptable to me, not vice versa. In fact, the day a post appears under my name, fangirling G, will be the day that the space-lizards finally captured me & substituted an evil replicant 😱
(DIR) Post #AT5HTL2Yt5lBBpxpCK by codewiz@mstdn.io
2023-02-26T21:42:45Z
0 likes, 0 repeats
@dropbear42 @globalc I have to say, the big GNOME 40 redesign addressed the main UX issues that made me switch to #KDE years ago. With 44, animations finally got smoother.I think they still need to embrace configurability a little more. They don't have to get to KDE levels but, come on, my phone is way more configurable than #GNOME!But it's definitely getting better, kudos to the developers.
(DIR) Post #AT5Q2tSxgUkvjDmFmq by dropbear42@fosstodon.org
2023-02-26T23:18:54Z
0 likes, 0 repeats
@codewiz @globalc I acknowledge & respect that many peeps like gnome, but for me anyway, i just cannot take seriously any DE which:1. offers a default file manager aimed at kindergarten children who've not yet mastered their fine motor coordination, thus need ginormous amateur-hour file & folder iconography. If i put out crap like that, i'd be plain embarrassed.2. actively stops me using my MANY apps built on SystemTray capability for core functionality. What fools.
(DIR) Post #AT5cOT53fH6NiReOSe by codewiz@mstdn.io
2023-02-27T01:37:22Z
0 likes, 0 repeats
@dropbear42 @globalc I agree that the decision to kill the system tray was premature, causing years of user suffering.Years later, #GNOME 44 is partially filling this gap with the introduction of "background apps":https://linuxiac.com/gnome-background-apps/#LinuxDesktop #linux
(DIR) Post #AT5dGMtEthPE9Zp91c by codewiz@mstdn.io
2023-02-27T01:47:09Z
0 likes, 0 repeats
The Linux desktop needs a well-designed model for managed apps, but it's taking longer than expected.Android, iOS, macOS and even Windows have mature app stores with sandboxing, automatic updates, APIs for resource access and for requesting permissions.Linux has two competing standards (#Flatpak and #Snap) and multiple barely-working GUI installers: Gnome Software, Ubuntu Software Center, Plasma Discover. If you tried searching for apps, you know exactly what I mean.@dropbear42 @globalc
(DIR) Post #AT5dzJEVLBoBqJCSxs by globalc@chaos.social
2023-02-27T01:55:13Z
0 likes, 0 repeats
@codewiz I think Flatpak seems to be leading right now - although yesterday when I installed #retroarch on Fedora, that was only available as Snap.I don't see much pain there, users can also install both on a system. Myself, I use almost zero Flatpak/Snap, most things are nicely packaged or just services accessed with a browser like video chat.Real numbers might be interesting, on what new starters with Linux really are troubled with.@dropbear42
(DIR) Post #AT5eAYppfmoRPv1cPo by dropbear42@fosstodon.org
2023-02-27T01:57:14Z
0 likes, 0 repeats
@codewiz @globalc Yeah, when i read that article t'other day, i felt a moment of semi-hope, but ofc it was dashed immediately upon realising this putative new UI will give poor suffering users the ability to see & kill background apps, but not actually interact with them... aka completely useless wrt my enduring criticism.
(DIR) Post #AT5eCLxSWJrq3iRmDI by jf@hachyderm.io
2023-02-27T01:57:37Z
0 likes, 0 repeats
@codewiz @dropbear42 @globalc That was never "killed" it was always trivial to add it back with extensions, many distributions did that. However this has arguably caused worse problems because every API for it has been pretty flawed and caused broken behavior in apps. So I don't think it was premature, it likely should have been removed sooner.The background apps API is the only one that actually works correctly but it took this long just to design it.
(DIR) Post #AT5iS4wlvznPkYsbjM by dropbear42@fosstodon.org
2023-02-27T02:01:09Z
0 likes, 0 repeats
@jf @codewiz @globalc Ofc i know of the extensions, but i also know, as does any other gnome user or temporary visitor, that inevitably extensions break with new gnome releases, & in some cases stay broken for monthS... some never recover, ie, their Devs walk away in disgust or despair [no doubt visualising Sisyphus].
(DIR) Post #AT5iS6Kuliha3jBP04 by jf@hachyderm.io
2023-02-27T02:15:15Z
0 likes, 0 repeats
@dropbear42 Yes, that is why I refer to distributions, e.g. this was supported by Ubuntu and a few others so they would keep the extension working whenever they did a release with a new GNOME version. So you could be reasonably sure an Ubuntu extension would work elsewhere.But even so, this was still trivial to keep working, I don't think the shell extension API for indicators has actually changed at all since the first release of GNOME 3 despite being considered "unstable"
(DIR) Post #AT5iS6yyMmkE3xvORE by codewiz@mstdn.io
2023-02-27T02:45:14Z
0 likes, 0 repeats
@jf @dropbear42 No matter how badly designed, before removing an API that many popular apps rely on, you should at least have a replacement already implemented, but #GNOME didn't even have a design.This forced Ubuntu and other downstream distros to come up with *something* to keep the UX from breaking.Good developers don't merely design good APIs. They also design a smooth transition between old and new APIs.
(DIR) Post #AT5jHjdiOqicizb7DM by codewiz@mstdn.io
2023-02-27T02:54:37Z
0 likes, 0 repeats
An example of a smooth transition is Pulseaudio -> Pipewire. Most users didn't even notice 👏An example of a badly managed transition was esound -> Pulseaudio, which broke sound in popular apps and games for multiple years 😩@jf @dropbear42
(DIR) Post #AT5mk5b4ejI8nMZfDE by jf@hachyderm.io
2023-02-27T03:33:19Z
0 likes, 0 repeats
@codewiz I think I am understating just how broken the old APIs were. They are unworkable. Like they are so busted that there is no way to transition them without breaking them further. They just don't work. This was all written up here a few years ago: https://blog.tingping.se/2019/09/07/how-to-design-a-modern-status-icon.htmlSure it would have been great to have the design of the background apps API twenty years ago! But it took lots of years of experience to just get to this point where it could be designed.
(DIR) Post #AT5qHoJ1kYP6sNu6vg by hemish@mastodon.world
2023-02-27T04:13:03Z
0 likes, 0 repeats
@codewiz @jf @dropbear42 the thing there were no official API's at all for themeing.
(DIR) Post #AT61lA315nQECVc58y by jf@hachyderm.io
2023-02-27T03:37:41Z
0 likes, 0 repeats
@codewiz And BTW this is what I was getting at. One of the reasons why it was important to just remove it early was to *avoid* this situation where some unworkable API gets dumped into someone's lap who didn't ask for it, and they are stuck trying to figure out how to transition away from it forever.Pipewire is an interesting example because there are actually many broken edge cases with Pulse compat that likely won't ever be implemented, you can see them if you check the Pipewire bug tracker.
(DIR) Post #AT61lAbl0dD9wFrpIG by codewiz@mstdn.io
2023-02-27T06:21:26Z
0 likes, 0 repeats
@jf Probably my audio needs are very basic, and were covered when #Pipewire was deemed good enough to replace Pulseaudio in #Fedora.No software is perfect, that wasn't my point. I'd call it a smooth transition when 95% of users are happy, and the rest can easily rollback for some time.
(DIR) Post #AT62x8FJiUBM2gdf0q by codewiz@mstdn.io
2023-02-27T06:34:58Z
0 likes, 0 repeats
#Wayland took years to reach feature parity with X11, and there are still some rough edges.Now suppose this was done without the escape hatch of an X11 session. Users with NVidia cards and users who need specific screen sharing apps would be up in arms.@jf
(DIR) Post #AT64RBYo3flsxmeJDk by codewiz@mstdn.io
2023-02-27T06:51:37Z
0 likes, 0 repeats
Disrupting workflows which are important to a significant share of users undermines their trust. Doing so intentionally is even worse: it gets them *angry* at us developers! By now we should have learned the lesson.Apple and Microsoft, while not flawless, have done a better job at retaining their userbase than #GNOME and #KDE historically did.That's one reason - perhaps the top reason! - why it's never "the year of linux on the desktop".@jf #linux #linuxdesktop
(DIR) Post #AT66KdYDn88leiNfIu by codewiz@mstdn.io
2023-02-27T07:12:51Z
0 likes, 0 repeats
@jf I just finished reading the blogpost, which seems well written. I've always wondered why libappindciator wasn't deemed good enough.Now I know, but I'm not sure why we couldn't address the issues with minor API changes to keep apps working and buy us the time to develop a solid cross-desktop protocol.By the way, are the new Background Apps based upon systemd scopes? Do they work with Flatpak apps? Is there a FreeDesktop spec or other design documentation?
(DIR) Post #AT68UfiUnI11B16D2G by jf@hachyderm.io
2023-02-27T07:37:04Z
0 likes, 0 repeats
@codewiz Well, the app indicators were always an optional thing on Linux, e.g. in KDE or GNOME 2 or whatever you could just delete the indicator widget from the panel. So apps needed to support a fallback for this anyway, if someone's workflow was disrupted then the app was buggy from the start.
(DIR) Post #AT6AcotQlBtprUE83M by jf@hachyderm.io
2023-02-27T08:00:43Z
0 likes, 0 repeats
@codewiz The backgrounding API has been around for a few years. It is a pretty simple API, it depends on a concept of a running app so it needs Flatpak or some other sandbox to work correctly. https://flatpak.github.io/xdg-desktop-portal/#gdbus-org.freedesktop.portal.BackgroundFor Rust apps, ashpd already has a binding too: https://docs.rs/ashpd/latest/ashpd/desktop/background/index.htmlThere is no need for the apps or portal to interact with systemd, Flatpak will automatically spawn systemd scopes for any Flatpak app.
(DIR) Post #AT6JhfrEgEKYsGad3A by anedroid@mstdn.social
2023-02-27T09:42:44Z
0 likes, 0 repeats
@globalc ibus, mozc
(DIR) Post #AT6Qeh18bxafHVkN4C by gtavo@c.im
2023-02-27T10:59:59Z
0 likes, 0 repeats
@codewiz @dropbear42 @globalc this page is restricted only for logged users?