News for hackers. Stuff that matters.
Re:Should JavaScript be split into two languages? Google pro... by hu3 on Sunday October 27, 2024 @12:18PM (#41963653)
Exactly.

I, like most devs, know what Lisp is.

I, like most devs, just don't care.

Re:Should JavaScript be split into two languages? Google pro... by DonHopkins on Sunday October 27, 2024 @01:26PM (#41964128)
And that proves my point that you're flaunting your ignorance and your anti-intellectualism. But you be you.

There's no point in trying to make other people stop talking about Lisp by complaining about how proudly ignorant you are, and how you want to remain that way, so you don't want anyone else to talk about it. This really isn't the place for that, since you always have the option of not reading, shutting up, and not replying and interrupting and derailing the discussion, so other more knowledgeable and curious people can have interesting discussions without you purposefully harassing them like a childish troll.

Re:Should JavaScript be split into two languages? Google pro... by hu3 on Sunday October 27, 2024 @04:33PM (#41965440)
Sorry to bust your minuscule lisp bubble but just because someone ignored your favorite niche language in an educated career choice, it doesn't mean they are ignorant.

Infantile language tribalism though, have no place in engineering and is blatant ignorance when coming from a supposed adult.

Re:Should JavaScript be split into two languages? Google pro... by kazinator on Sunday October 27, 2024 @05:56PM (#41966001)
Lisp is a family of languages, most of which are suited for many purposes.

Implementations of Lisp are no more niche than other languages with managed run-times.

Lisp has been used for even operating system development: Lisp code taking interrupts, and driving ethernet cards and disks and so on.

Which member of the Lisp family are you talking about, and what do you think is the niche?

Re:Should JavaScript be split into two languages? Google pro... by hu3 on Tuesday October 29, 2024 @09:12AM (#41983512)
> Implementations of Lisp are no more niche than other languages with managed run-times."

No more niche than Java, C# .NET and Python? Right...

> Which member of the Lisp family are you talking about, and what do you think is the niche?

You can combine all of the Lisp family together and still it wouldn't scratch the popularity, demand or job positions of any of the top languages.

Look, nobody denies Lisp'like languages are being used. Just like Fortran. :)

Re:Should JavaScript be split into two languages? Google pro... by kazinator on Tuesday October 29, 2024 @12:17PM (#41985862)
So what you mean by niche is actually popularity, and not a specific application area?

Fortran has a niche: numeric computing in scientific areas. However, even Fortran is not your grandfather's Fortran 66 or 77 any more. I had a semester of the latter once, as part of an engineering curriculum before switching to CS.

It supposedly has OOP programming in it, and operator overloading and such.

I don't know modern Fortran, so I wouldn't want to look ignorant spreading decades-old misinformation about Fortran.

Re:Should JavaScript be split into two languages? Google pro... by xscott on Sunday October 27, 2024 @04:47PM (#41965541)
If it's about career choices, people skills and charisma will get you further than any technical decisions you might make.
Re:Should JavaScript be split into two languages? Google pro... by reshlo on Sunday October 27, 2024 @04:57PM (#41965609)
> There's no point in trying to make other people stop talking about Lisp

Nobody is trying to make you stop talking about it. We’re trying to make you understand that the way you’re talking about it is elitist. When someone said they were confused by the syntax, you could have just explained it without judgement. Instead, you felt compelled to flaunt your membership of the in-group who understands Lisp, and try to make others feel stupid by implying that people who don’t understand it aren’t good programmers, or are anti-intellectual.

You’re doubling down on it in this comment, too, still insistent on making people feel like they’re “less than” because they don’t know Lisp:

> so other more knowledgeable and curious people

If I didn’t know Lisp, and my first exposure to it was from someone who sees this kind of toxicity as a reasonable way to speak to people, would I want to join their community?

Re:Should JavaScript be split into two languages? Google pro... by kazinator on Sunday October 27, 2024 @05:49PM (#41965959)
> If I didn’t know Lisp, and my first exposure to it was from someone who sees this kind of toxicity as a reasonable way to speak to people, would I want to join their community?

Wouldn't (didn't!) faze me. Every community has it. The most popular languages, platforms and tools in fact bring out unbridled hostility. Probably, hostility finds a peak in the second most popular camps. :)

We have already lost people who are influenced by this sort of fluff, because those people will be turned away from Lisp by the anti-Lisp trolling about parentheses, niches and slow processing over everything being a list, and so on. There aren't enough Lisp people around to counter it.

Re:Should JavaScript be split into two languages? Google pro... by kazinator on Sunday October 27, 2024 @06:10PM (#41966079)
I had a basic idea of what Lisp was before getting into it some 25 years ago. It soon became obvious that, no, I actually had no idea. It's not that what I thought had been wrong, but it had no content.

I knew Lisp the way I know that that guy walking down the street is my neighbor Bob. But since I've never had a conversation with Bob, I actually have no idea who he is.

When I see Korean writing in hangeul, I know it is Korean writing, but can't read a letter of it (nor speak a word of Korean).

These examples are like knowing what Lisp is.

The thing I had not expected was how the knowledge in the Lisp world and its perspectives are very informative about a whole lot of non-Lisp!