grose

18 ms·

1. 151.▲
   by grose 4y ago

   I was able to install "swipl" with pacman and execute arbitary Prolog code and it seemed to work fine. Then I installed "nethack" which became this insane Adventure-ripoff text based game with Nethack flavoring and a sta
2. 152.▲
   by grose 4y ago

   Yep, with multiple fonts derived from it: https://fonts.aahub.org/
3. 153.▲
   by grose 4y ago

   I think that's a fair take. Tailwind and css-in-js's popularity points to a mismatch between how people want to actually use CSS and how CSS was designed to be used. It looks like people want isolated components, not complex casca
4. 154.▲
   by grose 4y ago

   Well said. The 'no big framework' thing works for Go because the Go standard library defines a common way for dealing with HTTP. The difficulty, then, is identifying 3rd party packages that play well with the rest of the ecosystem
5. 155.▲
   by grose 4y ago

   Exactly! I think a lot of people are reading my comment as a takedown of Tailwind but that was not the intention. My point is that these kind of quick and dirty tools that others may consider an anti-pattern can be extremely productive and
6. 156.▲
   by grose 4y ago

   You (and super256) are right. You do need to understand CSS to use Tailwind well, which is more or less the point of this article. I should have probably said "it's for people who don't want to deal with cascading", but
7. 157.▲
   by grose 4y ago

   Tailwind is 100% an antipattern, spitting in the face of well-written CSS. It is essentially a crystallization of the 'utility class abuse' anti-pattern. There is already a well-defined way to write CSS inline, no need to obscure
8. 158.▲
   by grose 4y ago

   Other resources for logic programming and Go: ichiban/prolog - ISO Prolog interpreter in pure Go, getting close to v1: https://github.com/ichiban/prolog trealla-prolog/go - ISO Prolog interpreter embedded via
9. 159.▲
   by grose 4y ago

   Honestly I can't really say (I just ported it to WASM :-)), but here's more or less the start of the query loop: https://github.com/guregu/trealla/blob/main/src/query.c#L173... I believe i
10. 160.▲
    by grose 4y ago

    Oh yeah, it's definitely not bad. I'm quite happy with it. I imagine I'm hitting on some corner cases here that aren't really indicative of the average user. Thanks for the comparison. My reading of the numbers is that t
11. 161.▲
    by grose 4y ago

    Thank you Syrus, appreciate your work with Wasmer. Congrats on the 3.0 release and Windows support! I just fixed guregu/trealla on WAPM to work with the latest changes. I think WAPM is very cool and I hope more people start doing relea
12. 162.▲
    by grose 4y ago

    Here is an extremely unscientific benchmark using the Takeuchi function and Trealla Prolog: $ make wasm $ wasmer create-exe tpl.wasm -o tpl-wasm $ time ./tpl-wasm --consult < tak.pl -g 'time(run)' --ns '
13. 163.▲
    by grose 4y ago

    Nice article! I think this is an exciting approach to cross-platform support. I took a similar approach for Trealla Prolog's Go library: https://github.com/trealla-prolog/go The biggest roadblock at the moment is
14. 164.▲
    by grose 4y ago

    I'm not aware of exactly what you're looking for, but I think such a resource would be very valuable. Unfortunately, modern web development has almost completely eschewed simplicity. I can offer some leads, though. This is more of
15. 165.▲
    by grose 4y ago

    I found async generators to be handy while porting a C Prolog interpreter to WASM/JS. A `for await` loop is a natural way to iterate over query results, and as a bonus you can use `finally` within the generator to automatically clean u
16. 166.▲
    by grose 4y ago

    PragmataPro is an example of such a font. Love it. It comes in a monospaced and duospaced variant. https://fsd.it/shop/fonts/pragmatapro/
17. 167.▲
    by grose 4y ago

    I think in order to make HTML a friendly document standard it needs to be easy to type on mobile. At least in my experience it is quite painful typing HMTL tags (needing to dance between 3 keyboards). This could be implemented with a built-
18. 168.▲
    by grose 4y ago

    Thanks! This project is super cool. Looks like it is well on its way to replace the broken polyfill at https://wasi.dev . That makes sense about the stdio file type. I will play around with it and see what I can do. I think I nee
19. 169.▲
    by grose 4y ago

    Very cool. This is super relevant to me, I've been porting Trealla Prolog to WASI recently[1] and I've been considering moving from wasmer-js to libapps/wasi-js-bindings. This looks like a nice alternative as well. I tried ru
20. 170.▲
    by grose 4y ago

    'Organizational' is indeed a better way to describe it. Poor choice of words on my part.
21. 171.▲
    by grose 4y ago

    I don't think it's necessarily bad . In fact it is quite an elegant solution to issues between frontend and backend teams. I just think it's a great example of Conway's law. Conway's law (IMO) was never a negative
22. 172.▲
    by grose 4y ago

    BFF is perhaps the purest example of Conway's law. When the backend team cannot or will not make the necessary changes for the frontend team, another layer is introduced: the BFF. There is no particular reason why the real backend can&
23. 173.▲
    by grose 4y ago

    Thank you. Looks very clean, I will try poking at it soon!
24. 174.▲
    by grose 4y ago

    That's super cool. I'm definitely not an expert on the subject but this paper about dif/2 intrigues me: https://arxiv.org/abs/1607.01590 And perhaps Ciao's paper could offer some hints? http:/
25. 175.▲
    by grose 4y ago

    That was me who ported it :) Currently there’s no support for networking and stuff, would love to fix that.
26. 176.▲
    by grose 4y ago

    Recently I have been working on porting a Prolog interpreter to WASI (Trealla). I’ve been searching for a way to get these kinds of useful I/O features in WASI and this looks like a great solution. Is there a C API? I’d love to take a
27. 177.▲
    by grose 4y ago

    Before smartphones in Japan, this is how mobile websites did signups. Every phone had an email address and you verified it by sending a blank email via a mailto link. Restaurants and Karaoke places had QR codes on their menus for this. Seem
28. 178.▲
    by grose 4y ago

    The context package didn't exist when Gin was created, so they invented their own solution. There was a proliferation of these context types until the standard library created a common solution. chi uses it, but Echo doesn't. The
29. 179.▲
    by grose 4y ago

    I think this is a perfectly reasonable opinion. Nothing wrong with adding abstractions if you find them useful. I just prefer to combine small stdlib-friendly libraries so I stick with that. Echo (and Gin) are a more 'batteries-include
30. 180.▲
    by grose 4y ago

    I'm not a big fan of Echo using nonstandard context types and nonstandard function signatures for its handlers/middleware. It boxes you into making "Echo libraries" instead of "HTTP libraries". I would recommen