Recent Bookmarks and Annotations
-
Erlang (programming language) - Wikipedia, the free encyclopedia on 2009-12-01
-
-
The initial version of Erlang was implemented in
Prolog
-
-
-
y q on 2009-11-13
Hard to understand !!!
-
It has a small but powerful set of primitives to create processes and communicate between them
-
with 20 million processes
-
y q on 2009-11-13
Process-intensive
-
A message-handling routine
-
communication with them is transparent in the sense that communication with remote processes is done exactly as communication with local processes
-
processes may be created on remote node
-
primary method of error-handling
-
-
-
-
-
-
-
PhraseExpress – A Great Alternative Text Replacement Tool on 2009-11-29
-
FindMeByIP.com, What's my IP address? How good is my browser? What can it do? : what browser am I using, how modern is my web browser, and what's my IP address? on 2009-11-29
-
Accepted Papers on 2009-11-20
-
Osprey: Implementing MapReduce-Style Fault Tolerance in a Shared-Nothing Distributed Database
-
Osprey: Implementing MapReduce-Style Fault Tolerance in a Shared-Nothing Distributed Database
-
-
Osprey: Implementing MapReduce-Style Fault Tolerance in a Shared-Nothing Distributed Database
-
Osprey: Implementing MapReduce-Style Fault Tolerance in a Shared-Nothing Distributed Database
-
Osprey: Implementing MapReduce-Style Fault Tolerance in a Shared-Nothing Distributed Database
-
Reliable Storage and Querying for Collaborative Data Sharing Systems
-
Continuous Query Evaluation over Distributed Sensor Networks
-
Global Iceberg Detection over Distributed Data Streams
-
Efficient Rank Based KNN Query Processing Over Uncertain Data
-
Detecting Inconsistencies in Distributed Data
-
K Nearest Neighbor Queries and KNN-Joins in Large Relational Databases (Almost) for Free
-
Cost-efficient and Differentiated Data Availability Guarantees in Data Clouds
-
A New Algorithm for Small-Large Table Outer Joins in Parallel DBMS
-
Incorporating Partitioning and Parallel Plans into the SCOPE Optimizer
-
ive - A Petabyte Scale Data Warehousing Using Hadoop
-
Database as a Service (DBaaS)
-
Beans Place: AutoVer on 2009-11-17
-
Dr. Dobb's | Programming Erlang | July 18, 2007 on 2009-11-17
-
Virtually all language use shared state concurrency
-
-
-
-
pure message passing concurrency
-
-
-
Crash detection and recovery
-
-
-
AXD301 has 1.7 million lines of Erlang, making it the largest functional program ever written
-
It was a language for building fault-tolerant distributed systems
-
with lots of cheap processors and allow them to fail
-
Damien Katz: What Sucks About Erlang on 2009-11-16
-
Erlang's syntax does away with nested statement terminators and instead uses expression separators everywhere
-
Erlang's expression terminators vary by context,
-
-
If Erlang were a side-effect free functional language, such a restriction would make sense
-
You cannot even call user defined functions in if conditional expressions
-
Erlang allows a subset of the built-in functions (BIFs) in conditional expressions, but no user defined functions can be called whatsoever.
-
you can't distinguish easily at runtime between a string and a list, and especially between a string and a list of integers.
-
I personally wouldn't pick Erlang for most front-end web application work
-
CouchDB, a network database server
-
when it came time to write the test suite code for CouchDB, I found Erlang to be needlessly cumbersome, verbose and inflexible.
-
Erlang wasn't a good match for tests and for the same reasons I don't think it's a good match for front-end web applications
-
surprisingly limited and verbose, requiring you to state the type of the record for each reference in the code.
-
compile-time static and record members cannot be added or removed at runtime, and don't fit with Erlang's otherwise dynamic nature.
-
they aren't usable from the REPL command line, it won't accept record syntax without special steps and it still doesn't show you result records in record syntax.
-
we have to roll our own "restart the dead VM" solution and deal with cross-platform issues providing something I'm still shocked Erlang can't handle itself.
-
The extra file creation artificially spreads out the code over the file system, making things harder to follow
-
Erlang, the next Java on 2009-11-16
-
Its main problem is that there is no big company behind it
-
Its main advantage is that it is perfectly suited for the multi-core, web services future
-
-
the ONLY mature, rock-solid language
-
always on reliability, not raw speed, and the system has an incredible reliability history. Joe claims they have achieved "nine 9's of reliability".
-
-
"concurrent Erlang' is an object-oriented language
-
not going to make Erlang big is that "sequential Erlang" is a functional programming language
-
scale seamlessly from a single processor system to a hundred processor system
-
Unlike Java or Smalltalk, where you only write threads/processes when you want concurrency, Erlang programmers use processes for modularity, reliability, and reuse.
-
messaging is asynchronous in Erlang
-
building or using various kinds of internet services.
-
OTP, or the "open telecom platform
-
Processes in Erlang are objects
-
perfect example of the actor model
-
data abstraction and polymorphism
-
similar to a class in Smalltalk
-
Erlang fits all the characteristics of an OO system
-
-
it is really lack of SHARED state that implies no locks
-
Mnesia - Wikipedia, the free encyclopedia on 2009-11-13
-
Teradata 12 Certification Track on 2009-11-10
-
but cannot be transferred to another track
Home
