flavio81

88 ms·

751.
by flavio81 9y ago
Not all languages but here's a list: dynamic typing, strong typing: python (for the most part), Scheme dynamic typing, weak typing: Javascript, PHP static typing, strong typing: Pascal, Ada, Java, C# static typing, weak typing: C, Type
752.
by flavio81 9y ago
"Even humanities graduates can learn how to code in a few months and join the high-paying digital economy. " How sad are things getting. A humanities graduate, with deep knowledge about interesting topics, encourage to become a ch
753.
by flavio81 9y ago
These are really great questions and it would be the kind of interview i'd love to have, rather than silly "hackatons" or asking us to write the Quicksort algorithm from scratch!
754.
by flavio81 9y ago
My take is that having dynamic typing plus strong typing is a (pretty) good compromise. And static typing plus weak typing, insufficient.
755.
by flavio81 9y ago
My comment is applied to any language with weak typing. Example: Javascript, PHP, and (sadly) C, particularly when using pointers to void. However, in C it's okay since there are big performance gains when you have full control of the
756.
by flavio81 9y ago
Once code reaches a certain complexity level (and mind you, the threshold is rather low), you'll need dynamic generation of code and data (or else, write 10x the amount of lines of code). For this to happen in a safe way, you really, r
757.
by flavio81 9y ago
> Even today, years after Node has reached popularity and many lessons have been learned, developers with no experience outside the browser think they can write perfectly good server code, simply because they know the syntax (...) This i
758.
by flavio81 9y ago
The road to software hell is paved with ease to use.
759.
by flavio81 9y ago
Automated Distributed Execution of LLVM code using SQL JIT Compilation As collected by the SIGBOVIK group: http://sigbovik.org/2017/proceedings.pdf Quote: "Following the popularity of MapReduce, a whole ecosystem
760.
by flavio81 9y ago
best comment !! and true to reality.
761.
by flavio81 9y ago
For me, going from Lisp package installs to Node package installs was like traveling from a Bahamas beach to Siberia, with the same clothes. ES7 is okay, Node.js is good, V8 is GREAT, but NPM is an atrocity.
762.
by flavio81 9y ago
> Most of it is simple CRUD connected to a database If my apps were that way, i could have replaced my team with 20 well-fed monkeys.
763.
by flavio81 9y ago
The deeper problem is that JS is not strongly typed. Typescript gives you static type checks but the runtime is still weakly typed and will still do all sorts of weird type conversions.
764.
by flavio81 9y ago
> if only they'd have bolted in some support for "non-weird-looking classic OOP" like in "wanna type `window. Ah, so you want an inferior way of doing OOP? Because the reason Julia is the way it is, it is because it
765.
by flavio81 9y ago
I must say, the headline gives great ideas for a Dilbert comic strip.
766.
by flavio81 9y ago
To say that iteration should be "considered a code smell" is not a good thing to do for the programming community. Present-day CPUs operate on structures by iterating. On a typical high-level programming language, they are at some
767.
by flavio81 9y ago
> Sorry if dumb question but how is this possible when it's garbage collected? On a big or complex system you end up at least doing one or both or two things: a. Having to manage many temporal (transient) objects in memory. Thus you
768.
by flavio81 9y ago
"How to make Lisp go faster than C" (2006) http://www.iaeng.org/IJCS/issues_v32/issue_4/IJCS_32_4_19.pd... And these figures aren't using the SBCL Lisp compiler which should currently be faster
769.
by flavio81 9y ago
Specially if you require higher performance and there are no tail call optimizations.
770.
by flavio81 9y ago
> is quicklisp a solid part of this ecosystem, Yes, it is very popular. You can also, without Quicklisp, download manually the project and let ASDF do the rest of steps. > is it easy to find and install packaged compared to perl and p
771.
by flavio81 9y ago
> but has huge gaps by the standards of modern language Please detail, because i'm sure that the Lisp community would love to fill those gaps. After all, Lisp is addictive to the point of resembling a hard drug.
772.
by flavio81 9y ago
> though. CLs are inconsistent on how they can distribute base images and executables There is only one Common Lisp, the 1994 ANSI Standard. There are many implementations and they give you diverse options of delivering. For example if y
773.
by flavio81 9y ago
Just for showing how Bordeaux-Threads can be considered almost universally portable. This is the list of Lisp implementations supported by Bordeaux Threads: - Armed Bear Common Lisp (ABCL) - Allegro Common Lisp (ACL) - CLISP
774.
by flavio81 9y ago
The CPython JIT/compiler is written in C. Does this mean that a Python program is then a C program? Arc is not Racket.
775.
by flavio81 9y ago
> Many people underestimate how useful Perl DBI, JDBC, ODBC, Python DB-API, ADO.NET JDBC, ODBC, ADO.NET are not part of the language spec ; they are separate specifications. Your initial argument was that the language spec ("the st
776.
by flavio81 9y ago
> Last time I checked CL images were huge though. Something like 24MB for a "hello world" executable, even bigger with some compilers. You need to consider that Common Lisp includes a runtime, and this is a essential part of th
777.
by flavio81 9y ago
wasn't HN in Arc?
778.
by flavio81 9y ago
> is that the standard is stuck in time, lacking stuff like database providers, a common FFI or threading. You don't need database providers to be integrated in the language spec. Not in CL and not in many other successful languages
779.
by flavio81 9y ago
> Compared to Symbolics CL looks like a mess at least from reading the books. Which books, may I know? The Common Lisp Hyperspec is one of the best reference manuals for a programming language, ever. But it is not a tutorial nor a how-to
780.
by flavio81 9y ago
Um, i'm not sure. Python was designed with C compatibility as a main feature since the start, anyways.

More ›