I think the real limit of plain text is pretty obvious: you cannot embed pictures in it.
It’s like SMS vs MMS or modern chat. With pure text, you can at best add a link to a picture (which could get rotten or inaccessible for other reasons), but you cannot directly graphical content.
You can but it’s not part of a plaintext standard. You could certainly build a text editor which can decode a base64 string, but to transform that into a picture you need something implementing the GIF (or JPEG or PNG) specification, otherwise it’s just a binary blob.
I've run some benchmarks a couple years ago, I don't have them at hand unfortunately but off the top of my mind, seqread 4k produced around 1500 IOPS while seqwrite was like a third of that. The practical performance was abysmal, I moved PostgreSQL storage to a volume and it was very noticeably slower just by browsing the web app (compared to NVMe SSD storage).
For comparison, I'm now using UpCloud which uses network-attached storage for all volumes and easily hits 10k IOPS (up to 100k with some tuning).
I certainly may have missed something while testing this so I'm happy if someone else wants to contribute and correct me if I'm wrong.
No, quantum physics is not a sham. Lasers are an application of quantum physics, for example. Usage of quantum physics principles in non scientific (thoughts are entangled!) or arbitrary macroscopic contexts (since electrons can cross a barrier, a human can pass through a wall) is an entirely different thing.
> If you don't care about the user in the UI, you probably don't care about the user in the backend either.
Not necessarily. I hate frontend tasks not because I don’t care about the user, but because I don’t have decent graphic skills. I can code but I don’t have a good istinct for colors, size, font styles, or other frontend issues that feel more art than science.
I’m honest about it, and luckily my job doesn’t involve frontend tasks, but this doesn’t mean that I don’t care about the users. In fact, you could say that I avoid frontend tasks precisely because I care about users and I don’t want them to be tormented by my awful UI choices :)
> Frontend problems are just easier to see — bad UI, confusing views, ugly design. Everyone notices. Backend problems are hidden — slow API response, bad errors, hard to manage code
That’s one way to see it. Another way is that frontend problems are subjective. The same UI could be confusing for someone and reasonable in someone else’s eyes. What’s ugly? “Beauty is in the eyes of the beholder”, as the saying goes.
Backend problems can be hidden and random but they are objective. If an API returns 500, there is something wrong. It may do so only when a plane passes by or when a cosmic ray happen to flip a bit, but everyone can agree that a 500 is not supposed to happen (unless your API intentionally returns 500 for success…). The root cause may be obscure, but the existence of an issue is objective.
I would say privacy. No telemetry, no targeted ads, no centralized transcripts, possibly end to end encryption. Psychiatrists are bound by professional secrecy, and they touch on very sensitive topics (people’s fears, their private lives, sexual preferences, …). Privacy is a very strong concern if you want to build this kind of platform.
I can work on privacy segment well enough that both parties agrees on onboarding like only no recording is allowed in any way, no screenshots or online notes form the doctor's side.
Well, transactions in this context are business transactions, which may involve 1 or N remote calls. Imagine checks against no fly lists, fraud detection, flight delay and so on. Speed of light is also another concern. So it’s not as simple as doing 35k TPS on a local SQL database.
True, but a lot of those checks will be against a local snapshots of the data.
> But yes, you don’t always need cool technologies.
That's kinda the irony mainframes are incredibly cool piece's of tech, just not fashionable. They have insane consistency guarantee at the instruction level. Hot swapping features etc. Features you'd struggle to replicate with the dumpster fire that is modern microservice based cloud computing.
It’s not decentralized either, at least not in the Bitcoin sense of the word. Interactions between participants may be automated but they can ultimately rely on legal contracts and people. IATA is one of those participants, but everyone has to trust IATA in the airline industry because of their role. A decentralized airline system built to avoid trust in a central authority would be pretty different (actually the booking part may be the least of their problems there).
It probably doesn’t require consensus among all participants (pairwise consensus at every step should be fine), so there is very likely no voting.
It’s not even permissionless. It’s not like a random company could join this “chain” simply because they can generate a keypair.
It’s a fundamentally different problem, and it makes sense that the architecture is different.
It’s like SMS vs MMS or modern chat. With pure text, you can at best add a link to a picture (which could get rotten or inaccessible for other reasons), but you cannot directly graphical content.
reply