Skip to content
HomeVideos
AllLongsCategoriesPlaylists
BooksBlogsPodcasts
HistoryListsWatch laterLiked videosFollowing

The videos, books, blogs and podcasts Hacker News keeps recommending, all in one place.

VideosBooksBlogsPodcastsAboutPrivacySettings

Data from Hacker News, HackerTube, HackerBooks, HackerBlogs and Open Library. Credits · Not affiliated with Y Combinator.

HomeVideosBooksBlogsPodcasts
Ctrl K

    NeXT vs Sun

    hoffman60613

    3 HN recommenders · recommended in 15 months, 2015–2026

    YouTube

    17:48 · 116K views · Nov 23, 2011

    A 1991 NeXT promotional video that stages a head-to-head programming contest between a NeXT computer and a Sun workstation. It shows NeXT's interface builder and object-oriented tooling producing an application far faster than traditional UNIX development.

    HN uses it as the canonical example of rapid application development and object-oriented tooling productivity, though many note it is biased marketing.

    Software Engineering & LanguagesSoftware architecture & designGUI, HCI & interface historyTesting, debugging & developer tools
    1. 35:09
      NeXTSTEP Release 3 Demoblatherskyte625K views • 20 years ago
    2. 35:07
      NeXTSTEP Release 3: A Demonstration with Steve JobsJoseph Spiros184K views • 6 years ago
    3. 32:56
      Bret Victor The Future of ProgrammingJoey Reid305K views • 13 years ago
    4. 56:27
      In Search of TomorrowBerkeley Institute for Data Science (BIDS)18K views • 10 years ago
    5. 14:10
      Lotus Improv for NeXT 1990Thierry Hubert4.2K views • 8 years ago
    6. 8:19
      Code Bubbles: Rethinking the User Interface Paradigm of Integrated Development EnvironmentsAndrewBragdon284K views • 16 years ago
    7. 6:35
      Looking GlassVinko232K views • 20 years ago
    8. 46:18
      Om Next - David NolenClojureTV44K views • 11 years ago
    9. 16:48
      Yesterday's Computer of Tomorrow: The Xerox Alto │Smalltalk-76 DemoComputer History Museum38K views • 8 years ago
    10. 54:20
      Bret Victor - Inventing on PrincipleRui Oliveira339K views • 14 years ago
    11. 1:17:21
      The GUI should be better. A lot better.Accursed Farms397K views • 6 years ago
    12. 14:06
      Tomorrow Corporation Tech Demoretrogameinternals107K views • 3 years ago
    13. 2:50:14
      Simple Code, High PerformanceMolly Rocket464K views • 5 years ago
    14. 2:50
      Live Debugging in Smalltalkjarober1.2K views • 18 years ago
    15. 44:35
      Object-Oriented Programming is BadBrian Will2.6M views • 10 years ago
    16. 1:32:47
      Data-Oriented Demo: SOA, compositionJonathan Blow201K views • 11 years ago
    17. 23:41
      Windows 8: The Animated Evaluationblogphilofilms645K views • 13 years ago
    18. 35:42
      Progressive Performance (Chrome Dev Summit 2016)Chrome for Developers34K views • 9 years ago
    19. 28:03
      Object-Oriented Programming is Embarrassing: 4 Short ExamplesBrian Will2.2M views • 10 years ago
    20. 43:30
      Are we stuck with the same Desktop UX forever? | Ubuntu Summit 25.10Canonical Ubuntu510K views • 10 months ago

    18 comments from Hacker News

    1. @lprovenOct 2024· in “Hofstadter on Lisp (1983)”

      So very much this. I think programming languages are also long overdue for some controlled trials. They can't be blinded: any experimental subject bright enough to learn to program is probably going to know what language they are programming in. But trials comparing the effectiveness of different languages. How long they take to attain a specified level of proficiency, how long to learn enough to produce working code, and importantly, readability: for instance, how long it takes to find intentionally-planted bugs in existing, unfamiliar code. NeXT did this, way back in the 1980s, and Sun lost badly: this video There is a writeup of some of it here: [LINK] But speaking as a non-video-liker, this 17min one is worth it.

      RecommendsView on HN
    2. @indymikeMar 2017· in “Was object-oriented programming a failure? (2015)”

      Started programming in 1982. Object oriented programming was a huge advance - especially in developer productivity. A side effect was the dramatic improvement in developer tools: gui builders, IDEs, etc all improved dramatically. Probably the watershed moment for OO was this NeXT video that showed the difference: this video

      RecommendsView on HN
    3. @rileyphoneNov 2022· in “SwiftUI Is Convenient, but Slow”

      There's a fun bit of marketing [0] NeXT did when AppKit was the new thing, comparing building a reasonably non-trivial application with it to a Sun workstation using C. Obviously biased, but still an interesting look into the development environment that among other things brought us the Web and DOOM. 0. this video

      RecommendsView on HN
    4. @pjmlpSep 2020· in “Nova by Panic”

      It is a bit hard to explain in an HN comment something that requires live experience, You can start by having a look at, [LINK] "Eric Bier Demonstrates Cedar" [LINK] "Alto System Project: Dan Ingalls demonstrates Smalltalk" [LINK] "SYMBOLICS CONCORDIA ONLINE DOCUMENTATION HYPER TEXT MARKUP 1985" [LINK] You can see how NeXT builds on many of these concepts on the famous "NeXT vs Sun" marketing piece, this video Sun also had some ideas along these lines with NeWS, "NeWS: A Networked and Extensible Window System," [LINK] Naturally OS/2, BeOS, Windows, macOS, iOS, and even Android share some of the ideas. Now, before I proceed note that actually modern Linux distributions have all the tooling to make these concepts happen, but it fails short to have everyone agree on a proper stack. So basically, the main idea is to have a proper full stack in place for developing a Workstation computer as one single experience, from bottom all the way to the top. On Xerox's case, they used bytecode with in-CPU execution via programmable microcode loaded on boot, and later on just a thin native glue on top of host OS. The environments had frameworks / modules for the whole OS stack, supported distributed computing, embedded of data structures across applications (OLE can trace its roots back to these ideas), REPLs that not only could interact with the whole OS (commands, modules, running applications), it was also possible to break into the debugger, change the code and redo the failed instructions.

      CitesView on HN
    5. @mistersquidAug 2016· in “NeXT vs. Sun (1991) [video]”

      @12:19: this video > At this point, we threw the programmers an unexpected but not unrealistic curve. > Like a typical user, we asked them to add a feature not in the original spec. In this case, a button would recall all the trouble logs for a particular customer. > Using NeXT Step, the NeXT programmer completed the task in about 20 minutes. > [NeXT progammer discussing some details] > The sun programmer also estimated a time of 20 minutes, but it took about 45 before he was ready to test his version. This was about 20 hours in, which means that since they started on Wed, 30 October 1991 and assuming maximum 8-hour days, they have missed Halloween and would be at least halfway into Friday. The video states that the programmers finished on Sat, 2 November. The video goes on to state that the NeXT system enabled the NeXT programmer to add a number of features such as system fonts and button icons "for free", which goes to show that the video's intended audience are managers and executives of software development teams who would of course want faster development, ad hoc requests, and cost-free features. I personally would have been tempted to (╯°□°)╯︵ ┻━┻ once they announced a planned "unexpected" feature request because rather than train users and customers to frontload requirements in order to benefit from the design decisions that would be made as a result, the video encourages customers to believe their out-of-spec requests will be more quickly accommodated if only their progr

      CriticalView on HN