skysight-inc/HackerNews huggingface dataset:
stat to get filesize is a pathlogically bad pattern on Windows. If I remove the call to fileSize() in kvtest and instead replace it with 16k (since the max size in the post is 12k), I can significantly improve the time measured on Windows 10.

Before:

C:\temp>kvtest run test1.dir --count 100k --blob-api
--count 100000 --max-id 1000 --asc
Total elapsed time: 9.495
Microseconds per BLOB read: 94.950
Content read rate: 104.0 MB/s

After:

C:\temp>kvtest run test1.dir --count 100k --blob-api
--count 100000 --max-id 1000 --asc
Total elapsed time: 5.218
Microseconds per BLOB read: 52.180
Content read rate: 313.3 MB/s

showing here the stable-ish numbers after a couple of runs of each version to let the cache warm up.

Windows is a completely different beast than Unix and you need to know the beast to tame it.

You might say that stat+open+read+close should be compared/measured together. In that case my answer would be that you would not read all files in a directory in this way on Windows anyway. You'd use overlapped I/O with buffers of FS cache granularity (which is 64Kb, unless it has changed in recent versions of Windows). It wouldn't matter for smaller files anyway (since the OS aggressively reads ahead when you open a file) and would be better for larger files.

It is a bugbear of mine when I see complaints about Windows from people who never actually tried to optimize for the OS.

reading blobs in Sqlite from db is still ~3x faster on my Surface Pro 2017 (don't call it Surface Pro 5!), but that's to be expected.
Why? It's no worse than S-expressions.
I've never heard that being counted as anything but trolling.
What do you mean with quantum encryption? QKD (Quantum Key Distribution)?

Though the concept seems nice, it has quite a few issues in practice. Such as distance between coupled devices, and the need to have a dedicated physical communication line.

Oh and before you think you can just chain several devices to get longer distances: this opens you up to classical MitM attacks.

Source: https://www.nature.com/articles/npjqi201625
Namespaces are horrible in Python because the Python XML libraries are deficient. They're generally fine in e.g. Java. (Unless you're trying to represent QName typed data, but that's very niche.)
YAML 1.2 fixed this making booleans just true/false and it's a real shame that a lot of things still use 1.1
If by "Introduction to Algorithms" we mean the infamous book by Cormen et al...

When I propose to use it to prevent sea rise by drying the sea I only half jest. It's IMO one of the worst books to use except as reference when you already have a good grounding.
Yeah, I figured it was used to post-process it or something, but perhaps they simply have a diagramming department that uses that.
> Since this is now a 'security' issue will its implementation be opaque?

Security by obscurity doesn't generally work. FWIW, here's what WebKit has to say about what it'll block: https://webkit.org/tracking-prevention-policy/. I hear that a specific list may also be released at some point.
>and we know it would be a larger tax bill for us.

It would quite possibly be a net saving. The UK, for example, spends less public money on healthcare than the US. There's no necessary reason why you should end up paying more in taxes for universal coverage than you pay currently for insurance.
You think the moral has nothing to do with our deliberate industries?
The main issue I had with TOML is how much more syntactically noisy it is. Equivalent files with 2-3 levels of nesting usually become at least 50% longer than equivalent YAML.

More here : https://hitchdev.com/strictyaml/why-not/toml/
Availability of ER is still incredibly important. Nobody will refuse to be taken to hospital if they're in serious condition.

In my experience from Poland, people who lose health coverage find a way to get it back if they really need it. Get any legal job, enrol in school, apply for disability, etc. Sometimes pleading with the staff to skip the eligibility check works, too. And if everything else fails, the out-of-pocket costs aren't insta-bankrupting.
GitHub syntax highlighting is coming. If anyone wants to help with that that would be awesome. One of the top outstanding issues. Syntax highlighting is there for sublime and codemirror but one bug left in those implementations and would love help getting syntax highlighting generation going for Monaco and linguist so we’d have it everywhere on GitHub.

Your impression is correct though, without highlighting it’s awful. Try the Tree Language designer app to see it with highlighting, type checking, autocomplete etc...there are interesting ways to accomplish everything without syntax, often not obvious. But tooling is essential to make it better than existing options. Help wanted!
AWS Fargate Fast Autoscaling
Last I checked, the Sonos app is better than the SiriusXM app. Not that I use it much anyway, I mostly use Sonos/Sirius via Alexa control.
Does this address that once I am at 1% I charge it up to 5% in order to stay on the chat all the time?
>I do wonder if focusing on doing the very simple things well first (like python does right now), would be a better strategy, or it would just make people ignore the language because the simple things are already covered everywhere and not interesting enough for bringing people (compared to the amazing stuff Julia can do with supercomputers/clusters and state of the art stuff like Zygote).

This is just the difficulty of open source. I am a mathematician by trade, so I work on DifferentialEquations.jl, Zygote.jl, new forward-mode AD, and showcase this stuff in neural differential equations as part of my work. While it would definitely be nice if someone focused on startup speeds, it's not going to be the DiffEq/Zygote people, because it's not the stuff that I/we know. Julia has tons of great scientists and mathematicians, so the libraries in that area are pretty fantastic already, but we do need to find some people who know how to write apps and do devops. I plan to actually find and hire some devops people to help out Julia here. Julia has shown from its libraries that it's worth supporting, so now we should tie a bow around it for less hardcore folks.
I found "Introduction to Algorithms" to be _waaay_ too dry to deal with in beginning, though I'd welcome something else to get through the detail.

Personally I'd use Cormen as "dictionary" to get into detail of stuff I first read in A.D.M.
You're referring to extended attributes, which are like a key/value database for each file. Wikipedia says:

> In Linux, the ext2, ext3, ext4, JFS, Squashfs, Yaffs2, ReiserFS, Reiser4, XFS, Btrfs, OrangeFS, Lustre, OCFS2 1.6, ZFS, and F2FS[9] filesystems support extended attributes (abbreviated xattr) when enabled in the kernel configuration.

> The Linux kernel allows extended attribute to have names of up to 255 bytes and values of up to 64KiB,[13] as do XFS and ReiserFS, but ext2/3/4 and btrfs impose much smaller limits, requiring all the attributes (names and values) of one file to fit in one "filesystem block" (usually 4 KiB).

Applications that make extensive use of xattrs typically recommend one of the FSs that allow full-size xattrs. For example, OpenStack Swift, an object storage service, recommends XFS as a backing storage. (Source: I operate Swift clusters at $dayjob.) But if your metadata is not larger than 4 KiB, any production-quality Linux FS will do.
And they will get the yields in 7nm up and wafer costs down. It ultimately is about the economic cost of computation, which is still dropping. Smaller node sizes are not the only way to get more transistors and/or reduce total costs.
It’s terrible! A waste of time! No one should use it! It’s definitely not the future!
The ADA thing is relatively new. If you go anywhere in California, not just areas with a large homeless population, you'll find most businesses do not have a public restroom. This is different than every other state I've been to. This is because California has the Unruh Civil Rights Act, which makes each ADA violation subject to $4000 statutory damages, regardless of the actual damages. Thousands of these cases are filed every year in California. California businesses don't want to be exposed to this liability, so most of them have closed their public restrooms.

This lack of bathrooms creates a sort of death spiral. In high homeless areas, the few remaining ones have to serve more homeless people. Dealing with a parade of homeless people using public bathrooms as a shower or shooting up causes the remaining businesses to close their bathrooms. It becomes more difficult for homeless people to use the bathroom, so rather than go to the trouble of finding one, many use the street.

On the enforcement side, I'm not really trying to be proscriptive, just descriptive. Jail is not a nice place. The threat of being arrested though is a deterrent to crime. If there is no deterrent to pooping on the street, and the alternative is difficult, people are going to poop on the street.
This is a result of corn subsidies, not a naturally economically efficient land use.
Backups on databases like PostgreSQL are strongly consistent, regardless of where you take it from (master or replica). Postgres replication is strictly sequential wrt transaction commit order.

As such, splitting the database may incur in significant consistency issues that a backup doesn't incur into.

I believe this splitting technique is not a good one except for potentially narrow use cases.
I've been working on a software that's eavily based on XML and in a number of occasions I've been glad XML is strict and verbose.

you can quickly tell if an xml document is malformed (good parsers will tipically point you to the un-closed tag).

Yaml on the other hand would probably load anyway, with the application receiving garbage data, potentially misdirecting the application behavior...
Doesn't this not scale? Such that you would need millions of enormous towers to store enough energy to power the US total electricity usage?
It doesn't make sense to swap out other programs just to load video that will be immediately discarded after displaying. It makes more sense to have limited download and playback buffers and store most of video data on the disk.
I don't think the people leading the charge down in the LES are disproportionately rich, at least unless you count the implicit value of a rent regulated apartment, what they are is disproportionately older. And I get it--change can be disorienting, construction is noisy, and so on. But this is literally Manhattan we are talking about. If not here, where?
Would love to know why my comment got downvoted...
Capitalism is the source of PC culture not leftism.
I think that's why they said "modern ponzi scheme".

And no, mom-and-pop investors don't have full knowledge, not like insiders do. The fraud would come in if the insiders are being anything less than perfectly honest about current condition, future prospects, or their expectations.

Of course, this might not rise to the level of criminal fraud. But when you look at something like Groupon, which fell 90% quite quickly, and which had insiders taking money out early on, it's reasonable to suspect that at least some insiders knew what they were selling to the public was dubious, but did it anyhow.
That would involve your computer being already compromised. If that's the case AND you have enough bitcoins to warrant running a quantum computer worthwhile, you're not securing your coins properly.
> My key point about Moore's law is that it's about being able to 'throw new hardware' at a problem. If you're changing the game by saying, hey we've now got 1000 cpu chiplets [...]

You're ignoring the physics. You can do all you want with new hardware designs, larger dies, more CPUs etc but ultimately it cannot make the same exponential gains that came with process shrinkage because power consumption and heat dissipation problems increase with every extra transistor if the process size remains the same.

I'm not saying gains cannot be made without shrinking, but they will be incremental, at the most linear with a short window, but they will not be exponential and they will come with another cost (more power consumption). For Moore's Law to be revived, look to material science for answers.
My cursory survey of config / serialisation formats concluded that nothing is close to being good.

It's overly verbose, and hard to understand XML, it's no comments son, horrors of yaml or some okay format that doesn't have parsers for the languages (plural) you are using on your project.
Implementing QuantLib is also an interesting read on how the open source C++ library was built.

Although is a library for a small niche is interesting how Luigi Ballabio explains the process with some comments of why some decisions have been taken and some corrections/modifications that happened in the library.

https://www.implementingquantlib.com/posts/implementing-quan...
Thank you, I was reading the comments exactly to figure out if there was a FUSE sqlfs module. TL;DR this URL describes that, yes, there is. Why is this relevant? Because this way, you keep the flexibilities of a filesystem and, as a consequence of it being able to function like a filesystem, you keep the "power of Unix/Linux" ie. all your <asterisk>nix [1] tools keep working.

[1] Calling it Nix confuses with NixOS...
Its astounding people still have streaming subscriptions when you can just lookup and find a free version for whatever you wanna stream.
I use JSON in the end. I prefer to write TOML, then parse that into JSON. This seems to strike a nice balance between human/machine write/read. It's simple enough to reason TOML, even if it gets verbose. If I have to write YAML after 2 layers I usually write it as JSON and include the JSON in the 2nd level of key.
Sounds good -- but, if we move all of the web apps to be native apps, then I want a native environment that can safely run untrusted code.

Currently, none exist that I'm aware of. Phones aren't doing well on that front, and we haven't finished moving to Wayland yet, so that mess still exists. X11 is heaven for anyone who wants to fingerprint a device. And we still have to figure out whether or not we're going to allow high-resolution timers or raw access to the GPU, which is itself a pretty big fingerprinting target.

On mobile phones, the closest thing I have to a good adblocker is AFWall+, which doesn't work on iOS, and only blocks via the built-in IP-table, which isn't good enough to make me feel safe running apps like Facebook or Twitter. And most mainstream Linux distros (with a few exceptions like Qubes OS) are not shipping with the kind of process isolation that's necessary to guard against malware.

I guess MacOS is making some progress in this area at least? But for the most part, none of our computer environments were designed to run untrusted code -- Linux in particular was primarily designed to protect you against other users. The prevailing advice was, "just don't download malware", which doesn't reflect how people today use computers.

I want to stress -- there could be a solution to this. We could make a user-friendly native platform that replaced the web. But I don't think anyone has made one yet.

I want to advocate that it's a good idea for us to solve that problem (or at least think about it) before we get rid of Javascript. I don't care what happens on the web, except that the web is currently the most user-friendly, widely-used VM that we have. I see a lot of people suggesting that we burn that down, but I'm not sure they've really thought about what's going to happen afterwards.
Thinking about the origins of apps like this always feel like a chicken and egg situation. Did someone look at the battery level indicator API and ask what they could do with this? Or did they have the app idea first and wondered if there was a device API to make it work?
I was unaware of pinboard.in, and am now going back through my 'net searches to see why it didn't show up. Thanks for the pointer.

I'm not sure it will meet my needs, but it looks to be close, and will certainly be worth a proper assessment.
The superior replacement for XML, JSON and YAML is the SQLite .db file. Easy to “parse”, easy to manipulate programmatically, what more could you want?
>If you argue that X is better than Y and Z because X is all you know, you just sound like a cultist. Learn first, argue later.

Apparently, you didn't look in the mirror. Oh, well. Thank you for proving my prejudices right with this post =).
To be fair, there were debuggers pre-1.0, but the changes in the language syntax and compiler broke them. That one was just the first one to work with the new architecture that was released on the second half of last year (and since the language is now stable, we can expect it to stay functional and improve over time). There is also another debugger being made with a completely different strategy (embedding the debugger within the compiled code instead of interpreting it):

https://github.com/oxinabox/MagneticReadHead.jl
This page is paywalled. Wonderfully, if you have the noscript extension installed, it won't hide the content.
I think this article is a medium at best quality article about this important subject.

If this article seems biased and it probably is a bit, that shouldn’t take away from the reality of how these attention seeking narcissistic people on both sides are holding and broadcasting these views not because they believe in them but because others elevate them in society for them or shower them with praise.

If the article had mentioned corrupt tv preachers making money and having power by claiming to be Christians then that would have probably helped not make it seem so one sided.

I know people who say “I’m a communist” but they don’t actually do anything to back up that statement and are effectively tourists. I often say to them that they and their other communist friends could form their own commune, invite the poor and needy to join them and share their wealth to support each other and be equal. The problem with that of course is that camera lens the person wants to buy, and the expensive craft beer they like drinking and the new MacBook they want would all go out of the window whilst people they don’t know would suddenly have more food, shelter etc.

Truly good people don’t generally feel the need to tell people about the good things they do. You can find them volunteering quietly at food banks, churches, after school clubs, synagogues, mosques, youth sports leagues etc.

Anyone in this day and age who goes around telling others that they are a flat earther is either mentally ill or trying to be more interesting and is attention seeking.
Not local, but you can start using S4TF immediately via Google Colab.

https://colab.research.google.com/github/tensorflow/swift/bl...
When I watched Jennifer Garners Peppermint (2018) I naturally assumed typical Hollywood hyperbole. But then I saw this:

Skid Row, Downtown Los Angeles https://www.youtube.com/watch?v=KbTSDuQET94
WSL1 is terrible for I/O (which I suppose this is). WSL2 should be adequate.

Perhaps Dokan? Dokan has a FUSE wrapper [1]

[1] https://dokan-dev.github.io
What I most disliked about using Slack on a dev team was that there was no way to locate the information later. Suddenly, a discussion about the project requirements or technical implementation would take place. That decision became embedded in the project. But if you weren't there for the discussion, you had no input. And later, when you wanted to review the decision and the underlying facts, there was no way to find it.

So I would spend a lot of time reading back through the discussions in the various channels. And sometimes those micro-decisions were later contradicted with no acknowledgement.
It is not the same situation. If you write/read video sequentially, you get speeds about tens of Mb/s, and with swapping you get random access with speeds < 1Mb/s on HDD. So having limited memory buffer for video is better for the whole system.
Not only that, there are asymmetric encryption algorithms not vulnerable to Shor's algorithm, we're just not using them yet (because they're slower and haven't been as well-studied as RSA or ECC).
> My (naive?) view is that Nginx caches static files by default after the first hit

That's likely the OS's filesystem cache, not anything in nginx. If you're on Linux, you can confirm this by clearing the OS filesystem cache with

$ sudo -i
# echo 3 > /proc/sys/vm/drop_caches

and checking if the next hit on your URL looks like a cold load.
The fact that it injected something wasn't hidden. The fact that it injected a unique ID wasn't documented, thus could be considered hidden.
> it's not clear wether each member has the same amount of "power".

Each member gets one vote. Membership to the group is decided by the group, with a goal of no more than 1/3 coming from one company. The distinction I pointed out is both technically and practically correct.

https://github.com/ampproject/meta/blob/master/GOVERNANCE.md
Nespresso has ruined hotel coffee
It's also quite relevant for anyone with a morbid interest in those "logical" conlangs that try to divide the world into some sort of rational categories (Lojban, Ithkuil etc.). Though perhaps demotivating for those who attempt to create/learn one ;-)

Also, be sure to read Borges' "The analytical language of John Wilkins" if you like this sort of thing :)
Chat systems with artificial constraints seem to be all the rage: Must include picture, self-destructing after 5 seconds, 140, errrr, 280 characters.

And now fatalistic battery level requirements.

I can only wonder what the next iterations will include!

edit: This is the third app I've ever bought (others: Purify and PocketCity). I appreciate the creativity and simplicity.
My point was that the optics of it are terrible, as evidenced by the linked thread.
Cracking a public key in 10 minutes is much harder than cracking a public key (at all). Considering we haven't cracked anything yet, I wouldn't be worried about that. Also, if you're transferring thousands of bitcoin and want to be safe, you could always privately send it to a miner rather than broadcasting it. In that case the tx would have 1 confirmation before the the public knows about it, requiring them to also pull off a 50% attack.
Yeah, so far as I know the only algorithm that provides an asymptomatic speedup (for AES or similar symmetric key crypto) over a classical computer is Grover's algorithm. That would reduce a 256 bit key to 128, which is hardly disastrous.
Not necessarily. It's entirely possible to keep a daemon running with the loaded runtime to speed up start time. I'm not arguing if and whether these languages are suitable for scripting rather startup time alone need not be a disqualifying factor. If you evaluate holistically and arrive at a language you'll always have one thing or the other that is not as what you want.
Swapping is mostly random access operations, writing small blocks here and there, HDD can do about 100 seeks/sec, and it gives speed less that 1 Mb/s while sequential read/write gives speeds of order of tens Mb/s.
>But last week, her caregivers found her listless and bruised, reports the AP.

>In addition to Marium eating plastic, biologists believe she was pursued by an overly aggressive male during the mating season.

>"We assume she wandered off too far from her natural habitat and was chased and eventually attacked by another male dugong or dugongs," Jatuporn Buruspat, director-general of the Department of Marine and Coastal Resources, told the AP.

It seems that Marium died after being attacked by one or more males. Although the article mentions plastic in her intestines, nowhere does it say that the plastic was the cause of death. There is a good chance that a lot of the marine life invests plastic and we just notice it when we perform a necropsy after a death.
should just boot while charging