klipse 2016-11-06

well done @jrheard your article got very good feedback on HN and Reddit

thanks! just realized i ended up on HN somehow, i was out with friends last night and was wondering why random people kept following me on twitter šŸ˜„

i love this bit of feedback from the reddit comments:

Ha, that was fun~!
Also those live blocks are boss.

Nice!

I’ve deployed the infinite loop protection

You can test it in KLIPSE repl

I added a flag to display the guard in the transpiled js

by default, guard doesn’t appear

(defn foo []
  (while true))

(foo)
works like a charm

i like the default of 3 seconds, too, i think that makes sense

i noticed in the HN thread that someone put together an alternate version of the post’s code - https://gist.github.com/Haspaker/74f124859633edeb8d04465ce0053225 - that takes a while to run if you paste it into klipse

so it looks like people are actually using these klipse windows to mess around and come up with stuff, which is awesome!

i was worried that people would read the lines like ā€œgo ahead, try setting that foo to a barā€ and just skip right over them without trying it

and here we’ve got this guy putting together an alternate version of the algorithm right there in the klipse window!

Awesome!

I’m wondering why this code doesn’t cause an inf. loop

I know

because, you are using your own version of klipse and not the one from the cloud

@jrheard ā¬†ļø

ah yeah, yup - out of habit, i prefer hosting my site’s css/js/etc myself, that way i don’t have to reason about a third party’s uptime/speed/etc

plus i can control when i upgrade, etc šŸ˜„

Yeah that makes sense

i’ll definitely upgrade before the next post, though!

it’s basically done, but i’m going to hold off posting it for a couple of weeks due to real-life stuff, and also i want to do a few assorted housekeeping things to the blog’s code/setup first

you might want to configure the max-eval-duration

oh nice, will do

Great article!

Thx for mentioning how much you enjoy klipse metal