• 4 Posts
  • 15 Comments
Joined 1 year ago
cake
Cake day: June 17th, 2023

help-circle







  • Wrong wrong wrong. It was never about ease of use. It was always about taking control away from the user, and hiding authority for control. This kind of deceptive practice has led to what we gave today - cars selling subscription hearing seats. The truth is, the gui was always buggy and a product unfit for its purpose from day one. Apple sold it as a means to get consumers to accept a defective product from the start, perpetuating their ability to always sell updates, forcing consumers to pay for things THEY DO NOT NEED.


  • yesdogishere@kbin.socialtoTechnology@lemmy.worldWhat DID Apple innovate?
    link
    fedilink
    arrow-up
    4
    arrow-down
    38
    ·
    edit-2
    7 months ago

    Wrong wrong wrong. Macontoshs gui was crap and buggy as hell. Every seasoned it expert knew it was a shit lousy interface designed to dupe people into believing it was secure when in fact it proliferated viruses and security holes, and drove the control of computing into an avaricious humanity destroying company culture known as apple. DO NOT EVER PROMOTE THE GUI AS GOOD. ITS CRAP.


  • Wrong wrong wrong. The graphical user interface is crap and will always be crap. The whole matter of popularity is marketing bunkum. Console command interface was al ways faster and better than any gui for general computing tasks. The gui is fine for office tasks, but shit for everything else. The popularity of the gui today has driven a massive upscale of cruddy bloated virus infected software. The fact that most people now only know gui has meant that control of viruses has slipped away. Had console commands been the mainstay for computing, viruses and security holes would never have been allowed to proliferate as they do today.









  • ive switched to firefox for desktop windows for about 1 year now. Firefox is really capable and as swift as chrome. You also get a sense of less intrusiveness. Firefox also has the multi containers widget, though for me it breaks down after a while. The big difference now between firefox and chrome are things like automatic subtitles for anything running in chrome. So if a youtube or other video has no english subs, Chrome can do it. And soon, Chrome i going to go AI too. I’m not sure how firefox will survive that onslaught. I suspect mozilla will have a firefox fork partnering with a major competitor of google (eg: MS).


  • the worst part for me, was not only being unable to estimate the time to solve the bug, i found that often the problem was in syntax or shadings of understanding on how functions or bracket syntax worked. i could refer to all the biggest programming books off the shelves, and the answers they provided would not work. Programming is one of those professions where answers lay with people who had busted their brains or lucked it trying to make it work, and had collected over many years, snippets of code which they knew worked. If you weren’t chummy with these people, you would never find the answer. This isn’t really a worthwhile profession. Unlike physics, or maths, where there is an independent answer governed by forces outside of an individual human, programming is a profession which inherently depends on learning errors from another human. It’s a pointless profession and gets you nowhere in life at the end. Sadly. (Unlike say law, or accounting or physics, where at old age, you know more about the world around you.)


  • the worst part about debugging for me, is i have no idea how long it will be before i can solve a single bug. it could take me 2 hours, 1 day, a week, no idea. Because i have no idea where the bug came from. I have ti go through increasingly more detailed testing cycles. Then devise more laborious testing cycles. This is why i chose not to work as a programmer. In other professions, I know i can give an estimate of the time taken to complete the task. Debugging? No real idea. What if the boss says finish it by tomorrow? I might be there all night.