It does that for some decades already. The trick for dual booting was always to install Linux second. :/

You can write selects with many joins, as long they are regular and either add a column or reduce the result set. You have to write the joins explicitly though. Just shoving all of the restrictions into the where clause will definitely confuse everybody.

The trick is to assign someone the responsibility of the upgrade and give them the authority to tell the other developers how their newly added code shall look like. This will get you there eventually.

Seen it work on a >1 million SLOC project.

I’m definitely looking forward to Unpack[…]. This makes kwargs typing manageable for the first time.

The rest is nice too, but no game changers.

Well, you can still have the up-to-date plugin, you just have to pay for it now.

Since working with SQLAlchemy a lot (specifically it’s SQL compiler, not it’s ORM), I don’t want to work with SQL any other way. I want to have the possibility to extract column definitions into named variables, reuse queries as columns in other queries, etc. I don’t want to concatenate SQL strings ever again.

Having a DSL or even a full language which compiles to SQL is clearly the superior way to work with SQL.

I’m wondering if a field with more detailed information would be helpful for the users. Moderators might want to clarify or explain in more detail the function or intention behind a tag. This doesn’t seem to be considered in the RFC.

deleted by creator

Depends on how large your Python projects are. If you have a million lines of Python code, navigating quickly and directed is invaluable.

I used plain vim before for Python projects, but these never grew above 50k lines of code.

I never got so far, but had a system built which some parts of what you described. It was incredibly relaxing to develop with it. Our take as a team was: boring is better, we don’t want to be paged on weekends.

It teaches you to think about data in a different way. Even if you never will use it in your products, the mental facilities you have to build for it will definitely benefit you.

Completely agree. I really love SQL, but I hate it’s syntactic limitations. SQLAlchemy was my band-aid with an after-burner to make it bearable (and maintainable).

Python development without PyCharm (or IntelliJ) and the IdeaVim plugin is unbearable. List usages is a game changer. Don’t care much for anything else.

You could be onto something. On of my first language was “dBase” (early 90s) which, through it’s style, enabled you to build complex user interfaces with data storage very quickly. I only built small things with it at the time, but it influenced my desire for some better solutions than we have to today.

They don’t want you to see the “if benchmark_xyz { do less work }” blocks of code.

Easy. If my editor shows no errors anymore, it will run, instead of crash due to my ignorance of alignment, leaks, etc.

I’m just a lazy developer, so blame me if you want. I just don’t want to learn that stuff if I don’t really really need to. I have to memorize enough already.

Don’t anthropomorphize social networks, they hate that.

Aww, you didn’t normalize.

This is just perfect.

Scenario:

1. Sign up for RedHat account
2. Acquire source code
3. distribute source code
4. RedHat cancels your account
5. you still have the binaries (and are allowed to, they’re GPL)
6. you want the source code again… but can’t. Account is closed.

Now you’re in a situation where you’re entitled to receive the source code, but can’t because they won’t let you.

If this will ever go to court, I suspect RedHat will pursue a “corner case” solution. A canceled account will probably have access to the source code from RedHat *up to that very cancel-date" and you’ll not get a new binary (from them). So it should be mostly legal for them to do so.

However, as long as no trademark of RedHat is violated, distributing individual RHEL binaries (not the full images, they contain trademarked assets) should be fine. So you could receive a binary through that route and be entitled to the source code for it, starting the whole process over again.

One could always fork it, though I like the name. I’m a LeGuin fan.