Agreed. It’s really shit for new code, but if I’m writing glue code stuff or repetitive code it saves a lot of time spent on typing.

Introducing a Captcha on a form on my website basically blocked bots 100% of the time. It’s arguably good enough from a practical standpoint.

If someone really wants to exploit my site, then they will find a way. You can only make it harder but never truly impossible if you don’t want to dispose of all convenience.

100% that.

Especially that working software over comprehensive documentation part, which can be automated so easily if done right.

There’s so much value in TDD and providing a way to do integration and automated UI tests early on in a project, yet none of the companies I’ve worked at made use of it.

Also automated documentation tools like Swagger are almost criminally underutilised.

Unfortunately I can’t help you with Nobara, but I’m surprised you’re having troubles with EndeavourOS.

EOS has been working out of the box for me for almost everything.

Thanks for the response. Seems like I can’t assume other CS degrees are comparable.

We definitely have a strong focus on security in my degree, but I still believe that awareness of what you’re running on your machine and potential dangers of those programs fall into the category of common sense. Mishandling secrets, having bad authentication or not knowing how to setup SSL is definitely experience stuff though.

Neither young or naive. Just assuming others share my experience.

Makes sense, I feel bad for the guys that were happy for a chance and got screwed over. (By the hackers, not you, haha)

That’s a bad take. Unless you get your knowledge purely from shady tutorials or have a fast track bootcamp education, it’s unlikely you never touch on security basics.

I’m a software design undergrad and had to take IT Sec classes. Other profs also touched on how to safely handle dependencies and such.

While IT Security is its own specialisation, blindly trusting source code others provide you with is something a good programmer shouldn’t do.

If you need a metaphor: Just because a woodworker specialises in tables, doesn’t mean they can’t build a chair.

Edit: Seems like my take is the bad one 😂

It’s sad that this works. You’d think especially software professionals would be the most vigilant about running unknown code.

My immediate thought. And no worries about ink drying up and whatever else might break suddenly. Just pay a shop if you want printing as a service.

Ha! I’m partially looking at this issue in my bachelor’s thesis.

It’s not at all necessary to embed a browser, but it’s really easy to transfer your web app to a “near native” experience with stuff like electron, ionic, cordova, react native or whatever other web stuff is out there. The issue is mostly that native APIs are complicated and relying on web views or just providing your own “browser” is a relatively easy approach.

Stuff like Flutter, Xamarin or .NET MAUI compile depending on the platform to native or are interpreted by a runtime. There’s a study I use that compares Flutter to React Native, native Java and Ionic on Android and finds that unsurprisingly the native implementation is best, but is closely followed by Flutter (with a few hiccups), with the remainder being significantly slower.

The thing is. I don’t think these compiled frameworks lag behind in any way. But when you have a dev team, that’s competent in web development, you won’t make them learn C#, Xaml, Dart or C++, just to get native API access - you’ll just let a framework handle that for you because it’s cheaper and easier.

Edit: To add some further reading. This paper and this one explore the different approaches out there and suggest which one might be “the best”. I don’t feel like they’re good papers, but there’s almost no other write up of cross-platform dev approaches out there.

Edit2: I also believe that the approach “we are web devs that want access to native APIs” may be turned around in the future, since Flutter and now also .NET offer ways to deploy cross-platforn apps as web apps. I’ll get back to writing the thesis now and stop editing.

Reasonable

That made me laugh more than it should have.

I use this method and the only place where there isn’t some slight categorisation going on is the projects folder, because these are relatively short lived and then archived in their respective category again. For example university stuff has its own Area and Archive folder because otherwise it would be too much.

You can always argue that productivity methods like this don’t work, because some certainly don’t work for some people or some special workflows. But these methods can always be changed or just discarded. I’ve read a few books on productivity stuff and found some middle ground that works well for me, just like everyone should do if that interests them.

In case you’re interested I’ve tried out a few things and kinda settled on fish, but will still use bash for scripting.

Fair point. For me using a distro dedicated to making Arch accessible just is more attractive than having an installer and being on my own afterwards.

But yeah, EndeavourOS is pretty much just an installer with purple space theming.

Definitely. For now every fix that worked for Arch, also worked for me.

I think EndeavourOS profits greatly from being so close to Arch, because right now every fix that worked for an Arch user also worked for me.

Idk much about other distros, but maybe try Pop OS first and see if you like it.

As I mentioned I’ve ran into really weird issues with steam because of some missing dependencies that are mentioned on page 49 of google search results.

This will send me down another 4h rabbit hole today, thanks 😬