- Zig has the concept of illegal behavior, of which a subset is unchecked illegal behavior - basically undefined behavior, but if evaluated at comptime, it results in a compile error. The documentation also states that most illegal behavior is safety-checked unless you use the ReleaseFast or ReleaseSmall optimization modes (and don't enable safety checks for individual blocks).
- Archived blog post: https://web.archive.org/web/20240719152109/https://www.prime...
- Thanks a lot, this was quite enlightening, like what "buffering in the interface" really means. A follow-up post would nice!
I'm also curious what preserve in rebase is used for in practice. Prevent drain from writing buffered bytes too eagerly? But if it can write more data in a single syscall, what benefits does it give you? If the end of the buffer could still change, then you wouldn't want to write it yet, but then drain would need a similar parameter to not touch the bytes at the end (and therefore write none of the data). But the bytes in the buffer would still move towards the front, so this makes no sense.
- Another entertaining piece by the Lego Island guy!
My takeaway is that you should choose a passion project as your hobby and put in the time to learn and do whatever is necessary to achieve your goal on your own or together with similarly motivated people rather than relying on anyone external you have to pay - things go downhill fairly often and quickly it seems. Is any business a scam to some degree nowadays?
- I would argue that it's not meaningful to do so for larger files with comptime as there doesn't seem to be a need for parsing JSON like the target platform would (comptime emulates it) - I expect it to be independent. You're also not supposed to do I/O using comptime, and @embedFile kind of falls under that. I suppose it would be better to write a build.zig for this particularly use case, which I think would then also be able to run fast native code?
- > Most people would have probably driven around for years with a foreign GPS tracker.
So basically everyone with a smartphone? I'm not sure if it's really worse if the car has its own GPS and cell connectivity. How many people turn off their phone or leave it at home? And you can buy other people's location data, so...
- Some IT service corporations that are known for a very high employee churn rates often post the same position a dozen times, for each of their office locations.
Sometimes it's a 100% remote job, and they still post it multiple times with different locations.
They probably litter job portals this way so that they can compensate for the frequent personell changes. They are impossible to miss.
- Yes, it's sad. On the other hand, I think it's a good thing that people share knowledge less, publicly and free of charge on the web, because there is so much exploitation going on. Big corporations obviously capitalize on the good will of people with their LLMs, but there are also others who take advantage of the ones who want to help. A lot of users seemingly expect others to solve their problems for free and don't even put any effort into asking their questions. It's a massive drain for energy and enthusiasm, some even suffer from burnout (I assume more in open-source projects than on SO but still). I rather want it to be harder to connect with people sharing the same passion "in private" than having outsider who don't contribute anything profit off of activities happening in the open. This frustratingly appears to become the main reason for corporate open source these days.
> We’re hiring engineers.
Careers page:
> Sorry, no job openings at the moment.