61–70 of 131 posts
Also great timing after the recent Python Preprocessor post: https://pydong.org/posts/PythonsPreprocessor/
Could Hy hypythetically be implemented as a preprocessor like https://github.com/tomasr8/pyjsx?
Earlier quoted context omitted.
and for those interested in history, Docker was first announced 10 minutes afterwards on the 26:24 mark.
Now I know how those guys felt who were on the same episode of Ed Sullivan that introduced the Beatles.
I remember Hy! It blew my mind back in 2014 and is still cool today, it's great to see it still going and congrats on releasing 1.0.0! Also great timing after the recent Python Preprocessor post: https://pydong.org/posts/PythonsPreprocessor/ Could Hy hypythetically be implemented as a preprocessor like https://github.com/tomasr8/pyjsx ?
I'm wondering, is it worth learning Hy if I don't know any python? (coming from a clojure background) Or is python knowledge a prerequisite?
Yay! The birth of a language is a beautiful thing. I’m curious about the macros: how are these implemented? They seem like pretty straightforward unhygienic Lisp macros, which is a little bit of a disappointment, but better some macros than none at all! Anything about the macro system that distinguishes it from the Common Lisp system? E.g. anything borrowed from Scheme or Racket? Docs are sparse here.
Congrats! Two questions: 1. Does it support REPL-driven development? (condition system, breakloop, etc.) 2. Is there a standalone distribution? Distributing python in itself is a hassle, ideal situation would be to simply distribute a single Hy binary that contains all dependencies within it (either statically linked or as a zip file extracted in tmp directory).
>A convenient way to use this class to interactively debug code is to insert the following in the code you want to debug:
(.run (hy.REPL :locals {#\* (globals) #\* (locals)}))
import hy; hy.REPL(locals = {\*globals(), \*locals()}).run()
(one) nice thing about Raku is it does a surprisingly good lisp impression out of the box… https://www.codesections.com/blog/raku-lisp-impression/ [thanks to Larry Wall’s penchant for collecting stuff]
letrec, lambda, or & and are not functions in Scheme.
Any downsides to using Hy (over Python)? Other than my coworkers don't know Lisp? More concrete: Are there Python language features I can't use in Hy? Or performance penalties in using Hy?
Why not just use something closer to the metal: Common Lisp, Scheme, Clojure, Racket? Especially, use a compiled language, instead of an interpreter.
Any downsides to using Hy (over Python)? Other than my coworkers don't know Lisp? More concrete: Are there Python language features I can't use in Hy? Or performance penalties in using Hy?
Sure - you are piling another transpilation layer on top of already slow Python. Why not just use something closer to the metal: Common Lisp, Scheme, Clojure, Racket? Especially, use a compiled language, instead of an interpreter.
I loved the HYPE POST.[0] I work with corporate software. It is absolutely brilliant. [0] https://github.com/hylang/hy/discussions/2609