I have yet to find an alternative to the GraphQL protocol that has the following requirements:
- Good support for HTTP 1.1
- Provides typesafe contracts for queries and mutations
- Strong support for most common UI clients (JS/React Native/SwiftUI)
- Backend can be written in a language that isn't JavaScript/TypeScript
- Large developer community
Closest thing I've found is defining your schema using OpenAPI spec, and using tools to generate code from that source for the client and server, but this is a much worse DX than the process of defining GraphQL schemas.
My solution has been to use it as a second monitor, run it at native resolution, and only use it for apps where I can reliablably increase the font size (terminals, web apps/pages with good zoom support). I keep VSCode on my high DPI main monitor.
Because most self-hosted Git services like Gogs and Gitea include features not part of git, such as pull requests, releases, and issues, which require some kind of database.
That's an entirely different concern. If people would not shove their repository alongside those features, instead of relaying those through a standalone and documented manner, I would probably also be easily tracking those features inside my editor.
The web is just a way of delivering software to users. I think the person speaking in the video is worrying way too much about putting developers into boxes. At the end of the day, there are many problems in the world that can be solved with software.
> What most web developers spend their time doing is useless busy work that is not actually objectively necessary in order to create the functionality. It's just dealing with a bunch of weird conventions by some other software that they are trying to use that are there because some other other weird conventions by some other software that they are trying to use. If you just strip all that crap out, you can be tremendously more efficient.
Not only is this a very arrogant sentiment, but his reduction of all web development down to manipulating "weird conventions" doesn't fit with my experience. I don't sit around all day messing around with Webpack configurations or leaning new frameworks. I deliver software that addresses business needs, that happens to be accessed via a web browser.
He also says that jobs with the title "frontend", "backend" and "fullstack" for the web are not safe jobs. Many game developers, operating system designers, and large desktop applications will also have "frontend" and "backend" separations of responsibility as well, because they often involve different skill sets or knowledge.
Large endowments are not always a straight forward metric to use for determining how well off financially an institution is. Lots of contributions to endowments come with strings attached on how the money can be spent. Wouldn't be surprised to hear about a large number of new costs associated with COVID that wouldn't be covered by a lot of an endowment.
It's abundantly clear to me that Apple is not interested in improving the desktop experience. They simply want to show some shiny new features, and to continue to reduce the dimensions and weight of their laptops (even at the cost of usability). At this point I am hoping for a new unix-based alternative to windows with the same level of stability and usability as macOS. Long gone are the days where I would expect Apple to do what so many of us want with the operating system.
Very nice, that is one of the most annoying things about Jekyll. I know i'm in the minority of users here who is on Windows, but setting up a Ruby in environment is a pain. Nice work, the site is also well designed.
I just started building a blog with Gatsby, after a lot of research it was exactly what I was looking for. As the author of Gatsby, what would you say the major differences are between Phenomic and Gatsby?
- Good support for HTTP 1.1
- Provides typesafe contracts for queries and mutations
- Strong support for most common UI clients (JS/React Native/SwiftUI)
- Backend can be written in a language that isn't JavaScript/TypeScript
- Large developer community
Closest thing I've found is defining your schema using OpenAPI spec, and using tools to generate code from that source for the client and server, but this is a much worse DX than the process of defining GraphQL schemas.