home.netscape.com in 1997
web.archive.org
web.archive.org
You can also change the port number to your preferred year.
This is really fun on retro systems / web browsers.
Detailed instructions: https://theoldnet.com/docs/httpproxy/index.html
There's also Browservice: https://github.com/ttalvitie/browservice
It is lo-fi, not trying to mimic the orginal page, unlike those that do the giant image trick.
Just paste your URL to the end of this URL to use it: http://frogfind.com/read.php?a=
EDIT: example using a random MDN page: http://frogfind.com/read.php?a=https://developer.mozilla.org...
You can kinda tell when an idea grows directly from a core joke, pun or other clever play.
In the 656th century we will be behind 50 layers of NAT.
These days we're just browsing glossy magazines.
https://uxmovement.com/content/why-you-should-never-use-pure...
no idea to what extent, if at all, it is true. I can imagine there being a grain of truth in there but that implementing this correctly is much more difficult and nuanced than it might seem at first glance - most "digital designers"[1] probably don't get the budget/freedom to properly tackle accessibility in their commercial projects, I can also imagine that the majority of digital designers are 'young' and have close to 20/20 vision making it that much harder for them to truly put themselves in the shoes (eyes?) of people with lesser than perfect vision[2].
as someone with only a laymans' understanding of all this stuff I'm probably guilty of talking out of my **; I welcome someone with real graphic design credentials putting me straight :D
[1] "digital designer", a person working in/with visual design, who started employment, or was born, after the release of the first iPhone ;-) (alternatively someone working in the design industry who never had the privilege of buying a copy of "The Face" for the simple fact they we not born in 1985)
[2] a category I begrudgingly have to admit to being part of more and more ;-/
I also have (partially outdated) custom stylesheet that fixes that for websites I {used to,} visit often: https://jenda.hrach.eu/w/blackweb
I liked throbbers because they signalled "ok, I'm going to the network to fetch what you asked for" as opposed to the hourglass cursor which indicated ordinary computer activity. It was Windows 98 that ruined the experience and thrill of "going to the network", because Microsoft decided that the web and the local desktop should merge into a single, seamless experience. They seemed not to understand that the network was fundamentally different, and in many ways more dangerous, than the local PC because it is almost always, as we say today, someone else's computer; and that the end user should be made aware of and encouraged to respect that difference.
I think the nostalgia for the feeling of navigating cyberspace is part of what inspires art movements like vaporwave, with its incorporation of 90s GUI elements in its aesthetic. In the 90s, there was always this ambient feeling of "this boxy beige Macintosh isn't a sleek Ono-Sendai cyberdeck, but it's an acceptable interim substitute until you get a cyberdeck which could be any day now". We were sort of roleplaying at being a part of sort of a beta version of Gibson's tragically hip cyberfuture, not realizing that we were ultimately being sold the shitty parts of that future without any of the cool parts. It's kind of like the joke about Bill Gates in hell: the cool stuff was just the demo.
One weird side effect of this was that Internet Explorer and Explorer itself were integrated. At a time, you could set your desktop wallpaper to an HTML page. There were even "HTML apps" introduced around the same time* which I believe is still being somewhat continued today for Windows 10 widget development
I thought it was stupid and potentially dangerous because it misled users to treat the web and local resources equally, and put the same amount of trust in each. Of course nowadays, not treating local resources with the same amount of distrust we give the web is a major security fail, and that's why we must notarize and sandbox everything.
jwz's favorite throbber (also my favorite) captured this feeling particularly well since it is literally an animated compass[1].
I actually got really into the history of browser throbbers back when I was in college — I ended up archiving all I could find from the mozilla ftp and internet archive[2].
[0]: https://www.jwz.org/doc/about-jwz.html
[1]: https://www.jwz.org/compass2.gif / https://www.jwz.org/doc/about-compass-anim.gif
[2]: http://cs.gettysburg.edu/~duncjo01/archive/browsers/throbber...
While I used to maintain an SeaMonkey (Mozilla Suite) xpfe complete theme with a properly animated throbber, I actually still use the jwz throbber through my unfinished xpfe userChrome.css in Firefox to this day.
Sadly, there are no css dynamic css classes above the #PanelUI-menu-button element in chrome://browser/content/browser.xhtml, so it's not possible to properly animate it without javascript; for now, it animates when you hover over it.
[0] https://addons.mozilla.org/en-US/firefox/addon/firescape_nav...
That sounds interesting ..
Netscape Visual JavaScript helps make it practical and easy to develop sophisticated crossware applications through drag-and-drop components and simple visual programming. You can easily incorporate sophisticated functionality and database connectivity into web pages without writing code. Netscape Visual JavaScript enables you to deliver finished applications to users quickly and easily.
https://web.archive.org/web/19970613210706/http://home.netsc...
[0] https://web.archive.org/web/19970613210940/http://home.netsc...
https://internet.watch.impress.co.jp/www/article/970409/vjs....
Image via https://internet.watch.impress.co.jp/www/article/970409/vjs....
[1] https://www.amazon.co.uk/Official-Netscape-Visual-JavaScript...
[2] https://www.amazon.co.uk/Netscape-Visual-JavaScript-Dummies-...
Isn't that amazing? One of the most widely used telecommunication programs in the world at the time, every continent, claiming some two million users. That number does not raise much of an eyebrow now, but it blew my mind. I first used the Internet in 1996-7 at the local public college. Netscape Navigator, on the Power Macintosh. I was only in middle school, but already interested in computers.
One could stream video even then if you had the bandwidth. From NASA, from people with webcams pointing at their office parking lots. I was blown away. A multimedia world of millions of people. And mostly academics and some fellow geeks, back then. Being able to stream a video of repairs in orbit, from a computer in another country, on a machine I was already starting to learn to program myself, is a vivid memory. That experience changed me, and I got hooked online, for better and for worse.
Edit: There's an online disassembler here that can grok the downloaded file: https://onlinedisassembler.com/
Life was great when we could mod everything!
---
[1] I say 'they' I mean 'me' - I did application packaging at the time.
[2] Upvotes for those who guess the bank! :D
Does it still count as a guess if I clicked on your username, visited the website you listed on your profile and read the CV that you have on said website? :p
Topics include:
-mars rover
-global warming
-The P.R.I. losing their elections in Mexico
-clashes in Northern Ireland
-Congressional hearing into Chinese political influences
-Feds puzzled by low inflation (https://web.archive.org/web/19970709022322/http://www.abcnews.com/sections/business/ap_fed704/index.html)
Last one is way too ironic.I still use it as a reference anytime someone recommends making the same fatal software product mistake that Netscape did.
https://www.joelonsoftware.com/2000/04/06/things-you-should-...
and here's the netscape homepage but with the old netscape "mosaic communications" domain: https://web.archive.org/web/19980109011204/http://home.mcom....
https://web.archive.org/web/19961116025218/http://developer....
Check out that jaggy squinched text in those diagrams! Somebody resized a GIF file smaller to save some bandwidth, and so it would fit on a 640x480 screen. 1997 web design at its finest!
Pro Tip: Never name a user interface toolkit after "MFC" with "M" crossed out and "I" written in -- that doesn't make it sound very appetizing, and wrongly sets expectations that you can actually write a viable application with it, given enough pain and suffering. Just as you should never name a component system after "COM" with "XP/" written before it, for the same reason.
https://news.ycombinator.com/item?id=12968830
And while you're at it, you should never name a company after "Microsoft" with "Micro" crossed out and "Sun" written in, because it makes it look like you define your company in terms of your biggest competitor instead of having your own identity and mission, which is what losers and foaming-at-the-mouth libertarian Trump supporters like Scott McNealy do.
https://www.cnbc.com/2019/09/17/trump-silicon-valley-fundrai...
Marimba was much better at naming things, thanks to Kim Polese, who came up with the name "Java" when she was at Sun, then left Sun with several of the finest Java engineers to form the drum-themed Java start-up company, "Marimba". Their product "Castanet" literally cast a net to deliver interactive content over the internet, and their Java-powered HyperCard-like user interface builder "Bongo" actually let you interactively edit Java scripts to handle events, by calling the Java compiler at runtime (which was unheard-of at the time, but normal for IDEs to do now).
https://www.wired.com/1996/11/es-marimba/
I wrote a comparison of Bongo and IFC about a year before that Netscape page was captured in 1997.
https://news.ycombinator.com/item?id=19837817
>Wow, a blast from the past! 1996, what a year that was.
>Sun was freaking out about Microsoft, and announced Java Beans as their vaporware "alternative" to ActiveX. JavaScript had just come onto the scene, then Netscape announced they were going to reimplement Navigator in Java, so they dove into the deep end and came up with IFC, which designed by NeXTStep programmers. A bunch of the original Java team left Sun and formed Marima, and developed the Castanet network push distribution system, and the Bongo user interface editor (like HyperCard for Java, calling the Java compiler incrementally to support dynamic script editing).
https://people.apache.org/~jim/NewArchitect/webtech/1997/10/...
>While I was working at Interval Research Corporation in 1996, after playing around with and reading over the source code and documentation, I wrote up a deep comparison and analysis of Internet Foundation Classes (IFC) versus Marimba Bongo (which was written by Arthur van Hoff, who worked on Java, wrote AWT, and before Java wrote another user interface system for NeWS similar to Bongo and HyperCard in PostScript, called HyperLook), and other related user interface component technologies.
https://donhopkins.com/home/interval/ifc-vs-bongo.html
>This is a comparison of two component frameworks for Java, IFC and Bongo.
>IFC (Internet Foundation Classes) is from NetScape, and is similar NeXTStep, which was written in Objective C. It was written by some former NeXT developers, whose company NetScape bought because they needed a Java toolkit.
>Bongo is from Marimba, and is similar to HyperLook, which was written in NeWS object oriented PostScript. Marimba was founded by some of the original Sun Java developers, who left Sun to form their own company.
>[That also compares IFC with Microsoft's ActiveX/OLE/COM/MIDL stuff, and gets into some Java/JavaBeans/J++/CORBA/OpenDoc politics, and includes some comments by Arthur about IFC, AWT, Bongo, JDK 1.1, etc.]
>[...]
>Date: Mon, 06 Jan 1997 13:27:40 -0800 To: hopkins@interval.com (Don Hopkins) From: Arthur van Hoff <avh@marimba.com>
>Hi Don,
>Although I am pretty biased I would like to make one or two comments.
>We decided to build a very AWT friendly GUI toolkit. What this means is that there are as few gratuitous differences as possible. We did this for two reasons. One is that we don't want our developers to relearn what they know about the AWT, and secondly we are anticipating the integration of JDK 1.1 functionality sooner rather than later.
>The IFC has made a huge mistake in reinventing classes like the Event, Graphics, and Color classes. This makes it extremely hard to integrate IFC components into existing AWT applications (and visa versa). We think this is a great advantage of Bongo.
>We also focussed on mimicking the PC look&feel whenever possible. We've had very positive feedback on this feature. It seems to be what people want. If you want you can still create your own look and feel, but at least the default is familiar to most users.
>I strongly believe that JavaBeans is the right way to go. It is big, and it is not a framework for building widgets, but at a slightly coarser granularity it solves the problem of integrating components from other vendors very effectively.
>Over the next few months we are going to put effort into the following areas:
>JDK 1.1 integration
>JavaBeans support
>Extend the widget set with new business oriented widgets
>Extend the builder with better layout functionality
>Make the builder more content oriented
>Add better support for time based media
>Add some paint/draw functionality to the builder
>Further improve our support for PC-look alike widgets
>Have fun,
>Arthur van Hoff