Ha, that’s funny. When I run some Visual Studio builds on Windows it completely freezes at times.

Never have that issue on EOS with KDE.

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.

I’d have recommended it as well.

Popular stuff is usually available in most languages.

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.

I did check the bios settings but couldn’t really find anything that would directly affect a pcie card.

Most power management stuff that could cause issues is turned off. Fast boot itself was also off.

Classic!

Thanks! It’s really funny. Especially since KDE updated to version 6 and caused a lot of issues for other users - so it had to be the a software issue of course!

I’m still not entirely convinced, that it wasn’t a software issue that caused the device to misbehave.

It’s my cat, I am the user 😄

He cs_assaulted the counter

Why anyone would spend 1500 dollars and 300 hours on a parody is beyond me but it’s impressive work nonetheless for a solo dev.

The gameplay was fun to watch, but mostly just because the characters steps sounded like their shoes were sticky after they stepped into some spilled cola or zombie guts or whatever.

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.

deleted by creator

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.

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.

Back in school we were taught that products have lifetimes in which they are popular and once those run out you have to get a new one on the market if you want to keep growing.

I try to remain optimistic but if your product never breaks and is never “out of date” then the market will be saturated at some point.

There was this company in Germany that sold the “Römertopf” which was basically a ceramic baking utensil that never broke if treated right. They went out of business because pretty much everyone that wanted one already had one.

I hope someone smarter than me can carve a business out of producing robust and sustainable electronics and the like, because if no one is successful with it the big companies will never follow suit.