icsa

12 ms·

121.
by icsa 6y ago
Yes. In fact, Microsoft funded an effort to port popular (with its ISVs) open source software libraries to Windows/ARM in 2019.
122.
by icsa 6y ago
Check out https://twitter.com/i/broadcasts/1OyKAYWPRrWKb Go to 25:00 for the Python code generation (from a signature + comment) demonstration.
123.
by icsa 7y ago
I have built many billion+ row databases on a laptop with 16 GB RAM, using the 32-bit version. kdb+ uses memory mapping and can support databases much larger than available RAM. PostgreSQL is a fine choice and I use it for many projects.
124.
by icsa 7y ago
Try the 32-bit evaluation version of kdb+ ( https://kx.com/ ). Twenty million rows of data per day is easy with kdb+ - even on a laptop.
125.
by icsa 7y ago
The interviewers were very nervous. I spent quite a bit of time calming them down. Once that happened I was able to determine what it would be like to work with them - which worked out quite well.
126.
by icsa 7y ago
Yes. I interviewed through a full round (i.e. 6) of technical interviews. Once the firm (a startup) indicated interest in moving forward, I requested to meet with the CFO, VP of Sales & Marketing, and everyone who interviewed me. For ea
127.
by icsa 8y ago
The language for specifying computation in GENTLE is similar to a shallow backtracking version of Prolog. The language is translated directly into C.
128.
by icsa 10y ago
kdb+ map/reduce implementation operates across data in memory or on machines in a cluster.
129.
by icsa 10y ago
> 1) What happens when you run these benchmarks on a machine with only 16GB of RAM? kdb+ uses ~ 1.2 MB of Resident RAM at startup. In addition, kdb+ storage model in memory and on disk have very little overhead (a few hundred bytes) per
130.
by icsa 10y ago
IMHO, I would respectfully disagree. K/Q canbe used for all manner of software systems. PageRank can be done in a few lines of code - with clarity approaching the mathematical description. The solutions to the Advent of Code ( http:&#x
131.
by icsa 10y ago
Agreed. The variety of workloads (a la Stonebraker's One Size Doesn't Fit All paper) is where many big opportunities lie. I'm interested to see what kinds of workloads and use cases are of interest in the marketplace.
132.
by icsa 10y ago
> I've seen offers in the $1-10M range on the east coast to build competitive technology. I'm interested to know more about this, assuming you have time.
133.
by icsa 10y ago
Could you provide representative CEP use cases? I may be able to provide some insight.
134.
by icsa 10y ago
kdb+ also supports Petabyte distributed databases. i.e. much larger than RAM. E.g. http://kparc.com/q4/readme.txt (Trillion Row Benchmarks)
135.
by icsa 10y ago
One very important use case is the asof join. i.e. - "line up" two or more time series by time so that they can be compared or analyzed together. kdb+ does this very efficiently.
136.
by icsa 11y ago
The BTables discussion takes me back to memories of my first college computing class (in FORTRAN). We were asked how we might store a sparse matrix in less memory. The solution was exactly the same as BTables. We thought we'd done some
137.
by icsa 12y ago
Sure thing. What's your email address?
138.
by icsa 12y ago
I have seen this on a grand scale - 72MM LOC over multiple versions (10 year span) of multiple products by the same well-known software company. The occurrence of nearly identical code was the most surprising find. One product had minimal r
139.
by icsa 12y ago
> What does `(c)uts` tell you? Cut points (by \n, in this case) if one were to use the cut operator _ to tokenize a by leading \n. It's hint/reminder of the purpose of the definition. N.B. - This feature (i.e. str$chr) is undoc
140.
by icsa 12y ago
TL;DR - Map symbols or uses of operators to meanings. Context is semantics/meaning. I.e. - hints, documentation, use case, approach, etc. It's not about the code but the description of the code. The above code is the same, however
141.
by icsa 12y ago
> I told them I thought the readability was improved by having all the words together, but maybe it made it difficult to learn. I noted Arthur had recently annotated edit.k[1] and asked them if that layout made it easier for beginner pro
142.
by icsa 12y ago
"noun" in C: noun(c){A z;if(c<'0'||c>'9')R 0;z=ga(0,0,0);z->p=c-'0';R z;} "noun" in k: noun:{[c]$[(c<"0")|c>"9";0;c-"0"]} / $[boolean;
143.
by icsa 12y ago
The same could be said for writing a document in Chinese, Arabic or Hebrew. They all look like "line noise" until you make an effort to learn them. "For that matter, I suppose it's possible to write understandable, maint
144.
by icsa 12y ago
Agreed. The small(ish) vocabulary of operators makes K easier for me to use. Would you rather write/read: DIVIDE X BY 5 GIVING Y or y=x/5; The first is COBOL (designed to make code easier for "normal" people to read. The
145.
by icsa 12y ago
What you refer to as "cheating" is simply writing C like k/APL/J (i.e. functional versus imperative). Language implementations have this tendency. I've seen the same effect with Lisp implementations. N.B. - k/A
146.
by icsa 12y ago
See https://news.ycombinator.com/item?id=8477308
147.
by icsa 12y ago
What's left on the table is the efficient use of resources. When I mentioned to a friend that the current version of K5 was a binary < 100KB, his response was "I don't believe it. I can't write HelloWorld in less than
148.
by icsa 12y ago
Here is a style for K ( http://nsl.com/papers/style.pdf ) 1995. Interestingly, most of the concepts still apply. I believe the audience is developers using K in a commercial/production environment. The biggest diff
149.
by icsa 12y ago
I think that "It's what I'm used to." is the main reason - intellectual comfort zone. Having learned BASIC, FORTRAN and Pascal, C seemed like line noise - at first. As did PERL. And then k. Btw, COBOL seemed "too ve
150.
by icsa 12y ago
The SQL was not I/O bound, per se - that is database/implementation-specific. The benchmarks were evaluated on "hot" data with plenty of RAM available (like any good production system). Some databases don't manage t

More ›