It was common for people to vandalize and throw them in bodies of water for a while before people got used to the idea. I still occasionally see some repurposed from time to time
I often find that a lot of models will call the `--help` flag to figure out the commands and arguments nowadays. If I use a cli repeatedly, I'll generally ask it to create a skill
> But more than 800,000 students attend a program that would likely fail the measure, according to department data. Roughly half of those students are enrolled in for-profit schools, which already have a reputation for shortchanging students.
> Most traditional, four-year bachelor programs fare well, with roughly 1% failing the earnings test. When these programs do fail, it's often in areas like theater, music and studio art.
My knee jerk reaction was to suspect some kind of academic purge, but this honestly seems to mostly affect schools that were kinda scammy to begin with.
In practice, I could also see this resulting in people double majoring in art if they were truly passionate
> That's why cloud providers all use mini-VMs to run customer containers (e.g. AWS Fargate) or force the customer to manage their own VMs that run the containers.
This is only partially true. Google's runtime (gvisor) does not share a kernel with the host machine, but still runs inside of a container.
Sure, you can have your LLM code with any JavaScript framework you want, as long as you don't mind it randomly dropping React code and React-isms in the middle of your app.
If we're not there already, it's just a matter of time before LLMs will be able to read and understand a framework they haven't seen before and be able to use it anyway.
LLMs are already trained on JavaScript at a deep level; as LLM reasoning and RAG techniques improve, there will be a time in the not-too-distant future when an LLM can be pointed to the website of a new framework and be able to use it.
There's actually a huge twist to this: JS people deprecate things so fast that most of the training data will be for a version that either warns about deprecations on every run, or has been fully removed from the API.
To be honest I am being positive and hopefully we'll see an explosion of AI agent that will help iron out all the bug in FOSS that is hosted on different source code hosting platform. Renovate on steroid. I would work on that if my daytime job wasn't my main and only source of revenue.
Ask a FOSS maintainer and they will not be nearly as optimistic about AI reducing the amount of bugs. A lot of AI generated pull requests are broken or useless and the up wasting a lot of the maintainers' time
Think how much training has been done on such Javascript frameworks... no one stops wondering what the outcome would be. The only fact that when I ask to create an app, without any further detail about what to use, and it defaults on React, imo it's a total failure whatever the agent
Some good stuff in here. I had no idea about AsyncIterators before this article, but I've done similar things with generators in the past.
A couple of things seem borrowed from Bun (unless I didn't know about them before?). This seems to be the silver lining from the constant churn in the Javascript ecosystem
It looks like the number of dispensaries / smoke shops that have opened up in Texas have finally reached the critical mass to unlock enough sweet, sweet tax / lobby revenue.
It's only a matter of time before more states realize how much money they're leaving on the table without legalization.
I think the person you're replying to is trying to make the point that people are generally OK with this, as long as it does not have an adverse impact on their personal lives. The hacker cloning the hard drive is likely to leverage this data to defraud or blackmail them, but Google et. al are not.
reply