Slack would be a lot better if they supported clients via rest api or similar. I want to run it in a terminal window alongside IRC etc. I have no desire to put up with their ridiculous UI/UX decisions
Make a Slack clone, but have it perform way better than the original (less RAM, CPU usage), with a smaller storage footprint.
Also deliver on features faster than the original. And have those features be more tailored to what the users both want and need - and things they didn’t even know they needed as well.
I mean why set the bar any lower for Altman? Shouldn’t AI be able to produce an executable that minimizes RAM and storage? If not, why not?
If it can’t produce an executable that minimizes RAM and storage for something like Slack, are we supposed to believe it can for something more traditionally power-hungry (browsers), or storage hungry (Call of Duty, iPhone apps)?
Shouldn’t AI be on the forefront for reducing resource usage in general (not just digital resources), or is just a giant exercise in induced demand / Braess’ paradox?
Slack as an independent app is easy to find, and the icon shows when I have unread messages. Slack in a browser tab is one tab among the hundred or so open in one of my three browser windows. And there's no icon to show unread messages.
But it's so unreasonably slow. It lacks basic features like syntax highlighting on ``` blocks. It's basically become a super expensive and painful to use while Discord continues to be a joy.
And the 'start a thread' nazis are just too much to bear. Prediction: they will add subthreads within 3 years.
Social issues can't be solved by technical means. Just slightly incentivised in some direction (like discord's "this is the third reply, would you like a thread instead?")
But for the resource usage, ripcord https://cancel.fm/ripcord/ already proved you can have a capable client which is super light and fast if you care. This was made by a single person and in many ways is better than the official client.
This isn't how you use online chat. Somehow people did fine with IRC for decades without threads. I'm sorry you can't manage your own information flow or configure your own client and have to embarrass yourself to make other people to organize it for you.
What else should I do for you? There are hundreds unique snowflakes that think their message is what I should see - I don’t. Stop littering in a public space and behave like a grownup.
Mao tried picking industrial locations for survivability in case of war: https://en.wikipedia.org/wiki/Third_Front_(China) Turns out that places that are hard to reach for the enemy are also hard to reach in peacetime, so the project was ultimately abandoned.
Reminds me of that time when the US seriously built a bunker to store cash money and social security files... As if society would just pick up were it left of.
Why? I think any attack on China, Russia, India by major power will quickly escalate to nuclear. At this stage everyone will have much bigger problem than worry about datacenters.
It would very slowly escalate toward nuclear, and then all at once.
Nuclear rhetoric would escalate rapidly by the losing / weaker side.
It's a common fallacy that conflict between two nuclear powers would instantly jump to nuclear exchange. That isn't how it would go at all, although the propaganda that it would does likely help to prevent wars. Nobody is interested in vaporizing all of their own people by starting a nuclear exchange from the first bullets fired. There would be various high-intensity inflection points, triggers, that would risk nuclear escalation: when one side or the other starts losing a lot of territory; when one side or the other loses a major city; when one side or the other is at risk of operational collapse (leading to more rapid losses in the field); when one side or the other is at risk of losing their core territory / capital; and so on. The key inflection points would be prime candidates for nuclear threats, to try to get the winning side to stop or back off immediately or else. From there it'd be a complex equation as to when a side would actually finally set off a nuke (would it be a warning nuke first, etc).
Starting code when I was 14, sold my first bit of code at 17, which was written in 6502 assembler.
40+ years later, been through many BASICs, C, C++ (CFront on onwards) and now NodeJS, and I still love writing code.
Tinkering with RPi, getting used to having a coding assistant, looking forward to having some time to work on other fun projects and getting back into C++ sooooon.
Oh so many times over the decades, having to explain to a dev why iterating over many things and performing a heavy task like a DB query, will result in bad things happening...all because they don't really comprehend how things work.
reply