haspok

62 ms·

571.
by haspok 10y ago
I think this is great news for the Erlang VM: while you wouldn't want to use static typing for any program you write, there is a very specific use-case where you definitely want to do that: embedding business logic in your application.
572.
by haspok 10y ago
Curry On 2017 - Sun 18 - Fri 23 June 2017 Barcelona, Spain co-located with PLDI'17 and ECOOP'17 http://conf.researchr.org/home/curryon-2017
573.
by haspok 10y ago
It is not touch screen unless you want it to be. The FHD version has a non-reflective matte screen that is not touch enabled. It also adds ~1-2 hours to the battery life...
574.
by haspok 10y ago
That was 2 years ago actually. The community sorted out most of the issues, so about 6 months later the experience was actually quite good. Dell released the Linux version of the laptop too early, I guess they wanted to get some traction bu
575.
by haspok 10y ago
They did not fix the coil whine. Nor the dynamic screen brightness issue. Just FYI. Oh, and the I2S mode for audio is still broken in the latest kernels (headset microphone not recognized, loud pops at power saving switchoffs), so I have to
576.
by haspok 10y ago
One thing that is completely missing from the Erlang side of the article are the OOB monitoring and operating capabilities. An Erlang VM is a living system that has a shell which you can connect to, and control both the VM and the applicati
577.
by haspok 10y ago
Sorry for the nitpicking, but: "One of the things that Go (and Erlang) got right was using channels as the main mechanism for synchronising and communicating between threads." Erlang doesn't have threads and doesn't use
578.
by haspok 10y ago
Whenever in doubt buying a laptop for Linux, just consult the Arch Linux wiki on the specific model. If the given model (such as the XPS 13) is popular in the community, the amount and quality of the information collected there is mindblowi
579.
by haspok 10y ago
They obviously use cheaper components than others, keeping their costs low and profits high! That's business, and people keep buying their stuff anyway, so they made the right decision not to fix this issue (no, it's not been solv
580.
by haspok 10y ago
They did not fix that either. You might be lucky to receive a device that doesn't exhibit it, or you may not notice it, or you may not even bother about it. Dell doesn't really care - they still sell loads, and as long as the onli
581.
by haspok 10y ago
They did not fix it, but the latest BIOSes (on the XPS13) make it better. Some people still complain though. I don't notice it, maybe I'm not typing fast enough :) The real annoyance for me about the input devices is that the palm
582.
by haspok 10y ago
Re: audio noisiness, it was a kernel bug with the older (9343) version, did it happen again? https://github.com/advancingu/XPS13Linux/issues/11 It took a couple of months to get it fixed...
583.
by haspok 10y ago
Thank you for the detailed answer, I think you could expand on it and include it in your book as an introductory chapter, or even as a blurb (especially the second paragraph).
584.
by haspok 10y ago
Clojure seems to be a natural choice for microservices, but I never used it for anything on a larger scale. Good point, if it is something Common LISP gets right it is definitely worth a look!
585.
by haspok 10y ago
Let me try to rephrase my question: I know what I can use Clojure or LFE/Erlang for and what their strengths/weaknesses are. I don't really know anything about Common LISP other than it is a LISP, so I would love to hear some
586.
by haspok 10y ago
I'd love to read a chapter about why would someone choose Common Lisp instead of, say, Clojure (with all the JVM ecosystem behind it) or LFE (with the Erlang ecosystem behind it). What are the use cases in which CLISP stands out and of