artpar

Thanks for the tip, I did not know about contain: strict. position absolute ofcourse everyone knows. Will checkout contain. But doesnt sound like worth trying out html based canvas again just for contain. I feel like I have come quite far ahead with the native canvas approach.

I wanted to implement a whole canvas native workspace, I started with a html only implementation and "fake canvas" approach but even for moderate number of panels (~50) the responsiveness dropped quite a lot. So I went with a new implementation with "real canvas" and worked out the panels/interaction.

In terms of performance this approach worked out much better (able to easily handle 1000+ panels/nested panels at 60+ fps) but the complexity goes very high in the implementation of each panel. As in I cant just use for eg a markdown rendering js library or any third party ui component. And frequently make a change would result in massive performance degradation.

https://canaster.in/

Currently I have text/markdown/image/audio/video and pdf panel (you can drag and drop files)

I wonder if i should take another go at it and implement using html-in-canvas api. Afraid of the api being not maintained if they dont see benefit or usage?

i just found out about this. any thoughts why isn't this more main stream ? i was trying to make a in place replacement for google services on android (to begin with) but apparently just implement the protocols doesn't "work out of the box" for android.

I mean imagine if a (expert) human was just writing code for 3 years straight without doing any of the other things you mention like review/testing/refining. I would expect that app also to be performing/behaving poorly. So kind of like a worse waterfall sdlc. So perspective is okay ?

> A vibe coded app is, in human hours, not only a few days old but closer to two or three years old.

I think that's an interesting way to put the quality of vibe coded apps in perspective. A human developing a software will definitely notice the obvious issues if they are using it in much less time frame (6 weeks? 6 months?).

It feels like the waterfall style software projects which would be just built for years and when delivered turn out to be mostly useless.

I am not expecting any consistency. I am expecting a claim of consistency NOT to be made for keyboard shortcuts either on osx or windows.

Consistent but optional, sounds inconsistent to me. Anyways that was 1 example, here's some more.

⌘R Reload in Safari; reply in Mail; reveal an alias's original in Finder

⌘L Address bar in browsers; message filter in Mail; clear to previous mark in Terminal.

⌘I File info in Finder; italics in text; inspector in Terminal.

I can keep going. This is not to say windows/osx is worse or better, just that claims of consistency are not suitable on either

> I love that on macOS all in-app shortcuts are consistently Command+Something, like Q for Quit, W to close a window

Yeah consistency is great, similarly cmd+t closes a tab, wait cmd+w closes a tab not a window. and cmd+w in vlc does not close vlc, cmd+w in finder does close the window.

> because writing code used to be the slow part

I don't understand how people have that stated as a fact. Coding was never the slow part. Neither pre-llm, nor now. How it needs to be done is software engineering. And that corresponds now to the "thinking" part of llms, so unless you are making the llm "think in lisp" its not useful. How would that even work. training data to be completely in lisp ?

> Lisp programs are often much more concise because macros let you abstract away recurring patterns and make them part of the language itself

functions ?

> So the bigger the program gets, the bigger the difference. In my own experience the apps I've built in Common Lisp end up about six to seven times shorter than the Python versions

By that logic writing code in this concept language made up completely of symbols would take you even further ( https://github.com/artpar/guage ) but in practice it doesnt because llms arent trained to that extent on this.

Yeah thanks to LLM hill climbing and PPTs being easily available and they being nothing more than just xmls this did not involve any gotchas, just a about a weeks worth of goal chasing with manual verification. I did have to stop LLM into hardcoding a lot of times trying to escape the actual goal.

But based on this I thought I could make something similar for cad files, and they turned out to be an entirely different monster. the cad spec is like 1000x bigger than ppts, cad files themselves were hard to gather for test targets. 70-80% of their spec is public and remaining is driven by private vendors. the format itself is in binary. The LLM has been chasing that goal since about 2 months now and its nowhere close.

I have made puppt cli for this, it includes high dpi rendering per-slide/all-slides and in place editing

https://github.com/artpar/puppt

it allows your llms to see the ppt files structurally apart from just rendering it

100x.bot is completely powered by daptin, canaster.in (work in progress, i am redoing the frontend in webgl) is also running on daptin. there are various internal company services which are running on daptin which i cannot name here.

almost any project which matures to requiring a user authn/authz (and there are always assets owned by users) i default to using daptin

I have hardened it a lot over the last 10 years, especially in terms of transaction/concurrency/security. happy to help you setting it up in your project. you can dm me ( x.com/phparth ) or leave an issue on the github repo

hey I have built daptin for this and been running all of my projects with daptin as the sole backend server for data/authn/authz.

1. oauth/account management -> daptin can serve itself as a oauth provider as well as allow "login via oauth" on 3rdparty oauth servers. you get a full managed account including forget/reset password

2. permissions -> this involves more than rate limits, like who's the owner of what and you can manage permissions at user/guest/group level

3. handling payments -> fraud monitoring is usually part of the payment processor and you are not supposed to do much about it

and these days you can point your llm agent to the wiki to get most of the stuff done without needing to read the docs yourself. you just need a cheap vps (the $5 ones on digital ocean will be more than fine).

https://github.com/daptin/daptin/wiki

https://github.com/daptin/daptin/wiki/Permissions

The key takeaway pretty much applies to the authoring of the article itself. The LLM knew what all happened but couldn't put it into a readable article.

it is a javascript interpreter in javascript, based on the ast generated by acron parser. to avoid calling "eval" or "new Function" for code executed by un-trusted sources. a sandbox

screenshots in the github readme https://github.com/artpar/canopy

Here is an implementation you might like

https://github.com/artpar/terminal-tunnel

P2P with webrtc (pion ftw) with e2ee

client side is webui so you can use on any device

ps: the default Cloudflare Worker from my account is already maxed out so you will need your own exchange (self host on your account)

I tried that over a month

except '- the directness and simplicity of JavaScript'

https://github.com/artpar/guage

But somehow the language feels so foreign. it can obviously do hello world, but I don't have a real use case

PS: the "Pure symbols only" is no longer true, most symbols have been converted to English names

and, the "days" you see there in the markdowns are "claude code sessions", not actual days

I did show hn just yesterday you don't need tailscale or any 3rd party server. Just use webrtc and it's just your mobile and laptop. end 2 end encrypted. no 3rd party dependency.

https://news.ycombinator.com/item?id=46514587

Thanks! And wow, getting a kind word from a Pion maintainer means a lot. Your library made this whole thing possible. The datachannel API is incredibly clean to work with. Appreciate you and the team's work on it.