Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
wyager
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
16 ms
·
271.
▲
by
wyager
2y ago
Yeah, it does not matter to me, but that wasn't what we were talking about
272.
▲
by
wyager
2y ago
Actually, this subthread is about whether this is a "really important project"
273.
▲
by
wyager
2y ago
> Not everything will be rewritten in Rust. Yeah, but it's also not going to be rewritten in safe C++.
274.
▲
by
wyager
2y ago
> Safe C++ is a really important project What makes you say this? It seems to me like we already have a lower-overhead approach to reach the same goal (a low-level language with substantially improved semantic specificity, memory safety,
275.
▲
by
wyager
2y ago
We're implicitly talking about the US, though, given that the subject of the article is SV tech companies
276.
▲
by
wyager
2y ago
This is not worth reading, because it was not generated as part of a deductive process, where you start with some facts and work your way to some entailments. Instead, the causal process that let to the creation of this book and ad was that
277.
▲
by
wyager
2y ago
> If you want blocking code to run asynchronously, just run it on another task What kind of embedded work are you doing exactly? Linux "soft" embedded or MMUless embedded? I don't have infinite NVIC priority levels to work
278.
▲
by
wyager
2y ago
WAL: Write ahead log, common strategy for DBs (sqlite, postgres, etc.) to improve commit performance. Instead of fsync()ing every change, you just fsync() a log file that contains all the changes and then you can fsync() the actual changes
279.
▲
by
wyager
2y ago
It doesn't matter if something was evolved or designed; if there is a penalty on increased complexity, the systems will converge towards low-kolmogorov-complexity implementations. The information theoretic complexity of the human genom
280.
▲
by
wyager
2y ago
Ah thanks, will fix
281.
▲
by
wyager
2y ago
Using pointers correctly and safely in C basically requires tracking pointer rules substantially similar to the rust pointer rules, but in your head. Most people who don't do this just write incorrect code, although it might only rarel
282.
▲
by
wyager
2y ago
I think writing broken C is easier than writing correct Rust is easier than writing correct C. A lot of C(++) devs just like that they can mostly get away with writing broken code
283.
▲
by
wyager
2y ago
The niche is anywhere C or C++ is used, which it excels at
284.
▲
by
wyager
2y ago
I made this with rust in 2020 http://yager.io/vumeter/vu.html The embedded rust ecosystem has invanced a pretty insane degree since then. I have an ongoing embedded project and I have had to use C FFI calls a total of
285.
▲
by
wyager
2y ago
Rust solved this by autogenning code from mfgr published device xml descriptors. Eg https://embassy.dev/ Better than any C(++) embedded hal I've used
286.
▲
by
wyager
2y ago
The article also discusses a `TryTransmute` trait which will cover this case. Additionally, you often want to coerce from the constrained in-memory representation to the wire representation.
287.
▲
by
wyager
2y ago
Somewhat unindicative title, very cool algorithm! Looking forward to using this.
288.
▲
by
wyager
2y ago
There are tons of network protocols where only certain bit patterns are admissible. The algorithm linked here is substantially more useful than just "your entire type has to be made of u8s"
289.
▲
by
wyager
2y ago
There's not really a sufficiently compelling reason to use anything except UDP for future protocols aiming to replace TCP
290.
▲
by
wyager
2y ago
You could try cutting the AI process from the internet using LuLu
291.
▲
by
wyager
2y ago
> We as people pick the winners with our money, we don't really want nice things. I do, and I reject being branded as part of "we" here; most people and orgs just have bad taste. ("Taste" at an organizational lev
292.
▲
by
wyager
2y ago
It's OK if we've surpassed the needs and observational abilities of normies and we are now purely pursuing arete for those who can appreciate it. Eventually the level of arete usually passes some threshold that enables new normie-
293.
▲
by
wyager
2y ago
A lot of sites do this, annoyingly. I hate when my internet experience is degraded because the bottom pentile of users can't figure out how to do something.
294.
▲
by
wyager
2y ago
We were very fortunate to live through the aberrant time period in which there was a truly global data network. It feels almost like an inevitable fact of entropy that eventually the bureaucrats and petty fiefdoms would catch on to the exis
295.
▲
by
wyager
2y ago
Looks correct to me, and I like that it pointed out that my final equation I wrote is the klein-gordon eqn. Forgot to mention that in the original post
296.
▲
by
wyager
2y ago
Exactly. Didn't want to confuse it with the normal lowercase `m` that might show up in a wave equation derivation for masses-on-a-string or whatever Should probably have mentioned - the final equation in my derivation is the Klein-Gord
297.
▲
by
wyager
2y ago
I don't think your explanation hits the bottom of the ontic causal hierarchy. The fact that hbar is the quantum of angular momentum can be derived from the boundary conditions of a wavefunction with a closed dimension (such as an angle
298.
▲
by
wyager
2y ago
I have read a lot of documents on ncatlab and other places to try to pin down a coherent model of the physical role of planck's constant in fourier transforms on physical systems. I understand that it often serves as the scale factor f
299.
▲
by
wyager
2y ago
> QFT fields like higgs are not physical at all (but rather give rise to physical properties) I think this is a nonsense cop-out and bad ontology. What does it mean to "be physical" if not to be causally downstream of other phy
300.
▲
by
wyager
2y ago
At some point this all kind of drifts apart from ontic science and starts to become a matter of narrative or interpretation, but I would generally agree with that. Waves are mathematically-friendly possible configurations of the underlying
More ›