Hacker Newsnew | past | comments | ask | show | jobs | submit | TurboHaskal's commentslogin

I was going to say the same. In my experience I can say without hesitation green field projects is how you advance your career, become visible and get promoted.


You say this because you are on HN, very senior and/or living in a bubble.

In the vast majority of programming jobs out there you are not paid to solve problems: you are told very clearly what to do, how to do it and what technology you have to use for the job.

People don't hire analysts they hire "Java programmers".


> how to do it

If you've ever lead a team, you know how much more valuable people are if they don't need to be told how to do things. Even more if they don't need to be told what to do! But having to explain in detail the "how".. can be really a big time sink and only worth it if you are training someone to level up.


The thing is that the poster I responded to also is those three things. And I am just pointing out that his job was never to keep up with the frameworks.


Or, you could have been suddenly cheated on and exposed, or divorced and recently entered the dating market, or thinking about opening up your relationship after decades of monogamy.


But the number of such people is low, it would not be easy to find candidates for the trial. Just because there are some doesn't mean there are enough to make it worthwhile for the drug company to do the testing to be able to market it to such groups.


Sure. But if they are first class and you have a mechanism to assign them to variables then there is no need for syntax sugar.


It's funny how I started this way as well, and a decade later my Common Lisp code couldn't be more procedural and CLOS and LOOP heavy.


Maybe this is just me and my experiences but when I encounter people in the wild that seem dull I often assume they just have fringe interests that are kinda problematic to share with regular people they haven't built rapport with yet.

Like they're probably into something weird or niche that doesn't translate well in casual conversation so they just keep it surface level until they figure out if you're their type of person.


Yeah I don't get it either. Lisp is perfectly fine for this task although probably makes less sense now that Julia is a thing.

Reminder that before Python was used for data science, people used things like BioPerl and PDL and that didn't stop people from working on pandas and the like.

Also let people have fun.


Lispers might not like that it's not a Lisp, but I remember Luke Tierney also making a statement to the effect that the statisticians have spoken and they don't prefer the Lisp syntax.

So Julia is a happy middle ground - MATLAB-like syntax with metaprogramming facilities (i.e., macros, access to ASTs). Its canonical implementation is JIT, but the community is working on allowing creation of medium-sized binaries (there has been much effort to reduce this footprint).


Julia isn't a lisp, but I think it's the most lispy non-S-expression based language around these days. The language creators took the lessons from lisp very seriously, and it shares a lot of functionality and philosophy with lisps.


Well I think the original author was a fan of Lisp and implemented the first Julia parser in femtolisp, IIRC. (And femtolisp was a lightweight Lisp of his own.)


Julia is somewhat different:

1. readability with explicit broadcast operators

2. interoperability with other languages including R and Python

3. performance often exceeding numpy and C/C++ code

4. usability in numerous workflows:

https://www.queryverse.org/

The idea of using Lisp or Prolog in a production environment doesn't sound fun at all. Yet, they do make some types of problems easier to handle. =3


I am afraid it is a serious argument.

If you ever feel the need to write code like that lookup table, you are working on the wrong place and you have a hiring problem.


This reads like a cautionary tale about getting nerdsniped, without a happy ending.


" I was gaining a lot of money with Ruby on Rails

Then, I decided to move to Common Lisp and start gaining less and less money

Then, I decided to move to C and got Nerd Snipped "

Well, atleast he seems more happy xD

C is cool though


Yeah, I think every programmer experiences the "I should write a language" moment when the solution to the problem is abstracted to be the language itself.


I think every programmer should at some point write their own language.


He probably means Allegro CL which is in my experience the best one.

All the OS Lisp GCs are stuck in the 80s and honestly not very good. The one in LispWorks is pretty good though but I wouldn’t call it state of the art. It just works.


How does one go about testing how good a GC is or isn't?

I'm most interested in SBCL and JVM.


I would call the LispWorks GC also superb, and it's even open source!


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: