klysm

30 ms·

481.
by klysm 2y ago
The thing is though you can get to every note by stacking enough thirds - I don’t think it’s a particularly bad perspective
482.
by klysm 2y ago
Apply is really straightforward. The dictionary stuff is very annoying overhead but it’s nice keeping everything in one language.
483.
by klysm 2y ago
> The machine can inspect what it's written by scanning at low power. This is a fascinating property that seems very powerful
484.
by klysm 2y ago
Unfortunately I don’t think this has any relevance to that at all.
485.
by klysm 2y ago
> Runtime / performance This is notoriously difficult to quantify even in the simplest of examples. How do you even express goals here? What if the software is targeting a variety of platforms? > peak memory consumption Is this s
486.
by klysm 2y ago
What do you mean by such standards? What would example ones be for software?
487.
by klysm 2y ago
That doesn’t match my experience at all. I have many Python projects going back years that all work fine with pinned dependencies
488.
by klysm 2y ago
So pin your deps? Language backwards compatibility and an API from some random package changing are completely distinct.
489.
by klysm 2y ago
> If you want better software set minimal, measurable, objective standards. That becomes your foundation, your law. This is completely intractable in practice. The things that matter cannot be readily measured. Measuring a proxy to the t
490.
by klysm 2y ago
I don’t think this is a technology problem…
491.
by klysm 2y ago
I guess we have different ideas of what complexity is. I like it when the compiler doesn’t let me write incorrect code
492.
by klysm 2y ago
I guess this is just another instance where every system will end up Turing complete. Most don’t make it all the way to ISA though
493.
by klysm 2y ago
And there somehow isn't a single video of this?
494.
by klysm 2y ago
I’m not sure it’s even debt really. At a product level you can device to just tolerate the slowness indefinitely
495.
by klysm 2y ago
Terminals, ttys, etc. have some of the most arcane and outdated APIs I am aware of. It's like a window back into the 1970s
496.
by klysm 2y ago
it’s generally better to avoid the distributed systems problems if you can. Postgres is very flexible and you get very far with it if you use all it has to offer
497.
by klysm 2y ago
Yeah excel based data ingest is a pretty brutal problem to solve.
498.
by klysm 2y ago
I've had very nice experiences using systemd for developing embedded systems. Laying out all the unit files and just slapping the files in an overlay makes it super simple. The RAM usage isn't being calculated correctly. You can e
499.
by klysm 2y ago
I think the right way to look at this is the trade off spaces that are maligned with performance. You can usually gain something by losing some performance, so those who gain but don’t go too far overboard on things being slow will win. I w
500.
by klysm 2y ago
I think database schemas deserve to be protected with one’s life as the holy ground of the system. If the schema is fucked, everything else will be fucked too.
501.
by klysm 2y ago
Obviously that depends on the complexity of the TUI. React is the best tool I’ve used to build UIs out of all the tools I’ve ever tried. I don’t love JS at all.
502.
by klysm 2y ago
I’ve used both. MVC is too limiting
503.
by klysm 2y ago
It’s there as an escape hatch :)
504.
by klysm 2y ago
> lack of IC carefulness is not to blame when things break But if you can trust ICs a bit, you can move faster
505.
by klysm 2y ago
I have no idea what I’m talking about, but it seems like these restricted cases of inequality flow control type checking are very similar in power to dependent types, but don’t require the same level of complexity. It’s nice being able to w
506.
by klysm 2y ago
I really wish we just had a completely different API as a filesystem. The API surface of filesystem on every OS is a complete disaster that we are locked into via backwards compatibility.
507.
by klysm 2y ago
Kinda like log structured merge tree?
508.
by klysm 2y ago
Depends on how naive the conversion is. If you consider DST while making the conversion that’s not really a problem
509.
by klysm 2y ago
Seems pretty absurd
510.
by klysm 2y ago
UTC is generally a good idea for storing, but there are still some ways to have that bite you. If a user enters a local date time for a future event in a particular time zone, converting that to UTC could result in incorrect behavior if the

More ›