Walkman

Steve Jobs might have been an even bigger asshole.

Point 11. is called " return early".

me too! :D

The article is about that it is FORCING you to do it. Erlang is designed to restart processes, because they also know it's very hard to keep state but don't leak memory or be in a good state for a long time. Every application server has an option to "restart after N number of requests" for the exact same reason.

They are actually know what they are doing. I think they have a full time security guys and also have a bug bounty as others have mentioned.

I did a couple of upgrades of Nextcloud; one major and some minor, and the upgrade process is unbelievably fast, painless and stable. Never had any problem.

I don't know about any paid only plugin. Nextcloud is forked from ownCloud because the original founders of ownCloud didn't like the direction where ownCloud was heading (paid only features for enterprises) and they wanted to open source every part of it. They are unrealistically good people, making an unlikely good product :) See their reasoning of forking here:

- https://www.youtube.com/watch?v=UTKvLSnFL6I

- http://karlitschek.de/2016/06/nextcloud/

- https://news.ycombinator.com/item?id=12919330

Your overall system will be way more complex than a monolith with the same functionality would be.

This is not about generating code instead of writing it at all. It is about making customizations possible.

This is not about "trying to save a couple lines of code" at all. Sometimes you want to gives the customer the ability to customize the app however they want and sometimes this is needed in order to do that. E.g. custom profile fields, building custom forms themselves (like Google Forms), etc.

This is extremely clever! Something like this needs a deep understanding of Django and Python internals. The bullet points are written like they put it together under 10 minutes or so :D I love it!

I always wondered how far human laziness can go? This is an absolutely terrible library. Every command line is a HUMAN INTERFACE for interactions with your program, should not exposed random methods for command line usage...

Also, developing a Python library and not keeping the most basic standard (PEP8)? You should not be allowed near Python. I really have no better words for this, just fucking lazy. I hate lazy developers, because you are the reason most software is shit.

GitHub hosts git repositories, GitLab does that AND EVERYTHING ELSE TOO.

It has nothing to do with Go the language itself. There are tools for that and lazy authors have the same problem with other languages also.

Can you tell at least one specific example where they broke the standard library?

You are correct! :D

Isolating for security is a totally different topic. We talked about pinning the application to a specific version, and I suggested that it can be done with various tools, isolating from a bigger operating system where packages would automatically updated and Nextcloud would break after a while. It has nothing to do with security.

Of course you can do security for isolation on top of it any time, and sure, you won't get security updates after a while which would be nice, but there are tools to secure an outdated app in other ways either.

Why would you run the client in a container? I was talking about the server.

It can run in a container, a virtual machine, hosted on a cloud instance or whatever. Nowadays, you have infinite choices for isolation. One of my colleague runs it in a DigitalOcean droplet and nothing else.

Nextcloud is the successor of ownCloud.

This is exactly why I stopped using Dropbox and moved everything I have to my own https://nextcloud.com instance. It's very easy to install and upgrade, it is stable, have way more features than Dropbox and you have total control over your own data. Overall a superior experience. If they would do something I don't like, I would just never upgrade anymore and be done with it or just copy the files out of the /data/Nextcloud folder and move to another one open solution.

Well put!

This is quite nice, high quality documentation, the template is eye-catchy, very nicely structured, well done!

You can make modern CLI tools today with great discoverability, there are a couple of great frameworks that makes this possible like Click[1] for Python or cobra[2] for Go.

[1] http://click.pocoo.org/6/

[2] https://github.com/spf13/cobra

Yea sure, these are the two choices ONLY...

For example when a company acquires another, your workflows will be broken, you are forced to move and learn the new tool and you have no control over YOUR OWN data at all.

Usually if you want to use a library like this, you can't really do anything else, but implement the smallest common subset of the services combined.

In the minute you implement something provider specific, you just lost the whole point of this library and you did not needed it in the first place.

The most basic things are hard to grasp also. I had a really hard time understanding what is the difference between unicode, str, bytes and how to encode what when I started with it 5 years ago: https://stackoverflow.com/questions/14839028/how-are-these-s...

Nowadays, teachers have to start with generators and yield even for beginners, because most of the things are generators in Python3, which is not a trivial concept to understand when you have no programming background.

Very good question! Python have a couple of tools to handle concurrency and parallelism, but it's a mess.

For I/O bound programs, you can use threading (in stdlib). For CPU bound, you can use multiprocessing (also in stdlib). But these have huge overhead, (e.g starting a Python thread costs 32kb memory minimum.) and there are multiple solutions in the stdlib like ThreadPoolExecutor and ProcessPoolExecutor in concurrent.futures beside the threading and multiprocessing modules...

If you want to write async code, there is tornado with callbacks, tornado with the new async stuff, asyncio (tulip for Python2), the new async/await from 3.5 which is very immature. The async part of the ecosystem is like a totally separate whole new world, you can't really mix and match or pick parts from the other, however, there are brave folks like Andrew Godwin how tries to make Django async with not moderate success.

For web frameworks, there are a ton of servers which might fit you, but they are mostly very complex to set up or reason about like greenlets, pre-forked web servers and stuff.

I have 5 years experience with Python, using it every day and once I tried to write a custom SSH server and it took 1-2 weeks to grasp Tornado fully, then I tried the same with Go and WITH LEARNING THE LANGUAGE itself, it took me about 2 weekends and my server was up and running!

TL;DR: You can write concurrent code with Python but it's a mess and you will probably have a hard time.

It's NOT simple at all, see my comment above: https://news.ycombinator.com/item?id=17584388