undseg

found this[1] to be a great introductory course. Might want to have dipped into functional concepts beforehand, though.

Fairly sure it was recommended in here in the past and that's how I came to know it, can't give credit because I sadly don't remember.

[1]https://www.seas.upenn.edu/~cis194/spring13/lectures.html

This is always the first thing I look for in the new version announcements for big blogging platforms.

Would be amazing if I didn't need to know a completely separate technology and/or hack together bridges/site "staticizers" in order to have a quite basic functionality (the site be 100% static when no back-end dynamic interaction is needed).

That said, there are third party plugins for WordPress that do this. Don't know about ghost, but my hopes are for first-class support for this.

This is such an under-discussed argument.

Of course a private entity can disregard morality for the good of the public in their decisions (they're after profits), but what happens when that private entity becomes the town square? Or when it has monopoly over something that has become a basic utility for everyone?

At this time I'm starting to cringe at opinions defending these actions with "it's a private entity".

Free speech is not a concept that only exists in your constitution. It's a mistake to bring up the First Amendment in these cases just as much as it is to think that Free Speech only refers to the First Amendment or repercussion from the Govt.

Having the basic right of internet access being treated as a public utility would help greatly with these issues, I agree. It would help with monopolies and issues with regulation.

Of course, I don't see such an opinion being particularly welcomed here.

A chunk of the basic infrastructure of the internet is free just out of sheer luck (good willed inventors and founders).

That completely arbitrary.

There's no reason WhatsApp shouldn't be treated as a "dumb pipe for messaging" just like an ISP is widely regarded as necessary to be treated as such for data in general.

Where's the difference? Both are companies that want to make profits and face competition. If ISPs were a public state service, then that would be where to draw the line.

I can't help you with ASP.NET Core, as I have no experience building and/or deploying it.

What I can chime in with though is: In my days as a web dev I started off and learned the ropes with ASP.NET (MVC was recently coming up), and after moving to django for another project I felt right at home.

It's very impressive how the django project was able to rival a behemot like Microsoft in terms of usability, reasonable defaults and developer convenience, overall design, documentation, upgradability.

The REST stuff (django rest framework) and some aspects of managing models were actually quite ahead of ASP.NET at the time for getting you up to speed with things.

Of course the tech stack around them is completely different and something you'll want to think about, but in terms of features and how things are laid out you don't need to worry, django has you covered.

I'd imagine those insurance files being insurance against murder, torture, life imprisonment et al more so than being kicked out of political asylum, but I'm just speculating.

Can you elaborate on that? Provide sources etc. Genuinely curious

Back in the days Microsoft would have amazing customer support. And I'm talking about "API customers", many times I've seen them go out of their way to fix third party programs not working correctly by adapting their platform, it was a very efficient process. I guess that doesn't work as well at their current scale, or they care less because they're not building up market share.

While everything you said is true, imagine your final goal was to learn Javascript: going through Python wouldn't help significantly. I feel that was the point of parent. Certainly, learning your first language (or first language in a certain paradigm) is a whole different matter than picking up a bunch of other similar-looking ones.

Remember that github is not just git hosting. While I cannot envision a future in which they'd actively prevent you from export/crawl out your own data, migrating your workflow is not as easy as changing your remote.

I've hated that behavior for years, and am appalled to learn this it still works that way.

That's true, and I want to add that usually it's the company's fault for not guiding the project into the hands of the community (be it intentionally or because of incompetence). Rust is a great example of a "company's project" that reached (or is reaching) a nice spot in autonomy.