11–20 of 28 posts
Here's a list of softwares that I'd like to see explained in detail: #1 SQLITE #2 ProseMirror #3 V8 #4 WebKit #5 Kubernetes
Here's a list of softwares that I'd like to see explained in detail: #1 SQLITE #2 ProseMirror #3 V8 #4 WebKit #5 Kubernetes
To the authors: Please drop TLS in front of your site. It's near trivial and free. --- I wonder how to take this? Is it good to use these as a recommended approach? I would bet that there could be good examples and bad? Is any of these the leader in terms of approach used for their domain? (Graph databases for example). Could it be that these are `just interesting` but not authoritative?
Some people prefer to allow http as well, so as to not shut out ancient browsers that can't upgrade to modern security standards. I think that's unsafe, but I can understand the argument, our throwaway culture / planned obsolescence is a threat to life on this planet, and supporting antique hardware is one way to fight back.
To the authors: Please drop TLS in front of your site. It's near trivial and free. --- I wonder how to take this? Is it good to use these as a recommended approach? I would bet that there could be good examples and bad? Is any of these the leader in terms of approach used for their domain? (Graph databases for example). Could it be that these are `just interesting` but not authoritative?
> To the authors: Please drop TLS in front of your site. It's near trivial and free. Curious why you think it is needed in this case.
There are plenty of reasons to use HTTPS [0] relating to privacy, security, UI, and browser features, and there are virtually no good reasons not to. There are just 2 real exceptions I know of, neither of which apply here:
1. Using unprotected HTTP enables caching. In the context of something like an apt repo, or Steam, this could be a compelling advantage. (apt provides its own checksum-based security, and doesn't really aim for privacy.)
2. Very old smartphones might not support modern TLS. In some parts of the world this can be a real concern. Even here, HTTPS should be offered, just not required.
To the authors: Please drop TLS in front of your site. It's near trivial and free. --- I wonder how to take this? Is it good to use these as a recommended approach? I would bet that there could be good examples and bad? Is any of these the leader in terms of approach used for their domain? (Graph databases for example). Could it be that these are `just interesting` but not authoritative?
> To the authors: Please drop TLS in front of your site. It's near trivial and free. Curious why you think it is needed in this case.
Here's a list of softwares that I'd like to see explained in detail: #1 SQLITE #2 ProseMirror #3 V8 #4 WebKit #5 Kubernetes
Add React and Redux also . Although Redux is a lot simpler
See my "Idiomatic Redux" blog post series [0] for info on how Redux was designed, why it works the way it does, and the implementation details of both the Redux core, React-Redux, and our new Redux Toolkit package.
I also recommend the post "Build Yourself a Redux" [1] as the best "build a mini Redux" post I've seen.
Rodrigo Pombo's "Didact" series [2] does the same process but for React, showing how to build a miniature reconciler that even includes hooks.
I also have links to further articles about React's implementation [3] as well.
Finally, I specifically recommend reading my post "A (Mostly) Complete Guide to React Rendering Behavior [4] and Dan Abramov's extensive article "A Complete Guide to `useEffect`" to better understand how React behaves and how to use it correctly.
[0] https://blog.isquaredsoftware.com/series/idiomatic-redux
[1] https://zapier.com/engineering/how-to-build-redux/
[2] https://github.com/pomber/didact
[3] https://github.com/markerikson/react-redux-links/blob/master...
[4] https://blog.isquaredsoftware.com/2020/05/blogged-answers-a-...
Here's a list of softwares that I'd like to see explained in detail: #1 SQLITE #2 ProseMirror #3 V8 #4 WebKit #5 Kubernetes
There are some components running on top of this to provide networking, DNS, logging, etc, which simply run as containers on all machines.
Of course there are many types of objects, many possible addons for logging/network/..., and the API authentication is quite complex, but the overall concept is quite simple and builds directly on Etcd.
Earlier quoted context omitted.
> To the authors: Please drop TLS in front of your site. It's near trivial and free. Curious why you think it is needed in this case.
This topic crops up occasionally. With very few exceptions, all web content sent over the public Internet should be protected with HTTPS. The question isn't Why? , but Why haven't they bothered yet? There are plenty of reasons to use HTTPS [0] relating to privacy, security, UI, and browser features, and there are virtually no good reasons not to. There are just 2 real exceptions I know of, neither of which apply here…
Here's a list of softwares that I'd like to see explained in detail: #1 SQLITE #2 ProseMirror #3 V8 #4 WebKit #5 Kubernetes
(I was about to say that Sqlite was already covered, but no, I was confused, it was the old BerkeleyDb!)
Earlier quoted context omitted.
This topic crops up occasionally. With very few exceptions, all web content sent over the public Internet should be protected with HTTPS. The question isn't Why? , but Why haven't they bothered yet? There are plenty of reasons to use HTTPS [0] relating to privacy, security, UI, and browser features, and there are virtually no good reasons not to. There are just 2 real exceptions I know of, neither of which apply here…
I know the general case for HTTPS. I am a system administrator. I was asking for this particular case where I for one see no need.