| product | price | cores | RAM | SSD | Geekbench ST | Geekbench MT | Geekbench version | date of benchmark |
|---|---|---|---|---|---|---|---|---|
| Hetzner CP11 | 3,92€/m | 1 | 2GB | 20GB | 691/710 |
686/712 |
5.x | 2023-05-20 |
| Hetzner CPX11 | 4,75€/m | 2 | 2GB | 40GB | 869/856 |
1631/1626 |
5.x | 2021-10-03 |
| Hetzner CX21 | 5,83€/m | 2 | 4GB | 40GB | 681/663 |
1279/1248 |
5.x | 2022-07-18 |
| Hetzner CPX21 | 8,21€/m | 3 | 4GB | 80GB | [`9 |
Francis Chuang F21
All libraries have subtle rules that you have to follow for them to work well. Often these are implied and undocumented rules that you have to learn as you go. This is an attempt to document the rules of React renders. Ideally a type system could enforce it.
A number of methods in React are assumed to be "pure".
On classes that's the constructor, getDerivedStateFromProps, shouldComponentUpdate and render.
Many of us building single-page apps today use JavaScript module bundling tools that trend towards a monolithic "bundle.js" file including the full app and vendor code for multiple routes. This means if a user lands on any arbitrary route they need to wait for a large bundle of JS to be fetched, parsed and executed before the application is fully rendered and interactive.
This is a little backwards, especially when apps are used under real-world network (3G) and device
This is my response to an email asking about Domain-Driven Design in golang project.
Thank you for getting in touch. Below you will find my thoughts on how golang works with DDD, changing it. This is merely a perception of how things worked out for us in a single project.
That project has a relatively well-known domain. My colleagues on this project are very knowledgeable, thoughtful and invested in quality design. The story spelled out below is a result of countless hours spent discussing and refining the approach.
Conclusions could be very different, if there was a different project, team or a story-teller.