vemv

43 ms·

421.
by vemv 9y ago
Define 'boring'. Boring for me would be an homogeneous stream of code babble, possibly in mainstream languages that barely interest me. Also worth noting that languages/ecosystems grow kind of slowly, HN couldn't be poss
422.
by vemv 9y ago
I'm interested in Reason/Buckle, coming myself from the ClojureScript. The seemingly tinier minified compilation size would be a huge plus. But what are the actual sizes emitted for large scale projects (arguably the ones that mat
423.
by vemv 9y ago
Despite hype and success, Machine/Deep Learning have their own limitations, which is a generally admitted fact. At a fundamental level - are our brains actually comparable to how ML works (beyond some basic analogies)? Do we have an st
424.
by vemv 9y ago
I recently read that a lot of DBs do this, or at least have done so historically. Might be like patents - being more of a defense mechanism, rather than an actual device intended to be used against customers.
425.
by vemv 9y ago
What's its authorization story? More generally, how good actually is authorization in graphql? Official docs seem to essentially say "not our problem!", while various tutorials say "here's the best hack we could com
426.
by vemv 9y ago
Performance certainly matters. I applaud the tireless effort from the Atom core team. Personally I'm taking a pause off Atom (after 3 years professional usage) until it definitely improves. Best wishes!
427.
by vemv 9y ago
I'll refrain from buying an iMac Pro (which was on my roadmap) until the situation is fully clarified. I mean how frustrated would one feel if it turned out that one spent that amount of money in a computer that should be replaced as
428.
by vemv 9y ago
Could be, thanks for the pointer. But the 3-way merge apps I remember conflate the past context with the would-be result, which was confusing. Googling now I see that one of them has distinct "Reference view" and "Edit view&q
429.
by vemv 9y ago
One thing I miss on every merge tool is full history context for both sides ("side" == ours/theirs). i.e., I don't want to just see the final state of ours/theirs, but the changes that us/them did in order
430.
by vemv 9y ago
I disagree. Airbnb, Uber, Amazon and many others are extremely basic ideas that some person or another would have come up with sooner or later. Basically it was a matter of being in the right place, right time, right knowledge (and executio
431.
by vemv 9y ago
1.- If you are in the right mindset, ideas will come effortlessly. Read articles, work with cutting-edge programming languages (even for toy projects), be involved with communities. 2.- There are no blatant problems awaiting for a solution
432.
by vemv 9y ago
Yeah just realised that... Last time I checked it seemed alive, now not so much. Fingers crossed
433.
by vemv 9y ago
Built a home office v2 after working a couple years in various offices, coworkings or in my living room (couch != home office). Single best decision I've done in my career. Finally I'm in control of lighting conditions, noise leve
434.
by vemv 9y ago
Cool! Will have an in-depth look at it as I also love both Rails and Clojure (which can get you strange looks from both camps). TBH I have pretty clear that my next Clojure project will use https://github.com/arachne-framewo
435.
by vemv 9y ago
Your observations are on point, and collaborating with lispers is not free of bitter moments. At work we use cljfmt (similar to gofmt) plus a variety of hacky formatters and conventions. It works for us and I hope to open-source part of our
436.
by vemv 9y ago
An alternative ambulance service wouldn't be just an 'app', but an actual entrerprise with various logistical, legal and medical operations and probably hundreds of employees. The US would be a better place with that hypothet
437.
by vemv 9y ago
By the way I agree with `There is a better thing, even if you must make it`! But I make those 'things' within lisp rather than by exploring new languages. If done sensibly, colleagues will be able to use those custom abstractions
438.
by vemv 9y ago
Threading macros (-> / ->>) can greatly improve readability, putting lisps on par with Ruby (which I appreciate much). Best of all, emacs/Cursive lets you trivially transform a sexpr into a threading form, and back. So on
439.
by vemv 9y ago
Would agree with your view, but Lisps are arbitrarily powerful by the means of macros and interop. In my daily work (Clojure) I can use different concurrency and typing models than Clojure originally envisioned, via core.async, clojure.spec
440.
by vemv 9y ago
Similar sentiment here. Luckily I had the chance to move ruby->clojure professionally. I used said chance, but I try not to disconnect too much from the ruby world as it's such a nice/productive ecosystem. You never know when y
441.
by vemv 9y ago
I think the article's point would be more convincing if they related that study to real-world examples. Personally I cannot imagine how corruption makes the world any better?
442.
by vemv 9y ago
Thought the same. My wild guess is that those engineers are at their career peek in terms of energy / ability to deliver glue code, but a few years behind getting to be a well-rounded engineer that can live/work sustainably.
443.
by vemv 9y ago
In addition: by testing a devcard you also, of course, are implicitly exercising the underlying code. So instead of writing a test for code X, you can test a devcard using X instead, and kill two birds with one stone. Especially true if you
444.
by vemv 9y ago
For large/ambitious cljs apps I'd recommend unit-testing each devcard somehow. At work we haven't done it and it's a regret - not cool to find an outdated devcard that doesn't work anymore. (not a flaw in Devcards i
445.
by vemv 9y ago
Mutability, boilerplate, no built-in mechanisms/conventions for saner programming, tooling/trend hell
446.
by vemv 9y ago
Clojure(Script) is a general-purpose language.
447.
by vemv 9y ago
Thanks for the question but I haven't tried it myself (yet). With Clojure(Script) whole categories of complexities tend to disappear, so I'd expect that to be the case in this scenario too.
448.
by vemv 9y ago
Serverless stacks do run on servers, and on node.js in this case.
449.
by vemv 9y ago
I'd use cljs for Serverless architectures. There's JVM support in e.g. AWS Lambda, but JS is a more popular and lightweight target.
450.
by vemv 9y ago
The fact that you "just walk out of the door" says more about you than about clojurescript or the jvm.

More ›