skysight-inc/HackerNews huggingface dataset:
They were clearly referring to the OS of a device someone would browse on, not the OS of a network device.
I'm more looking forward to my 2023 WebMIDI Wrapped.
It seems that you can use whatever ORM you'd like. ActiveRecord included.
Slightly off topic I suppose, but RISC-V CH32V003 https://github.com/cnlohr/rv003usb is $ 0.10 https://www.aliexpress.us/item/3256804850399956.html?gateway...

Crazy.
> Why do they persist with models that don't represent reality despite knowing it?

Why do physicists ignore friction whenever possible?

In general, for any task, you take the simplest model that represents the aspects of reality that you care about. But you stay aware of the limits. That's true in physics or engineering just as much as in economics.

That's why NASA uses Newtonian mechanics for all their rocket science needs, even though they have heard of General Relativity.

That's why people keep using models known to have limits.

> [...] sage voices echo the standard dogma [...]

You do know that most of published economics is about the limits of the 'standard dogma'? That's what gets you published. I often wish people would pay more attention to the orthodox basics, but confirming well-known rules isn't interesting enough for the journals.

So if eg you can do some data digging and analysis that can show that maybe under this very specific circumstances restriction on free trade might perhaps increase national wealth, that can get you published. But the observation that most of the time free trade, even if the other guy has tariffs, is the optimal policy, is too boring to get published.

Compare also crap like 'Capital in the Twenty-First Century' that catapults its author to stardom with its comparatively boring refutation by orthodox economists that no one cares about.

> [...] dragged into the doldrums by policy posed by useless models.

Most orthodox economics is pretty unanimous about basic policies: for free trade, against occupational licensing, for free migration, for free movement of capital, for simple taxes without loopholes, against messing with the currency, against corruption, against subsidies, for taxes instead of bans (eg on drugs, or emissions, or guns), against price floors or ceilings or other price controls, etc.

Many doldrums happen when policy ignores or contradicts these basic ideas. Alas, economics 101 is not popular with the electorate almost anywhere.
I suggest that any JIT implementation will be faster than CPython default install, including the old ones at Xerox PARC, Genera and TI.

Calling out to C libraries doesn't count for CPython performance, that is C code, not Python, and any language with FFI can call into C libraries.
Average health insurance cost in the US is $5,250 per year, which would put disposable income just below Norway. The median American would need an extra $15,000 in expenses each year to have less spending money than the median German. To get down to UK or Italy levels of disposable income, the median American would need an extra $20,000/year in expenses. Cars, housing, and health insurance aren't that expensive, especially for the median American.

Typical Americans really are wealthier than typical people in other developed countries. As you said, they own cars (which tend to be bigger and more expensive than typical cars elsewhere). They also tend to have bigger houses with more amenities (air conditioning, dishwasher, clothes washer/dryer, kitchen island, etc). Some may consider these uses of wealth to be gauche or indicative of something unhealthy about American way of life, but that doesn't change the fact that they are uses of wealth.
There is no one to blame for, except the Russians. Me, being a born Russki, lived there until my pubic hair started to grow, speaking Russian and enjoying the Russian culture written, filmed and spoken - what the heck is wrong with you guys?
Sign up for business, get your install issues sorted out, then “downgrade” to 1 gbps.

(Assuming internet is a set and forget thing once it’s up and running)
You have done a lot for a student, your should be able to write up a great resume!

If you want, send me an email and we can work on it ?
I feel that Optane is a missed opportunity due to economics - the cost of adapting our algorithms to multi layer storage (breaking the abstraction) is much more expensive then the economic benefits of nonvolatile "RAM". Perhaps the cloud was the Optane killer - who needs nvram when you can just up the number of machines
> Either we want people to do things for us, want it super fast, and want to pay everyone for every second of their time.

Yes, you either pay people for every second of their time, or pay enough money for their work hours. There's no way out of this.

A courier or a taxi driver does not chose to sit on their ass the entire day. You can get a hundred orders in a row, or you can have no orders for an hour or two, and you have no control over that. And it's not like they can just get up, get a cup of cofee and go to a second job in the meantime.
> it displays the entire area for the entire time and switches frame content almost immediately.

I've heard this called the sample-and-hold effect. It looks a bit like a fast slide show, and really stands out in high-contrast, steady motion scenes.
Oh, I didn't have any cycles.

I was exposing a git repository as a DAG of directories via FUSE, and was translating git internal IDs, based on hash, straight to inodes in a one-to-one fashion. Git doesn't allow cycles (unless you break the cryptographic hash function).
Interesting. Which warehouse are you using?
Broadly, if you're happy with Django and haven't felt the need to transition to SPA, power to you. This is the case in some industries. It's generally not the case in b2c, though, and if you haven't felt the pain yet then you likely aren't in touch enough with your customers (or you haven't connected the dots).

I don't need to sell you on the concept though I will address your comment in depth.

In general, React (especially with typescript) provides a far better developer experience than Django+Templates. The latter is extremely brittle, difficult to test, difficult to refactor, difficult to organize. The former is robust, typed, testable, easily refactored. It's simply quicker to work with React. And this has quadratic effects on how quickly work gets done: The whole stack is easier to work with, which has gains on every level such as learning pace, testing, including third party libraries, deploying, finding and fixing bugs, ...

The advantages of an SPA are an extension of this. You get to move more logic in this frontend layer. Routing at the frontend layer is mainly a performance thing: You don't get to re-download and re-render your entire page when going from, say, viewing "Produc 1" to viewing "Product 2". The whole structure is the same but the content changes = you should only get to update the content, right? If you handle routing at the frontend level, this is something you can achieve.

But routing in frontend also enables some new things you just cannot easily do without it. For example now it's trendy to have apps that open content (such as a post) which opens in a preview window/drawer (saving your current state), but if you reload the page or share the url, it loads in its own individual view. Why is it trending now? Because SPAs have enabled that behaviour.

GraphQL integration is definitely not something that is required, and in fact in ~30 client projects of this type, I've only ever done it twice, for two people it was actually relevant for.

But: You generally want an API anyway. Writing your frontend<>backend communication as an API means you can offer it to your customers as well. It's a good pattern to follow, IMO. And if you're going to have that API, then separating the frontend into an SPA is much easier, because you can use that API to drive all the communication. This makes you a user of it (dogfooding).

As for forms -- Almost all form validation should happen both in the frontend AND in the backend, this is a textbook case of something which should be (mostly) duplicated. The backend MUST validate the input at some layer, lest you end up with security issues. But the frontend SHOULD also validate it, because it's a terrible experience to fill in 15 fields, submit, then see a "please correct the errors below" message with 3 of your fields red, your chosen password gone, the captcha to re-do, and that's if you ever manage to get good errors out of the backend because sometimes it just says "This value is invalid" and you have to manually figure out what's happening there (which for normal people means you'll sometimes hear "your X form didn't work" with zero additional feedback).
An atomic read-modify-write. Atomic non-seq-cst load/stores can be cheap.

/Overly pedantic
If there is some reason over here isn’t the same as over there then there will be a mechanism as to why that is the case and you will want an explanation.

You want your physics to apply everywhere and that’s why you start with the assumption that the same laws, constants, etc apply everywhere.

There’s no “ope stuff is just different over there” in physics, you look for those inconsistencies and then you try to explain them.
https://en.wikipedia.org/wiki/Eug%C3%A8ne_Fran%C3%A7ois_Vido... says he stole a lot of money from his parents' bakery, but wasn't imprisoned for that (though was for plenty of other crimes).
> Git repositories sometimes have submodules. I don’t understand anything about submodules so right now I’m just ignoring them.

Submodules are interesting, because they’re next to unusable from a user perspective (they’re a pain to maintain and interact with unless you never ever update them) but they’re ridiculously simple technically which I assume is what made them attractive.

A submodule is an entry in “.gitmodules” mapping a path to a repository URL (and branch), then at the specified path in the repository is a tree entry of mode 160000 (S_IFDIR + S_IFLNK), whose oid is the commit to check out (in the submodule-linked repository).
Exercise is difficult, lack of sunlight increases depression, and very few bikini beach parties ;)
Lithium is light years ahead.
> Why does “innovation” have to go hand in hand with fucked up labor practices?

While still losing a billion dollars a year, or more, for years.
This! I need to escape. Where is the promised land of opportunities these days?
Thankfully, there are a few projectors with very quiet fans. I haven't kept up with the current models, but Sony made some roughly eight years ago.
But then you can't just reset the state when crashes happen and data corrupts
OK, but if you've elevated phones to that level, is it any surprise that 13 and 14 year olds also see them as indispensable?
Knowing apple’s marketing moves, they could definitely do that: just use a single number to describe memory. And then pretend it’s a big number.
> browsers may even ignore your network's DNS settings

They should't. Bypassing policy is malware behaviour.

Funny that they ignore "my" network DNS, not ISP's. (in the name of freedom)
It's more likely in that environment than in prison, but I also kind of agree with GP, why do the people doing the right thing get saddled with remmediation duty on top of doing something they may even be volunteering to do? Asking a bit too much of good natured people I feel.
Visual Echos for stable AI animations
We recently introduced visual echos in AI animations. It is a novel way to create stable AI videos with Stable Diffusion based on ControlNet.
Edit: yes
For those who resonate with "why might this be useful", here are "plain git" alternatives to this tool:

> searching for a function I deleted

git log -G someFunc

> quickly looking at a file on another branch to copy a line from it

I use `git worktree` to "mount" long-running branches much to the same effect as Julias tool. To quickly look at a file from a non-mounted branch/commit, I use:

git show $REF:$FILENAME

> searching every branch for a function

git log --all -G someFunc

Note that -G can be replaced with -F for a speedup if the pattern you are searching for is a fixed string.
I think LLM is ready for non-critical-path NPC chatter that you "overhear" in the game.

Putting it in the critical path will take a lot of development/testing.

https://github.com/opyate/godot-llm-experiment
Yes, he's describing evaporation. Here's a thread about it, basically the answer is "we don't know" https://physics.stackexchange.com/questions/77130/why-does-p...
Silly hack of a product. x2 PCIe for Optane, 2x for NAND. Meant compromised bandwidth for all! The fact that it actually had value in some cases highlights how cool it could have been if it was a proper hybrid design.
If you can go negative but there's a floor on how negative you can go, is it meaningfully different from not being allowed to drop below zero in terms of worst case complexity?

The order of trades still matters in that case, right?
What other things do you think contribute to points?
UAW is also committed to unionizing Tesla.

https://www.reuters.com/business/autos-transportation/uaw-la...
Arena's rule engine and AI is based on Duels of the Planeswalkers, so they had several years to develop the AI player.
Extremely handy, saving these. Thank you.
Regular maintenance for bridges means tensioning cables, tightening loose bolts, repainting exposed parts. Not redoing the foundations every month.
What awful AI-generated illustrations.

Anyway, is there any justification for treating spacetime as a smooth manifold, except for mathematical tractability?
Based on real punishments. And people had their hands chopped off for petty theft too.

The historical element is more relevant. In the UK (and perhaps the US) in 1723 it was made illegal to hunt a rabbit - punishable by death.
Yeah I'm sad to see Optane go. I bought a few DCPMMs myself (and had to upgrade my workstation CPUs to support them) to test out the capabilities and maybe even write a little toy OS/KV-store engine that runs as a multithreaded process in Linux using mmap'ed Optane memory as its persistent datastore (never got to the latter part). The "do not use mmap for databases" argument would not apply here as you wouldn't cache persistent block devices to RAM, but the "RAM" itself is persistent, no writeback or block disk I/O is needed.

Intel discontinued/deprecated Optane, before I could do anything really cool with it. But Intel can probably still reuse lots of their cache coherency logic for external CXL.mem device access.

One serious early adaptor and enterprise user of Optane tech was Oracle. More specifically Oracle's Exadata clusters (where database compute nodes are disaggregated from storage nodes that contained Optane) and connected via InfiniBand or RoCE. And since Optane is memory (memory addressable), they could skip OS involvement and some of the interrupt handling when doing RDMA ops directly to/from Optane memory located inside different nodes of the Exadata cluster. I think they could do 19 microsecond 8kB block reads from storage cells and WAL sync/commit times were also measurable in microseconds (if you didn't hit other bottlenecks). They could send concurrent RDMA write ops (to remote Optane memory) for WAL writes into multiple different storage nodes, so you could get very short commit times (of course when you need sync commits for disaster recovery, you'd have to pay higher latency).

With my Optane kit I tested out Oracle's Optane use in a single-node DB mode for local commit latency (measured in a handful of microseconds, where the actual log file write "I/O" writes were sometimes even sub-microsecond). But again, if you need sync commits across buildings/regions for disaster recovery and have to pay 1+ ms latency anyway, then the local commit latency advantage somewhat diminishes. I have written a couple of articles about this, if anyone cares: [1][2].

Fast forward a few years, Oracle is not selling Exadata clusters with PMEM anymore, but with XMEM, which is just RAM in remote cluster nodes and by using syscall-less RDMA ops, you can access it with even lower latency.

[1] - https://tanelpoder.com/posts/testing-oracles-use-of-optane-p...
[2] - https://tanelpoder.com/posts/testing-oracles-use-of-optane-p...
Hmm. I don't know whether you edited your comment or I misread it, but I was sure you said "the Atheist believes in just one more God than the Monotheist"

The difference though I think is at the core: the monotheist believes in the concept of a god, they just believe the others that people worship are false gods.

The atheist doesn't believe in the concept of a god at all.
I think a lot of people explicitly do not want to bother with playing essentially paper magic, because it requires quite a bit more concentration if your board state is complicated to not miss any triggers or phase change too far accidentally.
It's all about the distinction between contract and implementation.

The difference with bugfixes is that pre-bugfix the intended API contract - including behaviour, not just signature - was not respected by the implementation and post-bugfix the implementation becomes (more) correct WRT the intended contract.

IOW:

- On a semver patch bump the API contract does not change but the implementation of that contract was incorrect.

- On a semver minor bump the API contract receives an addendum, the previous contract is still in effect as a subset of the new contract.

- On a semver major bump the preexisting API contract is voided and is replaced by a new contract. The new contract may or may not include all or part of the old contract as a subset. Breaking change => major bump is an implication, not an equivalence: one is completely free to bump major purely for marketing reasons.

Of course, the difference between theory and practice is that they're the same in theory: the contract is an ideal, the implementation may come close but will always fall short in some way.

I feel like many of both semver detractors and advocates get lost in theoreticals, reality is fuzzy, just use the damn thing. Or don't and pick up another scheme, but be abundantly clear about how your versioning scheme works so that users can make sense of it and automate version requirement declarations in their dependency manager.
I'd argue that you see the same thing in Sweden as in Norway, but without the oil in Sweden's case.

The music industry in Sweden is huge. Check out who wrote and produced many of the US top hits over the last 30 years. Not to speak of the local Swedish bands who make it big internationally.

The software industry is also huge in Sweden (Spotify, Skype, Minecraft, Battlefield, Klarna, Candy Crush, etc). The explanation for this is largely that the kids who grew up in the late 70s and in the 80s got very good support from their parents in getting their own home computer where they could learn to program. This is very similar to young chess players in Norway.

Sweden also punches well above its weight in some sports. Winter sports are kinda a given for a Nordic country, but tennis doesn't fit into that mold. Yet Sweden dominated tennis for a while. This was due to parents and society supporting young kids learning to play tennis in the 60s and 70s.
REST Framework is frankly... flawed. Full of good ideas, but in practice, it leads to development hell unless you're very rigorous with it.

FastAPI is the gold standard, which in the Django works means Django-Ninja.

If you've been building individual React components and integrating them without going the SPA route, then while there are some upsides to that, you are doing a lot of the effort but not getting most of the benefits.

If you don't need an SPA, then you don't need an SPA. Nobody should be getting this development pattern shoved down their throats. But from what you describe, it sounds to me like you went with a bad approach altogether, so no kidding it created more problems.

(Not to make it sound like a "no true scotsman" with the whole "bad approach" thing, but this is why it's important to get people who really know their shit in driving refactors like these, and can make a strong plan ahead of time, detailing what value is brought at each and every step)
This was a pleasant read and as a serial immigrant I can relate to moving countries on a hair trigger impulse. Like one line in a movie that reveals something about a different culture which captures your imagination. Makes me chuckle.

Reality is never quite like the movies but there's definitely something there. You do get some sense of fulfillment and you do usually get to experience what you wanted... The problem is usually not that the culture doesn't have what you thought it had (it often does), the problem is that there are often unseen downsides that simply did not occur to you and you could not imagine being a problem before you made the move since they are not a problem in your own culture. You don't notice what your culture gets right.
Oh jeez I was so excited for that!
Maybe Singapore? There are lots of English-speaking employers, the weather is great, and the better apartments come with rooftop tennis, gym, and pool. MRT is amazing and allows you to quickly go to free parks like the botanical garden if you feel like walking around outside. That will surely help with the winter blues. Lots of university students, too. But alcohol and/or parties are extremely expensive and dorms are typically gender-separated with security guards.
Don't you mean you run the restricted router in front of the ISP router?
Yes. GR does it and GR gives good descriptions for a lot of observed phenomena.
> And that's the difference. When you perform TouchID authentication, the secure enclave can decide to release a secret that can be used to decrypt your keyring. We can't easily do this under Linux because we don't have an interface to store those secrets.

> The secret material can't just be stored on disk - that would allow anyone who had access to the disk to use that material to decrypt the keyring and get access to the passwords, defeating the object.

I'll provide a broader explanation: you cannot encrypt your key with a fingerprint.

A genuine "throw away the key" lock is only possible when the decryption key is completely erased from memory during the screen lock, and you cannot use your fingerprint or face image as a key by itself.

A screen lock using stored secret is inherently incapable of providing encryption at rest. It's like a password on a sticky note.

A "throw away the key" is only possible with a password, or a smartcard.
A wonderful, bold, and colorful idea, already thought through carefully. And 5000:1 odds! It'll be more interesting how many more dozens of minds will find more testable consequences. Is it too much to hope that some untestable ideas will deservedly die?
A hallucinating Siri would be way more useful than the current version…
Great. So the question is: what is the intrinsic value of intrinsic value? I'm thinking either 0.6 or false.
It's pretty damn atrocious. I run a different startmenu and taskbar, but it still bugs me.

I still prefer Windows with ads modified to hide those ads over MacOS though.