FYI the google font link seem to break some FF users so I took that out.

Hi Hn'ers,

I making this posting to show you a personal project of mine that I've named Beunto (it's an app builder for single page web apps). I've chosen to link a blog post first since I feel there needs to be an understanding of what you are looking at. The post does link to a proto-type app [1], built with Beunto, that I've deployed for just the HN community to take a look at. With that said, there are some issues I want to highlight, in addition to the posts overview, that I think will help frame the current state:

* It is largely experimental at this stage.

* It requires js and I would consider it intensive.

* Currently has a large js payload (842kb minified, which I should be able to get to 500kb or so in the future)

* You don't need to create an account to check it out (that's only for persistence and search capabilities).

* It's not open source (at least not yet, as I've not decided on its future path)

* It has only been used with Safari, Chrome and FF on Mac OSX, so I wouldn't expect much outside of that set-up.

* Everything is very custom and I know there are HNer's with strong opinions against some things I've decided upon, so try to keep an open mind as it can and will change, evolve and continue to develop.

Thanks for checking it out. Tim

1. The Goal Tracker App: https://beunto.com/my/goals

> The only issue I've had with older folks is that they often say 'not my job'.

Which, from my experience, is not a bad thing. It's often a sign of someone who recognizes that meeting everyones else's expectations at the cost of their job expectations is short sighted and the equivalent of shooting yourself in the foot.

And rarely does anyone have enough time to even meet their personal job expectations.

There are those whom are just lazy and only want to contribute the least amount possible, but I think you'll find that's not limited to older folks.

There are two sides of "not my job." There is the Art of Saying No where you protect your deliverables, and there is the non-team player who wont help others.

> Right now the US has ~4 workers per retiree. That's going to be dropping to about 2 in the next few decades.

I think it's more like a 1/3 drop will take 45 years:

https://www.econdataus.com/workers.html

not that it changes your overall point by much.

I sure hope they put their retirement investments into companies that pay their workers enough that society still functions. My bet would be on complaints about how milk is five times as expensive as it was back in the 80s instead.

> nursing et al are very 1:1 jobs with or without the help of technology

How's that? I'm not familiar with the industry at all, but every place I've seen has far fewer nurses than patients. Is there a source on this information? Or some inside information I am unaware of? Or are you just exaggerating by using the term 'very'?

By 1:1 I meant that nurses spend time hands on with patients one at a time.

> Clojurescript.... Personally, I don’t like it on a matter of principle: I don’t like things that compile to JavaScript. It doesn’t seem like anything you really need to write better code.

Maybe I don't understand what the alternative is when you want to write client side code for the browser - js?? I use Clojurescript and find clear benefits.

By way of example I often found the general setTimeout functionality to be a nightmare for scheduling delays. Most of the time it works, but periodically I find it blocks or fails (via a dependancy chain) and then have to spend time arranging code abnormally to mitigate. In clojurescipt I use core async.

  (defn timeout [ms]
    (let [c (async/chan)]
      (js/setTimeout (fn [] (async/close! c)) ms)
     c))

Never looked back. Never had a delay problem - Ever.

cljs core.async and many other features have made it so much more enjoyable to write client side code. Don't even get me started on callbacks.

> Oh, and one last thing. I feel it’s obligatory at this point for me to say, please don’t spend too much time researching Scheme dialects. Just pick Racket and start coding

I've had the opposite experience so thanks, but no thanks.

What was your experience with Racket?

This dates back about 5 years ago, but I found Racket's libraries were rough. Often they amounted to prototype work that never got fleshed out, they were ill maintained, low in quality, and many just wouldn't load. And these were general purpose libraries; like even just basic database stuff.

I moved on to Clojure.