Just your typical internet guy with questionable humor

  • 15 Posts
  • 509 Comments
Joined 1 year ago
cake
Cake day: June 22nd, 2023

help-circle











  • In my opinion, C purists are people who REALLY need to wash their fucking dishes, touch grass and get some sunlight. They get too worked up because “all the important things are written in C”, the important things being drivers, kernel and most basic stuff that OS needs.

    Whenever one talks about performance, just reply with “use Assembly” and their argument is immediately invalidated. You can also mention networking, fault tolerance and how Erlang does a much better job than C or C++ could do, which is why “real adults with real jobs” created it in the early 90s

    But mostly, it’s ironic that they’re becoming C-Conservatives, blaming the “hot new language” for bringing “the kids”. You can read the same kind of logic and disdain for C programmers, from LISP programmers, in the Unix Hater’s Handbook (1994)






  • It’s time to return to the roots, to the C programming language CPU specific Assembly language

    Fix’d

    Joke aside, the answer to most of your questions is “because people with money said so”. As to why programs lag despite computers being more powerful, because shitty programmers and a general “BLA is cheap” mentality, where BLA is processing cycles, RAM, storage, network speed, etc. Funnily enough, the “program using everything the hardware offers” is an old complaint, as even Unix was considered a cancer during the 1980s, mostly by people whose computers did nothing but run very specific LISP code.

    C is not without its flaws, just like every other language. Teaching it over whatever the market desires may not necessarily make better programmers, nor better programs for that matter.

    I look at how programming has changed (…) it was all for the benefit of giant companies or the government.

    Giant companies first, govt second and as a side effect, as govts tend to be veeery slow in adopting certain computer related stuff. I suspect the main exception would be intelligence/espionage agencies, but they also much prefer others doing shit programming, makes their job easier.



  • Before even thinking about “which engine”, “which language”, people need to train and master the fine art of being aware of their own competence level.

    The second is being fully aware that your first game will likely suck and that not everything you make will come out as you dreamed.

    The third is knowing where and when to stop, especially regarding features. Many visual novels, effectively the simplest game to make regarding programming logic, die out in early access because the single dev decides to add a new character one too many times, forgetting there’s supposed to be an overall story to be told. Yes, feature creep is a problem even in fucking visual novels.

    To be fair, you can go places knowing pure Javascript ever since HTML5 became widely adopted, back in 2012 or so. There’s a variety of engines and frameworks, including for 3D games (Three.js and Babylon.js are the most known) and every major OS has a native web viewer, so you’re not stuck to fucking electron.