lf-non

34 ms·

361.
by lf-non 9y ago
I just found your demo video about McCLIM ( https://www.youtube.com/watch?v=kfBmRsPRdGg ) and found it to very helpful to put things you outlined into perspective. I have linked to it in a top level comment.
362.
by lf-non 9y ago
For the uninitiated, McCLIM demo [1] by Jack Daniel is a very good introduction to REPL driven GUI programming using Common Lisp and McCLIM. [1] https://www.youtube.com/watch?v=kfBmRsPRdGg
363.
by lf-non 9y ago
The rotation of technologies that depend on (and attempt to simply) the abstractions exposed by the browser's host APIs may be quite frequent, however the underlying DOM model seems very similar to what you are describing here. The web
364.
by lf-non 9y ago
Can you elaborate what you would expect from such a system ? As someone not having much familiarity with CLIM or common lisp, I seem to be lacking the perspective to appreciate the relevance of this technology in 2018. Things like support f
365.
by lf-non 9y ago
It is not about a ui pretending to look native. It is more about form interaction patterns that users are subconsciously habituated to. For example: - Pressing enter submits a form. - Clicking on a label focusses the input box. - In OS X re
366.
by lf-non 9y ago
Not to criticise the (very well written) article, but IMHO the best solution for rapidly prototyping cross platform GUI applications in Ruby is Electron[1] + Hyperloop[2]. GTK applications look very outdated/out-of-place anywhere outsi
367.
by lf-non 9y ago
I don't have enough experience with ReasonML but the primary reason I am hesitant to adopt F# in my production applications (which currently use typescript) is because of following reasons: 1. Record types are very inflexible. It is, f
368.
by lf-non 9y ago
What are the best options for building JSON RPC client/server in javascript ? Essentially I am looking at a Node.js based server and Browser based client as of now but cross language compatibility would be nice to have. gRPC pure java
369.
by lf-non 9y ago
For emacs users, the Wilfred/remacs[1] project may be equally interesting. It is an ambitious fork of emacs, written in rust. [1] https://github.com/Wilfred/remacs
370.
by lf-non 9y ago
Primarily because Kotlin is not a superset of javascript and thus does not inherit the quirks of javascript. Other than that, if your backend is kotlin then you can potentially share (non JVM dependent) business logic code with the backed.
371.
by lf-non 9y ago
Would it not have been much more pragmatic for FB to have collaborated with MS instead on F# support in dotnet core? That seems more practical given the context that F# can directly benefit from things like concurrency support in dotnet cor
372.
by lf-non 9y ago
Has someone done a comparision of Reason+Bucklescript with Fable[1] ? F# has embraced the OCaml syntax while at the same time cleaning out many of the warts (+., do end etc.). It also now has good tooling available on all platforms. Despite
373.
by lf-non 10y ago
I am very curious what is the target audience for this project ? Given its long history (dating back to 2011) it does not look like just an experiment or hobby project. I would have assumed it to be a solution for porting legacy programs b
374.
by lf-non 10y ago
With tiny modular utilities this is very much necessity - and not a bad idea if the different versions are being used in different contexts. For instance, when using gemified javascript libraries with bundler it is painful to upgrade to a d
375.
by lf-non 10y ago
Interestingly padlock-cloud is built on Go so it is likely to be much easier to deploy.
376.
by lf-non 11y ago
Writing styles in javascript is a very natural consequence of web applications becoming more and more dynamic. It is unfortunate that they are not more mainstream. We have pushed CSS pre-processors to the extent that they now have variables
377.
by lf-non 11y ago
This has been my primary concern and the reason for which I avoid boilerplate kits except to study them: > Fork-and-forget (or fork-and-follow) is not a great way to keep up with what's happening in the original boilerplate (and in
378.
by lf-non 11y ago
I wrote something similar a while ago ( https://gist.github.com/lorefnon/ddb1880e64d8e1071bb0 ) -- never intended to use this in production but had a good laugh with co-workers when I showed it to them.
379.
by lf-non 11y ago
It is interesting comparing the divergent chains of evolution: Rails inspired ASP.net MVC inspired Laravel inspired Adonis wrt. Rails inspired Sails inspired Trails Good to see the spirit of CoC and elegant pragmatism being carried forward.
380.
by lf-non 11y ago
Curious why the authors did not choose to use Babel+ES7 async/await instead of generators. The discussion in this ESDiscuss thread ( https://esdiscuss.org/topic/does-async-await-solve-a-real-pr... ) points to multip
381.
by lf-non 11y ago
While separation of concerns is certainly good to have, Have we traditionally been using this in the right way ? I think not. In particular separation should be enforced among components which is what React encourages, not between facets of