I only have a 3k monitor, and I can manage it. Sometimes I comment line-by-line even.
He/Him | Hu/En/some Jp | ASD | Bi | C/C++/D/C#/Java
I only have a 3k monitor, and I can manage it. Sometimes I comment line-by-line even.
It’s time to return to the roots, the times when you used goto
instead of function calls! Fortran and COBOL all the way! /s
Once you look beyond the “git gud” and “we must gatekeep programming from the normies” aspects of coding, you might want a language that is either way more productive than C (D), a language that offers memory safety and functional programming paradigms (Rust), or even a language that has relatively good portability even at the cost of performance (Javascript).
If you’re only grumpy about Electron apps, then be mad at the corporations that:
Strongman leaders create hard times.
If you thought misspelling a variable was bad, then get ready for misreading documentation of OS API, then not realize why your implementation doesn’t work for a quite a long time.
I would add to the downside that it’s not the best programming language for game development, etc. There was some blog post about how troublesome is it to develop games using Rust due to some of the features that are good in other areas, like the whole concept of “immutable by default”.
I can also recommend D, if you want to deal with different issues, like the D Language Foundation fearing of change due to not wanting to deal with division from a new and incompatible version yet again, the GC being both a blessing and curse, if you want to go without a (tracing) GC you’ll need to go with a custom runtime that potentially missing many of its features, the attribute hell, etc.
Thanks, but that’s not what I’ve wanted the help for.
EDIT: Why all the downvotes?
Fair point, at least they should give us two USB-C ports, at least on the flagship models.
Best if you get one of those USB DACs. Those even work on a PC with a converter.
And then you can sell USB-C -> Jack converters (which break after a while - I’ve dismantled one for recycling for my Raspberry Pi, later I might make one epoxy potted for my phone), easy to lose wireless earbuds, etc.
Headphone jacks can be waterproofed, manufacturers are just lazy.
Phones are so thin now that people are crying back the thicker ones…
Someone should saw off the legs of the techbros that came up with the idea of removing the headphone jacks from phones. Just like the headphone jacks, legs are technologically “superseeded” by cars and electronic wheelchairs.
The standard answer is C/C++.
The nonstandard answers are:
XML has its strengths as a markdown format. My own formatted text format ETML is based on XML, as I could recycle old HTML conventions (still has stylesheet as an option), and I can store multiple text blocks in an XML file. It’s not something my main choice of human readable format SDL excels at, which itself has its own issues (I’m writing my own extensions/refinements for it by the name XDL, with hexadecimal numbers, ISO dates, etc.).
Yes, I’ve meant declarations, which makes stuff much harder. There are tools that automatically writes you the header files, but it was a major PIA when I learned C++.
Okay, I likely have mixed it up with another language, which sounded similar…
Issue with C# is, that it’s quite far away from a system language, and I would have to write the engine’s main core in some more system-level language, and I don’t consider it good practice to write every component that doesn’t directly interfacing with the OS in a trendy scripting language.
I have talked to people about Rust gamedev (including those who left Rust for D due to gamedev), and it’s not a very good one, due to the functional aspects. Outsiders often joke about how Rust has more game engines than games.
Zig has the header file problem. Header files were originally created to get around memory limitations of old workstations, that no longer exist. They also complicate coding, since you now often have to implement things at two places at once. However, Zig not only copied C++'s multi-inheritance, but also its header files, without understanding the actual reason why it existed in the first place.
Classes can be useful for abstraction. Just because they often overused doesn’t mean they’re bad.
Without an explicit class, I would either:
doStuff(cast(void*)&localstate, values)
vs localstate.doStuff(values)
).While structured programming was a godsend to the chaos preceding it, newer programming paradigms should have been instead seen as tools rather than the next dogma. OOP got its bad name from languages that disallowed its users to develop without classes, and enterprise settings making its devs to implement things that could have been simple functions as classes, sometimes complete with factories.
Same is with functional programming. There’s clearly a usecase for it, but isn’t a Swiss-army knife solution for all problems of programming.
“You will be more conservative as you grow older” is not a truth, but a threat. If you don’t become a conservative under their regime, you won’t become old.