HNHacker News
TopNewBestAskShowJobs

lgrapenthin

386 karma · joined July 28, 2015

submissionscomments
lgrapenthin··on Covid-19 vaccine certs on the dark web [pdf]
Why do you say "free shot", while side-effects (short and long term) can't be ruled out on an individual basis.
lgrapenthin··on Making Emacs Popular Again (2020)
Its quite similar percentages to about a 10-15 difference of IQ points at end of the distribution curve.

https://commons.wikimedia.org/wiki/File:IQ_distribution.svg

lgrapenthin··on Making Emacs Popular Again (2020)
Just because it is expensive to learn Emacs doesn't meant that it isn't worth it. Fine, you aren't "going to put the time in". But what do you get then? A mess of programs and plugins that need to be replaced, rewritten or reconfigured all the time, and its not even close compared to a well managed Emacs setup.
lgrapenthin··on Companies that use Lisp extensively
This is exactly the kind of closed thinking that is luckily absent from Clojure and the Clojure community and one of the reasons I'd prefer it over any lisp.
lgrapenthin··on The Emacs Lock-In Effect or the Emacs Sunk Cost Fallacy
I am also a 10+ year GNU Emacs user. I haven't customized it beyond font size and a few settings. I even use the default theme. Other users seem to go crazy and try to make it into a spaceship. Then they claim that it takes a lot of time to customize it. It mainly is very different to operate from all programs and window managers that we are used to these days, and people perceive this as a wrong and try to "fix" it with confusing "starter packs". In reality, its meta features and comprehensive reference documentation make it a closed environment that is very pleasant to navigate.
lgrapenthin··on Mental Poker [pdf]
Not true, and they are more of a investor scam than anything else.
lgrapenthin··on Tetris in ClojureScript
Check out some of the videos on Youtube of the Genera Symbolics Lisp Machine platform.
lgrapenthin··on Proof-of-stake is inherently self-referential
You can't inflate a coin by creating another coin. The markets for each coin aren't going to be identical, as each coin attracts a different set of buyers.

In other words, there might be people who would buy ETH, but never BTC and the other way around.

lgrapenthin··on Proof-of-stake is inherently self-referential
"People with coin" in step 3 is way too broad. And indeed, ETH PoS has a consensus protocol to decide which "people with coin" get to validate, and that doesn't work by "because the blockchain says so".
lgrapenthin··on Toward a “modern” Emacs
Why make Emacs another non-Emacs editor? Having mentored people (programming Clojure) who tried to learn Emacs via Spacemacs or some other "make it dumb" package, even after 6 months, they understood nothing about Emacs. They couldn't solve problems not solved by the "make it dumb" package. While I appreciate the effort going into these packages, I don't see them meeting their goal: Helping people to learn Emacs. They only help people to not learn Emacs while using it like a standard editor.
lgrapenthin··on Clojure: A Lisp that wants to spread
I was mainly concerned with teaching Clojure in this project as everyone had little or no experience prior, so nobody was blocked by learners. Those who were fired all had one thing in common: They refused to adopt Clojure beyond its syntax in favor of patterns they learned to rely on in another language. This varied from porting Scala polymorphism to just banging out imperative while loops with atoms. I don't think they were incapable. They simply didn't want to learn it. Code reviews turned into arguments quickly, took endless time and lead nowhere.

Their code was never touched by those who stayed and were able to work together. Later it was rewritten, because in spite of tons of unit tests (which passed), it was full of bugs. The code was considered "write-only". The rewrites averaged at 5-10% LOC.

lgrapenthin··on Clojure: A Lisp that wants to spread
Instead of just measuring how many developers adopt Clojure and how difficult/easy that is, I'd also love a measure of how many developers Clojure "puts out of business". IME Clojure is quite aggressive on that front.

In 2017 a customer wanted a set of services written in Clojure. Based on their Java experience they wanted to hire 10 devs. When I arrived they had 4, over the 1.5-year period I was there, they hired and fired 4. When I left they had 3. All 3 were not experienced in Clojure prior to the project (Java), but by 2018 each knew the entire codebase and was able to modify it and able to step in for each other. They spent less than half of their budget and all goals were met ahead of schedule.

IME learning how to put Clojure and its ecosystem in good use takes more time and effort than other languages, but its effectiveness really compensates.

lgrapenthin··on US shutdown: Flight delays caused by staff shortages
If this country was actually run like a business with that much debt, a good CEO would reduce it in size. IMO that is exactly whats happening.
lgrapenthin··on Steve Jobs Never Wanted Us to Use Our iPhones Like This
Jobs didn't focus on, at the time, non-existent features, like the mobile web, because they didn't exist. The authors interpretation is not well supported
lgrapenthin··on Open Source is Not About You
No. Whoever is leaving should have left without ranting is the only issue I'm having with this aggravating distraction. Chas knows very well how Clojure is authored. I suppose some people believe their contributions or community status give them higher authority and a right to publicly pressure Rich Hickey. But in reality they are only doing more damage to the community and likely Richs creative process on the way out. If this is the price for their contributions I want to live without them without even thinking about it.

As a power user, to me this doesn't appear to be a community issue. A handful of individuals take themselves way too seriously and don't realize how they are hurting someone emotionally.

The entire idea that a different process would produce better results is an insult in the first place. The progress and effect we got with Clojure with no enterprise funding/influence is a true miracle.

lgrapenthin··on Datomic Cloud
Datomic uses distributed storage, writes are coordinated by a single instance (transactor). Reads don't block writers and immutability allows to query consistent snapshots. Does that address your concern?
lgrapenthin··on Datomic Cloud
I don't care so much about optimized tight loops written in assembly, rather about the ability to scale nowadays. Datomic uses databases like you describe e.g. Postgres as its storage. So it would be foolish to say that it beats their performance on a bare bones level. Instead, Datomics architecture and information model make it much easier and significantly reduce the overhead to design and implement applications that provide insane performance. I won't argue that you can hand rewrite every Datomic application in its underlying storage database and get more performance out of it if you do your caching and coordination right. It will take you much longer though (I'd guess a tenfold at least), likely have some very difficult to find bugs, and the result won't be as easy to extend. With Datomic, I get memory speed performance out of the box for the heavy hitters and so much more that it take would take some very uncommon requirements for me to choose something else nowadays.
lgrapenthin··on Datomic Cloud
The main advantage is that you can do time-consistent queries against any past database state across the entire database without any read locks. This frees resources and eliminates the necessity of timestamp tables.

Then there is Datomics caching model in combination with its local data based query engine. The vast majority of critical queries only read from memory. Data that is fetched doesn't block other consumers.

lgrapenthin··on Datomic Cloud
If after three years you think so only "probably", you probably still aren't confident about your requirements.

You don't say to your girlfriend "We had fun the last three years, but probably I'm better off with my ex" unless you have no clue what you are looking for.

lgrapenthin··on Datomic Cloud
Having built a variety of products with Datomic and performance requirements I can only disagree. Especially queries are insanely fast compared to other databases.

I don't know what your data team was doing, but they must have done it wrong.

My advice is to develop without a data team from the start ;)

lgrapenthin··on Datomic Cloud
I don't believe that Datomic is profitable for Cognitect or ever has been. Given how profitable it is for my customers that truly is a shame. I wish they'd open source it, primarily because reading Rich Hickeys code is always enlightening. But I can see how cautious they are about it and am just glad they haven't already sold out to some big company who pushes tons of "business needs" into it. IME you can't really compare Datomic to a SQL database. If you know Datomic it is like comparing a filesystem to a harddrive.
lgrapenthin··on Uber’s Payment to a Hacker, and the Fallout
Sorry, but is there a better record on this issue? This article just tries to connect vaguely described events into a story. Very poor journalism, reading this is a waste of time. Was the vulnerability a dumb mistake or an unexpected exploit? Was it disclosed to the company in advance? How does this case differ from other cases so that there are four lawsuits now and why has everyone been fired? Because they created a bug bounty system that resulted in bug disclosure? Nothing appears to make sense and the journalist doesn't worry at all.
lgrapenthin··on Distributed Simulation and the Time Warp Operating System (1987) [pdf]
Brian Beckman recently asked questions on the Clojure mailing list indicating that he is working on sth. related in Clojure.
lgrapenthin··on My Increasing Frustration with Clojure
As I said, the GIGO approach is only used where costly runtime checks would be the alternative. Macros check their arguments at compile time a lot.
lgrapenthin··on My Increasing Frustration with Clojure
If you look into the tickets you'll find that they aren't bugs but feature requests. Labeling them "show stopping bugs" is even more misleading than the now prominent clojure.set complaint.
lgrapenthin··on My Increasing Frustration with Clojure
Thanks for this long and elaborate reply.

Clojure tries to put as many user faults into "erroneous" as possible but in the OPs complaint it doesn't have the required information at compile time because it is typed dynamically. This is the fundamental problem with dynamic typing that more problems keep ending up in runtime. Behavioral concerns like security etc. are then often addressed by runtime checks.

Clojure avoids those runtime checks everywhere for performance reasons - It is a clear design choice. So your observation seems correct that the "C approach" is used in the dynamic parts of Clojure.

Since we don't have a standard, the official documentation is the contract we should rely on and very soon clojure.spec, which is intended as a "standard as data", is going to be.

lgrapenthin··on My Increasing Frustration with Clojure
Could you elaborate why? (Haven't done much C) - Is the point of view that it is the languages job to prevent the programmer from relying on uncertainties?
lgrapenthin··on My Increasing Frustration with Clojure
As a dev programming in Clojure professionally day to day this complaint (core team not fixing/prioritizing bugs) seems absurd to me.

The only example given for a bug is not even a bug but undefined behavior triggered by undocumented API usage.

If the author means clojure.spec by "greenfield development" (I don't see what else he could mean) he should really reconsider his complaint since clojure.spec is going to do what he is asking for (throwing a runtime error during development if you use clojure.set with the wrong datatypes).

My impression over the last few years is that the core team became truly excellent in reacting to users needs and reports often instantaneously, especially Alex Miller and David Nolen on the CLJS side.

lgrapenthin··on Mark Zuckerberg's Twitter and Pinterest password was 'dadada'
This reminds me of Gabe Newell whose password was "gaben" when Hackers announced gold status of Half-Life 2 early.
lgrapenthin··on SICP Distilled: An idiosyncratic tour of SICP in Clojure
Excercise 1.5 needs fix, def form is is invalid
← PreviousPage 4 of 5Next →