praveenweb

In my experience, Ghost has been the no-nonsense blog CMS that has been stable and just worked with very little maintenance.

I like that they are now moving towards static site JAMStack approach, driven by APIs rather than the current SSR model. This lets anybody to customise their themes with the language / framework of choice and generating static builds that can be cached for improved loading times.

The advantage of doing this is that it gives you the power of using your favourite language to build this and its a fun project as long as its just dealing with markdown. If you are building static sites with content sourced from a database or APIs then these static site generators removes friction involved in setting those up.

I would recommend pre-building html markup as much as possible for performance boost and hydrate on the client for dynamic content, instead of going the SSR route. Obviously this may not be applicable for all use cases though.

Shameless plug: I just wrote a guide to approach dynamic content on static sites a few days ago.

https://blog.hasura.io/approaches-to-add-dynamic-content-sta...

I use AdGuard Pro in combination with StevenBlack/hosts [0] and a custom DNS. This is used for system wide (not just Safari) ads/tracker blocking. Adding custom filters as and when required.

- [0] https://github.com/StevenBlack/hosts

This is useful for boilerplate code. But keeping it in sync with upstream isn’t possible due to it having a single initial commit and separate history. For that a fork is the only choice. I see how the use cases can pan out for templates. Glad that Github is releasing more features off late :)

Hey all,

We've been working on this for the last few months. We have put together a powerful and concise course that will introduce you to GraphQL and integrating GraphQL into your frontend stack, in the shortest amount of time possible. We will explore the fundamentals of GraphQL and especially the things that make GraphQL suitable for modern applications, like its realtime capabilities!

The course is light on opinions so that once you grok the fundamentals you can go on to choose your favourite libraries, tools and tailor your workflow.

We have tutorials for popular frameworks with more frameworks coming soon! These are completely open source. We'd love for you to try these out and let us know if you have any feedback & suggestions. You can leave them as issues directly on the GitHub repo.

Also, let us know which frameworks/language you'd like to see next :)

Apple is also slowly building a backup supply chain in India to handle such retaliation by China.

Hi HN, We've been working on this for the last few months. We have put together a powerful and concise course that will introduce you to GraphQL and integrating GraphQL into your frontend stack, in the shortest amount of time possible.

We will explore the fundamentals of GraphQL and especially the things that make GraphQL suitable for modern applications, like its realtime capabilities!

The course is light on opinions so that once you grok the fundamentals you can go on to choose your favourite libraries, tools and tailor your workflow. We have tutorials for popular frameworks with more frameworks coming soon!

These are completely open source. We'd love for you to try these out and let us know if you have any feedback & suggestions. You can leave them as issues directly on the GitHub repo. Also, let us know which frameworks/language you'd like to see next :)

Netlify’s offering seems to be a more polished experience for frontend devs. A dashboard to configure stuff like build commands etc is neat. The feature that i personally like is the ability to select any branch of the repo to be deployed by clicking a few buttons. Helps me immensely during dev/staging deployments. IMO, These tiny little features and UX differentiates Netlify from other static site hosting providers or DIY hosting

CPU bit might be relevant for those who care about Privacy. Apple markets the fact that all processing (some ML/AI stuff) is done on device and not on the cloud, hence requiring good processing power. But as you mentioned the battle is skewed towards Camera and Battery usage.

When Jio was launched in 2016, Mukesh Ambani (Managing Director of Reliance Industries, parent company of Jio) quoted saying “Data is the new oil and we don’t need to import it”

Jio comes bundled with value added free services like JioTV, JioCinema, JioMagazine, JioMusic(JioSaavn now) and bunch of other apps.

India is a price sensitive market and hence Jio would keep prices lower for as long as possible to keep other players out. Jio is already posting profits.

They are in it for the long game. The bottomline is that prices may not go up anytime soon.

You can take a look at the examples in the repo. Here's one simple todo app with Auth0 integration. https://github.com/hasura/graphql-engine/tree/master/communi...

But we are coming up with a more detailed tutorial on how to build realtime full stack CRUD apps with Auth integration in the coming week.

> Maybe you could provide some example/tutorial on "stitching your own GraphQL apis with hasura"

We have an example of schema stitching in this repo https://github.com/hasura/graphql-schema-stitching-demo

It stitches a weather API schema and a person schema. Hope it gives an idea.

Check out https://hasura.io - you get git push based deployment on a kubernetes cluster.

I understand that mobile app development can happen only with the respective editors and its quite obvious. For everything else, you seem to use Atom. Any specific reasons?

Of course there is no wrong answer. Just trying to understand what people use in 2018 for development.

I switch between vim and Sublime with vim mode.

How do you compare hosting static websites on Hasura (free SSL out of the box) or Heroku vs AWS S3?

I think cloudflare gives more options as a CDN than cloudfront.

If you like the git push flow of Heroku, i would recommend you to check out Hasura - https://hasura.io - Its a Baas + Paas for containers. Everything about your project is declarative and your apps are dockerized and deployed on to a Kubernetes cluster with free SSL.

If you are not concerned about the size of your production image and if your modules don't compile with alpine builds, you can stick to the same debian base image.

Or you can use alpine for dev if you are not concerned about debugging too much.

I would say it boils down to use cases and priorities.

Restarting the container is manual work. I prefer restarts being automatically taken care by watch tools or the server.

Apart from gunicorn being easy to configure, i just happened to use gunicorn first. I'm sure the same Dockerfile can be applied with uwsgi. Are there any benefits to using uwsgi over gunicorn? Open to exploring.

Instead of writing Dockerfiles, this approach requires me to write a docker-compose.yaml file. How is it more advantageous?

CMD will work in detached mode. i.e - "docker run -d". In an interactive mode i.e - "docker run -ti", you can land up with shell access of the container, where you can run commands / perform other tasks as required. In this case, we are running nodemon.

> But it seems over-applied for basic web apps.

Generally your app will be composed of multiple services (like Java, Node.js, some database etc) and there are benefits to run them as microservices (isolation, easy to develop, easy to scale) and hence Docker makes sense in those use cases. Though the app seems basic and overkill to use Docker, the architecture enforces this and adds the above mentioned benefits.

Depends on the use-case. For development, you would need to install some system dependencies, access to bash for debugging etc and hence the full blown base image. In production, you want the image sizes to be minimal and hence alpine base image. Also reduces the attack vector.

carbon is the latest LTS (Long Term Support) version of Node. Instead of using the latest version, which can have breaking changes and possible drop of support in the future, it is recommended to use LTS version just to ensure using a stable + well supported version. alpine base images are generally used to cut down the image size for production, because they are very minimal and works well for most use-cases. But you would generally use carbon or specific full blown version of node in development, because you can install system dependencies for bundling code.

You can ask Siri for "Latest ICC Cricket Scores" or more specifically like "India vs Australia Cricket Score" for international match updates.

"The problem is CSS has a global scope". CSS can be written in a way that it affects only specific parts of the site/app. "you change one thing and breaks the whole site's layout". There are use-cases when you want changes to reflect across the entire site and CSS can be easily used to achieve it. (Ex: changing color of buttons). Javascript can also break the whole site's layout. It just depends on what code we write.

I think sometime last year, Amazon removed the sales of Apple TV and Chrome cast from their platform. The platform decides what is profitable for them. After all the consumers and the businesses have their choices open on what to use. But i seriously want Apple to be diplomatic in this issue and allow whatever is best for everyone.

I would like to see a detailed explanation from Facebook on the business front for closing Parse. Developers would now be skeptical about using any Proprietary service for their backend.