mostlylurks

12 ms·

91.
by mostlylurks 3y ago
It is quite believable that AI might have a sufficiently detailed understanding of how humans express feelings (via text) that it is capable of emulating such behaviors quite accurately even without experiencing those emotions itself (possi
92.
by mostlylurks 3y ago
It is relatively rare, but software itself (not just the resulting program, such as "a game") can be art. Most examples of this focus on using code to communicate something humorous about the culture surrounding software. I cite F
93.
by mostlylurks 3y ago
C++ compilation times can become quite slow even when you're doing what you describe manually (known as a "unity build", and not particularly rare in some niches), even if you avoid including the same headers multiple times.
94.
by mostlylurks 3y ago
There's a section in the Parmenides which addresses this particular idea, though as a part of a larger argument on the nature of the one. Later platonist / neoplatonist thinkers also occasionally had similar notions. It would be i
95.
by mostlylurks 3y ago
People often learn the wrong lessons from literature. Design patterns, for instance, are something you should learn, not as tools that you should eagerly find applications for, but rather as a shared understanding of the kinds of patterns t
96.
by mostlylurks 3y ago
> Using ternary operators everywhere instead of if-else just because it's a few characters less This isn't a fair assumption to make. One good reason to prefer ternaries over if-elses in languages which lack if-else expressions
97.
by mostlylurks 3y ago
> Handling every “falsehood” gracefully yields a combinatoric explosion in the complexity of your data model. Sometimes this only happens if you started off with a model that made too many assumptions in the first place. For instance, re
98.
by mostlylurks 3y ago
Macros are perfectly capable of static polymorphism. That is one of their primary use cases. _Generic is simply an alternative mechanism for static polymorphism, with some extra capabilities and some limitations in comparison to your typica
99.
by mostlylurks 3y ago
You could remove all the arcane laws, regulations, and zoning which make constructing new houses ludicrously expensive. Most people would be perfectly happy to live even in a shoddy log cabin built by them and their family if it meant they
100.
by mostlylurks 3y ago
I see this opinion voiced all the time, and I can never understand how people can struggle with something like nested ternaries. Surely a straightforward use (i.e. not a weird edge case) of very basic syntax shared by most widely used progr
101.
by mostlylurks 3y ago
> No matter the quality of your code, if the product or service is not a good market fit. It will be retired. No one will stumble upon it or pick it up after it's gone. This applies to artistic endevours like books and paintings as
102.
by mostlylurks 3y ago
There are cases where the tradeoffs don't involve the actual codebase. For instance, there are certainly many developers who are 3x faster than the average developer simply as the result of having enough experience and/or skill t
103.
by mostlylurks 3y ago
Self-documenting code is perfectly capable of expressing the "why" in addition to the "what". It's just that often the extra effort and/or complexity required to express the "why" through code is not
104.
by mostlylurks 3y ago
> In practice this doesn't happen that often The primary reason that this doesn't happen that often is that neither Chinese nor Japanese use Chinese characters in a primarily pictographic manner anymore. Only a small subset of
105.
by mostlylurks 3y ago
> I would love to see the day where emoji becomes a viable form of cross-cultural shorthand. I have my doubts regarding this. We're already seeing a situation where different groups within a single culture, the young and the old, us
106.
by mostlylurks 3y ago
> Text is universally compatible, whereas emoji introduce compatibility and versioning issues across browsers and operating systems. To be specific, they introduce a lot more of such issues, but such issues were already there with plain
107.
by mostlylurks 3y ago
The existence of a committee, even an influential one, for a language does not mean that that committee actually controls that language. In the end, it's always the people who use a language that control it, not just in theory, but als
108.
by mostlylurks 3y ago
> In C++ I find it quite infuriating that try{} opens up a new lexical scope, which means you can't construct something, check for errors and move on You technically can with a small workaround (demonstrated below), though I persona
109.
by mostlylurks 3y ago
One of the downsides of the C++ approach is that it makes it more cumbersome to make changes in your code. If you for instance make a trivial change where you change a variable from a stack-allocated object accessed directly via .foo() into
110.
by mostlylurks 3y ago
> Maybe if you have big amounts of RAM Browsers these days have settings which automatically unload tabs to make sure you don't run out of RAM. I personally don't run into issues with 16GB of RAM, so I don't have those set
111.
by mostlylurks 3y ago
With the exception of syncing the list between devices (a feature I personally can't imagine myself needing or wanting, though I can definitely see why others would), these things are basically what tabs are for. You open things up in
112.
by mostlylurks 3y ago
If you don't understand how lifetimes and associated aspects of the language work, you might very realistically run into situations where your code will be a million times slower than the python, java, etc. equivalent, not faster. For
113.
by mostlylurks 3y ago
> What's wrong with enums? They don't compile down to just the same code with the type annotations and definitions removed, which is often considered to be the ideal that typescript should follow. Instead, they compile down to
114.
by mostlylurks 3y ago
Part of that is almost certainly because it is far, far easier to explain how to get started with create-react-app then it would be to explain the various alternative approaches, especially considering how inexperienced on average the kind
115.
by mostlylurks 3y ago
> Creating ‘N’ threads and adding them all to a sorted wake list will be between O(N log N) and O(N^2), depending on the OS and/or language runtime. This is not a fundamental limitation of scheduling systems, especially if you take
116.
by mostlylurks 3y ago
> completely changes how you write your frontend You can use it for only a part of your UI, and you can implement any parts of your UI that are embedded within react components without react as well. It doesn't lock you into doing t
117.
by mostlylurks 3y ago
"Not parsed ahead of time" might be the better qualification. At least in some forths you can cease parsing the file (in the "outer interpreter") at any point and perform any kind of computation or IO that you've pr
118.
by mostlylurks 3y ago
I would assume that there has to be an element of getting used to and your brain starting to expect the version that you tend to consume. I, for instance, have never drank the non-diet versions of sodas on purpose, even as a child, so when
119.
by mostlylurks 3y ago
The forced nesting that particular proposal makes it less ergonomic (especially for scopes with multiple such resources), and would bring very little benefit over a simple library-based approach (instead of a language feature), something li
120.
by mostlylurks 3y ago
> So if we know Symbol.dispose in advance we can simplify the code? Symbol.dispose is not a string, but a symbol. Its value cannot be written out in the code, only referred to indirectly (that is basically what symbols are for), nor is t

More ›