I know someone who’s literally making that right now. Remind me in a week, I’ll send you the link. He’ll probably be done by then.
Edit: donetick.com
West Asia - Communist - international politics - anti-imperialism - software development - Math, science, chemistry, history, sociology, and a lot more.
I know someone who’s literally making that right now. Remind me in a week, I’ll send you the link. He’ll probably be done by then.
Edit: donetick.com
For XMPP, have you looked into using snikket? It does most things you’d want out of the box without having to setup extensions yourself.
I got into ocaml recently. I love it. I honestly don’t see issues with the syntax, maybe because I haven’t used it enough.
Here is a docker compose: https://snikket.org/service/resources/docker-compose.yml
You only two configuration options in the config file: domain and email.
I’ve been wanting to do this exact thing. I already have wireguard setup. Please update us if you do this.
This makes matrix even less attractive to me lol. But you’re right, that’s a very good point.
cumbersome to parse
Parsers have already existed for so long in every major language. Why need to worry about parsing?
And why need to worry about transports working differently if they achieve the same thing? They seem similarly convenient if I understood what you said correctly
Why is JSON better than XML? It’s more modern, sure, but from technical perspective it is not objectively better right? Not something worth switching protocols for.
You mention XMPP has transports as opposed to Matrix bridges. I thought they give you roughly the same outcome. What’s the difference?
Any examples other than ocaml? From my understanding, ocaml’s type strength may only be found in a couple other languages. Haskell, scala, and maybe Rust. Any others?
Comparing cost to AWS Aurora is unfair. Give us the self host price, and compare to that.
Also, they should have tried Scylla or Cassandra. It’s very scalable and handles a lot of writes.
I won’t remember everything, but one very important things comes to mind:
in Typescript, it is very difficult to assert on a type (let me know if you’re not familiar with what I mean by this and I can explain further). In OCaml, this is trivial using pattern matching.
Why would you need that? The idea of a type system is it doesn’t let you apply a function on a structure without the structure being of the right type. But the lack of type assertion in TS makes people follow hacky workarounds, which defeat the purpose of type system.
There are a couple of other things, like immutable types by default, automatic tail call optimization, functors enabling higher kinded types, etc.
Also in ocaml, you don’t have to annotate any types on any variable or parameter, and you’ll still get full type protection.
The only valid argument against typescript is that it is too similar to vanilla JavaScript. It does not go far enough. We need type systems like Ocaml’s.
I suppose you can also complain about needing a build step, but I find this silly. There are so many tools that make this easy or automatic.
What niche communities do you wish existed or were more active?
What communities do you wish existed here or were more active?
What kinds of opinions do you think are lacking? And what niche topics you wish lemmy had communities for?
Been using them for over a year now. I’m not a proud or loyal customer, but it’s a very generous free tier and I haven’t regretted it.
Requiring a candidate to know a specific programming language is stupid. Nearly all of the commonly used languages in industry are similar.
It’s maybe more valuable to require knowledge in a specific framework, where knowledge is less transferrable between popular frameworks. Nonetheless, I personally rather hire an engineer that solves problems and learns flexibly rather than one that happens to know the right tech.
Some programmers are software engineers. They solve problems, sometimes problems with great ambiguity or non-straightforward solutions.
And some programmers are… code technicians? They understand and write code, but their job seldom involves problem solving. Often times, they’re asked to code an already solved problem, or mostly solved.
This is not a diss. I was in the second camp for a while. But it hurts your career to stay in that. So be careful.
Not just the pricing, but also the low footprint, tiny size and fanlessness.
donetick.com