skysight-inc/HackerNews huggingface dataset:
In software, we can generally agree that too many layers of abstraction introduces many issues since it is difficult to ensure each layer is perfect. For this imperfection we often pay a price: performance, maintainability, etc. However I think that often this imperfection is unintended and is a consequence of trying to make things better.

In the finance world, and particularly with mortgages, there are similarly many layers of abstraction but each layer has an imperfection built in: money.

Your mortgage, after its gone through all these layers and after everyone had extracted their pound of flesh from its value along the way ends up looking nothing like the original product. It might end up as a resecuritized security based on only the interest portion of a pool of loans or some other abomination. Just like a JavaScript application is a completely different beast from the the x86 asm executing on your CPU.

However, in software these layers exist to try to make things better. In the finance world these layers exist to only make money. To extract value from one place and move it to another. These layers don’t need to exist in this form but they do because they make people money. This is the lie.

Despite this, we can’t just remove all these layers at once but maybe we can remove one layer. Just like you wouldn’t rewrite your nodejs server in asm but might drop down to Go or something.

Alternatively you can say, “hey I don’t need this website so badly so I’m just going to not build it” and not play. Or maybe you have the time and inclination to build it “from scratch” from assembly.

Starting with a plot of land and only the money in your pocket reminds me of the true hacker spirit! :)
As for writing code, I write it cleanly and with proper, clear language in-code commenting for ME. Because I need to go look back at what I've done and why often.
How far away from that do you think we are and why?
I really hope you didn't harm anyone on the boat.
Ok I get it! It is very simple : RLE implies the removal of the cristalline lens and insertion of an artificial lens that corrects the initial ametropia. The procedure is exactly the same as cataract surgery.
The problem is that the lens is the organ that allows accomodation.
So while it is usually simple to give you a glass free vision for a given distance, you will need glasses for other distance (usually, you will have a good far vision and glasses to read) which is not something that you want when you are young.
The reasoning is that when a cataract surgery will be done anyway a few years after, it is more simple to do one surgery earlier than doing two.
Patients with extreme ametropia are more likely to accept glasses.
Finally, multifocal lenses exists, but they induce aberrations that are well tolerated when they follow the blurry vision and impairment of cataract, but not so well in previously well-seeing patients.
Most of my creativity comes from finding practical solutions to complex problems.

If something seems to complex or hard, I figure their must be an easier way to solve it.

A lot of it is stepping back and questioning the original problem you are trying to solve.
>Being exposed to pollution works against those chances, but you're still much better off exercising than not.

She won't run along roads due to high particle counts, but she'll cycle along roads because "exercise offsets it." There is no logic or consistency here. Either its still "good" to moderately exercise in the presence of these particles, or it isn't.
This is stupid. Most desktop people don't want to touch ARM anything and rightly so - Qualcomm's chips suck (Apple's do great but even they don't seem to think they're rest to go ARM Mac yet), there's no battery life advantage especially when you do all the desktop things and you have to deal with ARM snowflake crap along with vastly limited SoC support for new OS versions. And needless to say without specialized CPU support the 64-bit Intel emulation is going to be dog slow - remember emulating ARM Android images on X64?

There's literally no upside to this. I just wish AMD puts out a great mobile CPU and we can have even better competition for Intel in laptop market.

So no thanks - I'll let Intel have their laptop monopoly if that means I can run standard x86 hardware with great support for non Windows OSes.
Tapestry: Has the mythical “2-hour civ-building board game” arrived?
I'm saying Linux is "free and open," you can clearly see that in my comment.
Reportedly MS did consider buying Red Hat but backed out because of anti-trust concerns.

> "Microsoft, which, according to one source, is referenced throughout the proxy statement as 'Party A,' first expressed interest in Red Hat back in March. But Microsoft dropped out of the running on October 10, according to the proxy, 'citing concerns about securing regulatory approvals of a strategic transaction in the US and Europe.'"

Google was also considering it

> "Google, which one source said was 'Party B,' met with Red Hat in the spring of 2018 to discuss partnerships. As a deal with IBM got closer, Google continued to move forward with the sale process, but stopped short of making an offer. Though Google's former Cloud CEO Diane Greene spent a lot of time with Red Hat ahead of its sale, she struggled to get support from the company on her large mergers-and-acquisitions aspirations, according to one source. So on October 20, Google officially declined to submit a proposal and instead asked if Red Hat would explore a commercial partnership and a minority equity investment from Google."

Block javascript if you want to read the article:

https://www.businessinsider.com/red-hat-deal-talks-with-amaz...
Von Neumann: The Mathematician (1947)
This seems like a thoroughly detestable use of HN: a gratuitous, mean, and almost certainly uninformed (you spelled his name incorrectly) judgement of another human being as "overrated" or "underrated". Why not use your time to do something worthwhile?
If you are building a totally generic CSS library to use on a bunch of independent sites, then sure... utility first.

But the main reason I think semantic CSS is important has nothing to do with anything technical.

CSS is not just a technical contract with the browser, it is the place where your organization’s design language is made manifest.

If your pages match what’s in your designers’ mockups, that’s good. But if your CSS matches what’s in your designers’ heads that’s way, way better.

What that means is that “configurability” and “flexibility” and “composition” are anti-patterns.

Being able to do anything is bad.

The goal is the opposite: almost everything should be impossible to do.

The goal is that you can only do things that make sense within the design system.

That means making something that’s technically quite useless, but just barely can do the things your designers want to do.

The same applies to component names and arguments. That’s the other place where the design system contract becomes real.

So, if you’re a freelancer than yes, go utility-first. But if you work on one app day in and day out then you’re playing a different game with different goals.
The article gave a clear method of avoiding higher concentrations: stay further from sources of pollution. Even a tiny distance made a big change.

So sit away from the exhaust pipe of a bus, walk on the inside of the sidewalk, etc

Your initial comment is quite dismissive, on the reasoning that we can't see the particles, or detect them with consumer grade devices. Have you considered that you might be the sort of person who would have shouted down Germ Theory? It was quite unpopular for decades when introduced. We couldn't see or measure the germs.
Are you saying that you actually write the kind of code that I linked? Because my expectation was that you’d look at it and say “well, my code certainly doesn’t look like that. It’s quite reasonable in comparison, in fact.” I don’t think I’ve ever seen anyone write code like Dwemthy’s Array in a project that has to “do something productive”, even if they’re the only one working on it.
After the deal fell through, Schmidt literally wrote a public blog post as CEO on suns website welcoming Google's use of Java in Android.

The wiki article is leaving out a suspicious amount of facts in the case.
I agree that in principal most things are natural selection. The things that are not on a current time (a certain proportion of which bound to exist) frame are behaviors that will eventually be eliminated.
I'm honestly of the opinion that this shouldn't be allowed either. Accept that you need to name the variable 'fooErr' and just ban all shadowing
I've switched to this approach a while ago, and haven't looked back since. It makes everything so much simpler, hands down.

I have utility classes, grouped semantically into separate css files. I've built up a library of components that I use across my projects (so eg. if I need to change a button, I just change it on the component server). Encapsulating style, function and semantics in separate layers has really increased my efficiency as a developer.

Interesting challenges arise when collaborating with UX / UI designers. Quite a few of their tools (XD, Figma, etc) can output ready-made CSS blobs for front-end dev copypasta, but it's the old-school semantic CSS.

What I have found reassuring though is that in general, designers eventually come up with UI kits, and there are certain stylistic consistencies inherent to those. The kits usually translate very well to a functional CSS implementation because of that.
Auto repair is 90% diagnostics and 10% wrench turning. A lot of newer vehicles have symptom matrixes with a process for repair. Lowering the skill floor for mechanics.

What’s interesting to me about auto repair is how techs are paid. A lot of shops do book rate. Example let’s say you have to replace a front half shaft. Book rate pays you for 30min. If you take an hour to do it - you lose money.
Walter is right here. This procedure is the same (and not just for the 737 airframe family). Even though the cutout switches changed function (and this is the main area I actually fault Boeing on), if the flights had executed the cutout properly after the needed adjustments, they could have stabilized.

Source: my former business ran heavy check maintenance software for most of the world's largest airines.
> What I meant by that is that your average everyday person [...] has no practical way of detecting [nanoparticles]

How is that not true for PM2.5 pollution also? Or mercury, lead, sulfates, CFCs, hydrocarbons... Almost every regulated pollutant has significant health or environment effects at a level undetectable by an "average everyday person". Are you arguing that we shouldn't be reporting on any of this stuff?

I mean, what's the scenario you want to see? People never hear about nanoparticles from their general media until a bunch of elite scientists have already effected a mitigation plan? If these things have health effects people have a right to know, and it has to be someone's job to tell them, right?
That's more like the low end for L5, honestly. And 500k is the high end, for a top performer L5.
Topomax?
Maybe the sort of code you linked isn't the sort of code we're talking about? Nobody is running around bigco writing demoscene stuff or whatever.
That's reassuring: I'm (slowly) working through Hadley Wickam's r4ds online book, which is just fantastic. Thanks for the tidyverse tips!
You are of course technically correct, but it’s pretty well established at this point in time that the “tech sector” refers to IT and Internet companies. Taken to the extreme, you can technically call pretty much all human endeavors “technology”, so you need to follow current conventions in order to have a productive discussion.
As a long time, on and off Debian user, I've actually never had debian-installer install firmware properly. For the longest time, using the minimal install image, putting the firmware debs (or loose files) in the correct directory just plain didn't work. I think at some point, it started working and I could use wifi instead of ethernet to install, but even now the installer still doesn't install AMD firmware, so some kernel modesetting funny business doesn't work and I just get a black screen on first boot (but the system is otherwise functional). The same applies to the firmware-included non-free image.

I mean, I can (and do) manually apt-get the right firmware packages at some point, either popping a shell during install or after first boot, but it is definitely a maze of some kind, especially if you don't know what package contains the firmware you need.
> they would of beat

* they would have beaten
>This isn't your system any more than buying a CD makes the music yours. You're renting their system.

I really can't understand how people are ok with this. Now just with windows, but in general these days. Why are people ok with having things they don't really own after spending hundreds if not thousands of dollars on them. If I buy a computer, it's my computer, I don't give a fuck what operating system is on it, what fine print amd or Intel throw in saying their management systems are their property, I don't care. I'll do whatever I want with my computer and if Microsoft or any other company has a problem with it they can come sue me for all I care.
That's 3 false positives in a month, depending on how many seizures a patient suffers from, this might actually not that bad. Afaik a false positive doesn't have any direct consequences except "be careful and keep medication ready"?
Clips your data, changing the behaviour of smoothers etc, iirc gg.cartesian(ylim=...) is the thing that people usually want.
i dont reallly know that
East bay fullstack developer meetup group
If one component needs to know about the use-case it’s serving for another service in order to do its job, you didn’t factor your components correctly (i.e. either those components really are one component, or the component boundary should just be on a lower or higher abstraction layer than you put it.)

S3 is an example of a correctly-favoured service. Object storage is a non-leaky abstraction. Object storage doesn’t need to know what an object “is” or why something is storing one. There’s no use-case-specific policy that can be applied to only specific “types” of objects. There’s just objects and buckets, and policies you can apply arbitrarily to any object or bucket because they’re policies about objects and buckets, rather than policies about some higher-level thing.

If your component’s API doesn’t create a clear, obvious, “self-contained” abstraction like object storage’s “objects and buckets” abstraction, then you don’t really have an extractable component; you just have a monolith that talks to itself using an extra layer of indirection.
>Am I the only person that this is regression? How can code-duplication be defended by 'simplicity'?

Easily. People can avoid code-duplication in many ways, and some of them are harmful.

E.g. by building abstractions that get out of hand and add mental burden to track the program flow and bugs.

Or by making any small piece of code into a standalone 2-3 line function, so that anything always happens elsewhere, and keeping track of flow is made difficult.

Or by prematurely putting code into a function when it's just used in 2-3 places, and then when another need arises that doesn't fit in to the already captured function, hacking the function to handle different behaviour on different arguments/flags and ending up with monstrosities.
When considering latency, it's still not in the same league as Shenandoah and ZGC. We still had occasional GC times over a second with G1 on some production systems several years ago IIRC.
I find other people's go code is generally much more readable than other people's code in most other languages.

Go's simplicity and heavy idiomatic culture means all the code more or less looks identical. This is great for team projects.
In actual archeology, most of the innovative and interesting parts were probably also done outside of the client (the physical earth). Piecing together what wasn't recorded based on the few things that was recorded is the whole game :-)
There was a contingent of folks who argued that we should not build async/await, but that we should instead build a generalized effect system, or figure out monads and do notation, because async/await is a specific form of those things and we should wait until we can get the more general feature first. Higher kinded types is sort of in this space, GATs will provide equivalent power someday...

We rejected a proposal for dependent/pi types; we’re still adding a limited form, and may get there someday, but we didn’t want to go fully into them at first because the difficulty was high, and the benefit less clear, than just the simple version. (Const generics)

There’s a few other other features that we had and removed too I can think of off the top of my head. We used to use conditions for error handling. We had typestate.

There was a battle over type classes vs ML style modules, type classes (traits) won in the end. That doesn’t mean modules are useless...

I think the answers to these questions are very relative to your langauge’s values and goals. All of these features have good uses in other languages, but couldn’t find a place in Rust for a variety of reasons. Your language should be different than Rust, so you may find some of these features useful, and not find some of ours useful.

I would encourage you to read TAPL, I think it would help with what you’re trying to do. Oh and check out https://plzoo.andrej.com/
>I'll do whatever I want with my computer

You pretty much can, I don't understand why you're upset. Windows on the other hand is not your property.

Your laptop in this case is the CD, you own that. Windows is the music that you're renting.
The author did not even mention how Windows 10 pushes the "Your Phone" app. Which gives Microsoft full access to your android phone and your behavior and data on your mobile device. Unlike apple which provides this feature with end to end encryption.
I loved Cleese's talk and I wonder if there's the inverse of it somewhere? On the opposite side of the spectrum are those of us who make all sorts of wonderful connections but have difficulty putting A next to B next to C.

Perhaps it's Elon Musk's chats on thinking in first principles, but I'd love if anyone knows some introductions to linear, tight-knit, strategic thinking.

Edit: I also wonder if books on clarity in writing like Zissner's "On Writing Well" qualifies here. Writing is linear and the practice of it presumably should help the writer think more clearly.
How many years after we went to space using a central authority did it take before private enterprise could do it? How much did private enterprise depend on the technological development that arose from central and shared commitments to scientific development in that space?

We can have the same discussions about the NIH and new drug development (since most drugs simply can't make money). The internet, chips, Google itself was started as a federally funded post-grad project.

Things move much faster when we devote shared resources into risk taking that cannot make money. It might sound like waste, but government spending, I surmise, is what creates great economies. This occurs because technological advancement, especially those that can't obviously be exploited for financial gain in the market, are the true drivers of our economy.

Either way, we will soon begin to see who is right. There are several countries now competing with the US who were far behind when we went to our current model of low taxation, high free market. It should be interesting to see if their centralized scientific/technological systems outdo us over time.
This is great not only for accessibility but the extension gets rid of all the excess pop-ups that you might encounter when scrolling while reading.
I once thought it would be funny to offer a service that bought "bundles" of securitized mortgages, but would then separate them out and offer to sell specific mortgages to people's arch enemies who would presumably pay a premium.

the elevator pitch is "the google of mortgages".
This comment couldn’t be more shortsighted.

For one, I see Macs running on Apple’s own ARM chips a real possibility in the near future.
Can someone explain what the author meant with the following passage?

"... Navier-Stokes equations, which govern the flow of fluids, including air currents. In this case, let us hope that it does not have a real-world application."
MS removed 16-bit support on 64-bit Windows. Linux and WINE can run older Windows programs than Windows can! So, if Microsoft is the polar opposite, then Linux must be the stratospheric opposite.
> I think utility-first CSS has its benefits as well as it's drawbacks

What drawbacks?
No, I'll let you do that and then I'll show you that, irrespective of what you do—assuming the database isn't encrypted and with the DNA owner holding the key to his/her record—then you'll end up overriding the autonomy of individuals—people in our societies will be less free than they are now.

As usual, few bother to think important stuff like this through before it becomes a done deal. It would be interesting to see a class-action lawsuit against DNA database holders by those who consider their privacy invaded.

If governments don't step in to control and regulate this unholy mess soon then I'd reckon it won't be long before the lawsuits begin. I'd put money on it.
If it's a 32bit userland, then you don't have access to the other GPRs. The GPR field in AArch32 instructions is a max of 4 bits, so you can only encode r0-r15.
Can you explain why you think it makes O(n) blocks trivial to identify?

How is such identification made easier by manually writing out a `for` loop applying a function foo to each element rather than writing `map foo myCollection`?
Only browsers have this restriction.

The issue I linked above doesn't appear to explain this. I would instead recommend reading this[0] comment.

0. https://github.com/omarroth/invidious/issues/177#issuecommen...
> wouldn't it be more accurate to say that Microsoft is working on bringing x86-64 emulation to Windows 10 on ARM

Isn’t that exactly what the title says? Which bit are you quibbling with? Or has the title been changed?
That's really strange to me because I find go to be very readable. There are so few approaches to each of the basic programming building blocks in go that once you have read a moderate amount of idiomatic go, everything else just feels easy.
i've said this same thing (on r/math), because it feels like blind hero worship and fetishization, but i got pushback that "it's only human". oh well. most people don't care about the math but only about hero worship and math is just another opportunity.
Reminds me of pre digital music. Same things. Humans who knew their shit and who presented raw skill, acumen.

Yeah. I get that.

What if we are somehow forced to return? Some disaster or other.

Will we still be those same quality humans?
I don’t understand why some areas would warrant the response of “sometimes it works and sometimes it doesn’t”. What if we left other areas examined? “Let’s not bother to research sorting algorithms further. Some people write a sort and it goes fast, and some people write one and it goes slow, and that’s just the way it is”.

If a team can just “click”, isn’t it critically important to figure out why this occurs, so we can create other teams that click? It would be an awful shame if we were not as a species able to make effective use of all of us because we preferred to leave this to chance.