>framework people have decided to transform the three into just one - 'JavaScript'. Will it be that javascript lib's will win the day? I don't
>know - but I can say - I hope not. Javascript as it stands today is a terrible language - specially for large projects. The only reason several companies have moved that direction is because it's already there in the web browser. Not because the language is eloquent.
>
ACK on the not really eloquent part - you need a code/class template, self discipline, Linting, automatic source conversion to a standard-beautify and a draconian project lead to get about half way where python is without such things - excepting for the tabs vs. spaces ;-))
>Google on the other hand has started an effort to replace the entire underlining of the web with "Dart". Of course to get others to accept
>the new way to program the web they have a hybird way of producing javascript. But their main goal is to replace all of the current web
>tech. There are others that have presented other protocols in similar efforts. I wish them well because I'll be very sad if javascript wins.
There also is pyjamas doing something similar, there is coffescript - but inherent in all such schemes is the bad debugging expirience if something goes awry in the generated JS - no good link back to the code you wrote and to much magic in the conversion process for everyday usage. Which is the benefit of Node - one language back and front, even if it is not the fairest of them all.
>Building for the web today (and all the new form factors and input methods) is like building on quicksand!
Yes - but remember MS-Dos duking it out with CP/M, small Unix versions, DR-Dos, the apple II and the mac,
DR-GemDos againts Windows 1, II, 3.x, OS/2 ?
Ms-Dos plus Windows .LE. II was a poor joke compared to the other choices.
Less quicksand than today ? Not until NT4 showed Win95 eye candy with a half way solid backbone.
I was sold from that moment on for a dozen years, even if I took a couple of breaths of java smell in 96-98,
when Anders was not creating C# but J++ and I still had to leave OS/2 1.0,
which had allowed.me multi-MB[!] ranges of memory available in the late eighties in text mode.
Or the early dbAse wars ? dBase3+, dBase4, several versions of Clipper, Quicksilver, dBMan, Foxpro -
not all zombies now, but certainly after their prime today, as much as I love the fox.
Porting projects into different languages was not impossible (today: "we need a total rewrite"),
but just a technical diffculty. Looking for the right libraries for ISAM/SQL handling was just as
difficult back then as it is now for the JS-GUI stuff ;-)
The project I groomed from the mid-80ies to late 90ies moved across 4 OS,
through 3 different languages and was then a component used in 4 program pools
all written in totally different languages. And yes, the first feasability study on the mathmatical
model had been done in FORTRAN, which I was able to circumvent in actual coding ;-)
regards
thomas
Previous
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only