While not obvious from the article, it appears that they want something S3 like, but isn’t from Amazon, and possibly want to self host it. The article could be much more clear about the goals
Ah, thanks. Yeah I was confused because in his long list of vendors he didn't mention Wasabi, Backblaze etc. It appears that I do not know the context of his post.
Question: Do you mean real time, meaning there is some kind of expectation of task switching time, nothing can stop other threads from executing, etc; or do you really mean embedded?
Personally I don’t care what it is written in. I care what the code does and how well it does it.
Rust is a cool and interesting language that helps solve some problems, but it doesn’t make it immune from all. But that doesn’t make it inherently better, or worse for the job. We have seen this trend for everything from C++ onwards (Java, Ruby, C#, Python, etc etc)
Help me understand: why does knowing the language matter? I can see why for contributing to it, though there are other ways to contribute than code. However to use it, why? Do you only use projects you can contribute to?
I am curious, do we have any confirmation that the "AI hit piece" thing is real? It feels like everyone is just assuming it is, but it would be nice to see some confirmation.
Additionally Geerling raises good points, but I am not sure we should jump to his conclusion yet.
I am glad markdown is very reliable to you (and many people), and if you’re just talking about something with very light, formatting, then it can be. However, link have documents can be incredibly hard to read. I am dyslexic. I find markdown documents, markedly worse for me. All I’m saying is that we can’t universalize this experience
You might not, it depends on your use case. However SQLite is very small and lightweight, and amazing for read heavy databases. Using SQLite lets you bypass a lot of setup and configuration; then adding something like marmot lets you add being distributed after the fact.
Because accessibility should be front of mind for all apps. We don’t want disabled people to be treated like an afterthought or only using specialty apps. Anyone can become disabled and need these features, either temporarily or permanently and shouldn’t have to change their entire tool chain to adapt
> We don’t want disabled people to be treated like an afterthought or only using specialty apps.
We also don’t want non-disabled people to be treated like they are disabled (to not use other words).
And no, gray on gray is not accesibility, Narrator is not accesibility, dumbing down things is not accesibility.
I mostly think of when geohot wanted to make his own RISC-V core and cranked out some basic verilog. It was incomplete and barely commented, and never touched again. I suspect we are going to get a few blog posts of analysis and then he moves on to something else
Not really, I should have acknowledged it, to be sure. I am just saying a lot of people put a lot of faith into geohot's musings/side projects/whathaveyou, that doesn't pay off.
reply