True but I kinda got burned by dtksh which allowed ksh93 to connect to Motif widgets. After the deprecation of Solaris 10, I had to wait many years to be able to use my old GUI scripts again XD.With tcl you have the widget toolkit tk, a very comfortable way without much effort and lines of code of writing GUIs.
Come on, all programmers use heavy advanced programming languages for easy programming.bash and ksh for interactive use
sh for simple scripts (lowest common denominator / portability)
C for anything I cannot script (i.e X11). I don't bother with Python, perl, java and all that stuff because I despise pointless bindings and dependencies which can simply be avoided by using C.
Luckily the game industry is one of the last bastions of light where much of the engine work needs to be native C++ (with some C). Thus on Android the Google NDK (or Intel NDK) is king. There is still hope!You cannot use C on Android,... rapid software developments and customer implementations. There is no money there.
1. TKkpedersen, tk is one of the oldest toolkits, tcl/tk scripts may run on unixoides, Windows and Mac.
Spartrekus, scripting is more expresive: a script (including sh scripts) for example can dynamically write code and interpret it. Sure, a C program can also write a file and with system calls compile and run it, but that is not very elegant, not so expressive, not so readable. One uses C and scripting for different purposes.
Why? I run my scripts when I need to run them.Too much Scripting can slow down your system heavily.
Reaction score: 229
could be possible. In fact, Lisp always existed. tcl might be good.
Ahmmmm NO.could be possible. In fact, Lisp always existed. tcl might be good.
Ideally we should use assembler
Assembler allows to spend (lot of) time on a smaller approach, which could gain in efficiency for a given (small) base operating system.Ahmmmm NO.
Ideally we should identify the 5% of the code which eat up 60% of the time and tune that code. Find the 1% that has 40% of the time and maybe use assembler for that. What you might gain from using assembler for more than a few very hot spots will be spent in debugging and porting. Also you need to re-tune everything by hand when the silicon changes.
I know of one company where the long term archive for safety relevant stuff (about 30 years storage) ONLY accepts ASCII and PNG. Want to hand in your presentation, .doc or .pdf? Print it out page for page.One could also say, ideally we should save all electronic written documents as bitmap (I save my TeX code, not even as ps/PDF).
It is a consequence of what is today considered as important.Crivens, this is perhaps offtopic inside of offtopic thread.
I begun to use again FreeBSD because ZFS hails files using redundancy. Although ZFS is bloated for an archiving file system, I think (or hope) it will be there for 30 years: for normal use I preffer ufs. I use magnetic disks, not flash rom, for archiving, but the firmware of the disc is sure flash rom and the whole data goes with it. And are modern magnetic disks or tapes with so dense data reliable? And of course the format of the data must be readable in the future. Archiving is not a simple problem, is not solved, and unfortunately it seems there is no much interest.