You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! Thanks for writing the prolog book. Here's a sugggestion: a turn-key TLS solution/explanation that works out of the box would help adoption. Most web devs have little interest in the finer details of TLS cert management. A simple secure-by-default server.pl would greatly ease learning prolog. Take a look at this as an example of better UX for developers.
The text was updated successfully, but these errors were encountered:
E.g. in the first section of the explanation, just put the steps that a user need to convert a http app to https. No variants, no branching or "choices" whatsoever, all the explanation can come later. Secure by default is important and to do so it has to be easy to use.
Hi! Thanks for writing the prolog book. Here's a sugggestion: a turn-key TLS solution/explanation that works out of the box would help adoption. Most web devs have little interest in the finer details of TLS cert management. A simple secure-by-default
server.pl
would greatly ease learning prolog. Take a look at this as an example of better UX for developers.The text was updated successfully, but these errors were encountered: