RE: [OT] node.js and express

I’m also seeing diabolical messes in the devops on the web apps too though. Regards, Greg Dr Greg Low 1300SQLSQL (1300 775 775) office | +61 419201410 mobile│ +61 3 8676 4913 fax SQL Down Under | Web: www.sqldownunder.com | http://greglow.me F

RE: [OT] node.js and express

Well, I used Hotdog, Dreamweaver, Interdev (back in the ASP days!) – but you can’t say that tooling’s good just because there’s lots of it. It needs to actually solve problems at hand, and my experience in any fast moving area, is that the tooling takes a while to catch up. Firstly the landscape

Re: [OT] node.js and express

> > Well, I used Hotdog > [This is a Friday topic but] Good god! I remember seeing a prominent newpaper picture back in 1996 of Steve Outtrim lounging back in his Ferrari, purchased on the sales of HotDog HTML editor (apparently he was too young to get insurance for a Porsche). Writing HTML was th

Re: [OT] node.js and express

The whole web committee structure is why we are stuck in purgatory quagmire swamp of hell. For example, when ECMA 4th Edition almost got legs to move JS forward but Adobe were being a bit of a political animal when it came to hedging their technical bets. Basically, at the time Adobe donated a bun

Re: [OT] node.js and express

@Ken, your definition of Technical Debt isn't that different from that of Martin Fowler's. Although I'd say (with some seriousness) that JavaScript is Technical Debt ;-) I've found many of the things you mention far worse in the web-world (where you sometimes have to cater for everything from a mo

RE: [OT] node.js and express

From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Nathan Schultz Sent: Wednesday, 23 November 2016 5:10 PM To: ozDotNet Subject: Re: [OT] node.js and express @Ken, your definition of Technical Debt isn't that different from that of Martin Fowler's. Althou

Re: [OT] node.js and express

As I said in my first e-mail, (when Greg was wondering what the key drivers were for web-development), I said "accessibility". Thick clients are simply not transportable. So the simple answer is, you don't. On 23 November 2016 at 14:21, Ken Schaefer wrote: > > > > > *From:* ozdotnet-boun...@ozdo

Re: [OT] node.js and express

Thick clients can be more easily done today with platforms like Unity3D for example. Ignore its a game thing and focus instead on its 2D/3D rendering pipeline, as once you get socketed into this you start to realise that the targeting platforms issues fall away quite quickly reducing you back to wh