Showing of the model's capabilities - okay, but it's not like it solved the problem on its own, and apparently not particularly efficient. Are there practical applications that justify the investment?
283 karma · joined February 18, 2016
Showing of the model's capabilities - okay, but it's not like it solved the problem on its own, and apparently not particularly efficient. Are there practical applications that justify the investment?
A perfectly normal thing to do.
I'm not sure if it's actually needed - a lot of things have been tried and the paradigms that persisted you can choose between but it seems to be a matter of taste. I often feel that the real issue is the lack of maturity and stability. I rather want a complete UI toolkit including learning resources (not reference docs!), no matter how boring, instead of super clever implementation that is never in a usable state.
> We’re hiring engineers.
Careers page:
> Sorry, no job openings at the moment.
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.