What mature implementations of S3 are there? MinIO that rugpulled the community, Garage that doesn’t even have proper setup scripts in their Docker containers and expect you to do the init manually, or Zenko cloud server that more or less got abandoned? I think there’s also SeaweedFS which might do better but I’m surprised at how shitty everything seems in this space - surely people aren’t being crazy and either storing their files on the FS directly to expose access to them through their app (hello directory traversal attacks) or storing them in relational DBs (hello wasted bandwidth and bloated backups).
The odd jank extends further, like Sonatype Nexus and some other software hardcodes AWS regions to choose from when configuring the storage even though your self-hosted implementation doesn’t have anything to do with AWS so you just have to come up with fake regions. If the cloud vendors each have to reimplement it because there is nothing as quality as PostgreSQL is for DBs, but for S3, then I’m hardly surprised at the state of things.
Bannon was already jailed for failing to adhere to a congressional subpoena.
What he probably means is being killed in prison, "suicided" when the cameras are mysteriously off, but this doesn't make sense, he's in the side of the oligarchs.
Yes, people were arrested in UK, but UK is not USA. It is a country with different legal system, different politics and somewhat different ideology.
The Trumps history was known prior election, but it was only advantage for him. Kavanaugh is on supreme court. People in Epstein files were defended with bad faith and excessive benefit of the doubt in the past and will be defended the same way again.
When it comes to abuse, harassment and such, when you look at supreme court, president, ministers, politicians, college leaders, religious leaders etc etc etc, there is no history of even credible rape accusation being a disadvantage for the person. There is a track record of hysteria that something might happen to those important people and then elites circling the wagons protecting each other.
There are going to be angry blogs from progressives and feminists, they will be accused of overdoing it and of moral panic. And if democrats gets voted into power, they will continue reconciliatory doormat politics of last 40 years.
According to reports from locals in Asia and Europe, they are traveling and enjoying life to the fullest while harassing local communities during those trips.
Would have to be quite a few years - last time price bump was in 2022 by 10% due to increase in energy costs because of the war in Ukraine. Naturally prices didn't go down.
This is not a situation where you'll have thousands of people editing the same document, that'd be insane with Django for sure - but at general collaboration tooling with <100 (random number I made up) editing, Django is unlikely gonna be the bottleneck
I see, in your broad and experienced mind, document editors don't have users, permissions, and the whole document management itself, comments on lines/threads, reactions on comments
Seriously, theyre all as cookie cutter perfect usecase for Django as you can get, but I guess you haven't actually thought about the domain and just wanted to take a dumb on other devs with intern-to-junior level insights
Obviously, you don't need the model abstraction for any software, ever. It is just more or less suited for a domain.
And in this case, as would be obvious from thinking about it, the only part it's not suited for is the live syncing of the text edit on the frontend, which is one one small part of the whole.
Django is perfectly capable. I'd use Phoenix for its scalability and performance, if it were me, but I've built large-scale projects in Django before, and it worked well.
TLDR: C++, WASM, and some form of GRPC with C++ on the server side as well. Because you need a language that's fast, can contain high complexity and large programs without collapsing (which is a short list of languages) and can work fast for the bits that need speed.
That article is seemingly all about the perf of the complex frontend app with a custom renderer running in the browser, nothing to do with what’s happening on the server.
In my opinion one inherent property of languages is how large the largest program is that can be written in those languages. There's languages that work well for short programs. Bash, perl are examples on one end of the spectrum. Then you have things like lisp and Python where the largest programs are a lot larger already, but still hit obvious limits. And then you have the languages that support really large codebases. Java, C++ are ones currently in use.
There's new languages where it's a bit of an open question still where they lie on the spectrum. Go would be one of them. I'd guess somewhere between Python and Java. Javascript I would argue is between perl and python. And Rust ... well ... good question.
An office suite is a gigantic application, which will need feature upon feature upon feature upon feature. If you want it working on the web, I'd propose something like C++ and WASM.
Wt actually isn’t terrible, with the added benefit of being able to leverage the enormous c/c++ library ecosystem. Also, it can be quite fast if you care for it to be.
Edit: also appears to be based in the eu, how fitting for this thread.
It really depends on how it’s used. I love Django in certain specific situations. You know that saying though about when you have a hammer, everything looks like a nail…
reply