+1 for this. This is kinda the same issue with encoding, just UTF-8 everything and move on.

Great sum up, yes, the major issue with VS Code is the licensing issues that Microsoft caused there.

Gluetun, is overkill if you already have a working setup. Your system is able to handle this in a much simple way with built in tools.

You can use systemd to restrict some daemon to your your VPN IP. For instance here’s an example of doing that with transmission: override of the default unit by using the following command:

systemctl edit transmission-daemon.service

Then type what you need to override:

[Service]
IPAddressDeny=any
IPAddressAllow=10.0.0.1 # --> your VPN IP here

Another option, might be to restrict it to a single network interface:

[Service]
RestrictNetworkInterfaces=wg0 # --> your VPN interface

Save the file and run systemctl daemon-reload followed by systemctl restart transmission-daemon.service and it should be applied.

This is a simple and effective solution that doesn’t require more stuff.

• https://www.ctrl.blog/entry/systemd-application-firewall.html
• https://www.freedesktop.org/software/systemd/man/latest/systemd.resource-control.html#Network Accounting and Control
• https://www.freedesktop.org/software/systemd/man/latest/systemd.resource-control.html#RestrictNetworkInterfaces

Just… lol.

I believe what you’re suggesting is more around the lines of IPFS and I2P, but for large media files webtorrents could be a great solution.

Capable developers touch whatever language is required to get a job done.

There isn’t much of a difference between writing a theme for Guthemberg and the classic editor. In fact your current theme should work just fine in Guthemberg as it just adds the extra html for the built in blocks to your posts / pages. You aren’t required to create a block based theme and split everything into blocks, that’s kind of a myth around Guthemberg.

That or you develop your theme with the features you need baked in. This is the irony of the Hugo people, they’re capable developers that can make themes but they can’t just create a simples Wordpress theme from the ground?

Yeah, everyone with a decent amount of content will just pick Wordpress and move on. It works, it’s reliable, it’s well supported and will keep running for decades at least.

Finally someone going for the right approch with AI.

Yes, this industry is pretty much a race to the bottom (when it comes to wages) by adding methodologies and micromanagement at every corner to make people more “productive”. It’s just sad to see that most people don’t realize that they’re in the race to the bottom just because IT is still paying more than average and/or doesn’t require as many certificates as other fields to get into. The downside of the lack of professionalization is that people abuse developers everyday and the benefits like having more freedom to negotiate your higher than average salary are quickly vanishing in the fact of ever more complex software and big consulting companies taking over internal development teams and departments companies used to have.

To make things worse cloud / SaaS providers keep profiting from this mess by reconfiguring the entire development industry in a way that favors the sell of their services and takes away all the required knowledge developers used to have when it came to development and deploying solutions. Companies such as Microsoft and GitHub are all about re-creating and reconfiguring the way people develop software so everyone will be hostage of their platforms. We now have a generation of developers that doesn’t understand the basic of their tech stack, about networking, about DNS, about how to deploy a simple thing into a server that doesn’t use some orchestration with service x or isn’t a 3rd party cloud xyz deploy-from-github service.

Consulting companies who make software for others also benefit from this “reconfiguration” as they are able to hire more junior or less competent developers and transfer the complexities to those cloud services. The “experts” who work in consulting companies are part of this as they usually don’t even know how to do things without the property solutions. Let me give you an example, once I had to work with E&Y, one of those big consulting companies, and I realized some awkward things while having conversations with both low level employees and partners / middle management, they weren’t aware that there are alternatives most of the time. A manager of a digital transformation and cloud solutions team that started his career E&Y, wasn’t aware that there was open-source alternatives to Google Workplace and Microsoft 365 for e-mail. I probed a TON around that and the guy, a software engineer with an university degree, didn’t even know that was Postfix was and the history of email.

All those new technologies keep pushing this “develop and deploy” quickly and commoditizing development - it’s a negative feedback loop that never ends. Yes I say commoditizing development because if you look at it those techs only make it easier for the entry level developer and companies instead of hiring developers for their knowledge and ability to develop they’re just hiring “cheap monkeys” that are able to configure those technologies and cloud platforms to deliver something. At the end of the they the business of those cloud companies is transforming developer knowledge into products/services that companies can buy with a click.

Here’s my experience TL:DR; take: requires learning how to manage people, delegate. You’ll spend 80% of your time in pointless meetings and writing docs. Moving between jobs will be harder because companies are most likely to promote their seniors to TL instead of hiring and also because salary expectations are higher.

The article misses one thing, typically companies that use XGH can’t keep most developers around for more than two years. You end up with teams that are constantly changing members and there are usually 2 or 3 very old guys that stick around and doesn’t give a shit either way.

When you get to a job and you find that all people are new and there are new teams being created for everything and whatnot that’s a very strong signal that XGH is employed on that bussiness.

That’s not a solution, it is the exact opposite - adding even more compilation and complexity to things. The ideia is to move away from compiled stuff as much as possible. WebAssembly makes sense for very complex and low level stuff that you can’t run interpreted with reasonable performance.

Less compilation usually equals code more maintainable in the long run. Think about it: if you don’t need a compiler and the hundreds of dependencies that will eventually break things will last way more time. Websites from the 90’s still work fine on modern browsers and you can update them easily while compiled stuff is game over once you lose the ability to install run said compiler and related dependencies.

Oh I’m not worried, at all.

I believe both are true… and I also develop a LOT in Angular (with TypeScript).

TypeScript is great but the thing is that if you look at the history of TypeScript and JS/ECMAScript you’ll find out that TypeScript sometimes is the testing ground for the future features of ECMAScript - pretty much like what happens with Sass and CSS that how even has nesting and scopes.

The issue with TypeScript/Sass etc. is that it requires a compiler and that’s totally obnoxious and completely defeats the point of having interpreted code on browsers. Depending on the project it might be better to go for TypeScript + Angular/React or other compiled solution or simply something vanilla with jQuery or the Vue runtime (no compilation) and other libraries.

If TypeScript ever goes away the underlaying features that make it great will be implemented in ECMAScript in the same way that we got modules, classes etc. and I really hope it happens. Less compilation usually equals code more maintainable in the long run because you won’t require hundreds of dependencies (that will eventually break) to get it to compile.

Well WinUI is supposed to fix the mess caused by UWP and later on UWP that came from the Windows 8 era… WinUI is decent, at least it isn’t lacking major features like the other two.

.NET MAUI is a very different thing… it’s a cross-platform framework for creating native mobile and desktop apps with C# and XAML. It’s like Qt and obviously when we’re talking about developing apps for Windows, Linux, macOS, Android and iOS with a single frameworks things are bound to be harder.

I don’t disagree with you. I believe I wasn’t very clear about my view.

Swift is great yes, a very decent language and as you said also made to take UIs into consideration and I’ve nothing against it. Now, when people do projects like this it usually comes from a place of need, of not being very happy with the current toolset and/or the belief that something could be made better. This project, besides being a student project, must have some roots into that as well.

I’m happy there are Swift bindings available but it really just proves what I said earlier - people feel the need to experiment with other things because their current Qt toolset might not be enough or provide a great experience.

but there are also options in the Windows world. Everybody isn’t using what Microsoft uses and even Microsoft doesn’t use the same UI toolkit everywhere.

Yes… but we all know there’s a LOT more fragmentation in the Linux space. Qt is probably the most cohesive and ecosystem-like way to develop desktop Linux applications but once again it’s not like what we have on Apple and Microsoft. Both of those companies provide at least one complete development ecosystem that is very tightly integrated with their systems and one can pick up learn and be very productive with it and unfortunately under Linux we things a bit more scattered around.

I never said it was fragmentation, I simply implied that the fact that someone is writing bindings for a language that while open is mostly apple centered says a lot about the lack of a decent development framework.

I’ve said it countless times, and I’ll say it again:

Half of the success of Windows and macOS is the fact that they provide solid and stable APIs and development tools that “make it easy” to develop for those platforms and Linux is very bad at that. The major pieces of Linux are constantly and ever changing requiring large and frequent re-works of apps. There aren’t distribution “sponsored” IDEs (like Visual Studio or Xcode), userland API documentation, frameworks etc.;

Things on the Linux GUI land are so messed up that we even got this. Well, at least with Swift and Adwaita for Swift we may get to something closer to stable, long term APIs and useful documentation…