HackerTrans
トップ新着トレンドコメント過去質問紹介求人

nc0

no profile record

投稿

Neocities

neocities.org
3 ポイント·投稿者 nc0·3 か月前·0 コメント

A quine that plays snake over its own source

github.com
1 ポイント·投稿者 nc0·5 か月前·0 コメント

コメント

nc0
·2 か月前·議論
As far as I know, platforms like YouTube and Twitter prefers using their own "link shorteners" (t.co etc) to track clicks and other metrics.
nc0
·3 か月前·議論
None, it just received the help of the vast majority of well-payed SWE to make it that way
nc0
·9 か月前·議論
Guess where the companies got the ideas and schemas from?
nc0
·昨年·議論
> Say something everyone lives everyday around the world. > "This is an extremely ignorant take."
nc0
·昨年·議論
You also have to remember the context.

First that visual debugging was still small and niche, probably not suited to the environment at Bell Labs at the time, given they were working with simpler hardware that might not provide an acceptable graphical environment (which can be seen as a lot of the UNIX system is oriented around the manipulation of lines of text). This is different from the workplace where most game developers, including J. Carmack were, with access to powerful graphical workstations and development tools.

Secondly there’s also a difference on the kind of work achieved: the work on UNIX systems mostly was about writing tools than big systems, favoring composition of these utilities. And indeed, I often find people working on batch tools not using visual debuggers since the integration of tools pretty much is a problem of data structure visualization (the flow being pretty linear), which is still cumbersome to do in graphical debuggers. The trend often is inverted when working on interactive systems where the main problem actually is understanding the control flow than visualizing data structures: I see a lot more of debuggers used.

Also to keep in mind that a lot of engineers today work on Linux boxes, which has yet to have acceptable graphical debuggers compared to what is offered in Visual Studio or XCode.
nc0
·2 年前·議論
I also recommend anyone interested to have a look at the Erlang/OTP ecosystem, especially for their design decisions. While the language and the platform isn't popular, the OTP team does present rich architectural patterns and ideas that can improve your design