uhura

6 ms·

1.
by uhura 1y ago
This kind of stance cannot be made without properly setting the context for the software. It is very clear that different software backgrounds have different needs a different development strategies that are more efficient. LLMs are a tool
2.
by uhura 1y ago
I’ve been having those discussions with friends for the last 3 or 4 years. The downside of having local infra is pretty much having someone that has the experience to do it right. While this article covered the higher end, the math on the l
3.
by uhura 2y ago
I believe that this long game of Swift being "good for everything" but "better for Apple platforms" will be detrimental to the language. This does not help the language nor seems to bring more people to the ecosystem. Co
4.
by uhura 3y ago
The article reflects well many aspects of western life experience and might be poorly applicable in other contexts. The text shows signals of it when associating certain kinds of relationships to be more prevalent in certain social-economic
5.
by uhura 3y ago
I believe the general strategy for this kind of product is to drive CX conversion. Amazon usually offers auto repurchase too, so if you are going to buy once and Amazon is cheaper, the second time too..., by the third you might actually dec
6.
by uhura 3y ago
I don't get the " Maybe Rust isn’t a good tool for massively concurrent, userspace software " conclusion. Rust is all about lifetimes and the borrow checker. Async code (a la C#) will introduce overhead to reason about lifeti
7.
by uhura 3y ago
But then, how could you guarantee type safety? This yield is not an object, it is handling the execution context to another stack.
8.
by uhura 3y ago
I would prefer to add a `yield` param to functions so it can better interact with the current type system. This means that for a function to yield, it needs to have the so called `yield` param and you can only yield inside a yield function
9.
by uhura 3y ago
Check the “introduction” paper about the family of OS [1], it provides a good introduction to get the how and why. My two cents is that composing applications at the FS level is more expressive than Files/Sockets/HTTP requests. Gl
10.
by uhura 4y ago
This might not be a popular opinion but it was what worked for me: - Research a little about PostScript and the display version. - NextStep Developer Documentation [1] - Apple older documentation (it is archived, but covered a lot of stuff)
11.
by uhura 4y ago
The comment mentions original iPhone screens. They were 3.5" and we hold phones differently because of the sub 4" displays. The idea back then was maybe to separate the confirm action from other actions located at the bottom bar.
12.
by uhura 4y ago
This kind of article develops a dangerous line of reasoning. The failure of Plan9 is not about what went wrong or right. It is about how the market evolved and made decisions, which goes beyond the scope of this comment. The first conclusio
13.
by uhura 4y ago
Old WWDC content has a lot of value. They cover a lot of core technologies that Apple has no interest in covering and documenting again (because they deprecated and are removing old documentation instead of improving them...). The channel i