> Groovy also deserved a special mention, and the pudding is Grails.
I vaguely remember that when Groovy became more typed (statically typed that is. I believe you could always put the types in but they were not checked.) there was a theory that it kind of hurt possible uptake of the language.
The reason being is that people felt well if we are adding types and a project is requiring it why don't we just use: Java, Scala, Kotlin etc. Like did Java getting more features or Kotlin coming really hurt Groovy or just that it became more of a typed language.
An analog (typed language stealing users) could happen to Elixer but I'm not really sure which language it would be.
> I think the new self-distillation technique for LLM and code generation as proposed by Apple
Speaking of Apple and eventual typing Dylan was an amazing language that just never got traction. Open Dylan still exists but few know about it. Its eventual typing is unique because Dylan does CLOS-like multimethod dispatch instead of pattern matching.
I tried to embrace this knot especially since I grew up sailing and know all kinds of ways to tie knots but I just can't seem to keep the tension as well as the traditional way. I can sometimes get ankle slip on my shoes so I like to have it tight at the top (not all shoes have lock lace holes).
The causality of what? I'm probably missing something obvious here. The cause of people getting paid less in game development I said has to do with margins (although I now think there is more to it than that).
> People want big tech on their resume because it makes them look qualified.
I think I said that?
> People with top qualifications work at big tech because of pay.
Actually I am not sure if that is true. I think top qualification people work at these places because of other reasons than just money. I'm talking Carmack working at Facebook for example is because of more possibilities and less the pay. Like FB is we have this really smart team for you and this tech for you and you can make your own products etc.
After all there is academia and that mostly pays shit and plenty of qualified people there.
> If low quality engineers worked in big tech, it wouldn't be a coveted qualification.
And I think that is probably happening more now. The 10x developer was kind of a myth. More people for less money these days particularly with AI is becoming more of the norm.
Your new point is excellent btw. I should have considered that.
I also hope it doesn't sound like I don't care for these developers who are being taken advantage of. They should be compensated fairly for their work.
EDIT I should add why I think it is a great point especially since I make recruiting software. The greatest increases in salary for most people is done by switching companies or jobs. If you don't want to leave the company because you really like what you do it would skew it so that salaries are lower.
~~Perhaps now especially since these companies are predominately hiring oversees contractors but circa 2009-2015 when I was around entrepreneurs and startups this was discussed.~~
~~Ultimately the goal is the same: make more money. So I disagree the motivation is "very different" its just a lot harder now to do a startup.~~
You kept editing your comment so disregard the above. I misread it the first time and then it changed. I left my response thats makes no sense now.
I think it is mostly just margins. Sure there are lots of people willing to work for no very little money for game dev but I would say there are tons of people willing to work for very little money for FAANG companies because they want that on their resume.
In fact since we are on hackernews that is kind of thing people wanting to be entrepreneurs do. Work at recognizable big tech company for a few years. Leave to be a founder of a startup. Investors ... well that guy came from google they must know what they are doing etc (the irony is they probably have less of the skills to start a company going that path).
I have to agree (ignoring the whole C doesn’t throw exceptions).
I have been looking at our bugs, logs and exceptions recently of the past 6 years and an enormous amount of bugs are caused by methods/functions that have multiple parameters with the same type (Java).
This happens because (my theory) we use java and java doesn’t have type aliases or value types as well as easy destructuring. It also doesn’t have named parameters (well there is a compiler option to retain the parameter name but it’s not like ocaml label parameter or python kwargs).
So often times in boring business programming you are dealing with methods with 5 to six strings so it’s very easy to mix up the parameter order.
Very few “hard” bugs were caused by NPEs where as the previous problem caused serious pain.
People complain about the parens in Lisp but what kills me about Lisp in general is not the parens but the fact your brains has to read the code from bottom to top and/or right to left. This is because of prefix notation.
And while I do not like object oriented languages its far more natural to English readers such as myself to write and read things from top to bottom and left to write.
Now of course some FP languages have operators to (Haskell, F#) to allow left to right function application and you could of course make macros in Lisp in whole it doesn't really fix the problem entirely.
You can also of course mitigate the above with judicious use of let expressions but more often than not people inline anyway.
I'm try to understand how Ruby has any relation to Clojure's purported dying other than I guess a few critical things were said at a Ruby conference.
What is becoming less popular is dynamically typed languages or perhaps more correct to say languages who's types are not statically analyzed at compile time.
So if there is anything hurting Clojure I believe it is the increased uptake of languages with much better type systems than in the past (Scala, Swift, Rust, and even Go).
Particularly Go as clearly it is eating a lot of the jaded JVM crowd (that .NET core should be taking up but for various reasons have not).
Hell even Python is moving towards being more type oriented or at least having support for optional typing.
That being said I think out of all the dynamic languages Lisp, and thus Clojure are the best. I even like Elisp. Its the only time I do like a dynamic language (other than quick shell like scripts) and that is because the runtime is integrated so heavily with the development that essentially you are getting your types constantly checked (as well as auto completion and code lookup).
I don't know much about contract management so take most of what I have to say as an ignorant opinion.
I'm trying to figure out how ContractBeast's problem of continuous usage is any different than almost all the business tools out there that require human intervention (with the exception of email, and MS office suite).
It seems every investor and entrepreneur has this desire to make "crack" and not just tools. Good tools don't need to be used all the time. They don't need to provide some sort of gamification, feedback loop, or enjoyment.
As for money making good business tools don't need even need to be used by the user... in fact they really should be automated. I know this because we had some of the some problems ContractBeast did and the key was not getting the endusers involved at all. Automate and integrate so they are almost out of the loop completely (again I don't know much about CLM... maybe this isn't possible).
As far as top down selling it is almost impossible in the B2B market to do something different. Managers force users to use tools and those users use MS Office most of the time but those tools still get bought and eventually those tools do provide value (aka sales force).