I used HotDog back in 1996 or something cray cray like that. Then I went to HomeSite and then I made a wrong turn somewhere and did Coldfusion/DHTML/Java ... it defined me in a lot of ways.
As for Tech Debt, the problem or issue with this entire JavaScript / Web mediocrity or bust is nothing really advances other than shortcuts to solve already solved issues. We've not really moved the needle forward we just obfuscated the stench better, as when you look at the web today vs even when Plugins were all the rage, at least the plugins forced the world into a different gear instead of this ongoing "natural" we seemed to be in. Oh but its different now as we shifted the boundaries a little and made the browser the plugin (hows that working out btw). Developer maturity is now reduced to "*here's the latest flavour we conjured today to its best to abstract you from thinking about JavaScript its purest form instead we're gonna just make up some attributes to bolt onto your DOM/Node structure and you just have to guess along with us as we progress this forward*" I'm not jaded about the web, but I feel JavaScript / Node etc is the digital herpes of internets. Outbreaks occur every 3-4 years and still no cure. Ok.. i'm jaded ;D Reliance on event based layout systems may have been a great idea when CPU was a variable to factor into our existence but if we can all move forward to a FPS model, whereby we firstly work to a "how many things do i need to do to prepare for a visual frame change" whilst also making some sweet love to an async / yield discipline to discreet work...that'd greeaat.. Next comes Screen targeting and this weird game of UX Tetris whereby dev teams place "user experience" onto a pedestal up until the point where Responsive vs Adaptive wars break out, then its reverting back to "developer knows best" response(s)... again... I'm just saying... if Serverside / Client-side JavaScript is still the best idea of the day, what was the worst? --- Regards, Scott Barnes http://www.riagenic.com On Tue, Nov 22, 2016 at 3:04 PM, Nathan Schultz <milish...@gmail.com> wrote: > Ken, I'm curious as to why you think there is less technical debt in > web-applications? > > I agree that the web is less mature - but it's not because of lack of time > or tooling. A mate of a mate made millions making web-development software > in the mid 90's (HotDog software), and I was doing web apps in Visual > InterDev (which is before Visual Studio's time). > > On 22 November 2016 at 12:13, Ken Schaefer <k...@adopenstatic.com> wrote: > >> A couple of possible reasons: >> >> >> >> - All the emphasis is on centrally delivered applications (aka >> web based), so that’s where all the innovation and change is happening. It >> will take time for maturity and tooling to catch up. >> >> - It’s harder to bypass the full technical cost of development >> when something’s centrally delivered. It’s easier to incur “technical debt” >> when you build a little thick-client app – the real cost of the app gets >> buried in IT operations. >> >> >> >> Cheers >> >> Ken >> >> >> >> *From:* ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-bounces@ozdot >> net.com] *On Behalf Of *Greg Low (??????) >> *Sent:* Tuesday, 22 November 2016 2:33 PM >> *To:* ozDotNet <ozdotnet@ozdotnet.com> >> *Subject:* RE: [OT] node.js and express >> >> >> >> But that’s a centralized vs distributed argument. I understand that. By >> why exactly does a centralized development process have to be orders of >> magnitude slower than a distributed one? I just think the tooling has let >> us down -> big time. >> >> >> >> 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 >> >> >> >> >> > >
