skysight-inc/HackerNews huggingface dataset:
> Property rights is not propping up stocks and bonds.

I'm not talking about propping up stocks and bonds, I'm talking about ensuring fair, open markets for such things. I'm entirely talking about "protecting ownership so you can invest in building things over the long term without them being taken." That same concept of the government protecting your ownership of some shiny objects applies to protecting shareholders from a company publishing fraudulent financial statements, or selling bonds that are actually objectively worthless with actual review, or shenanigans that effectively remove such ownership aspects.

> 0% is hardly a massive incentive to hold cash.

Negative rate bonds are (or at least were) a thing as well. If it costs more to put your shiny objects and fancy paper in a safe and protect it than having an account at a bank then there's incentive on it even if there are costs. And sure, even with inflation there's still some incentive to hold some amount of dollars. Liquidity has value after all. Even though I'm OK with some slight inflation on dollars I still tend to hold some amount of them. After all, I didn't buy lunch with stocks!

And even then, it is not about 0% being an incentive to hold, it is about not having an incentive to invest. As I already stated, IMO its worse for society overall to encourage people to hoard fancy paper and shiny objects compared to actually investing it. But hey maybe you'd prefer for people to not invest in bonds and what not and instead just have piles of fancy paper and shiny objects instead of roads and infrastructure and more productive enterprises. I'm sure that'll work out well for them.
I'd be quite confident that the vast majority of people who don't live in or travel to Europe a lot have never heard of it.
I guess I'm one of the rare folks who started reading TFAS and left without any big revelations or takeaways. I got bored half way through and stopped. Shrug...
Thanks for this. This all makes sense.

I mean, I figured every different size drone would handle differently.

I guess I am surprised there isn't or can't be a quadcopter simulator with really realistic physics though in this day and age. Maybe just not enough market for it for that level of accuracy and realism.
Maybe some third world countries offers itself as a Internet Heaven.
I use Proxmox since 5 years at home. Mostly docker nested in unprivileged LXCs on ZFS for performance reasons. I love the reliability. Proxmox has never lost me. They churn out constant progress without making too much noise. No buzzwords, no advertising, just a good reliable product that keeps getting better.
I have severe apnea and have been skinny most of my life, as I get older (in my mid-40s now) I can gain _some_ weight, but I'm still slim. My apnea is caused by having a narrow airway entrance and thick tongue that just completely blocks the entrance during sleep when my tongue relaxes and falls back. Has nothing to do with my weight, just the genetics I inherited. I use a CPAP that helps. My AHI is really low with it on. Now I just need to make myself go to bed earlier, I definitely have that "revenge nighttime procrastination" thing where I stay up way too late.
Spark is pretty well engineered and quite good.
I only learned about it last week because I was considering a trip to Amsterdam. But I'm also happy to have "airport" added to "JFK" "ORD" or "SFO" which strike me as obviously airports.
interesting to think about this as Philly tries to ban face coverings/masks in public (masks are already banned on SEPTA which is wild)
> I suppose the reason is because it takes more time?

I assume so. I didn't even notice that the article didn't motivate that `async: false` is bad. I always avoid it if I can since you might as well perform independent tests concurrently.

From the docs [1]:

* `:async` - configures tests in this module to run concurrently with tests in other modules. Tests in the same module never run concurrently. It should be enabled only if tests do not change any global state. Defaults to `false`.

[1]: https://hexdocs.pm/ex_unit/main/ExUnit.Case.html#module-tags
An apples to apples comparison means ... you should be picking cars that are roughly equal in price. You didn't. So it isn't an apples to apples comparison. You're contradicting yourself.

Look up what the word "average" means. If you are accusing Tesla buyers of buying privileged expensive cars, then you are necessarily also accusing the vast majority of new car buyers of the same thing. There's no way around it.

Toyotas and Kias are not representative of average new cars in America. Teslas are.
> How likely am I to break my OS with EndeavourOS are there any things I should avoid?

The exact same chance Arch has to break something: so quite likely, as in, it's not a matter of IF, but a matter of WHEN. The exact WHEN being dependent on how unlucky you are.

I'm sure I'll get a dozen downvotes and replies from people saying they've been using Arch since the beginning of time and never had an issue, but a full update of EndevourOS left me without working sound. Not ideal considering I'm applying for jobs and need sound to work for interviews.

For that I need an OS that's 100% bulletproof, not something I need to read up tutorials, blogposts, newsletters, wikis, to learn how to manage, since I don't want another part time sys-admin job, I want something to JustWorks™ without any studies or maintenance.

For a secondary tinkering/learning machine it's a very nice OS since the documentation is also nice, but I would never daily drive it on a main machine that I use for earning a living.
it's a poorly written article because it didn't explain how the wage theft happens. i mean does the pay stub simply not reflect all the hours they worked? are they talking about overtime? is this for part time work or full time? for full time, it should just be 40 hours, how does the employer not pay out the full 40 hours?
Does anyone have a link to a publicly accessible version of this paper?
It cannot be overstated that the actual study data without exception points to the opposite conclusion, that pythagorean intervals (mathematical ratios) are in fact what we prefer.

Study link: https://www.nature.com/articles/s41467-024-45812-z

Start with figure 3. Non-musicians generally favour pythagorian style harmonic ratios, while trained musicians tend to prefer equal temperament.

Each of the following intervals in the data confirm this:

- The pythagorian major 3rd ratio 5/4 is slightly flat compared to 5 semitones. Non-musicians nailed it, musicians prefer the sharp ET version.

- The range from 10-11 semitones is rated relatively high by non-musicians. This range includes the 7th harmonic, 7/4

- Even the 11th harmonic, taking place between 6(tritone) and 7(perfect fifth) is rated highly by non-musicians relatively to musicians.

- The "9" major 2nd octave, 9/4 JI, aka 14 semitones, is tuned more perfectly by non musicians (9/4) compared to musicians

Later the authors experiment with a artificial gong style instrument (fig 5). However its harmonics are remarkably close to several standard pythagorean ratios. You see 1.52f0 (slightly sharp perfect 5th 3/2); 3.46f0 (slightly flat harmonic 7th 7/4); 3.92f0 (slightly flat double octave 4/1). These harmonics are so close to a guitar or piano or human voice, it can't really even be considered inharmonic at all.

With this instrument, you get, yet again, more pythagorean intervals:

- sharp major 2nd, 9/8 ratio (makes sense; started with a sharp 3/2 and 9/8 is just (3/2)^2 modulo octaves).

- People still correctly tune the major 3rd 5/4 ratio (slightly less than 5 semitones) even without a 5th harmonic. bonkers

- Sharp 5th, which makes sense as the harmonic is 1.52f0 instead of 1.5f0

- Heavily emphasized harmonic 7th interval between 9 and 10 semitones

Later, the authors experiment with various mis-tunings of the pythagorean intervals (Fig 8). The most highly rated intervals are slightly sharp or flat from JI. This is evidence for JI intervals being pleasing--slightly sharp or flat creates a pleasing rhythm of Just harmony. It's like just harmony but better.

In conclusion, essentially every plot in the study points towards pythagorean, mathematically tuned harmony being more pleasing. Even in surprising ways. I could not find a single data point indicating otherwise, except for indoctrination of musicians towards ET leading to things like preferring sharp major 3rds and not recognizing the harmonic 7th interval.
Just because your position is unpopular doesn't make it wrong.

async/await is particularly damaging because it breaks the paradigm of Javascript. That no one can draw a picture explaining it is a huge problem, and it encourages people to write callback hell code by hiding how ugly it is. Unfortunately, whether the code is pretty or ugly the massive webs of nested callbacks are still a source of massive complexity and potential failures.

I constantly see tests in the wild that are passing even though the assertions fail because people don't understand the concurrency model they are using. And at least 60% of the time there was no reason for that concurrency to exist in the first place, except that it's what the code example looks like.
Interesting that it cost 2x as much as SpaceX's Dragon, and was delayed by 7 years. Is this due to Boeing being a traditional defense contractor that's used to squeezing gov contracts for as long as they possibly can, and getting away with it? Like mismatched incentives?

I know that's a really loaded and biased question but should there be this much of a discrepancy between one private company (arguable one that's even more experienced) and another (one that is smaller?)
Hi Ian!

Portland has also been working on the “next steps” pointed out in this article. Street bioswales provide absorption and holding capacity. Downspout disconnection programs and new build codes drain rooftop rain locally on the property or out to the street instead of directly in to the sewers.

I think we have an easier time due to our lower density. Most lots have decent amount of exposed ground for rain infiltration, and the area has well draining soil. Tougher for cities more tight and built up. I think Seattle codified water management before the latest building boom so hopefully they will do alright too!

https://www.portland.gov/bes/stormwater/about-green-streets
Tbf the fans may be broken on them, or at least not far from being broken.
I.e., plan to waterblock it.
Why x86 doesnt need to die
That this is quid pro quo doesn't in itself imply anything unusual. Your comment could be rephrased as "investment through the use of a company's resources is an exchange of business". Quid pro quo can be used to describe an illegal exchange involving a politician, as it could be considered political bribery, which may be why you thought there was some negative implication in the term, but there is nothing unusual in a business exchanging the use of its own resources for an investment or partnership in another company.
> Cost: one speaker and tubes was probably cheaper than 200.

I'm pretty sure there were 2 speakers in each arm rest. I think it's more about them being harder to break and cheaper to replace. When I flew on an airline that used them, they came clean in a sealed bag. They may have been brand new, or at least cleaned and sterilised. Electronic headphones are unlikely to be as cleanable.
Would you say the same about say a freelance developer that "invests" 500 hours of work in exchange for X% stake?
Even if you're not much of a tinkerer, Ben Eater's videos are massively helpful if you want to truly understand how computers work. As long as you come in knowing the rudiments of digital electronics, just watching his stuff is a whole education in 8-bit computer design. You won't quite learn how modern computers work with their fancy caches and pipelines and such, but it's a really strong foundation to build on.

I've built stuff with microcontrollers (partially aided by techniques learned here), but that was very purpose-driven and I'm not super interested in just messing around for fun.
Stack Exchange expands beyond Q&A format with 'Discussions'
Yes, I have similar thoughts. Getting older, traveling more, seeing the hustle and bustle of large cities, becoming more aware of all these details that many people don't think about, etc...has all greatly expanded my world view. One of the big thoughts that these kinds of realizations have left me with is how vanishingly small each human's view is compared to the total scope of the universe. None of us is able to escape the confines of our skin and our personal perspective. However, we all tend to extrapolate this vanishingly small slice of ours to the whole universe. Problem is, it's very difficult to figure when that extrapolation is valid and when it is over-fitting, which is probably the root of a lot of human conflict.
This comment is just a veiled mattress ad :p
My suspicion is that learning music theory (for any specific cultural norm) is a bit like learning about font kerning: https://xkcd.com/1015/

Many of the auditory things that trained musicians describe as creepy or weird, seem unremarkable to me.
Yeah I'm also on the schema first side of the debate.

I think for me it comes down to a few key points:

- APIs are forever, the choice of language/framework is an implementation detail

- Constraining yourself to what can be represented in the specification is better than generating a specification from implementation that may not be capable of expressing the full details

- When working with diverse languages it provides a common ground/language for discussing API changes. Eg: if you have java backend, kotlin android, swift iOS, react/whatever web you can bring everyone together with the spec

- Subjective, but a good spec will include a bunch of documentation and examples that tend to create a lot of noise in the code. I personally prefer to keep this in the spec and the implementation smaller

I think the main counterpoint to this is that you can generate the spec and then take that and change your mind if you later change language/framework etc - it's not a one-way door.

My biggest bug bear is that regardless of spec first or implementation first, you should have something you write once and generate the rest of the glue from (eg: docs, client sdks). Writing each piece manually/independently always leads to drift and bugs.

(I'm working on my own little openapi -> typescript code generator over here https://github.com/mnahkies/openapi-code-generator - eventually plan to support more than typescript, and adding typespec support is something I'm currently considering)
There is a reason why I rarely trust teetotalers.
Newer Apple computers have unified gpu and cpu memory, so they are BLAZINGLY fast with local models.
NYC already has plenty of unpaid parking tickets from the UN diplomats. It won't be anything new.
I really like EndeavourOS, compared to something like Manjaro. It's essentially 99% vanilla Arch with a few QoL improvements and a distinct theme. That's it.

Manjaro, on the other hand, breaks too many things and goes off the beaten path more than I care for. Pamac is kind of junk too, as I prefer yay.
Sagittarius a* Event Horizon Telescope Results. VII. Polarization of the Ring
For all of my side projects, it's a `TODO.md` file that I typically break down into three sections: "Features, Bugs, Future". Each item is a bullet point, which I rearrange as it suits me.
I'm from the EU and had the impression that there is more talk about those regulations than actually enforcing them.
The only way a bespoke component model framework works is if everyone adopts it. All the multitude of Java component-based web rendering systems failed.

Luckily for react everybody did basically adopt it so their component model did not fail.

It is always funny to watch people mock Java in the 1.0 version of their framework and some other thing and then come back and look 5 years later and their stack is easily or greater and complexity than the old Java stacks.
This seems like it is entirely a human problem, not any kind of technical failure. The fix is the same as it always was -- people need to be trained to say no by default, do not trust inbound calls ever, and never ever share your credentials.

If you follow that advice, this attack poses no risk other than annoyance. If you do not give your password to the creep who calls you claiming to be apple support, you will be okay.
Cranking up the parameter count is literally how the current LLM craze got started. Hence the "large" in "large language model".
https://en.wikipedia.org/wiki/Truth_Social has some pretty interesting details!
Having written quite a bit of open API specs, I don't agree with you. Json is hard to read, yaml has own quirks, especially when you try to spilt it into parts.
Amazon also tries to invent own language for describing apis, so I guess they are not happy with open API too.
Anyway, without ability to generate code from spec, there is not much use from it. Code gen/nswagger/open API generator and others produce terrible code, at least for java/c#/typescript(there's 4.1k open issues for open API generator), using custom generators for codegen make problem less painful, but that is additional burden, I'm looking for better alternative, would be very interesting to see what they will do with code generation.
Does this work with VMWare Workstation as well? I'd love to run macOS in a VM on my Linux desktop for the few apps I have to use on macOS...
The technique was part of the functional programming pop culture 10-20 years ago.
I'm not sure if we're talking about the same things. I am not confident that I understand your comment well enough to confirm/reject, so I'm going to clarify for that reason.

> I understand it that the above quoted text represents the device's long term private key?

The device owns an internal, inaccessible long-term 32-byte key called UDS. (I called it "device secret" in other comments.) The device contains fairly minimal firmware, primarily there to initialize the device and accept the bytes that are the program-binary.

When a program-binary is sent, it is written to memory. Then a secret is derived for the program, called CDI. Then device-firmware passes over control to the firmware-binary by jumping to the entry-point (IIRC).

`CDI = blake2s(UDS, blake2s(program-binary), 32-byte-user-secret)`. (Note: this is done in device-firmware and only the CDI is exposed to the program.

> You can do this:

I think here we're on the right track, but I'm guessing you're suggesting an rough idea. So, yeah, from the CDI one can derive a key for identity.

So the current protocol describes using that deterministically generated identity for authentication, and generate random bytes for deriving an ephemeral keypair for the key-exchange.

The client only needs an ephemeral keypair so relies on proper randomness only. (And it keeps a record of the identity public key, to verify its proof.)

> Next problems are replay attack prevention and forward secrecy. The two-birds-with-one-stone for that is for each side to:

I think these are not possible. Assuming (for this discussion) that your client is honest, you start off every session with proper randomness in your (unpredictable) ephemeral key. So from the first message on, replays are not feasible. Forward secrecy should be covered given that the whole session key, as it is established, is based off fresh input from randomness.

This, of course, leaves open the discussion on long-running sessions that keep using the same key without rotation. This is not addressed.
Chromatic 3: Visual testing integrations for Storybook, Playwright, and Cypress
Thanks for the input mNovak! That's a great perspective :D. I'll definitely consider it :D
Choosing a street at random, there are red "Congestion Charging © Central ZONE" signs on both sides of the road, as well as a huge painted © on the road lane for turning into the road.

https://www.google.com/maps/@51.5168161,-0.1655445,3a,49.9y,...
I've refused to work on AI-related initiatives at previous jobs, and will again if they ever come up. I have deep ethical objections about LLMs in terms of power use, consent for providing training data, fitness and safety of LLM-powered solutions for problems that cannot afford errors, and the potential and already-happening effects of replacing human workers without a suitable safety net for when their incomes disappear.

Crucially, I do not think predictions that all these issues will improve is a good enough justification to keep innovating before they have improved. Harm caused now is not undone just because we fixed the flaws later.

In that sense: I think feeling weird about the hype train is completely normal, but for different reasons. I do not want any complicity in legitimizing LLMs.

Besides ethical concerns, I also think the myriad applications of LLMs are mostly misguided market waste. In that sense, profiting off the hype could be seen as you simply slurping up some of that waste for yourself, and while I don't like that function of the system, I think the system is the issue rather than you trying to exist within it. If you don't share my ethical concerns or aren't objecting to the market's function of trying all ideas and assuming the good ones profit, then you're probably not really doing anything scummy by your own standards.
Connecticut, USA wants to penalize insurers for backing fossil-fuel projects
The Playstation, at least, supports quads as a draw primitive. It does decompose these quads to tris for rasterization[1].

The Nintendo DS actually supports both tris and quads as rasterization primitives, which has some interesting consequences for shading[2].

[1] https://psx-spx.consoledev.net/graphicsprocessingunitgpu/#gp...

[2] https://melonds.kuribo64.net/comments.php?id=13
As someone who wrote a custom dsl to Open API spec script (in Ruby) I'm really interested to see if type spec would be a better output. Our spec is > 12k lines and we haven't even included everything that needs to be defined.

Does anyone have experience layering this on to an existing API (as opposed to defining the API and then building the code)?
You know what? Screw these greedy bastards
(Boots up windows laptop)
I’m just not going to use them anymore
(Goes to Amazon.com to order milk)
It has to be open source
(Unlocks iPhone)
Thoughts on Permanence
https://en.m.wikipedia.org/wiki/Quorn

The UK has been eating fungus based meat replacements for decades.
Most definitely. I wish I could foresee a time when the people growing the crop are the ones who mainly benefit from it. But, I doubt it.
I did :D I used screen.studio
>Changing between terminals at Heathrow is much less fun.

I decided to stay at a Heathrow airport hotel a while back. Turned out I had to change terminals and I'm pretty sure it took me at least as long as getting a shuttle bus to one of the hotels would have taken.

You often have to walk quite a ways too.

Overall though Heathrow is pretty good among the large European airports.
I've studied many systems over the years and never found any that matched or outperformed their backtests. So far our live results have hit between 1/4 and 3/4 of backtest performance depending on the model. Needless to say the high inflation and high interest rate market climate over the last two years hasn't been seen in the rest of the backtest period, but conditions are starting to normalize now.

Nevertheless, it would be prudent to expect any algorithmic trading model to underperform its backtest going forward, but there's enough leeway in the CAGR and max drawdown figures to underperform the backtest and still produce substantial alpha, especially for the more advanced models.

Right now the models are specialized to trade equities. I may develop new models that trade commodities in the future though.