Our team is currently migrating our whole production system from Linode and GCP to Digital Ocean. Your comment is raising warnings, I'd like to hear more from DO itself.
I'm in the process of moving a project from Django to Node, these are some of the reasons: 1) Typescript everywhere: we are developing several frontends using Typescript, mostly with Angular and some Nativescript. Too many times I terminated a Python backend line with ";", mixed "true" and "True" or tried to solve a problem with a stream of (reactive) functions; 2) Django is sta(b)le: major changes, like Django Channels for websockets support, tend to have a difficult time in replacing the status quo and being first class citizens. This has a chain effect on the ecosystem which usually rely on the stable core. You may see this as feature because of the stability or as a limitation. If you, like me, may need websockets or GraphQL subscriptions, you will probably see the limitation first. Another issue related to stagnation is some degree of features overlap: if you are doing REST with Django you are probably using the Django REST framework, a third party framework built on top of Django. If you are using the DRF you will probably notice some similarities between forms and serializers and, as a matter of fact, serializers can replace forms and it is a good idea to do so, to avoid repetition. There are other similar cases, this is just an example; 3) The Django automatic admin is a trap: at the beginning it is a dream come true. You can do those boring CRUD parts literally in seconds, right? Then you start to push business logic into it. You do the first compromises: "ok, adding this single feature to the admin may require a little bit more time than what it would have taken with a stand alone dashboard, but the admin saved me tons of time so who cares?". Then you do it again. And again. And you will even change the way you reason about models because they will impact the UI the admin will generate. Very soon you will have a nightmarish mutation which will fight every new line of code. Of course I'm not saying that a feature should be avoided or considered bad because it can be used in a wrong way. I'm saying that you must know the tool and its limits to avoid the side effects, and often the ability to better see the bad parts come with experience; 4) performance: this is a very complex topic and depends on many different factors. For starters you may not need better performance at all, maybe your application can handle your workload without missing a beat because often web applications are IO bound anyway. But you must know that Django use a blocking IO design and this has some consequences regarding the number of concurrent clients served, the process model, memory usage, etc...
Unity is reworking the whole network stack and they did significant investments in this area. So at this point implementing multiplayer using UNET or external libraries is possible and tricky but it is not really a good or future proof idea.
I would really like to see some more recent tests as Unity before the 2018.x releases had a "ux/easy of use/developer first" approach but they did significant improvements on rendering quality and efficiency on the 2018.x versions.
I'm exploring Nest [0] for my next project. It is a "glue framework" on top of Typescript and many Node libraries, with an Angular like style.
Every Node library used has a framework module which provides the integration with the framework [1] so it appears to be both flexible and easy to use.
I am just starting to explore Nest and I'm liking it, my previous experience on the backend was on Django for many years and Nest seems like a breath of fresh decoupled air, coming from this heavy monolithic experience.
> DigitalOcean is also working on a managed kubernetes service, which should be less expensive than AWS,GCP,etc
What makes you say this? A 4 GB RAM VPS on DigitalOcean seems to have a very similar price to the corresponding GCP VPS. The load balancer offerings show similar prices too.
I share most of your toughts, they really should put some real effort in UX. Example: domains informations are linked to user accounts, if you want to edit registrant, administrative or technical contacts you are required to create full OVH user profiles.
We evalued PHP for a GraphQL/REST backend and we found some really good points: the design of Symfony, the ACL system, the huge productivity gain of API Platform (https://api-platform.com/). In the end we discarded the whole stack anyway because of the heavy use of docblocks annotations which made our test code hard to read and hard to debug.
Salvini will not become PM in Italy. His center-right coalition was held together by the requirements of our electoral law and is already starting to fall apart. Di Maio will most likely become the PM of a very weak coalition and while his party had strong anti-EU claims they pretty much retracted every single one of them as soon as the polls started to show a strong chance of winning the election.
I am a paying customer for Netflix and Primevideo and I just had to pirate the Altered Carbon tv series because I play it on a ultrawidescreen monitor (21:9, 3440x1440) and the Netflix web player is putting black bars all around the videos (horizontal and vertical black bars). This is because the video is supposed to be played on 16:9 with horizontal black bars only.
With the pirated version I can just tell MPV to apply an autocrop script and use much more space on my monitor.
I use a dark theme on my Gnome desktop and in Firefox default form input elements follow the theme settings. The textarea I'm typing in here on HN is barely readable with this colors.
Nintendo customer support in Europe is known to be quite bad. I am a day one customer for the Switch, the controller has a defective antenna (it is a well known hardware bug) but sending it back would mean to lose a lot of time with the italian customer support and in the end have all my system data wiped out. I'll just wait for them to enable cloud savegames, buy a second Switch and sell back my current one to a retailer like Gamestop.
I agree with you and I think Google is still underestimating the amount of required resources because the framework is still not really "done", a couple examples: universal (SSR) just hit a stable release on angular-cli so it needs time to be widespread and supported in the ecosystem. The are core components like the i18n waiting for a major refactor because they lack basic features: https://github.com/angular/angular/issues/11405
This project seems really interesting, I guess it could pretty much replace SPAs (and related javascript fatigue) in a lot of use cases. Am I missing some significant limitation other than moving some computation back to the servers?
I don't like the debugging workflow described in the linked article "Debugging techniques in Elixir", it reminds me of DDD: a separate tool not integrated with my main development environment and requiring extra manual steps. I tested both the Jetbrains plugin and the vscode extension, both failed (unsupported versions, bugs, etc...).
To elixir users: what do you think about the state of debugging tools? What is your workflow?
Can anyone compare this to other backend frameworks like Django and Rails?
Are non-Windows operating systems well supported as development platforms? I did some quick searches and the standard Visual Studio popped out a lot inside documentation, doesn't seem like a good sign.
How would you compare it to Elixir and Phoenix?