Earlier quoted context omitted.
killing xul was the worst decision after the australis redesign
People seem to be forgetting how clunky and resource intensive XUL was, and how many times they had to kill xulrunner.exe just to keep their desktop running.
Nook Browser
121–125 of 125 posts
Re: Nook Browser
#122Earlier quoted context omitted.
> What most sticks out to me is the "Managers" directory. I've seen similar patterns before, even at my current place of work, but they seem to correlate with less experienced implementations What is wrong with such structure? How would you structure this code? Genuinely asking
There are no peer-reviewed studies yet for me to corroborate this with, but I've seen this pattern primarily from a specific type of autistic, and it's similar to an actor pattern: a Manager is expected to entirely "manage" whatever feature it's concerned with. This is usually different from a simple module by not collecting related functionality regarding the feature, but rather trying to contain the entire feature…
Re: Nook Browser
#123Earlier quoted context omitted.
Why, do you? Perhaps quibbling over an upvoted comment is a pattern that tires me. You karma cumulative karma is around 120 if I read it correctly. Mine is 7356. I think I know how to turn a popular idiom.
A second spent thinking about HN karma is one too many. >Perhaps quibbling over an upvoted comment is a pattern that tires me. You could just simply not reply if you think I'm not engaging in good faith, as opposed to actively sabotaging the forum with pointless trolling. What's the point?
Re: Nook Browser
#124Earlier quoted context omitted.
There are no peer-reviewed studies yet for me to corroborate this with, but I've seen this pattern primarily from a specific type of autistic, and it's similar to an actor pattern: a Manager is expected to entirely "manage" whatever feature it's concerned with. This is usually different from a simple module by not collecting related functionality regarding the feature, but rather trying to contain the entire feature…
What the hell are you talking about?
Re: Nook Browser
#125Earlier quoted context omitted.
To me I always assumed it was heir apparent to NeXTSTEP. I feel like there was a lot of missed opportunities back in the day. Imagine all the manpower going into Gnome and/or KDE going into GNUStep and keeping up with Apple APIs + embrace/extend of Apple APIs.
Precisely. Gnome, KDE, XFCE, and literally any other Free Software DE implement the Windows kind of desktop organisation. While WindowMaker/GNUStep show what the unexplored future could've been.
NeXTSTEP's own "Features and Benefits"[1] 6 pager doesn't particularly feel illuminating / compelling either. I'm interested in object integration, object persistence, and object linking, but I don't really know in practice what that was like or what was really there & used. The rest sounds fine & maybe quite advanced for it's age, but it's not clear to me that there was a bunch of material left unexplored over time. Other than what remains a really interesting but abstract idea, that I don't know how was used, of there being objects, somewhere, which plenty of programs individually have & which COM & DCOM had in Windows for years, which CORBA, DCOP, DBus and others also had.
I want a lot to know more. But I just don't know what exactly people are excited over. I don't know what remains novel, what got abandoned. It feels like an early version of a modern desktop, in any decent Linux compositor / display server.