It can use new information when performing new tasks. It can store experience based on mistakes it made. It can store knowledge in several ways (context, files) and use it when needed.
There is a chance it will forget something, but the same can be said for humans.
Using JSON as a configuration format is a big mistake. JEP authors could learn a bit from package.json problems. Hope JSON will not be used in anything significant for JDK configuration.
This is the right way to look at it. Anything with a ton of JS ads chewing up memory now is just as bad, or worse, than a ton of Flash ads were in the early 2000s. But Flash sites were, essentially, SPAs at the time. And they were far more performant than most JS SPAs are now (although a lot of that also has to do with React/Vue/etc. and how poorly-trained coders choose to deploy them).
Is there a Linux server run on fully open source hardware (what would that mean btw?)? Should we stop using "open source" because almost all computers are not fully open source?
Quite a lot of open source hardware is licensed under the BY-SA Creative Commons license which is an actual open source license. E.g. the Arduinos and things like the Milkymist One which can actually run linux.
What are you even trying to say? The fact that this is hardware isn't what makes it non-open source, there's plenty of open source hardware out there. The thing that makes it not-open-source is that the license is non-commercial.
If you can't legally use the product, the fact that the source is available is meaningless. CC-NC is a source available license, not an open source license.
Aim of many styling solutions is to completely remove brittle CSS files .
reply