Readit Newsastroanax commented on Roblox on Linux with recent Wine 6.11 roblox.fandom.com/wiki/Ro... · Posted by u/homarp
Last I tried to run Roblox on wine the problem is Roblox policy officially consider Linux to be cheat software and ban anyone attempting that immediately.
That doesn't seem to be an issue now, tried it with Grapejuice and didn't get banned. From the Grapejuice Discord, this also seems to be the case for other Roblox on Linux users.
astroanax commented on A from-scratch tour of Bitcoin in Python karpathy.github.io/2021/0... · Posted by u/yigitdemirag
Does this blog entry hang Brave on Android for anyone else? Happens on two phones for me.
Disabling js doesn't make it hang anymore for me.
astroanax commented on Dennis Ritchie’s first C compiler (c. 1972) github.com/mortdeus/legac... · Posted by u/jnord
The original keywords - https://github.com/mortdeus/legacy-cc/blob/master/last1120c/...
Interestingly, long was commented
Am I the only one who thinks that this concept is perfectly good, and all the things the site doesn't have are just great further development of the idea?
What's wrong with a "wikipedia for recipes"? I would LOVE that.
All the complaints about the quality of the recipes or the lack of more in-depth explaination of each one, some kind of voting/reputation system for the recipes and for the submitters and the voters, Yes those are all good ideas to make the db more useful than just a db.
But you have to start somewhere. How is the core idea here of a public cookbook not fundamentally awesome? I mean hello... GIT. Recipes that are living documents that can be honed over time, complete with viewable history of what changes have been made so you can decide if you agree with them. Branches and forks for all the hundred variations on any given thing. Revisions by better experts than the original submitter of some recipe.
So, today on day one it doesn't already have the benefit of years of contributions and incremental improvements and revisions, Quelle Suprise!
Git might not be the best way to manage recipes, especially when you're targeting a section of users who might have never heard of what it is. Sure, the idea of 'viewable history' is nice, but the average cook would find trouble with it. A wiki seems much better suited for this.
To add a recipe, you need to a learn markdown and create a PR. Learning markdown might not be hard, but learning to create a pull request, after creating a github account might put them off.