HNHacker News
TopNewBestAskShowJobs

correct_horse

532 karma · joined March 1, 2019

submissionscomments
correct_horse··on Lying to the Ghost in the Machine
> Every time you add an abstraction layer to a software stack you can expect a roughly one order of magnitude performance reduction, so intuition would suggest that a WebAssembly framework (based on top of JavaScript running inside a web browser hosted on top of a traditional big-ass operating system) wouldn't be terribly fast;

I realize this isn't the point, but WebAssembly is arguably on the same level as JavaScript, the alternative being that WebAssembly is lower. (WebAssembly still needs to call JavaScript to manipulate the DOM, so doing anything UI with WebAssembly is kind of like an abstraction layer built on JS). There's a reason cryptominers sometimes use WebAssembly. That's not to say that V8/Spidermonkey on top of glibc on top of Linux isn't bloated...

correct_horse··on We should pay politicians more
This would most probably result in corporations laying off the lowest paid employees and paying contractors to do the same work.
correct_horse··on Technology Without Industry
I can suggest "The Selfish Gene". It is about evolutionary biology, not molecular biology. I'm not really sure what you're looking for.
correct_horse··on Technology Without Industry
> Biology is non-toxic

Except for the toxic organisms (poison frogs, newts, fish, etc.). The best you can say on this line of thinking is that biology is biodegradable, except even that isn't true. Modern diatoms don't biodegrade - they mostly turn to sediment at the bottom of the oceans. Further, coal is mostly made of what used to be woody (lignin-containing) plants that couldn't be biodegraded when lignin first evolved[1]. The unique aspect of modern industry that makes it not sustainable is its scale and speed. The solution might involve industrially creating organisms with a similar scale and speed (like ones that can metabolize plastic).

1 https://en.wikipedia.org/wiki/Coal#Formation

correct_horse··on Dependency on rust removes support for a number of platforms
I did not realize how inconsistent python versioning is, or that compatible release (`~=`) doesn't use the semver way. https://www.python.org/dev/peps/pep-0440/#compatible-release
correct_horse··on Dependency on rust removes support for a number of platforms
LLVM had a C backend which went unmaintained until the Julia folks picked it up and updated it for LLVM 10. I'm not sure about its current state.
correct_horse··on Dependency on rust removes support for a number of platforms
pyca/cryptography replaced C code with Rust code without bumping the major semver. This broke people's CI because it removed support for certain platforms which Rust barely supports or doesn't support at all. People are arguing over this change in the github comments, but the problem from my perspective is just with semver. The maintainers didn't do semver right.

Edit: the maintainers didn't do semver right because the maintainers didn't do semver

correct_horse··on NYT reporter falsely accuses tech investor of using a slur
The authors of that article pulled off a motte and bailey fallacy[1]. The motte is "There should be message forwarding limits and group size limits on encrypted messaging platforms".

> It’s interesting to note that WhatsApp has restricted message forwarding for exactly this reason [preventing false information spreading like on social networks]

We can all agree message forwarding limits are a good idea - no one like spam. The bailey is implied to be that we should keep tabs on identified extremists even in encrypted platforms.

> I share your worry about the encrypted apps becoming, essentially, huge shadow social networks.

> there’s now this debate about whether it’s good that all these unsavory characters from the dregs of the internet are disappearing from big social platforms, or whether it’s dangerous to have them congregating in spaces where researchers, journalists and law enforcement can’t keep tabs on them as easily.

The authors (or speakers, as this article is a dialog) never make the bailey argument. Instead they make arguments that would naturally lead to the bailey, if taken seriously. Private messengers could become "shadow social networks"? Well if they do, they must be policed like social networks. Also note in the second quote how the speaker distances them self from the argument with "there's this debate". They don't mention the alternative to the current situation, so it is left to the imagination of the reader - should we allow "unsavory characters" back on social media platforms? Or is the alternative that we continue keeping tabs on them on the encrypted messaging apps?

[1] https://en.wikipedia.org/wiki/Motte-and-bailey_fallacy

correct_horse··on A Polar Vortex collapse sequence has begun
Hm. I didn't consider that interpretation.
correct_horse··on A Polar Vortex collapse sequence has begun
Slight correction - temperatures are not higher than ever before. The eocene (60 million years ago) was 10-14 degrees hotter than now. That level of warming would be bad to say the least, but it has easily been this hot before.

Also relevant, a few times in the Pleistocene, 20,000 years ago, temperatures peaked a couple degrees hotter than they are now.

correct_horse··on Google Bans Parler from the Google Play Store
The bitcoin folks correctly point out that if cash were invented today it would be made illegal. I suspect that if unmoderated conversation with strangers were invented today it would face a similar fate.
correct_horse··on The Fatal Flaw of Ownership Semantics
I probably shouldn't have said newly C++, but my frame of mind was relative to the lifespan of the language.

> Rewriting the Rust std lib to use RefCell everywhere would be possible, but would make it almost entirely useless.

Maybe not useless, but certainly worse than it currently is. The point is that you can switch one function to using RefCell (a breaking change, but) totally possible

correct_horse··on The Fatal Flaw of Ownership Semantics
This article compares the hierarchical nature of the type system of OOP languages (think Java) with the hierarchical nature of ownership in languages with Ownership/Move semantics (Rust and newly C++). The author notes that "composition over inheritance" is a rejection of the strictly tree-shaped OOP type system. In the same way, Rust's `RefCell` is an escape hatch from the strict hierarchy of ownership, maintaining a run-time invariant of one owner rather than a compile-time invariant.

One difference I see between these two escape hatches are switching costs. Rewriting the Java standard library to use composition and not inheritance borders on impossibly difficult. Rewriting the rust standard library to use RefCell instead of &mut everywhere would be arduous and possibly automatable, but not impossible.

correct_horse··on YouTube-dl source code encoded in two images
I'm not sure if this is a joke, but I'll humor you. Yes - it's called git.
correct_horse··on Cargo-style dependency management for C, C++ and other languages with Meson
Python is a bad example. Cython and pypy are very widely used. IronPython, Jython, etc. also exist. Go is a better example, but even Go has a gcc backend, although it is rarely used in production as I understand.
correct_horse··on Why mmap is faster than system calls (2019)
mmap is more general than memory mapping files. It "establish[es] a mapping between an address space of a process and a memory object". In particular, many allocators (malloc and friends) use mmap to get a block of memory from the OS with mmap(0, size, PROT_READ|PROT_WRITE, MAP_ANONYMOUS, -1, 0); or similar.
correct_horse··on Why mmap is faster than system calls (2019)
Call me pedantic, but mmap is a syscall. The title would have been better as "Why memory mapped files are faster". The author does address this with "Mmap stands for memory-mapped files." It does? I thought mmap stands for memory map. To be clear I enjoyed the contents of the article.
correct_horse··on Compact nuclear fusion reactor is 'very likely to work,' studies suggest
Nuclear fusion happens in man-made thermonuclear bombs. I believe it also happens in research reactors that require more energy than they produce due to various inefficiencies.
correct_horse··on Water on Mars: discovery of three buried lakes intrigues scientists
It won't sublimate if it is always in the shade/in a cold region. See https://en.m.wikipedia.org/wiki/File:Phase_diagram_of_water..... At martian surface pressures (close to 0) it needs to be warmer than ~ -60C to sublimate. Interestingly that's roughly the average temperature measured by rovers. https://en.m.wikipedia.org/wiki/Climate_of_Mars#Temperature
correct_horse··on JDK 15
gson uses reflection to serialize types, including standard library types, which are not guaranteed to have the same fields from one release to another. Presumably the people who write the jdk realized this potential source of bugs and tried to prevent it from happening, meaning fewer ambiguities about what changes are breaking at the expense of breaking gson (and probably others). see: https://github.com/google/gson/issues/1216
correct_horse··on In spite of an increase in Internet speed, webpage speeds have not improved
Blinn's law says: As technology advances, rendering time remains constant. Usually applied to computer (i.e. 3D) graphics, but seems applicable here too.
correct_horse··on The Case Against OOP Is Wildly Overstated
This is generally accurate, but I want to highlight the awesomeness of opaque structs. In C you can declare a struct in a header file, but not its fields ie struct point;. Then in the corresponding c file you can write out the whole definition ie struct point {x: float; y:float;};. Any code that includes the header can pass pointers to struct point (or pointers to pointers, etc) but can't directly pass points around because the compiler doesn't know their size.

All this said, this is basically OOP in C, and the code is still bound to the data, only it is bound by naming (point_add()) not by a scope (point.add()).

correct_horse··on Typometer: A tool to measure and analyze the visual latency of text editors
In addition to these excellent points, the "1 ms" pixel response time is measured grey to grey i.e. favourable to the display and not real-world. The bigger problem with advertised pixel response times is there is no industry standard measurement procedure (which grey to which grey?, is hdmi processing latency counted?), so pixel response times are vague, mostly useless marketing.
correct_horse··on Launch HN: Openbase (YC S20) – reviews and insights for open-source packages
I was going to ask how you plan to prevent fake reviews, but this mostly answers that. Curious to see where you'll go after being stretched too thin.
correct_horse··on Linux kernel in-tree Rust support
Shoutout to the lovely pyo3 library for letting you incrementally rewrite small parts of your Python in Rust.
correct_horse··on Linux kernel in-tree Rust support
I'm a bit uninformed as well. Obviously it must use assembly in some places, it has makefiles for building and some scripts in perl. Here's what a cloc clone has to say.

    tokei
    ===============================================================================
    Language            Files        Lines         Code     Comments       Blanks
    ===============================================================================
    ASN.1                  11          484          343           33          108
    Assembly                3         2751         2450            0          301
    GNU Style Assembly   1296       370153       270691        56418        43044
    Autoconf                6          347          303           20           24
    Automake                3           31           23            3            5
    BASH                   54         1991         1438          321          232
    C                   28971     19846129     14634535      2351170      2860424
    C Header            21110      6056898      4465297      1010398       581203
    C++                     8         2313         2016           68          229
    C++ Header              2          125           59           55           11
    CSS                     1          137           80           29           28
    Device Tree          3351       900862       735380        54238       111244
    Gherkin (Cucumber)      1          252          174           50           28
    Happy                   9         5750         5061            0          689
    HEX                     1           86           86            0            0
    INI                     1            7            3            3            1
    JSON                  328       174872       174872            0            0
    LD Script              15          412          317           48           47
    Makefile             2587        64666        43896        10957         9813
    Module-Definition       2          124          109            0           15
    Perl                   53        40583        31126         3931         5526
    Python                118        36932        29072         2980         4880
    ReStructuredText     2621       548840       417105            0       131735
    Ruby                    1           29           25            0            4
    Shell                 556        85666        59725        10972        14969
    SVG                    59        39038        37555         1405           78
    Plain Text           3230       239573            0       197373        42200
    Unreal Script           5          716          446          162          108
    Vim script              1           42           33            6            3
    XSL                    15          300          183           78           39
    YAML                  921        91167        72962         3985        14220
    ===============================================================================
    Total               65340     28511276     20985365      3704703      3821208
    ===============================================================================
correct_horse··on YouTube deleted an electronics repair channel [video]
The banned channel apparently contained mostly "vintage audio repair", not exactly Google's bread and butter. Also they allow numerous other creators doing repair (ifixit, louis rossman, even the channel that posted this video).

This probably isn't an anti-repair move, but a Kafkaesque bureaucratic one. Still an annoying problem.

correct_horse··on 1:60 scale Boeing 777 made from manila folders
Upon first reading, I thought this meant baggage claim carousels
correct_horse··on LIVR: Language Independent Validation Rules
All the examples are for validating JSON, and the documentation repeatedly mentions JSON, but I can't tell if this project is usable with non-JSON serialization formats. It never explicitly mentions that it is JSON-only.
correct_horse··on React Native's re-architecture in 2020
Tl;dr React Native communicates with native threads over json, which can be slow. Soon the JS will call native (UI) methods directly.
← PreviousPage 2 of 5Next →