HN user
what a wonderful chronicle of how esoteric research became not-esoteric, and truly world-changing, and how the NSF enabled it
pour one out for the NSF folks. RIP </3
This article maps out the landscape of programming abstractions for working with LLMs. Prior to this, there wasn't any thorough attempt that we know of to make sense of and organize all of these different approaches and philosophies for programmatically incorporating LLMs into larger systems or pipelines. Hopefully this is helpful to folks who are trying to make sense of the landscape of abstractions for working with LLMs!
Ouch Peter. Massive offense taken.
In our research, we've found that editing is usually serial or asynchronous.
Medium-to-large-size company with a town hall = many people editing a document at the same time. Workshop at a company or a university with a modest size classroom = many people editing a document at the same time. I can't tell you how many times our web-based collaborative code editors would fall over during talks with small audiences we would give back in the days when I led the Scala Center.
Just because one of the benchmarks you have seen (of a multitude of benchmarks) breaks automerge by stressing it in what we believe is the most stressful scenario possible– multiple concurrent users, which is sort of the point of concurrency/collaboration frameworks, does not make it artificial or worth so flippantly discarding.
long-form essay with Automerge and that the end-to-end keypress-to-paint latency using Codemirror is under 10ms (next frame at 100hz)
Not at all what we measured.
I'd just like to register here that Yjs is the framework most widely used "in real usage" (your words) and not automerge (for many reasons, not just performance.)
still not as fast/efficient as Yjs. there are some benchmarks here from late September’23: https://arxiv.org/abs/2212.02618
disclaimer: i’m a co-author and the paper is focused on a different CRDT framework, but point is that it measures Yjs and automerge side by side
Reminds me a bit of like 2019's version of RMI...
There's a methodology of teaching programming focused on understanding and designing programs.
It's in the book (available online for free) called How to Design Programs: https://www.htdp.org
It introduces the notion of a "design recipe" for structuring thinking and problem-solving for programming.
Important note: it's a beta... So, feedback wanted. To try it out, head to https://scastie.scala-lang.org (link buried in the blog article)
Corresponding blog article here: http://scala-lang.org/blog/2016/08/09/the-scala-library-inde...
The blog post talks about an index, not a package manager
Sure, https://hackage.haskell.org/.
What continent is "Davis 338B" on? Maybe it'd be good to include a bit more location info if this is an event that's being announced?
I found very little meat in that article... Right when I had been excited about points that seemed like they were about to be made, the article unfurled into a biography and promotion of Graeber's next book :/
Given the number of people that have their fb accounts hacked every day, I'd be pretty concerned about giving Facebook my credit card info too.
For a ground-up, thorough, and free course on functional programming in Scala, take the course Martin Odersky teaches our undergrads at EPFL (Functional Programming Principles in Scala): https://www.coursera.org/course/progfun
Given as a MOOC on Coursera.
A "how it's made" of the amazing product intro/page would be a very nice read!!
PS, you also changed the title. Just saying.
(The second revision of the original title still has nothing to do with programming languages, btw... It's a programming languages conference.)
Key words: (1) programming language (2) academia (CS/PL) (3) industry
The title keeps changing, but these 3 keywords aren't kept. The words chosen mean something totally different on each revision.
Just wondering – why couldn't we keep the original title?
The original title (which is most accurate) is: Curry On: Mainstream PL and academic PL should talk more often
This also works (and illustrates that it's an event): Curry On: Mainstream PL and academic PL should talk more often. Here is a venue.
The overarching point is that this is all about designers of mainstream languages (and industry) and academic languages (academia) coming together.
Someone changed the title of the post to something that doesn't describe the event at all. It's about bringing industry and academia together.
Turns out that Bjarne Stroustrup will also be talking about the evolution of C++ alongside of Curry On http://2015.ecoop.org/event/invited-speakers-bjarne-stroustr...
True.
And on that note – Curry On is co-located with ECOOP, and Curry On registration also covers ECOOP. So you can attend both on just one ticket :)
Nope. The current trend in JavaScript has nothing to do with a type system.
Here, you have one industrial-strength statically typed language that you can write both the front-end and the back-end in. The end goal is to simplify the development of complex web apps, the thesis statement is that static types could make this end goal easier to reach.
Or, said another way, Scala now officially runs on both the JVM and in the browser.