News for hackers. Stuff that matters.
Re:Languages Which Almost Became CSS by frik on Friday August 04, 2017 @12:58AM (#14926419)
I used Arachnophilia (old native application, not the Java based one), Frontpage and Dreamweaver.

HTML 4 Transitional used to be very popular back in the 1999/2000. The XHTML movement was a weird hype, I tried it out but TinyMCE/WYSIWYG-editor spit out old HTML3 code at that time, so I tried XHTML 1 Transitional, but used .html extension as IE6 didn't support .xhtml. Anyway XHTML2 was a trainwreck, they were nuts to propose an completely incompatible syntax, a failed ideology and I switched back shortly after to HTML4 (2004). There was also a weird short hype around a new incompatibility Javascript version 4, short E4X. XML used to be everywhere, and some nuts tried to make XML part of JavaScript syntax - Mozilla and Adobe were into this crazy land. Thankfully it died, and there was never a JS4, but the JavaScript 5 strict was superb. CSS was okayish since IE5.5 and especially IE6 and MozillaSuite. Then there was the hype to not use tables but do everything with CSS divs. I quickly learned that a few tables and using CSS for everything else worked well in practice and gave one a responsive design long before it had a name. Loading data asynchronous used to be possible with XML on both IE56 and Firebird/earlyFirefox already in 2003, I found only two sites back then that had documentation for that obscure API back then, but it worked great - made a CD-ROM based elearning software written as one-page-app (HTML4, CSS and JS) with loading data from XML files and showing text, pictures and multimedia videos (Flash MX, before there was FLV format), that was two years before it became well know as AJAX (now XHR).

https://en.m.wikipedia.org/wiki/XHTML#XHTML_2.0

https://en.m.wikipedia.org/wiki/ECMAScript_for_XML

Re:Languages Which Almost Became CSS by tannhaeuser on Friday August 04, 2017 @02:19AM (#14926719)
E4X was a standard for XML literals in JavaScript supported by Mozilla's JavaScript, including Rhino. It was hated or unknown at best because "XML sucks", so Moz removed it a couple years ago. Of course, today folks cheer at React's JSX, which is more or less the exact same thing, yet comes with the Facebook licence. Goes to show how much irrationality there is in the evolvement of web standards. It's also something to keep in mind when judging use of the newest ES7+ syntax sugar on a project.
Re:Languages Which Almost Became CSS by coldtea on Friday August 04, 2017 @05:44AM (#14927451)
>Goes to show how much irrationality there is in the evolvement of web standards.

Well, for one E4X was never adopted by other browsers that mattered, only Mozilla.

Second, it's main use was for working with XML, which the web is glad we got rid of.

Re:Languages Which Almost Became CSS by type0 on Friday August 04, 2017 @06:34PM (#14932930)
Oh, XML will soon be only remembered as that thing which used to stand for X in AJAX.
Re:Languages Which Almost Became CSS by rhinoceraptor on Friday August 04, 2017 @12:56PM (#14930036)
JSX is really just syntactic sugar for function calls, I suppose you could use React components as data structures but that's not really the intended use case.
Re:Languages Which Almost Became CSS by pjmlp on Friday August 04, 2017 @01:44AM (#14926595)
XHTML hyper here.

Had the browsers properly adopted XHTML and the accompanying standards, and today we could already enjoy something like XAML on the browser instead of having only Chrome supporting WebComponents with workarounds like ShadowDOM to preserve local changes.

Re:Languages Which Almost Became CSS by icebraining on Friday August 04, 2017 @03:43AM (#14927053)
I also liked XHTML, but why do you see it as a transition path to something like XAML? Isn't it basically well-structured HTML?

I mean, I get that it's extensible thanks to XML, but that doesn't mean browsers would actually have an incentive to create and implement such extensions.

Re:Languages Which Almost Became CSS by pjmlp on Friday August 04, 2017 @04:50AM (#14927276)
The XAML like parts were the set of XHTML components standards.

https://www.w3.org/standards/xml/components

Basically Events, Modularization, Fragments, XForms, XQuery and possibly other parts that were still being worked on when the HTML 5 hype started.

And were we are, yet to have a Web UI designer that can match Blend, Qt Creator, Netbeans Matisse, Scene Builder, Glade, Delphi, C++ Builder,....

When I do web development I always feel like I am stuck with something not better than Notepad for GUI programming.

Re:Languages Which Almost Became CSS by tannhaeuser on Friday August 04, 2017 @08:07AM (#14928052)
Ok I have to disagree here. I believe the failure of XHTML was to cram everything into XML; I found XForms especially pointless. Now don't get me wrong, and as you know from my other posts here I'm as much of a markup geek as can be, but IMO markup is first and foremost for representing and authoring text. Just that browser content is mostly text, however, doesn't mean everything has to be markup. To the contrary, I believe XHTML (and XML in mainstream apps) fell out of favor because the spec authors tried to anchor each and everything on XML, rather than on something that makes sense for the task at hand (a phenomenon not unheard of for JSON and YAML as well). In XForms, for example, XML was used as a programming language which just never made sense. You know you're doing it wrong IMHO when you have to discuss whether you want to store your data in attributes or element content, a distinction that only makes sense for text data.

It's sad and surprising how much time and energy was wasted on XHTML. Back in february I met Steven Pemberton (XHTML spec lead back then, and of ABC/Python fame). He's just such an inspiring guy to talk to, but unfortunately, there was no time for recapitulating the XHTML situation.

Re:Languages Which Almost Became CSS by allover on Friday August 04, 2017 @05:21AM (#14927379)
> And were we are, yet to have a Web UI designer that can match Blend, Qt Creator, Netbeans Matisse, Scene Builder, Glade, Delphi, C++ Builder,....

Huh, my experience was all those things are terrible (spent some time with Qt and researching Glade, also inherited a Delphi codebase full of spaghetti code at one point).

Visual UI tools are great for prototyping, awful for maintainable code. Anyone I know who's spent any time with them ends up wanting to go back to the code.

There certainly are good Web UI designers [1], it just seems no-one wants them. There are successful visual Web UI prototyping tools tho.

[1] http://macaw.co/

Re:Languages Which Almost Became CSS by pjmlp on Friday August 04, 2017 @05:35AM (#14927418)
Those tools are wonderful and make my life on native frontend projects enjoyable, versus the pain having to deal with of Web design, which I happen to have experience since the early days (first coded web apps were C based cgis in 1997).

Trying to manually hack GUI generated code is an anti-pattern.

One has to leave the code generated by the tools to the tools, everything else should live in other code files.

Sadly I never heard of Macaw, specially on the enterprise circles I move on, in any case they seem to be gone now.

Re:Languages Which Almost Became CSS by tannhaeuser on Friday August 04, 2017 @04:46AM (#14927266)
You don't need XML for that. HTML can be parsed using SGML precisely and elegantly [1] (if I may say so for a project of mine).

If you see value in XML, you really should look into XML's big sister SGML. It gives you downward compat with XML, tag inference, type-aware (injection-free) variable and macro expansion, custom Wiki syntaxes (markdown and others), an integrated stylesheet language without new ad-hoc syntax, full HTML 5 parsing with short forms for attributes etc., and more. You might actually like it.

[1]: http://sgmljs.net/blog/blog1701.html

Re:Languages Which Almost Became CSS by pjmlp on Friday August 04, 2017 @04:57AM (#14927303)
I was a big fan of Docbook, back when SGML was more well known, thanks for the heads up.

However this is meaningless if the browsers keep being a document engine, full of workarounds to translate a mix of document tags, coupled with some generic <div> and <span> into some kind of general purpose GUI layout engine.

Having to find the proper incantation of CSS3 transforms to portably trigger GUI acceleration is a good example of such hacks.

Even if it is yet another hack, webcomponents + shadowdom looked it would be the solution, even if a bit hackish, but it is Chrome only.

Re:Languages Which Almost Became CSS by laumars on Friday August 04, 2017 @04:18AM (#14927192)
I loved Arachnophilia. Awesome little editor. Wasn't keen on Dreamweaver - I mean I guess it's ok if you're a designer but not really something I'd have ever recommend for developers. Frontpage though; you're brave admitting to using that!

My favourite of the failed web technologies was VRML. Back in the 90s I used to create epic 3D landscapes that would render inside the browser much like how some experiment with WebGL these days. But this was long before it was 3D accelerators were common inside PCs (they were still very expensive so most graphics cards software rendered 3D models). VRML I think was a victim of being too ahead of its time.

The web was exciting back then. Nobody really knew what you could or couldn't do with it. These days I feel we've lost something with all these bloated frontend frameworks which act like magic boxes in that an alarming number of frontend developers don't understand how their code executes. But I guess that's what happens when science or technology becomes business.

Re:Languages Which Almost Became CSS by type0 on Friday August 04, 2017 @06:46PM (#14932993)
> Frontpage though; you're brave admitting to using that!

FrontPage was a great educational tool, sure it produced crappy HTML, sure it was IE biased, but it made you learn, it was fast and came bundled in Office. Countless numbers of hobby web pages were build thanks to it.

Re:Languages Which Almost Became CSS by coldtea on Friday August 04, 2017 @05:36AM (#14927430)
>Wasn't keen on Dreamweaver - I mean I guess it's ok if you're a designer but not really something I'd have ever recommend for developers.

Mostly because of cargo cult -- as Dreamweaver produced very clean HTML output.

Re:Languages Which Almost Became CSS by laumars on Friday August 04, 2017 @06:18AM (#14927586)
> Mostly because of cargo cult

That was my point. If you're familiar enough with HTML to use Arachnophilia (which, if anyone isn't familiar with that particular editor, was basically just the Notepad++ of it's day) then Dreamweaver would just seem excessive. Hence why I'd recommend it for designers rather than developers ;)

> as Dreamweaver produced very clean HTML output.

Cleaner than Frontpage and most of the other design tools out then, sure. But my experience of Dreamweaver around that era was that it's HTML output still needed a lot of manual refactoring in a text editor afterwards. While it was better than most GUIs it was still a long way off "very clean HTML output".

I'm sure things have improved significantly in the last 15/20 years though. But that was certainly the state of things back in the late 90s / early 00s.

As an aside note: I won a Source Code Planet (anyone remember them?) competition one month with an entry I made in Dreamweaver. It was a mockup of a Window 95 or 98 (I forget which) desktop with functioning start menu. I always felt naughty for winning based on something I built in a tool that auto-generates a lot of the code for you but then other projects I released were a lot more credible (eg DirectX games) but far less popular. I guess it just goes to show how little most people cared for code quality even back then.

Re:Languages Which Almost Became CSS by frik on Friday August 04, 2017 @01:30PM (#14930324)
I remember Planet Source Code, it was the Github of the late 1990s. Everything from VB, C++ and HTML samples were there. A one stop community platform. I remember I coded a Windows 98 shell replacement, a Frontpage WYSIWYG clone, an Paint clone, DirectX8 games in VB6. Then MSFT canceled VB7, me people moved elsewhere. Then Sourceforge took over. And later Google Code took over. Then Github took over.
Re:Languages Which Almost Became CSS by type0 on Friday August 04, 2017 @06:49PM (#14933008)
Sourceforge is not dead, it's just sleeping.
Re:Languages Which Almost Became CSS by frik on Saturday August 05, 2017 @05:10AM (#14934897)
Well, technically PSC (Planet Source Code) isn't dead either. There still new VB6/etc code gets uploaded even in 2017. https://www.planet-source-code.com/vb/scripts/BrowseCategory...

GitHub is the current thing, PSC/Sourceforge/GoogleCode are still technically (at least read-only) around.