It is not at all the same definition. A CDN is not a programming language library, which is how I had defined frameworks (with other qualifiers). All frameworks are (one or more) libraries in a programming language. A CDN is, ultimately, a network of running servers that serve up content. It's a distribution mechanism for content, not a method of building software applications (which is what frameworks are). You can use a CDN to deliver the code for a framework/library to a web browser (or anywhere else, really), but that is not the same as saying that it is a framework itself, because it is not.

A bunch of people in this thread, including myself, have been trying to help answer your original question (part of which is clarifying terms, since you seem to be confused about how things work, which is understandable for someone inexperienced), and yet you've been very combative and lashing out at people in spite of describing yourself as an amateur. When experts in the field correct your misunderstandings, it's wise to learn from the information you're given rather than telling everyone that they are wrong. Your attitude will not get you very far and will simply make people unwilling to help you learn.

Your question makes little sense, and then you tell people to search for... Something?

Sure! Go to a sub where people are trying to be helpful and give an attitude when they ask you to make sense

The quoted text makes no sense. It has gaps. And the comment you dismissed seemingly pointed that out.

Websites don't have a file system. They serve content as responses.

PHP is not a filesystem. ASPNET is not a filesystem.

You could be talking about managing files, you could be talking about sourcing web responses from local files, or you could be talking about something else.

Yeah I've quit startups twice when they ran out of money. They were both transparent about it and not everyone quit. One of them got bought and is still alive. One of them found a bit of extra money...

But to be honest a big part of quitting was because the product obviously wasn't commercially successful enough, and I didn't really want to work on a doomed product.

I don't really understand what you're asking tbh. If you want to quit, quit! You don't owe them anything.

I don't really have a lot of time to educate every single passerby on the most basic of terminology.

A simple search could do you a world of good, pal. I'd start at the Dunning-Kruger-Effect and go on from there.

Try reading the post and you will see it's about finding a filesystem tool used in web development such as Laravel or NodejsFS. There is no ambiguity here, this isnt about thumb drives or operating systems.

That's kind of their whole thing

I have sometimes switched to "do the job I would stay for" mode, but it's a fine line between that and "burn bridges" mode. In the end it hasn't worked out; things kept going downhill, though it did help confirm my feeling and improve my day to day a little.

So I'd say trust your instincts — if it seems bad and you've raised concerns and have a way out, take it. The caveat there is to always be on the lookout for better options / do the occasional interview, since you won't have as high a bar once you absolutely have to get out.

oh, I also just remembered: You might like Zig! They're a C-based language, not a framework, but they're staunchly anti-ai. If complying with your moral compass is something you want to pursue (which I think is valid, I think most devs wish they had the breathing room to do that) you might want to consider it!

I've looked it up and apparently there is a zig-based Web framework called Jetzig. I have never used it or heard about it before, but at first glance the functionality it offers seems solid enough.

I don't think what you asked made sense either. I initially thought you were going to ask a question about different file explorers because thats a relatively common topic, but what you asked made no sense.

I mean, that's simply an incorrect definition and not what anyone means when they use the word, speaking as a senior engineer working on web applications over the last 10 years. Such a broad definition is practically meaningless since it encompasses pretty much everything in programming.

A database is 100% not a "framework", it is a software application that allows clients to retrieve data by supplying queries in a dedicated DSL.

cdnjs is also decidedly not a framework, nor is any other CDN. CDNs are an infrastructural component in networking that allows content to be cached in servers that are geographically distributed over large distances in order to reduce the effects of network transmission time (since content can be served from servers closer to the client). It has very little to do with programming.

A framework is a library (or possibly, set of related libraries) in a programming language that aims to be very "batteries-included", insofar as the programmer gives up precise control over the program they are creating in exchange for having many commonly-needed things for the task (typically, SPAs or web servers) already done for them. The reason I said it's perhaps ill-defined as a word is that the line between what counts as a library and what counts as a framework is a bit blurry.

I'm not quite sure what you're looking for, but the term "non-binary data" is sending me haha

Anyways. I've used Laravel for about a year now, and it's ..fine. I don't like the push towards AI slop or their constant attempts to push their own cloud services or whatever onto you either, but it hasn't been much of a hassle to just ignore that part.

What I like about Laravel is just how opinionated the framework and the documentation is (like how it wants you to build Factories and set up proper test data when making new database Entities, and how the Inertia routes encourage a clear schema). It's also been pretty pleasant to get the basics right out of the box, like proper auth and login functions. And I like the kind of stuff that you can do with blade templates! I'm using them to serve dynamically generated SVG files and it works really well.

I haven't really needed any sort of crazy file management things though, so my opinions might be completely irrelevant to your use case. In fact, my Laravel project is really not set up for any sort of large data, since that's just not a thing I need. I'm running it in an AWS EC2 instance (the smallest one, as that's included in the AWS Free tier) with just an sqlite database right in there. If I suddenly wanted to manage files in my application, I'd probably be looking at doing that with AWS S3 buckets. Which would work I guess, but I personally really prefer interfacing with S3 buckets via AWS Lambda, and those work much better with Node, Go, Ruby or Python. I'd probably be leaning towards Node, since that's just what I'm most familiar with. Doesn't mean that it's the choice I'd recommend, because your project might have completely different technical requirements! Web dev is a confusing clusterfuck of edgecases.

If Laravel looks like it works for your requirements right now I'd say go for it. No one knows what the future looks like - it could be completely enshittified in a year, or it could be totally fine because the maintainers have just been riding the AI hype for marketing clout while still making a decent framework. If you stick to decent coding practices, switching to a completely different framework really won't be the end of the world.

Alternatively, since you're looking to hire someone for your project, maybe just focus on finding the most capable engineer you can and let them choose whatever tech stack they seem fitting? They'd probably have a much better understanding of your requirements and could make choices that work well together contextually.

The bigger paid models or potentially the local ones if given access to search the web can probably get you the right answers. The big ones have pretty much memorized half the internet, but can still be wrong so pushing them to verify their answers.

But the harder part is trusting what they say regardless. I can't just take an answer for truth, and unless I can verify the statement (fact checking myself, looking up the source, running/testing the code, etc) then it gets harder to do anything with AI. This is the thing I hate about AI in general, people just take whatever they say at face value. Lawyers with fake citations, random people asking chatgpt about random facts and such. Its a tool that people put too much faith in to do thinking for them.

Right? The bottle has opened. It has taken so much mundane work out of programming. Also, I feel like a human is just as likely to create great looking code changes with a possible flaw. You just have to review the code. Whether it's a person or a bot, "lgtm" can only be used sparingly.

Rewriting all code after everyone has been using AI tools to break it doesn't sound any better than writing good code now, be it with or without LLMs.

I haven’t paid

edit: Well I did for grok, but not on purpose. Grok still failed too.

Are you using real agents or the free chats on the web, because the latter ones are really dumb. Even when you ask them to search the web for basis you don't get much success.

But they do work, maybe not as a full replacement but my god the amount of boilerplate I can avoid in creating unit tests from scratch. Extracting and finding information in the code base is also useful, not everything is an easy text search of tracing a few code paths. It's an incredible tool for these kinds of work.

If it becomes harder to tell the difference then it also means it's closer to matching reality. And todays AI can do very impressive "reasoning", managing to debug complex issues I have had.

The most important part is that you as developer is fully responsible and can stand behind what they do and deliver using AI agents.

Don't be a dick to people that are actually trying to help you, when you admittedly don't know what you're talking about.

Typing shit into spreadsheets isn't something software engineers typically do... And usually shit that's typed into spreadsheets has to be accurate. There are major consequences if not, and AI is not reliable enough for that kind of work.

You’re confusing constructing the LLM, which is done with an actual AI (neural network) and a massive corpus of text (stolen from millions of humans in the greatest intellectual theft in history) and running the LLM, which is done with a random number generator and a massive matrix of probable next words.

You are arbitrarily deciding that the former is not part of the LLM.