I have setup a rustdesk server with docker, it was surprisingly easy to get started. It was for a friend who is managing the IT services of a small factory, the completely switched from TeamViewer and they are satisfied. More importantly their users, who are worse than your average windows user, found the transition relatively painless.
I have been using for the past month. I am not a power user, I mostly use it when I need to access libgen. Previously, I was using nordvpn. I feel proton is faster both when connecting to a server but also the connection is faster/more reliable. For example, if I forget to turn it off, I can watch a yt video without any issues.
I can provide some context from Greece.
First of all, the unemployment rate is high. The official figure is currently at 12.5% but has been steadily decreasing from its peak of 27.7% in 2013. The real numbers are probably higher since people that haven’t been employed within the last few years are not accounted.
As a result, labour rights are non-existent, overtime is rarely paid, wages have been stagnant since 2008, it is really common to work in unsafe conditions, and worker abuse occurs so often noone bats an eye.
While we do have unions more often than not they are powerless. For example, last year we had a major train accident (57 people died), the goverment blamed the train workers, their response was pretty much “our strikes for the safety issues that lead to the accident were deemed illegal, while our attempts to raise the issues were dismissed by the ministry of transportation”.
We have had major nationwide protests with more than a million of people taking to the streets, but noone feels like that ever lead to anywhere.
IMO one of the greatest problems is the lack of information. Mainstream media are corrupt, and independent media are sabotaged or persecuted by the government. People do not know their rights, we have been trying to survive for so long that we cannot imagine a better future, and that allows employers to freely profit from laborers.
One interesting development is that lately more collectives are popping here and there, from coffee shops to softwafe development houses, more and more people are fed up and try to take matters on their own hands (even if in absolute numbers they are still very few).
I am definitely guilt for that, but I find this approach really productive. We use small bug fixes as an opportunity to improve the code quality. Bigger PRs often introduce new features and take a lot of time, you know the other person is tired and needs to move on, so we focus on the bigger picture, requesting changes only if there is a bug or an important structural issue.
WOW! https://github.com/modularml/mojo
Been looking for something like this, thanks a lot!!!
Edit: Had a quick look at the docs. Mojo’s initial build was published Sep2022, it’s fairly young, but seems to be getting a lot of attention (on GitHub they have the same number of stars as mypy 🤯).
For anyone interested, their roadmap is an interested read. They seem to be taking a step-by-step approach, trying first to nail down core features first before moving to stuff like python inter-op and syntactic sugar.
Mojo still doesn’t support classes, the primary thing Python programmers use pervasively! This isn’t because we hate dynamism - quite the opposite. It is because we need to get the core language semantics nailed down before adding them. We expect to provide full support for all the dynamic features in Python classes, and want the right framework to hang that off of.
The “why mojo” section give a lot of background too. They are implementing an ML-IR compiler, which is really promising for optimization (think all the goodies we could use from LLVM).
Hey, I am sure I have it, I rephrased the comment, thanks for bringing that up.
Myth: You are lazy.
Truth: It’s highly probable you are neurodivergent.
While, accurate numbers are not available, I have seen people estimating that 20% of people working in FAANG are neurodivergent. If coding comes naturally to you but the laundry is your mortal enemy, it’s worth learning about ADHD/ASD and other common disorders. Being a coder can be a sign, the immediate feedback helps a bunch of us, or as Russel Barkely says “when you solve a problem on a paper, NOTHING HAPPENS”.
Edit: Rephrase.
Totally agree, I had the fortune to read Domain Driven Deign by Eric Evans early in my career. While, the book may be outdated, it helped me understand that my job is to turn the unknown or ambiguous into code. I find that much more exciting than being a coder.
For anyone interested, Wikipedia provides some arguments against meritocracy.
https://en.wikipedia.org/wiki/Myth_of_meritocracy
Meritocracy is argued to be a myth because, despite being promoted as an open and accessible method of achieving upward class mobility under neoliberal or free market capitalism, wealth disparity and limited class mobility remain widespread, regardless of individual work ethic.
I totally agree.
IMO the notion of merit is an illusion. It hides the assumption that people can be ranked and compared, but do we truly want to live in such a society?
Also, is that even feasible?
It’s impossible to objectively compare humans of similar “skill level”. For example, think of Plato and Aristotle, they have been dead for thousands of years and their work has been studied but millions of not billions of people, yet people still argue who was the best philosopher of the two. How can we have a meritocracy if we cannot evaluate merit? You may be able to distinguish experts from beginners for a certain skill, but, when considering roles of influence/power, there are multiple skills and attributes to be considered, and the same principle applies.
It’s easier to cheat a merit metric than to evaluate it. Any algorithm that makes a decision based on merit will need to either evaluate or compare it. Both are going to depend on the presence of absence of features that once known to a cheater they will be able to fake them. That makes evaluation and cheating a competing game, where the evaluator and the cheater contiously adapt to one another, with the cheater being much able to adapt much faster.
Any meritocracy will have to be open about it’s evaluation process. If it’s not participants with merit cannot know how to demonstrate it and the process is prune to corruption.
Personally, I believe making decisions based on trust is much better. It’s hard to build trust and it cannot be cheated. Of course, cheater may try to influence decision makers with bribes or blackmail. But, once this is found trust is destroyed and they get rejected.
this is a method, and always was a method, I just wanted it to look like an attribute for aesthetic reasons
I think “aesthetic reasons” is an oversimplification. There are certain assumptions a developer makes when reading some code that uses properties. While these assumptions are not clearly defined and may differ per developer, I think there is a common core.
(1) There are no side-effects. The object is not mutated (or any other object), no IO takes place.
(2) The time and space complexity is O(1).
(3) The result is consistent. Consequent calls to the property should return the same value unless there is a mutation between them.
(tried to delete this comment but somehow didn’t work, I re-read the article and have a different outlook, sorry for the low effort comment)
Start a religion, I guess?
That got me good, thanks for the laugh!
To be fair, I’ve seen some Linux desktop configs that were pretty fucked.
That’s the reason I named it the “rule 34 of linux desktop configs”. In the past 2 years, I have observed a friend’s journey to a fully automated setup. It started with a bash script, which was then converted to an ansible playbook, then a python script, and now a ublue config.
The depths some people will go to fuck (figuratively) with their machines is inspiring!
Maybe, you get to choose the point. What were the moments that made it all worth it?
I am interested to see what 2024 has in store for the Linux desktop.
Immutable distros seem to be the new cool thing, and for once I buy it, they greatly increase stability and reproducibility. It’s about time we see the rule 34 of Linux desktop configuration, if you can think of it there is already a GitHub repository with a configuration for it.
Also, gaming has greatly improved! If a few years ago you said to me I could buy a PS5 controller to play games on my Linux machine, I would lose my mind. Well, the order is arriving on Thursday!
Some governments are making honest efforts to go full open source, investing in the libre office and other tooling they deem necessary.
Last but not least, nowadays most apps are browser based, they are cross platform by default.
The title is pretty self explanatory. Yes, I want to know if it’s AI generated because I don’t trust it.
I agree with the conclusion that it’s important to disclose how the AI was used. AI can be great to reduce the time needed for boilerplate work, so the authors can focus on what’s important like reviewing and verifying the accuracy of the information.
Just do it, whenever you fix a bug, add a test case for it, the cost is not going to be noticeable. You may choose to not upload the test suite right away, but wait until someone notices and asks you about it.
rape survivors are going to have a hard time…
I wasn’t able to find a definitive answer, but after skimming Wikipedia I think a reasonable range would be at least 3 but probably less than 17.
https://en.m.wikipedia.org/wiki/Bird_intelligence
Anecdotal evidence from the 1960s has suggested that crows can count up to 3. It has been shown that parrots can count up to 17.
Hi, I am a building a platform with the goal of supporting apps like this, and I would be interested to develop a plugin for your use-case as an experiment (no fee).
I am working alone on this and this is not my first priority, so I cannot make any guarantees about the timeline, or the scope of the plugin. But, if you are interested we can have a chat on matrix.
The project is not open source yet, but I am planning on doing so once (a) I figure out how to properly apply licensing, and (b) remove any potentially critical information (credentials) from the repository.