I believe there are a large number of feature requests on Lemmy’s GitHub page, making it difficult for developers to prioritize what’s truly important to users.
Github issues are annoying that way. You could solve it by closing down "issues" and using discussions instead. People can up and downvote discussions, and you can see that from the listview, unlike with issues.
And you can have threaded conversations in discussions.
I assume they're talking about this api
Any tools that interface well with it?
Lots of tools, but it depends on where you want to use it. For example, inside Obsidian you can use it as a text generator
Inside VSCode you can use something like AI Genie
If you just want to use it raw, you can use postman
Java makes things run in a VM
Docker makes things run in a VM
Virtualbox makes things run in a VM
Why did we need any of those things, should have just put everything in Java instead right 🙃
Why would they? WASM is Web-Assembly, so Assembly is a lower level language than Java.
You can use C# WASM through Blazor, and Java WASM though JWebAssembly. WASM as core is supposed to be language agnostic. So If you want a JVM in WASM you can build it on top of it
Rebasing is for noobs.
git reset head~42
git push -f
Not all features are for everyone. Maybe you're experienced enough that showing a graph seems like an overkill when you can just read the warnings.
But I can imagine for someone that's more entry level the graphs could make it easier to understand what the problem is
Are they though? Aren’t DTO’s supposed to be pure data objects? [...] So what about extensions?
I'm not 100% familiar with Kotlin, but I think extension methods in Kotlin are the same as C#, basically syntactic sugar.
So you'd write an extension method like:
public static class ObjectExtension
{
public static void DoSomething(this object input) { }
}
this being the keyword making it an extension method - and you can call that function on an object by doing object.DoSomething() - Yes. But underneath it's the same as doing ObjectExtension.DoSomething(object) (A static invocation to your ObjectExtension class and DoSomething method.
So on the surface it looks like you're injecting a new method into your DTO, and your DTO is not a pure data object anymore, but actually you're just creating an helper function that's statically invoked - that looks like you can call it "on the object" but actually you're not.
As for whether it's a good / common practice to create mappers like that in Kotlin, I don't really know. I do it often in C# though.
Javascript is a fad, we should all move to WASM. 🙃
But no, TypeScript is not a fad. Unless a better "Typescript like" thing comes out - I know how in frontend land people like to make their own substitute framework that does something slightly different than an existing framework - But I don't really see why anyone would want to make a NewTypeScript, and not just expand existing TypeScript
243650.0054 = 47,304$/ year / instance. How many instances are hosted by AWS? How many are hosted by Google? How many by other Redis aaS?
Formatting it like 47,304$/ year seems like you're saying it's $47k, but it's just $47. How much would it cost any company to self-maintain their Redis instance?
Don’t contribute back in a significant manner
They have multiple people full time employed that are contributing, and how are they "hampering its development"?
If you look at the top contributors: https://github.com/redis/redis/graphs/contributors
Soo actually these cloud providers are some of biggest contributes to the project. They're not just taking Redis and aren't contributing. The opposite actually lol.
Besides, you're acting like Redis is some poor little startup, but they're a company with 991 people (by their linkedin stats). Its like if Oracle would change the MySQL license, and then you side with Oracle "Poor little Oracle, everyone uses MySQL, but no one contributes" - yea no
They were allowed to leech, [...]
Services like AWS and Google Cloud offer 1000s of "free software" (like Redis) as a service - like AWS Elasticache - and if you look at the pricing, cache.t2.micro for example, is $0.017/hour, while just a plain t2.micro vm is $0.0116/hour. So effectively AWS is only "leeching" $0.0054 an hour on the Managed Redis that they're offering.
An AWS managed Redis is just easier, otherwise I'd have to boot my own t2.micro, and install Redis there. I'd still be using official Redis on AWS, because self-hosting is still fine in the new license, it's just more work for me, because the license doesn't allow AWS to do it for me anymore.
and the naive, purist opensource community ([...]) will happily join the ranks of businesses that couldn’t be bothered to donate to Redis
It's funny how people are now siding with Redis. When other companies did something similar (like identityserver4 was FooS, and then they created their new commercial company - and everyone was like "fuck you, you people are sellouts.".
Most of the time when a FooS project goes commercial, people make a free fork and the commercial project slowly dies
How about figure out what you can and can't access first. Like can you access the rest of the internet openly?
Are all sites allowed, are some things blacklisted, or are sites whitelisted? If things are whitelisted on the network, it might be pretty difficult to find a hole.
Anyways, you mentioned your phone - If you have unlimited data, I'd suggest you just set up your phone for tethering, and create a private wifi from your laptop to your phone using mobile data, that should bypass all network restrictions.