Saphyel

I'd recommend for your use case Wordpress (or static site generator like MkDocs).

You can use the one hosted in wordpress and change the domain, so you don't have to worry about hackers or anything. This one is a plug a play, so unless you want to do a custom template/plugin you don't need to learn to code.

* Django is like a wordpress but less popular and less SEO friendly (or less popular for them).

* Flask will require you to learn a lot of html, python, etc.. it will consume you a lot of time to get to the same point to the other 2. Flask can get better results than the previous two but for your use case I don't think it really matters.

For a blog I prefer static site generators to be honest. Fast, cheap, secure and better for the environment.

Django and Wordpress are still valid use case for a blog.

FastAPI or LiteStar with python

Symfony with PHP

Ruby became popular in the web dev space only, because of the frontend stuff and RoR. When node appeared Ruby became almost deprecated.

Python is not great at anything really, Numpy is good because uses C code, PIP is crap, the stdlib has 0 consistancy, types are comments, you have to learn venv, etc... But Python is everywhere, it is in the web dev, devops, data. And now is even in the browser, Excel, rpi, etc... so learning python means you can do anything anywhere.

now do it in Rust!

youtube-dlc is not maintained.

youtube-dl is not maintained but not very active because is stable.

yt-dlp uses youtube-dl as a core, so if something breaks still needs to go to the youtube-dl and fix it.

I was wondering how to organise a project, it is only to show minimal code to try things...

* So I was thinking to create branches from 0 to do some work on it.

* Other approach I was thiking is everything in master/main but different folders.

They are meant to be small scripts or structures so I don't see a big reason for having different repositories

If you feel like Google is becoming hard to trust, let me introduce you Apple.

If someone ask which company is more evil between the Wagner Group or Apple, I'd choose Apple without thinking.

I use Firefox on my desktop PC, FF on my linux laptop and FF on my android phone. Works like a charm but pople like to give their data to Google so...

your problem is not FF, it's the iphone, replace your phone and you'll have the browser you want with the extensions you want. Don't blame the innocents.

This is bad news for EU and the world but I guess congrats for meta and google.

How do you think Apple got the 3 trillion??

Spoiler: it's not because privacy or moral that they sell on their marketing. it's because of the lack of those.

I think I'm in the other side of your problem? I found easier to read Rust code than untyped Python.

My big issue with python (and others like plain JS) is they don't type things and it's easy to forget what is what

Also Rust program are usually small, in the other hand in Python I see objects that extends from 6 objects and they can be as big as 1k lines with data inside

If you really have ADHD after 10mins reading untyped python how can you remember if you are passing a dict or an object? or what it was 200 lines above of the same object ? or what it has the 6 other objects that you are extending from?

My recommendations are:

* Framework (easy to upgrade)

* slimbook (great customer care and support and the laptop are nice)

* Dell XPS

Depends on the project. I have a website that is a made of MD files (I'm using a static site generator) and it's fast and cheap to mantain (free).

For complex things like if you need DB or something else depends on your knowledge.. I'd go for Rust for the API and Bulma.io for the Frontend.

For JS only next.js and Tailwind looks like a good bet but no clue.

Probably companies have actions with Apple so they buy and promote their sh#t.

In all the companies I had been so far I always requested a Linux and they came back with a lot of bullsh#t

Slimbook

Docker, Rust, RISC-V.

None of them are new but still trendy

I think Digital currencies and Rust.

More chinise apps will conquer the market like tiktok is doing

12 factor app and SOLID.

When you have to review code you notice sometimes people that dislike OOP are doing a lot of messy code. Procedural code or procedural code hide in a object is not OOP and it's horrible to review!

slimbook (with Ubuntu 22.10)

Works like a charm.

At work I'm forced to use a MBP and I hate it, battery last 1h is always doing noises is painfully slow, nothing works well with M1, updates requires 1h lost on a black screen. And sometimes release broken things...

A lot of people in this thread already mention the befenits so the big question would be why the hate? I kind of understand people that doesn't want to learn new things their against it... but everyone else? Do you dislike to make your life easier?

Team Firefox here. It's great for devs, privacy and it's quite fast.

At work I'm force to use Chrome

My god's name is my username

I had been trying to push this PEP ( https://peps.python.org/pep-0582/ ) which requires a very minimal work and it will help a lot of people and it seems stuck

So I'm not really surprised PIP is pretty much abandoned/dead. No one wants to introduce changes or improve it, it is easy to think: it works (for me), so why change anything?

I use slimbook they are very nice

In most of the events only sponsor are allow to do spam or say they are recruiting. Normal attendes are not allow to do that and they will be ban for the next events.

Half of the apps I need to work with doesn't work or require to use an older version so not great.

My personal laptop is Dell XPS13 Developer ed. It's nearly a year old and works like a charm I can install anything I want, I can watch whatever. Battery wise last a lot.. 5-8h average depending on what I'm doing.

At work I'm force to use a MacBook, a lot of dev tools don't work very well or doesn't work, every dev has different weird issues, every other day we have a different thing that doesn't work some of us had to request to replace the MBP for a different one because it was very slow and the battery only last 2h if you are lucky.

I think depends on the context.

* If you are doing a library you can safely let the Error do the thing.

* If you are building a web/API catch all the errors, log them and send a nice generic error to the client.

* If you are doing a CLI tool I prefer to do like the library but if it's for a final client probably I'd try to do it like with the web/API.