Advertisement
Guest User

An opinionated treatise and rant on lisp and programming lan

a guest
Nov 21st, 2014
314
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 2.59 KB | None | 0 0
  1. We should should create a lisp with better tooling. Now, before you go and bash me for creating yet-another-lisp, let me explain why. The lisp programming language's tooling is <i>pathetic</i> as compared to other languages. I am not talking about any specific lisp implementation, I am talking about the lisp implementations that are currently relatively popular (e.g. Clojure, racket, sbcl etc.). I have always failed to understand why most new programming languages has such poor support for windows when 80% of users run Windows?! Foss advocates always complain of windows and the .Net platform being a vendor lock-in blah blah blah when they are ignoring the fact that most language developers are ignoring the windows platform and focusing more on *nix OSes. Most implementation of non-Microsoft languages on windows are often some half-baked port that does not work well and has huge amount of compatibility issues. Installing clojure on windows gave me an absolute headache as it installs via an obscure batch file that would not functuon properly in an multiuser environment and I had to manually comment out lines of code to try to make it work. This brings us back to the issue of lisp. Lisp evangelists always advocates for virtues of emacs/vim or some other obscure * nix editor when most of them look like absolute **** on windows! They complain of not enough people adopting their sacred language when the barrier entry is a complex nightmarish labyrinth straight out of a Dante's poem. Beginners learning to code and any developers who wants to get-things-done would want a batteries included environment such as visual studio that has everything working correctly and you can start coding business logic immediately instead of digging through layers of config settings to fix a pedantic linting problem in one of your editor's plugins or trying to figure out the best way to describe an Gui and the best way to link it to some external framework. The only lisp that seem to have a slightly reasonable attempt at tooling is racket though their license made it completely for any aspiring developers who wish to profit from software. All in all, IDEs are tooling are IMPORTANT! Not everyone is a Linux geek who wants to spend the day setting up frameworks and editing configure files. I am considering creating a better dynamically typed compiled general purpose language with full GUI and IDEs but without any form of *nix support just to spite the *nix community. Developers, stop locking out 80% of potential users of god's sake. Windows 10 is going out for free so do you still have any excuse to ignore this operating system?!?
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement