pkolaczk

80 ms·

931.
by pkolaczk 10y ago
Not so fast. The first mover advantage is often severely overestimated. There are many examples of companies which failed despite being the first to deliver. Apple was not the first company to invent a smartphone. Facebook was not the first
932.
The Longflow Manifesto(github.com)
204 points by pkolaczk 10y ago|181 comments
933.
by pkolaczk 10y ago
Yes, this! And this happens particularly often, when you use standard cotton laces which make knots harder to accidentally undo. The synthetic ones last much longer, but are slippery and easy to untie.
934.
by pkolaczk 10y ago
I also think he does. Currently all new cars come with some kind of automated assistants, some even semi-autonomous. Unfortunately they are much less reliable than humans. They are still struggling with "easy" problems like keepin
935.
by pkolaczk 10y ago
Which ironically, is a model with probably best performance and scaling characteristics. If you want high performance, you should avoid sharing mutable stuff as much as possible.
936.
by pkolaczk 10y ago
If he sorts 1 mln items, I guess he runs out of L1 cache and probably out of L2 cache. Therefore memory accesses may pay the biggest role here and that explains why he sees almost no improvement from recursion elimination.
937.
by pkolaczk 10y ago
The data are not either conistent or inconsistent. The data are either correct or incorrect, and the definition of "correct" is determined by business requirements. Most of the time weak eventual consistency model provided by Cass
938.
by pkolaczk 10y ago
If you're applying non-destructive updates without quorum, you would not get monotonic read consistency, because stale reads would be possible. You could write a row, immediately read it back from another replica and find out the row i
939.
by pkolaczk 10y ago
RDBMSes can cause similar inconsistencies if you don't know what you're doing. It is like setting read uncommitted and then complaining about dirty reads.
940.
by pkolaczk 10y ago
Cassandra is perfectly fine. If you want your writes to be consistent, learn to use LWTs properly. The same way, if you want your data to be fully consistent in RDBMS, learn to use SERIALIZABLE isolation level (which is not default in most
941.
by pkolaczk 10y ago
Quorum reads + writes and applying non-destructive updates only are enough to get linearizabile consistency in Cassandra, even if clocks are not perfectly synchronized.
942.
by pkolaczk 10y ago
You can use Cassandra LWT as a building block for multi-partition transactions, in a similar way like CAS atomic operations are used to build locks, mutexes and monitors and then monitors are used to implement ACID transactions in RDBMS. Ho
943.
by pkolaczk 10y ago
DELETE ... IF EXISTS DELETE ... IF <condition> UPDATE ... IF <condition>
944.
by pkolaczk 10y ago
Technically, Cassandra was a person in Greek mythology. So still ad hominem.
945.
by pkolaczk 10y ago
Details matter. All updates in the Datastax post are protected by LWT. That code is correct. The OP's code was wrong, because he was mixing non-LWT updates.
946.
by pkolaczk 10y ago
It is optionally consistent if you know how to use it and you know its limitations. Their use of Cassandra was obviously wrong. Mixing LWT and non-LWT is like having only half of your shared data protected by mutexes - this isn't going
947.
by pkolaczk 10y ago
While technically you're right, the CAP theorem uses a very strict definition of availability, which is often not needed to consider the system available in real-life. Also the consistency in CAP theorem is defined as linearizability,
948.
by pkolaczk 10y ago
"Those turbocharged <1L little hatchbacks would absolutely trounce your big car for efficiency." Only if you drive them like in the lab tests. If you drive them normally, expect a very big discrepancy between the lab tests and
949.
by pkolaczk 10y ago
Yup, and it is also nice that if you just touch the brakes when going downhill the AT downshifts to engine-brake stronger. I can also feel when the converter locks up when accelerating. Particularly when the engine / AT are cold the ac
950.
by pkolaczk 10y ago
This is true, but the clutch bearings and spring may wear faster if the clutch is kept disengaged for too long, instead of switching the gearbox to neutral.
951.
by pkolaczk 10y ago
My Mazda CX-5 locks up in all conditions, even if it is cold and in the first gear. And it has better EPA than the same model with MT.
952.
by pkolaczk 10y ago
"Do you have data to back this up?" Official data (source: https://www.mazdausa.com/siteassets/pdf/features--specs/2016... ) * Mazda 6 2.5L SkyActiv-G MT: 25/37 MPG * Mazda 6 2.5L SkyActiv-G AT:
953.
by pkolaczk 10y ago
Removes boilerplate? Yes. Confusion? Sometimes. Bugs? Not really. async/await doesn't inherently change the concurrency model, it is just a different notation for the same thing. Therefore you can still have all the same bugs as w
954.
by pkolaczk 10y ago
Scala is doing it exactly as in JS. We have async/await as a macro library transforming the code to a FSM. The original author posting this probably didn't know that, under-the-hood, await doesn't really block in Scala nor in
955.
by pkolaczk 10y ago
While their raw benchmark data may be ok, the summary chart makes no sense. They calculated the average and median runtime of all the queries, without first normalizing the results, despite the fact that there is a very huge runtime varianc
956.
by pkolaczk 10y ago
The code is not very self-documenting either. There are >50 line long functions with mixed levels of abstraction, and error handling code is completely mixed with logic. I find such code quite hard to read and lack of comments doesn&#x27
957.
by pkolaczk 10y ago
Technically correct, but filesystems are mostly about I/O. For example this Baidu filesystem copies blocks of data into userland memory and transfers them in RPC messages - any system using proper zero copy approach would easily beat
958.
by pkolaczk 10y ago
LMAX, New York Exchange.
959.
by pkolaczk 10y ago
Sure and this DFS in C++ memory use is probably huge compared to many hand-crafted assembly or C programs from 1980s. But who cares? 100 MB or even 1GB is really tiny for today's server hardware. And Java runtime itself is a few MB rea
960.
by pkolaczk 10y ago
HDFS biggest problem is its SPOF master-slave architecture, not JVM nor GC. With a truly distributed shared nothing system Java Gc would not be a problem, because servers can now run with no major Gc for hours or days. So two servers or cli

More ›