i_s

10 ms·

61.
by i_s 9y ago
People tend to drop type providers in F# for non-trivial programs, because the benefits need to be extreme in order to justify adding flakiness to the build. Type providers also have the problem of yielding errors to people who may not be i
62.
by i_s 9y ago
Here is one in Swift I did a few years ago that does: https://github.com/isaksky/sudoku-swift/blob/master/Sudoku-S... This one solves all 50 from Euler: https://projecteuler.net/problem=9
63.
by i_s 9y ago
You can still support arbitrary filters and ordering, as long as you always sort by the ID last. The nice thing is the queries actually get more and more efficient as you approach the last page. (The normal approaches have the same cost acr
64.
by i_s 9y ago
> who can blame a novice Even experts fall into this trap, actually: https://sqlperformance.com/2015/01/t-sql-queries/pagination-...
65.
by i_s 9y ago
Ah, nice trick - thanks for the tip.
66.
by i_s 9y ago
> custom execution module to translate a graphql request to a single sql query If I have a schema like this: users projects (many per user) blog_posts (many per user) What SQL do you generate to handle a request fo
67.
by i_s 10y ago
It is really how disappointing the options to share data with workers are in the browser. Combine the limited options options to transfer data quickly, and the limited API available in the worker itself (no version of a DOM, even a gutted o
68.
by i_s 10y ago
I've thought about this too, and unfortunately it is not feasible, because of the poor/nonexistent meta programming support in F#. Phoenix uses macros for optimizing functions from templates at compile time, handling translations
69.
by i_s 10y ago
May be worth exploring this from the other side too. Why do you think it is ok for a programming language to lock people into to using just 1 core per process?
70.
by i_s 10y ago
Great to hear that the map literal is there. Completely agree it boils down to personal preference.
71.
by i_s 10y ago
In general, it seems like the authors of Elixir were able to capture more of the cool things about Clojure than LFE. Check out some of the top level functions in Elixir: update_in put_in get_in http://elixir-lang.org&#
72.
by i_s 10y ago
I can't prove that it should. Just providing a list of initial impressions from someone who has been using Clojure for a while, FWIW. It's necessarily subjective. Seems like it would be a good idea though, since Clojure is a new l
73.
by i_s 10y ago
As a Clojure fan, I tried using this, but I got the impression it has learned next to nothing from Clojure, so I ended up going with Elixir instead. Particularly: - No data structure literals (?) - (except e.g., '(1 2 3) for lists) - M
74.
by i_s 10y ago
Xledger | Colorado Springs, CO | Full-time (on-site) Xledger is a finance, project, and business information system that gives customers tighter control of their businesses. We are expanding our team in Colorado Springs, which focuses on Cl
75.
by i_s 10y ago
If you're building a complicated dynamic UI want to take advantage of the latest ideas in front end data architecture (like om.next, or the the stuff in Elm), F# is still a bit behind when it comes to these ideas. The community has bee
76.
by i_s 11y ago
No one is maintaining state by constantly clobbering namespace level variables in Clojure, though. What actually comes into play are ways the language and standard library encourages passing data around and manipulating it, which in Clojure
77.
by i_s 11y ago
Pretty strange that you put Clojure in the "anything goes" category when it has been the clear leader when it comes to immutability. Lots of those languages you put in the other categories don't even have persistent data stru
78.
Suave v1.0.0 released (F# Web development library)(github.com)
1 points by i_s 11y ago|0 comments
79.
by i_s 11y ago
> Being given a pre-packaged task to complete feels very procedural and bland... This part is important: > Having a consistent test also allows me to compare candidates easily and without bias. Also, I think most people would care mor
80.
by i_s 11y ago
> Constants are defined via let, and variable are allowed to vary through a var. Though constants are lame, as only the binding itself is constant and you can change everything inside them as usual. That is at best misleading, as it is n
81.
by i_s 11y ago
There is nothing in the language itself that allows multi-threading. Going forward, they are adding support in the language for the async keyword, similar to F#. Any way to achieve parallelism would have to be from APIs, e.g., like WebWorke
82.
by i_s 11y ago
But was that code in the GC implementation, or your program? Because if its in the implementation, then that is a different matter. We have to distinguish between simplicity of implementation vs simplicity provided the user. I agree that if
83.
by i_s 11y ago
Most people consider garbage collection to be a net win in terms of simplicity. Have you thought about why? Not every feature interacts with other features in complicated and error prone ways.
84.
by i_s 11y ago
This talk has a lot of very weak points. He made the claim that more features hurt readability (~6:10), because when you are reading you have to waste time thinking about why the programmer chose the set of features he did to write the code
85.
by i_s 11y ago
This is one of emacs' killer apps. I know some people (myself included) who use sometimes emacs just for this, even if we have to use Xcode or another tool to actually write the code.
86.
by i_s 11y ago
I did now, and the only relevant retort I saw to this specific claim was that it is possible to work around it by using cern.colt.map.OpenIntDoubleHashMap (third party) instead of java.util.HashMap. So someone has worked around the problem
87.
by i_s 11y ago
> The issue of primitive specialisation of generics is only tangentially related to type erasure, and run-time visible generics are actually much less useful than Java folk wisdom insists. Run-time visible generics are pretty important b
88.
by i_s 11y ago
> That is, as an example in our case, we can’t expect that a Haskell data type that today maps perfectly to a SQL row will continue to do so after any of the two is modified. But we can and do if we use the compiler to dynamically genera
89.
by i_s 11y ago
> HList has some properties that are very interesting to us. To start with, not only we can store an arbitrary number of elements of different types, but we can also know statically—that is, at compile time—both the number and types of t
90.
by i_s 11y ago
If Cocoa KVO was well done, this would not need to exist: https://github.com/facebook/KVOController

More ›