It is interpreted. It actually implements a Python (-like ?) interpreter that can run on a microcontroller. See e.g.: Compile MicroPython code for Micro Bit locally.
Stuff that is beautiful but useless because it does not make food or houses cheaper.
Or from Ciro Santilli's best random thoughts:
Without technology, one cannot survive. Without art, one cannot live.
But that sure enough has a Jesus semi-precursor, and likely many others: man shall not live by bread alone.
Searcing beauty is a painful thing. You just keep endlessly looking for that one new insight that will blow your mind.
The key missing point would be "usefulness". See also: Section "Art".
Framework built on top of React.
gothinkster/realworld blog example by Ciro Santilli: node Express Sequelize Next.js realworld example app.
Basically what this does is to get server-side rendering just working by React, including hydration, which is a good thing.
Next.js sends the first pre-rendered HTML page along with the JavaScript code. Then, JavaScript page switches just load the API data.
Next.js does this nicely by forcing you to provide page data in a serialized JSON format, even when rendering server-side (e.g. the return value of
getServerSideProps). This way, it is also able to provide either the full HTML, or just the JSON.Some general downsides:
- it does feel like they don't document deployment very well however, especially non-Vercel options, which is the company behind Next.js. I'm unable to find how to use a non Vercel CDN with ISR supposing that is possible.
- Next.js is very opinionated, and like any opinionated library it is sometimes hard to know why something is/isn't happening, and sometimes it is hard/impossible to do what you want with it unless they add support. They have done good progress, but even as of 2022, some aspects just feel so immature, some major-looking use cases are not very well done.
In theory, Next.js could be the "ultimate frontend framework". It does have a lot of development difficulties that need to be ironed out, but the general concepts, and things it tries to integrate, including e.g. webpack, TypeScript, etc. are good. Maybe the question is when will someone put it together with an amazing backend library and dominate and finally put an end to the infinite number of Js Frameworks!
In-tree examples at: github.com/vercel/next.js/tree/canary/examples
In order to offer its amazing features, Next.js is also extremely opinionated, which means that if something wasn't designed to be possible, it basically isn't.
No prerender with custom server? It forces you to write your API with next as well? Or does it mean something else?
TODO can it statically generate pages that are created at runtime? E.g. if I create a new blog post, will it automatically upload a static page? It seems that yes, and that this is exactly what Incremental Static Regeneration means:However, Ciro can't find any mention of how to specify where the pages are uploaded to... this is pat of the non-Vercel deployment problem.
- github.com/vercel/next.js/discussions/25410
- vercel.com/docs/next.js/incremental-static-regeneration
- github.com/vercel/next.js/discussions/17711
- www.reddit.com/r/nextjs/comments/mvvhym/a_complete_guide_to_incremental_static/
- github.com/vercel/next.js/discussions/11552#discussioncomment-115595
- stackoverflow.com/questions/62105756/how-to-use-aws-with-next-js
- github.com/vercel/next.js/discussions/17080
- github.com/vercel/next.js/discussions/16852
Can't ISR prerenter by URL query parameters:
That plus the requirement to have one page per file under
pages/ leads to a lot of useless duplication, because then you are forced to place the URL parameters on the pathnames."Module not found: Can't resolve 'fs'" Hell. The main reason this happens seems to be the that in a higher order component, webpack can't determine if callbacks use the require or not to remove it from frontend code. Fully investigated and solved at:
Overviews:
- www.reddit.com/r/reactjs/comments/8evy5d/what_are_the_downsides_to_nextjs/ 2017 What are the downsides to Next.js?
Ciro Santilli managed to port it to Sequelize for PostgreSQL as shown at: github.com/cirosantilli/feathers-chat/tree/sequelize-pg
Contains several computer vision models, e.g. ResNet, all of them including pre-trained versions on some dataset, which is quite sweet.
Documentation: pytorch.org/vision/stable/index.html
From the 2020/2021 Oxford physics course handbooks we can determine the following structure:
- Year 1 (CP, "Coure Preliminaries", "Prelims"). Take all of:
- CP1 Classical mechanics, Special relativity
- CP2 Electromagnetism, circuit theory and optics
- CP3 Mathematical methods 1. Complex Numbers and Ordinary Differential Equations. Vectors and Matrices.
- CP4 Mathematical methods 2. Multiple Integrals and Vector Calculus. Normal Modes, Wave Motion and the Wave Equation.
- Year 2 (Part A). Take all of:
- A1 Thermal physics. Kinetic Theory, Heat Transport, Thermodynamics.
- A2 Electromagnetism and optics
- A3 Quantum physics. Quantum Mechanics and Further Quantum Mechanics.
- Short options: at least one of:
- Mathematical Methods
- Probability and Statistics
- S01 Functions of a Complex Variable
- S07 Classical Mechanics
- S10 Medical Imaging and Radiation Therapy
- S13 Teaching and Learning Physics in Schools
- S14 History of Physics
- S20 History of Science
- S21 Philosophy of Science
- S22 Language Options
- S25 Climate Physics
- S27 Philosophy of Space-Time
- S29 Exploring Solar Systems
- S33 Entrepreneurship for Physicists
- Year 3 (Part B). Take all of:
- Michaelmas term
- Hilary term
- B1 Fluids
- B3 Atomic and laser physics
- B5 General relativity
- B7 Classical Mechanics (for MPhysPhil only?)
- B8 Computational Project
- B9 Experimental Project
- Year 4 (MPhys). Select two from:
Trinity term, the third and final term of each year, contains mostly revision from the previous two terms, after which students take their final exams, which basically account for their entire grade. Trinity is therefore a very tense part of the year for the students. After that they have summer holidays, until coming back for the next year of madness.
The official external course landing page: www.ox.ac.uk/admissions/undergraduate/courses/course-listing/physics. 2021 archive: web.archive.org/web/20221208212856/https://www.ox.ac.uk/admissions/undergraduate/courses/course-listing/physics) In those pages we see the rough structure, except that it does not have the course codes "A1" etc., and some courses are missing.
At web.archive.org/web/20221229021312/https://www2.physics.ox.ac.uk/sites/default/files/2011-06-03/course_v3_pdf_80151.pdf page 11 we can see the global course structure giving the two options, 3 year BA or 4 year Oxford physics masters:
Year 1
(Prelims)
|
|
v
Year 2
(Part A)
|
+-----------+
| |
v v
Year 3 BA Year 3 (MPhys)
(Part B) (Part B)
| |
| |
v v
BA Year 4
(Part C)
|
|
v
MPhysPractical courses notes: www-teaching.physics.ox.ac.uk/
Some others with lecture notes:
Pinned article: Introduction to the OurBigBook Project
Welcome to the OurBigBook Project! Our goal is to create the perfect publishing platform for STEM subjects, and get university-level students to write the best free STEM tutorials ever.
Everyone is welcome to create an account and play with the site: ourbigbook.com/go/register. We belive that students themselves can write amazing tutorials, but teachers are welcome too. You can write about anything you want, it doesn't have to be STEM or even educational. Silly test content is very welcome and you won't be penalized in any way. Just keep it legal!
Intro to OurBigBook
. Source. We have two killer features:
- topics: topics group articles by different users with the same title, e.g. here is the topic for the "Fundamental Theorem of Calculus" ourbigbook.com/go/topic/fundamental-theorem-of-calculusArticles of different users are sorted by upvote within each article page. This feature is a bit like:
- a Wikipedia where each user can have their own version of each article
- a Q&A website like Stack Overflow, where multiple people can give their views on a given topic, and the best ones are sorted by upvote. Except you don't need to wait for someone to ask first, and any topic goes, no matter how narrow or broad
This feature makes it possible for readers to find better explanations of any topic created by other writers. And it allows writers to create an explanation in a place that readers might actually find it.
Figure 1. Screenshot of the "Derivative" topic page. View it live at: ourbigbook.com/go/topic/derivativeVideo 2. OurBigBook Web topics demo. Source. - local editing: you can store all your personal knowledge base content locally in a plaintext markup format that can be edited locally and published either:This way you can be sure that even if OurBigBook.com were to go down one day (which we have no plans to do as it is quite cheap to host!), your content will still be perfectly readable as a static site.
- to OurBigBook.com to get awesome multi-user features like topics and likes
- as HTML files to a static website, which you can host yourself for free on many external providers like GitHub Pages, and remain in full control
Figure 2. You can publish local OurBigBook lightweight markup files to either OurBigBook.com or as a static website.
Figure 3. Visual Studio Code extension installation.
Figure 5. . You can also edit articles on the Web editor without installing anything locally. Video 3. Edit locally and publish demo. Source. This shows editing OurBigBook Markup and publishing it using the Visual Studio Code extension. 
- Infinitely deep tables of contents:
All our software is open source and hosted at: github.com/ourbigbook/ourbigbook
Further documentation can be found at: docs.ourbigbook.com
Feel free to reach our to us for any help or suggestions: docs.ourbigbook.com/#contact