auto greeting = "Hello" ~ " World!";
immutable x = 9 + 99;
auto:immutable::var:val
3,097 karma · joined October 22, 2008
auto greeting = "Hello" ~ " World!";
immutable x = 9 + 99;
auto:immutable::var:val
Good on Cisco for open sourcing it.
I'm interested to hear what regular scheme programmers feel about this news.
You can always go back to the basics and use simple TeX for your documents if you think groff/troff is simpler.
However, I'd encourage you to give ConteXt http://wiki.contextgarden.net/ a try because it is the spiritual successor to TeX (one tool for all the typesetting) instead of having to depend on "third party" stuff like LaTeX, most of which very few of us (outside the original sty author) understand.
with the new "Bash for windows", it will hopefully get easier in future.
ConTeXt is excellent if you care about design -- visual, layout, use of non-traditional typeface families, non-traditional print medium, create magazines, glossies, etc.,.
Writing a new style, class etc., for LaTeX feels like it's for "experts only". On the other hand, extending and creating new styles etc., for ConTeXt is much more natural part of creating the document.
ConTeXt is also highly programmable and extensible using Lua, XML(think machine generated catalogue).
With Metapost (graphics language), you can create highly sophistical vector diagrams. I have found pgf/tikz to be highly opinionated and it take much more upfront learning compared to metapost.
ConTeXt is also more intuitive, IMHO.
TeX appears bad from a distance, mostly from hearsay, until you have to write an actual technical book of certain expected high production standards and you realize TeX gives you the best shot at doing so.
There is a learning curve. It is an investment of your time, but it pays off.
Also, it is not like LaTeX et al are standing still in time. There are companies and teams working on improving the ecosystem everyday. I personally like ConTeXt unless I'm doing a predefined template exists (for conferences etc.,) where it makes sense to just use their LaTeX guidelines.
You will see PostgreSQL will come in handy once you get beyond the initial import stage..
PostgreSQL's type system will come to your aid . SQlite essentially treats everything as string, which can turn nasty when you get serious with your queries etc.,
* Rust - http://rustbyexample.com/
* C/C++ like familiar syntax. * as fast as C++ (faster in some, slower in others) * type inference (auto keyword) * Garbage collected language by default. * Multiple compiler implementation (DMD, GDC, LDC) * Debugging symbol support * Package management with versioning and pkg repo * IDE/Editor support - Visual studio/xamarin/emacs * Very easy C FFI * compile type function evaluation * meta programming * The concurrency story is more "mainstream" than Go's (no "goroutine" and other fancy stuff). * Multiple new books on the topic
D has a lot going for it, except for breathless fans :) (not knocking breathless fans here. D can use some)
Pretty much how, parens are not a concern for actual lisp programmers.
There are some strong auth/auth open source communities - https://github.com/Jasig that serve millions of users.
I continue to dabble in Rust, but D is so much more comfortable.
When you are applying "Free market principles", you go to the place that maximizes your enjoyment/treatment per $$ spent.
Examples:
- http://www.seas.upenn.edu/~cis194/lectures.html - http://www.scs.stanford.edu/11au-cs240h/notes/
edit: They have series of blog posts documenting the same too - https://www.sociomantic.com/search/tag/dlang (6 so far).
(which are pretty good at guarding their students' privacy.. though you should definitely check their policies before signing up)...
All these languages are statically typed and in my understanding of Programming Languages, way better than Go.