03:52 <lunarkitty> Has anyone here tried using the webview bindings for ruby?

03:52 <lunarkitty> Seems like a neat way to do a UI

03:58 <kinduff> like from webview/webview?

05:03 <lunarkitty> kinduff: yeah

05:55 <evan> Hello

05:57 <evan> Here are anybody?

13:27 <isene> It seems gnome-terminal is orders of magnitude slower than urxvt with rcurses. Other performance comparisons between the two?

14:35 <Rounin> isene: Does urxvt have full Unicode and OpenType / TrueType rendering and all that stuff? That's probably going to increase complexity a lot

14:36 <Rounin> If one is like variable-width with full support for Tibetan and the other's monospace only...

14:37 <isene> Right, but simple printing of ANSI escape sequences is excruciatingly slow in gnome-terminal. Like, silly-slow...

14:39 <Rounin> It probably throws the full rendering engine at even the simplest problems :D Not to mention kids today and their bloated software and all that

14:39 <Rounin> I work with JavaScript development every day... Ask me how I know X(

16:33 <isene> LOL

17:38 <kjetilho> Rounin: yes, urxvt has full Unicode support and Freetype rendering. probably doesn't support "proportional" fonts, but they don't make much sense anyway.

17:38 <kjetilho> (the U is for Unicode)

18:02 <Rounin> kjetilho: Ah... So it might just be a lot more efficient and/or simple than gnome-terminal

20:00 <havenwood> isene: Congrats!

20:01 <havenwood> Lemme look.

20:06 <havenwood> evan: If you check back in we're here but don't always respond immediately. You can use the logs to keep context if you don't use an IRC bouncer. :)

20:07 <isene> havenwood: I'm curious about your feedback on this one

20:09 <havenwood> isene: The readme looks quite nice on first impression. I'd focus on the "gem install rcurses" installation path since the other is system dependent and less appealing. Maybe remove it or relegate to a development installation section.

20:10 <havenwood> I think ```ruby for the code blocks would look nice.

20:13 <havenwood> isene: First meaningful feedback, an `rcurses` gem should minimal or no footprint outside the `RCurses` (or `Rcurses`) namespace.

20:14 <havenwood> If you like top level `Pane`, and so on, probably do a `module RCurses` and have folk explicitly `include RCurses`.

20:14 <havenwood> (Otherwise two gems could have a `Pane` and we're toast.)

20:15 <havenwood> With the explicit parent namespace per gem we can not `include` when there's be a conflict and use the uglier, full namespace.

20:16 <havenwood> I think it's an important convention to follow as long as Ruby has no other way to designate namespace at the moment.

20:18 <havenwood> Move `Pane` code to `lib/rcurses/pane.rb` so `RCurses::Pane` namespace mirrors its file location.

20:19 <havenwood> Or rename your gem `pane` works too. 😈

20:20 <havenwood> (Since the name is available.)

20:22 <havenwood> isene: You seem to be missing a gemspec. I'd go ahead and cut a gem.

20:24 <havenwood> I'd lean towards making the `String` monkeypatch optional with an explicit require. Or a refinement.

20:29 <havenwood> isene: I wonder about using tty-cursor as a dep and mixing in your additional behavior. If you decide to use it inline, double check their MIT license requirements for republication.

20:30 <havenwood> (Just add their little LICENSE contents above where you use the code.)

20:30 <havenwood> Or no need if you use the gem through the gemspec.

20:31 <havenwood> s/use/reproduce/

20:31 <havenwood> Uhg, for parenthetical.

20:32 <havenwood> To be clear, add the LICENSE above where you use exact code or no need if you use the gem as a dependency rather than reproducing the code inline.

20:33 <havenwood> isene: My main feedback would be to cut a gem and in the process shape it a bit into gem conventions. 💎

20:35 <havenwood> You technically cannot choose to public domain someone else's MIT code, so I'd adopt MIT or use the gem as a dependency rather than reproducing its code.You technically cannot choose to public domain someone else's MIT code, so I'd adopt MIT or use the gem as a dependency rather than reproducing its code.

20:36 <havenwood> I'd suggest using it as a dependency.

20:37 <havenwood> You also might consider a public domain license for yourself, like https://spdx.org/licenses/CC-PDDC.html

20:37 <havenwood> RubyGems understands SPDX licenses, and it's really nice to use the official one in your gemspec for the license you intend.

20:37 <havenwood> CC-PDDC would be one option to capture the public domain spirit.

20:38 <havenwood> https://creativecommons.org/publicdomain/

20:39 <havenwood> And for RubyGems, I'd just give a pass through the guides and follow where it says to put things. https://guides.rubygems.org/

20:40 <havenwood> isene: TL;DR: cut a gem and adopt MIT or use that bit of code through a gemspec dependency.

20:41 <havenwood> Congrats on the project milestone!

21:42 <isene> Gem is already cut and published to RubyGems (hence the gem install rcurses) - but I have the gemspec thingy in a different local directory. But yes, it's better to include it in the Github repo. I'll do that with all my gems (now 14 in total). It's not actually using tty-cursor directly - rather that I found the ANSI codes there - and nobody has license to those... I use the Unlicense for most I

21:42 <isene> publish on Github.

21:42 <isene> And thanks for the namespace suggestion. I will certainly fix that :)

22:37 <johnjaye> Rounin: if you work with javascript everyday can you give me a tldr list of tools to use

22:37 <johnjaye> so when i'm done learning ruby i can just dive in

22:43 <Rounin> johnjaye: Hmm... I'm not really at the forefront of what's fashionable there, but I just use whatever editor is at hand where I work + React to make single-page apps (isn't Angular the other popular one?) + TypeScript to get some sanity occasionally, + Yarn or NPM to get dependencies ... For packaging the app (minifying etc.) I tend to use create-react-app, which apparently one shouldn't do, because it's past EOL... Some people are saying it's Vite now?

22:45 <johnjaye> right but i haven't even heard of half of those.

22:45 <Rounin> Hmmm, presumably

22:48 <havenwood> Rounin: Or Svelte

22:49 <Rounin> havenwood: Ah... It rings a bell! Guess I should figure one of those out one of these days

22:50 <havenwood> I've been liking HTMX and adam12 has pointed me to Unpoly.

22:50 <havenwood> They both pair fantastically with Ruby backends.

22:50 <havenwood> Then you can sprinkle just a tad of JavaScript on top where needed.

22:51 <havenwood> https://htmx.org/

22:51 <havenwood> https://unpoly.com/

22:53 <Rounin> Ah, right... JavaScript for the frontend... I was imagining some sort of beautiful union of Ruby and JavaScript in one file

22:53 <Rounin> Scruby

22:53 <Rounin> If noone's used that name yet, we should use it for something

23:05 <kjetilho> Scruby::Do!

23:05 <adam12> Unpoly is love. Unpoly is life.

23:54 <havenwood> I think this proposal to fill critical missing HTML gaps makes sense https://github.com/alexpetros/triptych