That "just" was too flippant. My bad. What I meant to convey is "hey, there's some fast compiling going on here and it wasn't that hard to pull off. Can we at least take a look at why that is and maybe do the same thing?".
So there's this guy you may have heard of called Ryan Fleury who makes the RAD debugger for Epic. The whole thing is made with 278k lines of C and is built as a unity build (all the code is included into one file that is compiled as a single translation unit). On a decent windows machine it takes 1.5 seconds to do a clean compile. This seems like a clear case-study that compilation can be incredibly fast and makes me wonder why other languages like Rust and Swift can't just do something similar to achieve similar speeds.
@AndyKelley I'm super curious what you think the main factors are that make languages like Zig super fast at compiling where languages like Rust and Swift are quite slow. What's the key difference?
Not all SWE jobs have the same culture and there's work outside of silicon valley. That said, it sounds like you've decided that this isn't for you anymore so what is? What's something that makes you excited or you find yourself thinking about a lot. There's a lot of other opportunities out there, and you should feel proud of the experiences you had and mistakes you made. Don't worry about what others think and go find another chapter to start. (That said, you may need to accept a lower salary for a while.)
Languages that encourage making DSLs are a two-edged sword. On the one hand, you get to make a language that is more clear and fine-tuned to your use-case. On the other, you have an ad-hoc language with no support that you have to maintain along with the documentation (considering that you can't expect anyone else to know the DSL ahead of time). As I've gotten older, I've determined that well-designed APIs in a well-known language are a better alternative to DSLs.
Yeah this is a fair point. In honesty, the attempts I have made to have GPT help me think creatively has usually left me disappointed and feeling like it was picking safe, middle-of-the-road solutions. That could be on my prompting skills but also I tend to view LLMs as more of a fuzzy information retrieval tool than a creative/reasonable one. It just hasn’t shown me original ideas that have seemed compelling to me yet (maybe I just need to beg it to be more “original”).
I don't entirely agree. This mentality is what leads to brutalist architecture offices that suck out the soul of all who work in them. People "live" and "work" in their apps and should feel alive while they do that. (That said, I don't think this new material style is necessarily the way to achieve that...)
To be fair, if you try to paint something on a webpage that follows the mouse cursor it's gonna be laggy af even in really simple toy examples. The blame may fall more on browsers.
This seems like another case where jblow's opinions are guided by his experience as a game dev. Games can be "finished" and never touched again. I think I mostly agree with him that software could be made to be timeless to some degree. But, in the world of web apps and saas, the culture is to offload much of the work to third party libraries/APIs which locks you into a never-ending cycle of dependency management. I don't know if this culture is totally necessary (maybe to ship fast and keep up with security updates?), but in a world where users expect software to be constantly improving you can't expect anything to be "done". Maybe you could get close if you built everything in-house, but even still you have to keep up with security flaws.
Among the many ways that AI causes me existential angst, you've reminded me of another one. That is, the fact that AI pushes you towards the most average thoughts. It makes sense, given the technology. This scares me because creative thought happens at the very edge. When you get stuck on a problem, like you mentioned, you're on the cusp of something novel that will at the very least grow you as a person. The temptation to use AI could rob you of the novelty in favor what has already been done.
Where can I go to learn how to scavenge for microcontrollers and load/operate an OS like this on them? (Low-key would like to know that I could do that if need be).
Odin really hits the sweet spot for everything you would want from a language for the game dev and game-dev-adjacent space in terms of simplicity, convenience, and speed. I think a major design decision of the language that will make or break it for users is the fact that the language gives you common features instead of giving you the means of abstraction to make those features yourself. For example, instead of preprocessor macros you get the `when` clause for conditional compilation because in Bill's estimation, that's one of the only real needs for macros. The same goes for data structures. Odin gives you the certified classics like dynamic arrays and maps but doesn't give you a whole lot to make your own custom data structures (it's possible, just not encouraged by the language design). All in all, I think if you want to make an application with a language that has batteries included and you don't need a lot more than that, Odin is nearly flawless.
I love jetbrains IDE for all sorts of features (their git tools like diff checker are unmatched imo). I've been wanting to use them for C++ for a while now specifically because I find that many LSP solutions are not that great. Looking forward to using the non-commercial version of clion!
I connect with this article very deeply. There was a time when I came to a similar conclusion about rust. That is, its requirements for your code become a puzzle in themselves and make the job a little less boring but when the novelty wares off it’s not so fun. Avoiding boredom at work is a lifelong struggle of mine.
Question from genuine ignorance: are scientists not incentivized to do good work even if it doesn't result in cool/useful/desired outcomes? I would think that even "the data from the experiment was inconclusive" should still be considered a valid contribution to the field as long as it was done correctly.
I love Rust and wanted to use it for gamedev but I just had to admit to myself that it wasn't a good fit. Rust is a very good choice for user space systems level programming (ie. compilers, proxies, databases etc.). For gamedev, all of the explicitness that Rust requires around ownership/borrowing and types tends to just get in the way and not provide a lot of value. Games should be built to be fast, but the programmer should be able to focus almost completely on game logic rather than low-level details.
I mostly agree with the sentiments in this article. I was once an extremely zealous FP acolyte but eventually I realized that there are a few lessons worth taking from FP and applying to more conventional programming:
1. Pure functions are great to use when you have the opportunity.
2. Recursion works great for certain problems and with pure functions.
3. Higher order functions can be a useful shorthand (but please only use them with pure functions).
Otherwise, I think simple, procedural programming is generally a better default paradigm.