source available. Lots of non free components make this not open aource, but cool nonetheless (you still need someone elses permission [source 2, steam, and almoat certainly other dynamically linked libraries] to make this work, which goes against the definition of open source)
.foo {
.nested {
property: value;
}
}
I dont like pizza that much as a staple in my diet (too unhealthy imo, it is delicious tho) so thats not too bad, but as a cali-born, kentucky-raised filipino, yes.
G has mexican, cajun, columbian, and tex mex. Seriously south florida is insane food choice as well. Hell, I can get california burritos too. D has filipino, thai, arabic, and indian. Incredible vegan options and protein options and who doesnt love spicy thai chicken and rice? Either of those and im set for life :)
sounds like you shouldve been using a password manager this whole time :)
Related: https://piefed.social/post/1264646
Writing javascript (or any programming language, but sticking with ‘script’ here) to consume an http api from an agpl service (such as lemmy or mastodon) does not force you to open source whatever client you have.
Consuming an agpl client library (maybe mastodon or lemmy provide an sdk I dunno, or some third party one) and you embed it in your app and interact with that agpl code, then yes you must open your code up.
For example, there are closed source Mastodon clients that make a lot of money. Look at the mastodon client from tapbots. The owners of mastodon have a winning case if they sued them, if your logic held up. Tapbots can safely create an entire application and consume the mastodon api without worry, why can’t you and your script?
Using an API isn’t distributing
Replace C with lisp and you’re 100% correct. Even then Rust is better than lisp IMO.
Lots of people in countries outside of the west use android tablets for their main computer
A neat side-effect of GraphQL being transport agnostic is that you can do things like GraphQL over a websocket or avian carrier :)
If only “fullstack” or “typescript” devs weren’t so scared of CSS. They can optimize a weird join, they know the Big O notation of a function that operates on a list that’ll never ever exceed a size of like 1000 items so who the fuck cares, but as soon as you ask them about grid, layers, container queries, or even what things like houdini can hopefully do one day, they just collectively shit themselves.
What corporations and enterprise software development practices have done to the web makes me crash out, sorry. Very few people who actually care about CSS are making a living wage making things with it as their job.
I love that little language. I learned ReasonML for fun and built a few toy apps a long time ago, but ReScript has been cool to watch
little bro thinks f in FOSS means free as in beer 😂
Arm yourselves with the AGPL and the GPL friends.
you can just fork and rename it to something else corporate-friendly? the only one preventing “foss” from doing it is you
This kind of stuff might be worth mentioning in their discord and asking if it’s worth writing some docs on :) go get some contributor cred 😄 Even just writing reproducible steps and solution and why the solution works could be worth it because then a technical doc writer can take that and start from there.
deleted by creator
I mean, to make such a point that the only point of the page was simply to satisfy a requirement of someone else’s volition and yet creating that page and apparently saying what you’re saying—seems like there’s something misaligning here :P
Also I no doubt that they hate people who talk too much and hate making jokes — there’s some seriously unserious stuff inside of the rules they posted. They are serious folks who have zero tolerance for laughter apparently :D
My headcanon is they’re a bunch of people who have a super religious supplier with strict checkbox rules and they are fucking with them.
if he’s complaining about plaintext secrets, sure. But if he’s talking about using session cookies he is wrong and should know he is wrong.