Which part of "commodity" is confusing???
3,324 karma · joined August 5, 2020
Which part of "commodity" is confusing???
Funny how we don't hear that movement much...
Anyone pretending gen-ai code is understood as well as pre-gen-ai, handwritten code is totally kidding themselves.
Now, whether the trade off is still worth it is debatable, but that's a different question.
weasels gonna weasel
We had a potential pet poisoning, so was naturally searching for resources. Google had a summary with a "dose of concern" that was an order of magnitude off. Someone could have read that and thought all was fine and had a dead cat.
(BTW cat is fine, turned out to be a false alarm, but public service announcement: cats are alergic to aspirin and peptobismal has aspirin. don't leave demented plastic chewing cats around those bottles, in case you too have a lovely but demented cat)
It's just not. I've been a developer for 25+ years, and in technical diligence looking at companies getting investments for seven, and have done diligence on 100+ companies. It's ALL OVER THE PLACE. It depends on the product, the company, the team, the way the company is managed, the business domain, etc.
For some companies, products, and teams.. the code absolutely is the hard part, and building that insanely sophisticated software is worth millions. I've seen scientific software that sold for millions of dollars per copy.
For others, the code is essentially commodity plumbing around some operational knowledge of a domain that makes nice dough with minimal code complexity. I've also seen founders who were going to spend the rest of their days floating around the bahamas because they wrote the right PHP-ball-of-mud in the right domain at the right time, sigh.
The world of software is vastly broader than the vast majority of programmers think. And there are a lot of very, very different ways to make money in it.
It's noticeable to me all the time, but if I'm borderline migraining, or recovering from a migraine, the difference between shifted and not is something I can feel instantly. Shifting all the way over enables me to eek out some work after a migraine without it flaring back up again.
And we are going to need more curration so goddamned badly....
- Install Stylebot extension for your browser
- make an entry for youtube.com
- enter this css: .shortsLockupViewModelHost { display: none}
Bam, no more shorts.
The single C file convenience really is helpful. When I was figuring out the byzantine build process for incorporating s7 into a mixed JS, C, Scheme app, it was great to not have any additional foot guns there. On my eventual todo list is porting some of the same work to incorporate into JUCE apps for mobile, so good to know that worked for you.
Fennel is another language I have been watching, good to hear that worked out well.
https://ccrma-mail.stanford.edu/mailman/listinfo/cmdist
In my context, I have rigged up a REPL in Max, so I wind up using that instead. (Which is freaking awesome, because I can script all of Max from my vim buffers.)
Happy to answer other questions.
For people interested, I will update that page today with thoughts five years on.
TLDR: still really happy with the choice!
The first is that it seemed at the time that Scheme was going to be easier to work with, and that has proven true. It's a lot easier to do music theory hacking and integrate with Max using a lisp 1. Being able to seamlessly change whatever the first form is (function, hash-table, list, vector) with no change to the code has turned out to be really really nice in my work.
The second was that when I started I knew little about Schemes and Lisps and it seemed when going through the docs like ECL at that time was going to be a bigger lift to get going.
Best HN site today, IMHO.
I do not understand what has happened to him here... there was an entire "AI winter" in the 90's to 2000's because of how wrong researchers were. Has he gone completely delusional? My PhD supervisor has been in AI for 30 years and talks about how it was impossible to get any grant money then because of catastrophically wrong predictions had been.
Like, honest question. I know he's super smart, but this reads like the kind of ramblings you get from religious zealots or scientologists, just complete revisions of known, documented history, and bizarre beliefs in the inevitably of their vision.
It really makes me wonder what such heavy LLM coding use does to one's brain. Is this going to be like the 90's crack wave?
I was, coming from being mostly a highlevel language coder, suprised at how much I like working in this combo.
Low level stuff -> raw C. High level stuff -> Scheme, but written such that I can drop into C or move functions into C very easily. (The s7 FFI is dead simple).
It's just really nice in ways that are hard to articulate. They are both so minimal that I know what's going on all the time. I now use the combo in other places too (ie WASM). It really forces one to think about architecture in what I think is a good way. YMMV of course!
Savantism can be pretty damned weird. I've known a few, including a couple who will never have an adult career beyond local gigs because of their mental disabilities in other, non-music areas. The Oliver Sacks book "Musicophelia" has fascinating case stories about it.
An example page (not mine) of it running in the browser is here: https://actondev.github.io/s7-playground/
I really hope the racket effort gains traction too! Excited to see this. In comparison, s7 is much more minimal. Though this also means the FFI is dead simple too, so extending it and bridging to js functions is much easier, and everything in s7 is available now in WASM - CL macros, keywords, hashtables, first class environments, continuations, etc