I develop almost exclusively in Python and I can't think of changing anytime soon. I see a lot of well-argumented criticism to the language which makes a lot of sense, and yet I think it's misplaced.

If your code needs C-level performance, write the critical parts in C/C++, this used to be the mantra. I don't like where the new development is going to address what problems that are the direct consequence of fundamental design choices. Then if you write computationally intense code in Python that's your fault. As much as I can't stand JS and all the derivatives, I think it has its own ecosystem niche and reason to be, much like Python.

Cutting out those that want to write an OS in an interpreted language, there is no doubt that Python did a terrific job at addressing the needs of countless programmers or people that needed to quickly write code for doing something (scientists). Ignoring that would be silly. So I think people should reconsider their blind criticism.

Not to disagree entirely with you on the anti-feature claim, but the argument is fairly weak. The highest reaction time of humans is between 200 and 150 milliseconds (with training). At 30 frames per seconds, a crappy standard for today's GPUs performance, each frame is rendered in ~33 milliseconds, meaning you could pack a bit more than 6 frames in your reaction time window (with training). At 144 FPS, the ideal refresh rate for Counterstrike (which a compulsory Google search reports as "Criminally smooth. For hardcore and professional players"), you have 7 ms/frame, which means your GPU could render 25 frames by the time you actually perceived a movement. Is it a cheap trick? Absolutely yes. Are you going to notice any difference? Not likely, unless you're playing against your cat (reaction times: 20/70 ms)

I've diligently read all the comments at the time of me posting this and beside a bunch of reasonably argumented points about the fact that basically in principle the same could be done with properly written C++ code, I couldn't find any good arguments about why not Rust, then. What's the cost of writing the same code in Rust instead of C++? since performance is not an issue, frankly I don't see why not use it for the majority of development currently done in C++. The argument of "just use better programmers" does not hold because even navigated Linux kernel developers seem to make trivial mistakes, why not embracing a language that can prevent the most common source of critical bugs (C/C++ buffer overflows, from a bunch of past ./ posts)? To me it seems mostly a hubris issue that "navigated" programmers seem to suffer from. I can clearly be wrong, but so far I couldn't find an argument convincing me otherwise.

Beware of the incredibly idiotic design of the webcam in the bottom left corner of the screen. People on the other side of your teleconference will see your head peeking behind your ginormous fingers and knuckles. Not enough? The sensor quality is mediocre (to be nice), and the touchpad sucks. Also, some models (mine is 3560, if I'm not mistaken) will overheat the CPU and trigger lots of MCE and dmesg warnings. Other than that, I've been a relatively happy owner of an XPS13 DE for a while and I'm satisfied with the battery life and the overall power.

Apparently, you're one of them

I'm a big fan of unlocked phones myself, and over the years, I've looked at the Lineage project more than once. If you google the official website, you will land on a fancy and modern page with all whistles and bells about the core values and the mission of the organization, and the links to download their software.

I did it again, today, and the outcome is still the same: I I have no idea about how this custom OS looks like, what offers, and what are the limitations (if any).
The About link shows a page with the vocabulary definition of the name of the OS, and a not-so-obvious link to Wikipedia.
I'm sure there are a bunch of smart people out there that are willing and able to send me a link full of screenshots and the features of LineageOS, but the fact that a reasonably tech savvy person can't find any of these from their own website (and not using Google, thank you) is disappointing, to say the least.
I'm thankful for all the volunteers that spend time supporting a large number of phones, etc... but I'm still disappointed.

(Apologies if it might look like I'm trying to turn this place into a venue for having useful conversations)
Isn't that a bit of an overkill? I can think of a number of alternative options:

- running multiple profiles for different activities, i.e., Firefox/mail profile and Firefox/browsing profile

- running different browsers for different activities, i.e., Firefox for the email, Chromium for incognito browsing

- running different browsers/activities as different users, i.e. "sudo -u mail_only firefox www.gmail.com"

They would all have much less overhead, but I'm not sure if I'm missing something obvious here.

To be fair, I found a more detailed changelog that mentions a few more bugs, but it's just lot of papercut fixes: tons of warnings removed, Unicode quircks corrected, UI changes... but nothing about high CPU usage, instability, and other major issues.

It's still possible to see the desktop and all the windows on it every time the system resumes on a laptop, before the KScreenLocker kicks asking for the password... but, hey, now it compiles with "strict" compile flags, and finally exports the install location for DBUS interfaces via CMake.

"Shake it, baby!"

Come on, make users happy and do what a dot-14 version should do.

I'm not even picky, you guys can choose them from any of these lists:

KWin

Plasma Frameworks

PlasmaShell

But what TFA has to say about?

Blurred backgrounds behind desktop context menus are no longer visually corrupted.

It's no longer possible to accidentally drag-and-drop task manager buttons into app windows.

Yeah!.... I guess?
[DISCLAIMER: I am indeed a KDE user]

I usually don't care much about these discussions, but I feel there might be some room for clarification.
I'm not sure if Python is really the future of programming language, but it definitely provided a glimpse of what a possible future might look like. Whether people like it or not, this programming language lowered significantly the access barrier required to start writing useful and powerful code, without sacrificing functionalities.
It's not C/C++, it's not incredibly memory efficient, and performance is significantly lower than compiled languages, but...

There are professional programmers using it for the most obvious thing (prototyping new code) as well as writing complex programs that were not worth the time investment of writing in C++. Although, the big difference is the democratization of programming for people like me that don't have the time and the resources to build serious programming skills. The lower access barrier allowed many people to implement their ideas, make them work, and spread them around... sure, in a high-level, slow, and memory inefficient language, but do we really care? There are many places where the idea is far more important than the implementation like often in the scientific world, notoriously famous for providing crappy code.
Tons of people have benefited from countless programs doing very complex operations, or just simply scratching long standing itches (matrices operations, 3D operations, data sanitization, etc.).

If your Python code is really useful and needs to be made faster, you can hire a programmer to re-write it in C++, but in the meantime it might have reached a significant critical mass of interest/users that make it possible (getting funding, etc...).
Python is likely how an everyday programming language might look when most of the people will write a program at some time in their lives. On the other hand, if Python is the only reason to define yourself as a professional programmer, then it's obviously a problem.

...or on the equivalent, current version of it.

Double the amount of hardware required to run the mill.

Frantically restore the original setup from the backups.

Come up with a new name, like StandPoint.

Deploy a brand new interface with lots and lots of unused space... poor responsiveness... cumbersome workflows... automatic error correction... Clippy integration ("I see you are coding in Python. Do you want to try C#?")...


Time to update the list of pro's of GitLab.

Never owned an Apple device, and yet, I found myself envying anyone with an iThing, right now. Excellent phones like the Nexus 5/6x series (disclaimer: which I own) are going to be dropped by the new OS. Why? Probably, because they lack the newest AI chip to process buzzword at unprecedented speed. In the end, it really sucks to have only two choices: either being owned by the big, flaming Eye of Sauron that all sees, or being locked in the Golden Orchard.

Don't worry, this revolution it's going to be affecting mostly countries other than US, or, best case scenario, be limited to the gazillion of colorful and expensive ads from the providers. I've been in EU visiting my family, and I've helped my sister setting up her new Android phone, which, incidentally, is the very same model as mine. Well, using the 4G downloading large apps from the market was blazing faster than I experience even with my WiFi at home or at work. On top of that, she pays way less than a third of what I do. And Japan is even more advanced than EU.

Actually, I just remembered that when I moved to US the terrible state of mobile and internet speeds in general, and the absurd prices were the greatest disappointments.

When I was a kid I was exposed to BASIC (I owned a ZX81 and a C64) at home and Pascal at school, but what really hooked me was what could I do with them that was mostly entertaining, and just minimally useful. With the Commodore, it was a hacking a couple of games typed from a magazine. With Pascal was generating relatively nice graphics with for-loops.

Programming is a tool, and it should be thought as such: teach them how to tackle a problem with an algorithmic approach, e.g., how we can enumerate all possible combinations of who-seats-next-to-who in the classroom, using some constraints (Joe wants to sit next to Eddy)... whatever.

Teach a lazy kid how to make a computer work for him, and you've created a programmer. [Insert Bill Gates' quote here]

You may want to avoid clearly obsolete-wrong patterns ("GOTO is Evil"), but other than that, any language is good. Eventually, they'll find their language of choice, but they would likely keep the basic set of skills that built back when they learned.

...will be your screen. In a video call you will be able to look at the other party in his/her eyes and it will not appear like you're reading something else.