6 ms·

And, perhaps (?), that ties in with the GUI being the most proprietary thing here, thus, them building that last/less or wanting to de-emphasize it?

cxr 2mo ago
Aristo already exists and looks great: <https://hn.algolia.com/?dateRange=all&query=aristo%20cxr&sort=byDate&type=comment https://hn.algolia.com/?dateRange=all&query=aristo%20cxr&sor...>
- ripdog 2mo ago
  The real link: https://www.cappuccino.dev/aristo/ https://www.cappuccino.dev/aristo/ Looks great, so sad that it's yet another web framework. Kinda smacks of GNOME, though.
  - kentosi 2mo ago
    Oh wow I remember trying cuppaccino about .... 15 years ago maybe? Fun times, though I never built anything serious.
  - deleted 2mo ago
    [deleted]
- terhechte 2mo ago
  Man I used to develop SAAS software using Cappuccino. Since I knew Objc (and JS/CSS) really well it was such a beautiful system for development. I'm sad it never went anywhere
  - Bluestein 2mo ago
    May I ask what made it special? It does look awful "elegant" and well put together ...
    - terhechte 2mo ago
      when Cappuccino was written, Apple was still using the Objective-C + AppKit stack. It had been honing this stack for years, every WWDC brought useful and deliberate improvements. Back then macOS development was much more niche (and tech in general). They could take their time. MacOS releases happened every couple of years, not every year. Not the kind of outcome we have nowadays where changes are rushed because of demand. Cappuccino improved upon javascript by using a different language (objective-j) that added many features js didn't have, and it used the same (mostly) well-honed api as AppKit. In comparison to other js UI frameworks of its time, it was lightyears ahead.
      - Bluestein 2mo ago
        The entire pace of releases itself made everything more "breathable" and (ostensibly) higher quality.- PS: Compare to today, with code slop (and good agent-mediated code: It also increases overall speed).-

cxr 2mo ago

Aristo already exists and looks great: <https://hn.algolia.com/?dateRange=all&query=aristo%20cxr&sort=byDate&type=comment https://hn.algolia.com/?dateRange=all&query=aristo%20cxr&sor...>

ripdog 2mo ago
The real link: https://www.cappuccino.dev/aristo/ https://www.cappuccino.dev/aristo/ Looks great, so sad that it's yet another web framework. Kinda smacks of GNOME, though.
- kentosi 2mo ago
  Oh wow I remember trying cuppaccino about .... 15 years ago maybe? Fun times, though I never built anything serious.
- deleted 2mo ago
  [deleted]
terhechte 2mo ago
Man I used to develop SAAS software using Cappuccino. Since I knew Objc (and JS/CSS) really well it was such a beautiful system for development. I'm sad it never went anywhere
- Bluestein 2mo ago
  May I ask what made it special? It does look awful "elegant" and well put together ...
  - terhechte 2mo ago
    when Cappuccino was written, Apple was still using the Objective-C + AppKit stack. It had been honing this stack for years, every WWDC brought useful and deliberate improvements. Back then macOS development was much more niche (and tech in general). They could take their time. MacOS releases happened every couple of years, not every year. Not the kind of outcome we have nowadays where changes are rushed because of demand. Cappuccino improved upon javascript by using a different language (objective-j) that added many features js didn't have, and it used the same (mostly) well-honed api as AppKit. In comparison to other js UI frameworks of its time, it was lightyears ahead.
    - Bluestein 2mo ago
      The entire pace of releases itself made everything more "breathable" and (ostensibly) higher quality.- PS: Compare to today, with code slop (and good agent-mediated code: It also increases overall speed).-