12thwonder

6 ms·

1.
by 12thwonder 4y ago
I made a similar editor a while ago https://apps.apple.com/us/app/aerial/id1483897826?mt=12
2.
by 12thwonder 4y ago
it seems like less sophisticated version of reactive paradigm to me, am I wrong?
3.
by 12thwonder 4y ago
Most of the UI/UX designers that I see at work and other places are basically graphics designers. I just wish UI designers learn more about interaction design than just pure graphics design.
4.
by 12thwonder 4y ago
I think this article is more about alternative rasterization algorithm for 2D geometry. 'vector graphics' is misleading as vertices used in graphics APIs are vectors.
5.
by 12thwonder 4y ago
> creation of a Beizer curve: ... clearly a CPU algorithm. isn't this just a tessellation basically? GPU-based tessellation is very common, mostly for meshes but can be used for line-like figure too.
6.
by 12thwonder 4y ago
can you elaborate on what "protocol" looks like? or can you give us some example?
7.
by 12thwonder 4y ago
I like this. It is very hard to find out if the definition already exists or not in the codebase. This can lead to multiple definitions of the same thing or the truth. anyone has a good way to deal with this?
8.
by 12thwonder 4y ago
good article. my questions now is how can we avoid over-plannings and under-plannings? a lot of time I feel like the diminishing return of a planning is pretty steep for many situations but it's hard to tell how much time we should spe
9.
by 12thwonder 4y ago
I am amazed at how small the codebase is, and also pretty readable. great to see work like this, thank you!
10.
by 12thwonder 4y ago
good to know, thanks! I personally would like to know when the GPU resources become available (freed) thus still inclined to prefer RC over GC tho.
11.
by 12thwonder 4y ago
this is a really good benefit of RC codebase. Resource management becomes much more harmonious and easy to follow.
12.
by 12thwonder 4y ago
like Chris said in the article, it is difficult for GC languages to interop with C/C++ codebase. in addition, if your system requires precise control over when and when not to use CPU, like resource-intensive gaming, browsers, OS, then
13.
by 12thwonder 5y ago
my understanding is that the author is talking about stack usage at runtime not the size of an entire stack which can be set by the pthread API you mentioned. it's confusing because the article starts with a discussion of how default s
14.
by 12thwonder 5y ago
what is your view on Clojure.spec?
15.
by 12thwonder 5y ago
Throwing away is easy but remember, you have to do the runtime check instead of compile time check, and that is not so easy in a lot of cases
16.
by 12thwonder 5y ago
sort of. I don't write tests at early stages, do you? I don't see types as serious tests and I don't think they are robust. let's say that some integer must be between 10 and 100, do you use type checks for this?
17.
by 12thwonder 5y ago
good point. Yes, during prototype phase, rigid typing actually helps quite a bit. I still do that myself, simply because I don't have to "run" the program to see if I'm on the right path when I'm just sketching thin
18.
by 12thwonder 5y ago
yeah, but my point is that checking system that you had created will be thrown away at some point in my experience. so why bother writing types? that is my attitude at least at very early stage of a project. later in a project where you kno
19.
by 12thwonder 5y ago
back in the days, I had this infatuations with the idea of having everything checked at compile time by using type system. and I see many people following this kind of path with type system of Haskell, rust, and maybe typescript. granted, i
20.
by 12thwonder 5y ago
why not struct Foo{ bool some_flag : 1; bool other_flag : 1; .... } ?
21.
by 12thwonder 5y ago
I feel like you are talking about types in programming languages but Object–relational impedance mismatch is still a thing and I'm not sure if you want a solution (for the mismatch) at DB level.
22.
by 12thwonder 5y ago
> I wonder what kind of application I need to try application that deals with highly dynamic data. lots of variants (OR type) in tree/graph. (photoshop's layers come to mind.)
23.
by 12thwonder 5y ago
I think what you are saying makes sense for a lot of projects. but point I was trying to make is that there are projects that have to deal with highly dynamic and complex data structures. I used file system as an example but any trees/
24.
by 12thwonder 5y ago
do you think having a DATE type will increase performance for example as opposed to use INT/LONG type? if stronger type systems will ensure performance, Haskell will beat C in benchmarks but that's not the case in most situations.
25.
by 12thwonder 5y ago
but do you want, for example, a file system where you have to define what kind of files you can store? This folder can only contain JPEG and PNG files, this folder can contain only A or B ....etc. useful in some cases but I don't think
26.
by 12thwonder 5y ago
off-topic but the author's negative sentiments toward c++ is interesting to me as it is quite opposite with me. I use c++ mainly but when I have to use javascript at work, i really hate it for whatever reason. wonder if other c++ progr
27.
by 12thwonder 5y ago
Right, Browsers too are written in c++ for the most part
28.
by 12thwonder 5y ago
I personally don't see that capitalism itself is the culprit of the issues mentioned but I don't like monopoly powered by free software. as long as competition is in place, I am kinda ok with big companies exploiting(?) free soft
29.
by 12thwonder 6y ago
I do agree with most of your points, porting may not be possible. However, I was just wondering if the future of C/C++ can be much safer than it is right now. for example, GCC's GUARDED_BY macro is a big help in thread safety fo
30.
by 12thwonder 6y ago
for new projects, sure. but when it comes to existing c/c++ projects, I'm not a big fan of rewriting everything.

More ›