HNHacker News
TopNewBestAskShowJobs

lgessler

1,767 karma · joined September 29, 2015

https://lgessler.com
submissionscomments
lgessler··on Lemonade files S1
> which comes with fake “typing…” indicator.

Being forced to use a chatbot sounds annoying, I agree, but for people who aren't like us on HN who are in the know, the typing indicator fulfills an important function: instant replies can be jarring to users and inhibit their ability to understand the interaction as chat. (There is some evidence to think this intuition is right, by the way: https://chatbotresearch.com/wp-content/uploads/2018/11/icis2...)

Let's not get into whether chatbots have done more harm than good, but I think we can agree that if we're going to have them at all we should do them right.

lgessler··on Bhūribhirbhāribhirbhīrābhūbhārairabhirebhire
Sure, it's a fact of Sanskrit that of all the well-attested classical IE languages it's done the best job of preserving PIE's case system. But what's this have to do with the question of whether Sanskrit has some especial status as a tool for thought, AI, or whatever people are claiming in this paper and elsewhere? Is it that using inflection for indicating grammatical relations is somehow superior to using adpositions? I'd be very interested to hear an argument that makes the case for this for something more than aesthetics, but I can't imagine one myself.
lgessler··on Bhūribhirbhāribhirbhīrābhūbhārairabhirebhire
I admit I haven't read the paper, but as someone who works in NLP and is in a linguistics department I have to say that this claim seems absurd. Leaving aside what "viable in NLP" means, all natural languages are rich in ambiguities, redundancies, and hazy polysemy that don't occur in, say, FOL used for knowledge engineering. And Sanskrit, being a natural language, is no exception.

If it did turn out that Sanskrit were exceptionally well suited for something in AI, I'm willing to bet that either the domain of AI or Sanskrit (either the systems in its grammar, or our respect for it as a natural language that can only imperfectly be captured by a formalized grammar of it) would need to be so constrained in scope that this supposed exceptionality would seem rather cherrypicked.

I'm not saying Sanskrit isn't cool (it's super cool), but I am saying we should resist insinuations that it's somehow more conducive to sophisticated thought or whatever.

lgessler··on Zoom Acquires Keybase
Come on, the engineers at Keybase are serious crypto nuts. Give them some more credit
lgessler··on Bill Joy's greatest gift to man – the vi editor (2003)
Do you remember the time when every time you wanted to copy or paste something in a word processor you would dutifully hike your mouse up to the Edit button so you could select "Copy" or "Paste", and how when you learned that CTRL+C and CTRL+V was a thing your mind was blown with how much quicker it was? Vim gives you that experience, except times a gajillion because it not only speeds up what you already do in a WYSIWYG word processor but also gives you powerful new tools to edit that have no WYSIWYG equivalent.
lgessler··on Which is better on Android: divide by 2 or shift by 1?
In defense of the author re: 2, since the application domain seems to be manipulating indices for a binary tree represented in an array, the integer will always be non-negative.
lgessler··on I’ve made a conscious effort to stop apologizing for bugs in my code
GP meant "harder" in the "it's possible to get things "perfect"" sense, not in the "leads to a more challenging professional life" sense.
lgessler··on Which is better on Android: divide by 2 or shift by 1?
Question from a perf noob: it seems like this in principle only shows that there's no difference for a Pixel 3 because other Android machines could have processors that have/lack an optimization for shift or divide. Couldn't a different Android phone have different performance characteristics?
lgessler··on The Chaos Programming Language
There are none, at least in the familiar OOP sense:

> Chaos language is not object-oriented. So everything is done by functions and data types.

lgessler··on Shirt Without Stripes
A good demonstration of the linguistic fact that far from being meaningless, prepositions (adpositions, more generally) are actually highly consequential for meaning and are highly ambiguous between different meanings. Here's a paper that'll give you a good appreciation of this from an NLP perspective if you're curious: https://www.aclweb.org/anthology/W16-1712.pdf
lgessler··on JACL: JavaScript Assisted Common Lisp
It was close to happening, too[1]:

> Eich originally joined intending to put Scheme "in the browser",[10] but his Netscape superiors insisted that the language’s syntax resemble that of Java. The result was a language that had much of the functionality of Scheme, the object orientation of Self, and the syntax of Java.

[1]: https://en.wikipedia.org/wiki/Brendan_Eich#Netscape_and_Java...

lgessler··on JACL: JavaScript Assisted Common Lisp
When I saw this I thought "I wonder why someone would make a JS-hosted Lisp when ClojureScript exists and is used widely." I then found that the author has had significant involvement in the Clojure community, which piqued my curiosity even more. Alan, if you're reading this, I'd be interested to hear about why you're pursuing this project!
lgessler··on “Sequel” to the million dollar homepage using WebGL
I think this position is a little too extreme. Many ads fit your description, but some don't. In many parts of the United States, for instance, you simply need a car to live life, and car ads have the power to shape car buyers' choices in these areas. In a case like this, it's not true that they're buying "something they don't need in the first place".
lgessler··on U.S. Jobless Rate May Soar to 30%, Fed’s Bullard Says
I think GP means the government should provide these.
lgessler··on MIT moves all classes online for the rest of the semester
For one thing, profs often teach some classes repeatedly, which means they dont have to put substantial effort into planning for subsequent offerings. If the planned content is somehow unsuitable for a different medium of delivery, this would take some planning that they weren't expecting at the beginning of the semester.
lgessler··on How Do We Know That Epic Poems Were Recited from Memory?
I'm unsure of your point here--isn't memorizing the text itself much harder than knowing this kind of high level structure, which I venture many people had/have no conscious awareness of anyway?
lgessler··on Clojure: A Lisp that wants to spread
In the abstract you're right that equality is subtle and complicated, but it seems to me that in practice, most practicing software engineers just want value-equality on garden-variety data structures most of the time (remember == for Strings in Java?), and that for this use-case, a leaky abstraction is fine--preferable, even. At least, the alternative--forcing users to consider the subtleties of equality even in circumstances where it can be safely ignored and having them memorize dozens of cryptic equality operator names--is excessive and unnecessary.
lgessler··on Clojure: A Lisp that wants to spread
My personal take: CL is a multi-paradigm rummage bin that demonstrated to the world the greatness of many features (e.g. macros, CLOS), but is also beset by many design flaws--some due to genuine infelicity of conception, and some due to unavoidable limitations of software and hardware at the time. (For one thing, there are approximately 101 ways to test equality). The result is that you could be a career CL programmer and see code written in a style you've never seen before, and that it suffers from design flaws that, if fixed, would result in something that would no longer be Common Lisp. Scheme's problem is kind of the opposite: it's stripped down, but also has not purged all of CL's unfortunate baggage, and very conspicuously lacks an out-of-the-box and full-featured package manager.

Clojure, being just over 10 years old, has gotten to benefit from decades of witnessing other languages' spectacular design disasters, and it was designed by one person in a few years instead of by committee over decades. This results in a language that is much more aesthetically coherent, adhering to a pragmatic flavor of FP, and avoids a lot of gnarly warts: for instance, Clojure has one basic way to test equality irrespective of data type, and all basic data structures are immutable.

lgessler··on Joe, a Postgres query optimization bot
> Every time when an engineer starts communicating with Joe, a new full-size copy of the database is provisioned.

It looks like users get their own disposable copy. Nothing's run on the prod copy.

lgessler··on Ontario's new license plates have a problem: you can't read them
Can you explain? As a cheap and pretty much failure-free means of visually broadcasting the identity of a vehicle, they seem pretty irreplaceable. Anything requiring electronics is much more prone to failure. Even airplanes have their call signs written clearly somewhere on their body.
lgessler··on Jupyter Notebooks to Web App
Agreed, my personal gripe has always been that notebooks encourage people to write code with _no_ functions or abstraction, often leading to 400 lines of gobbledygook with bad variable names that somehow gives you F1 scores and graphs at the end. You can write functions in notebooks (and I do when I write mine), but there is not a culture of this in place, and arguably the notebook interface itself encourages you _not_ to write functions.
lgessler··on Proposals for Go 1.15
Sorry, I didn't make the point I wanted to, which is that GP (on my reading) seems to think that breaking changes are necessary and unavoidable for the long-term health for a PL. I'm saying Clojure seems to be perfectly fine even without any breaking changes in over 10 years, and that it seems like it'll continue like this indefinitely.
lgessler··on Proposals for Go 1.15
It doesn't have to be like this. Clojure is over 10 years old and has more or less achieved its vision of never having a breaking change in the core language. This comes at a cost (many rejected proposals, very very slow acceptance of them) but it's still proof that you can avoid breaking changes if you are sufficiently cautious. (It probably also helps that Clojure has a full-fledged macro system that lets users write libraries that would have had to be compiler plugins or language proposals in other languages.)
lgessler··on Autocomplete as an Interface (2015)
I don't think there's anything inevitable about AbstractSingletonProxyFactoryBean. This absurd design pattern has its roots in Java's misguidedly restrictive approach to abstraction, which all but requires classes and inheritance to be the primary units of abstraction. More graceful abstractions are unergonomic or impossible since Java was not designed e.g. for higher order functions. The requirement that everything be in a class and the ontological awkwardness that often ensues when some conceptually non-object-y entity must be coerced into an object results in a lot of incidental complexity.
lgessler··on Yatri: First electric motorcycle to be made in Nepal
It's approximately same sound that's in "all": https://en.wikipedia.org/wiki/Open_back_unrounded_vowel
lgessler··on Yatri: First electric motorcycle to be made in Nepal
I'm generally in agreement and want to anticipate an objection—that the sounds of foreign words often fall well outside of any given person's native set of sounds.

Take Iran for example. It's rendered often in English as [ɑɪ.ɹæn] (eye-ran). What it "should" be is [i.ɾɑn] (ee-rahn). Fortunately, all the sounds in [i.ɾɑn] are ones that occur in most varieties of English (with the exception of the [ɾ], but that's minor), so most speakers are able to accommodate without issue.

Now compare that to Shanghai: its English rendition is [ʃeɪŋ.hɑɪ], and its Mandarin pronunciation is [ʂâŋ.xài]. Most Englishes lack the voiceless retroflex fricative [ʂ], and the same for the voiceless velar fricative [x], and to make matters worse, Mandarin is tonal, which puts the correct pronunciation of this word squarely out of reach for almost all English speakers.

It still makes sense to insist that people try as hard as they reasonably can. Perhaps to say that speakers should get as close as possible—in the case of Shanghai, for example, maybe this would mean [ʃɑŋ.hɑɪ] instead of [ʃeɪŋ.hɑɪ].

lgessler··on State of JavaScript 2019
Overview page
lgessler··on State of JavaScript 2019
Ha!

BTW Sacha, thanks so much for Discover Meteor, it was what I cut my web dev teeth on! Somehow I hadn't heard about Vulcan until now. It looks really interesting and I'll be looking into it more.

lgessler··on State of JavaScript 2019
So sad to see Meteor solidly in the avoid quadrant, but it seems deserved. Meteor is what I learned how to do web development with back in 2015, and it was fun. It didn't take much to make stuff happen, and the baked-in live sync was like magic. I'm still eager to whip Meteor out for proof of concept prototyping because of how convenient it is to have a schemaless database and a framework that abstracts away HTTP, but for one thing I feel Meteor's big bet on Mongo hasn't paid off.

Also surprised to see ClojureScript's satisfaction rate at 60%. In the past year or two it's become much easier to use NPM packages, which was IMO the last remaining huge missing piece. It's now a great language for web development, providing what JS couldn't: a rich standard library with, ahem, consistent API's, a strong FP flair with excellent immutable data structures built in, and maybe most critically of all, a somewhat constrained macro system that allows users to write and distribute third-party libraries for syntax that in other languages would have required an extension of the language standard.

All of that is (I think) desirable by anyone unless you're hardcore anti-FP (with the one exception, I guess, that macros can be and are abused, though I haven't seen it very often in the CLJS ecosystem). So why hasn't ClojureScript seen more adoption? It's the age-old curse of Lisp, I guess: those dang old parentheses which decades of CS curricula taught in ALGOL descendents have rendered foreign and horrifying.

lgessler··on Using Clojure for Web Apps
Sure, and we could argue about whether mutable code is necessary at systems layers. But at application layers (i.e., the ones most developers work at), cost of development is almost always going to come before performance, and I think it's clear by now that OOP, at least insofar as it has been instantiated by Java, C#, and friends, has not delivered on its promise to simplify application development.
← PreviousPage 7 of 13Next →