Not surprising in a kleptocracy thogh.
Not surprising in a kleptocracy thogh.
It does that for some decades already. The trick for dual booting was always to install Linux second. :/
Well, as a consolation there is Rottenegg in Germany. Not nearly as catchy though.
Esteemed personages.
In the general public I don’t think it’s pure xenophobia, but in large parts a fear of not being able to communicate. The behavior they expose then is almost indistinguishable from xenophobia and for the receiving person in no way better, though when a foreign looking person is able to communicate, most hesitations will fall away.
I know that this is obviously not applicable to 100% of the population, but so is the other belief. There are obviously also die-hard foreigners hating nationalists, as in every country.
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.
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.
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.
How much power does this thing draw?
They don’t want you to see the “if benchmark_xyz { do less work }” blocks of code.
The one argument that even flies understand:
Switch light on outside of my room. -> Get out!
Which will result in only those remaining which are complicit. This is clearly a negative outcome. 1. For the people resigning, as resigning didn’t advance their cause, but made the situation worse. 2. For society, because it made the institution less trustworthy.