5 ms·
The modern web makes me want to throw up
- imwillofficial 5y agoI stopped reading at “slack is a glorified IRC client.” This statement ignores that mountains of functionality that makes slack a popular choice in big tech. Workflows are a big one, chat behaving as expected instead of mysteriously strange depending on client, LDAP, SSO, I could go on and on.
- nikau 5y agoAll I know is mirc could switch channels instantly on 25 year old hardware whereas slack takes seconds a lot of the time. It's pathetic how slow and resource hungry it is.
- DeathArrow 5y agoMirc was written in C++.
- nikau 5y agoYes, and it does local caching and doesn't make me want to throw up.
- musicale 5y agoI mean, channel chat largely is. Same for channels on Teams and Discord. Not that they don't have other potentially useful features like multimedia posts, notifications, reactions, voice/video calls, file uploads, wikis, full office suites, etc.. But the author's point isn't that they lack features - it's that they're clunky web apps. He isn't wrong. Full disclosure: I dislike Slack, find Teams to be clunky, buggy and generally unpleasant, and tolerate Discord but for gaming only.
- mixedCase 5y agoI'm sorry, but channel chat certainly is not like IRC. Threads and reactions, and to a lesser degree multimedia, make a drastic change on the experience. Those three features allow conveying a lot more information in a smaller cognitive space. Threads allow smaller groups of participants to carry on with a conversation for a long while without hogging the chat and without making it any less public. Reactions allow showing support or many other kinds of sentiments to someone's statement with a tiny bit of vertical screen state for huge swaths of people, doing the same on IRC is wholly impractical. Multimedia is an obvious convenience. Having to rely on external or ad-hoc services to support it is annoying at best, anti-user at worst, meaning people often just don't share anything at all because most don't think of the medium as multimedia capable. I do think that desktop chat applications should not be the bloated abominations they are, but any less than the experience that software like Slack or Discord provide would be a worse alternative to the overwhelming majority of people who today use and enjoy either, no matter how optimized.
- LinuxBender 5y agoFor what its worth, threaded conversations with multi-media experience existed long before any of the current and popular chat platforms. Usenet by design was threaded, allowed binary uploads, is highly distributed, fast and resilient. Clients are very light weight. The downside of them today being spam. Surely that could be solved with signed messages or something else. A big upside to usenet in my opinion is the lack of censorship.
- nikau 5y agoNone of the above excuses the fact that slack and teams suck because they keep refreshing the same data over and over again. Whether its electron framework limitations or poor coding I don't know, all I know is every electron app I'm forced to use at work is terrible. Even totally static items like default emoji in teams keep showing up as a grey box placeholder for a few seconds until they are downloaded each time, its garbage.
- DeathArrow 5y agoYou could also send files over the IRC.
- mikelward 5y agoGoogle Play Instant aims to address the second point for Android. https://developer.android.com/topic/google-play-instant/ https://developer.android.com/topic/google-play-instant/ I guess it would work on Chrome OS, too.
- brnt 5y agoDon't think that's what the author meant.
- BugsJustFindMe 5y ago> we need to be able to run native apps without installing anything Apple solved software [un]installation decades ago on the Macintosh. Drag in, drag out, no fuss. Only crappy developers use installers on macOS for things that don't strictly require system modification. Windows and Linux developers can join that party any time they want, but both ecosystems have their heads too far up their own respective asses re application packaging to make it happen.
- maccolgan 5y agoTo be fair, on Linux that problem is also solved and has been solved for a while, just use an AppImage.
- BugsJustFindMe 5y agoMaybe, but the percentage of *nix developers producing AppImages for their applications is approximately 0%, and when they do apparently the community thinks it's still ok to make users jump through hoops like manually editing file execution privileges a la https://inkscape.org/release/inkscape-1.1.1/gnulinux/appimage/dl/ https://inkscape.org/release/inkscape-1.1.1/gnulinux/appimag... . And _then_ users have to work around the fact that every Linux distribution except for one has no readily visible place for a user to drop their AppImages into in the first place, because /opt, which I assure you is a completely fantastic and clear and obvious name for the folder that you put your applications into unlike Applications or Programs which are both stupid dumb names that nobody understands today, is relegated to a dark corner like the hideous goblin it is. While "drag to the Applications folder" has been a right and proper way to install software on the mac since the 80s.
- mikewarot 5y agoTo be fair, you just copied files to a directory and ran the code in the days of MS-DOS. The real problem is mobile code, and how to safely run it. In a decade or two, the idea of running a program with capabilities to access the world by default will seem as insane as letting inmates run a prison.
- nikau 5y ago
- pull_my_finger 5y ago> Nobody even thinks about how long it takes from the point when a user decides to install an app to when they see the first content. On the web we count that time in milliseconds and on native apps we count minutes. There aren't any hard technical problems there - we obviously manage it on the web, so its easily possible. If developers had to ship a browser with every webapp I think the situation would be reversed plus some. Shared libraries solved this problem before browsers did. The problem is more likely that developers can't or it's not cost/time effective to build an app without relying on bloated frameworks, or use frameworks built for rapid prototyping and never go back to build it right. That's a problem on the web and native.