skysight-inc/HackerNews huggingface dataset:
ReMarkable Updates Software to 2.6 with Improved Features for Reading
Including pinch-to-zoom, PDF link navigation, and original ePub format. Excited to see this update!
"Is this what senolytics do?"

I learned today that senolytics are molecules that "... can selectively induce death of senescent cells ..."[1]

Which is interesting but you can already do this with exercise.

Nick Lane wrote a fascinating book[2] about this subject which suggests that your internal mitochondrial population is under selection pressure from your own activity.

If you don't put any pressure on it, energetically ill-performing cells are allowed to thrive.

[1] https://en.wikipedia.org/wiki/Senolytic

[2] _Power, Sex, Suicide_
It's super simple and it works for you - yeay! great!
If it will continue to work for you - double yeay!

However, as soon as I read, I saw a lot of red flags:

- Do you really want to copy from a development computer to your production? No staging at all? ("go test" doesn't mean that you have 0 bugs)

- Are you really sure that everything works exactly the same on different versions of GoLang? (Hey, a new guy in your company just installed unreleased Go 1.17, build on his notebook and pushed to production)?

- That VM with systemd died at 1am. No customers for you until 7am (when you wake up)

BTW. I am not saying that you should do Docker or CICD. The thing which I am saying that when you cut out from your process too much, you are increasing risks. (As an example, you didn't remove unit tests part. Based on "Anything that doesn’t directly serve that goal is a complication" you probably should have. However, you decided that it would be way too much risk)
>"The Carolina Reaper is a cultivar of the Capsicum chinense plant.[1] Developed by South Carolina breeder Ed Currie, the pepper is red and gnarled, with a bumpy texture and small pointed tail. In 2017, Guinness World Records declared it the hottest chili pepper in the world, surpassing the previous record holder, the Trinidad Scorpion "Butch T".[2]"

[...]

"Scoville scale: 1,569,300 on average SHU"

Related:

Scoville Scale:

https://en.wikipedia.org/wiki/Scoville_scale
Seems a bit brittle.
Facebook’s testing a new design for its new post composer on iOS
I kinda like it. What do you think?
The Wikipedia article gives examples of safety tests where the T3 tested as relatively safe: https://en.wikipedia.org/wiki/Volkswagen_Type_2_(T3)#Safety_...
HN died on me before I was able to add the link of little utility I cooked to readd those totp seed phrases: https://spa.bydav.in/otp.html
Release of format preserving encryption in Python
It takes way less time than building these vehicles will and can be done cheaply with local electricians. It’s strange how common magical thinking about EVs is, like electricity is this newfangled thing that we don’t understand and need massively new, poorly understood infrastructure. We don’t. And that’s a huge advantage.
Please tell me you have photos of that driving setup.
This is an excellent summary of the problems with social networks as currently implemented. All the incentives are pre-wired to make them horrible places.
This isn't necessarily true, especially for the original building program. Pre-war apartment buildings for the masses (Zinshaus) were raised quickly and weren't maintained well. E.g., before regulations outlawed the cheaper variety in the 1990s, cheap apartments often lacked a bathroom of their own and relied on shared facilities. The public building program, on the other hand, was up to modern standards (and taking pride in doing so), while it was still aimed at efficiency and never intended to rival the residential buildings raised by private ownership for the middle class. So, if you expect high rooms, stucco, etc, you're probably in the wrong market. (Also, you may not be part of the intended audience, anyway.)
In theory they should address different needs, however many celebrity scientists have proclaimed that "philosophy is useless", as if the scientific method is the only path to knowledge and anything else is hearsay. It's silly that they think they have any authority on this, really.

https://qz.com/627989/why-are-so-many-smart-people-such-idio...
Not dismiss but inquire.

I don't know enough about Pine, but aapl/goog have had hackers battle testing their platforms for a while. I don't see how an open platform can leapfrog ahead unless aapl/goog truly are sabotaging security for "big bro"

yes, cloud is a big hole, but are we hiding from the law? aapl only responds to warrant requests -- supposedly.

(on a side note, afaik, aapl is building their own baseband proc, which presumably will be a good thing for security)

What you said makes a ton of sense, but curious to see in practice how the security of such a device will hold up. you'd have to expect that the platform will have holes, being so new -- and that there wont be enough eyes on, not without adoption. paradox.

yes, open device means far greater flexibility on security posture but this presumes a mature, battle tested tool set. (and may or may not be built on a better foundation than corporate closed phone tech -- hence inquiry)

contrarily and back to my original inquiry -- i still wonder if there are fundamental design choices inherent to Pine that separate it from (or bring it on par with) commercial offerings. (besides those elucidated by you and another commenter -- thanks). for instance, physical boundaries such as a secure enclave, etc

i challenge the notion about aapl and casual hackers. every non-trivial platform has bugs, whether open or closed. there isn't a way to casually own an up to date iOS device, for instance -- if one had such an exploit it would be worth a lot of money to aapl or a broker

sorry for free form reply
https://theremotework.xyz
I was able to use my experience implementing C++ name lookup rules to make a less complex one for D:

There's no notion of a "primary" template. Templates are looked up like functions are.

C++ has rather complex function overloading rules that differ substantially from template overloading rules. The former is a hierarchical list of rules, the latter is based on partial ordering. D uses partial ordering for both.

D doesn't need argument dependent lookup, because it has modules.

D lookup sees all the declarations in a module at once, not just ones prior to the point of use.

The end result works pretty much the same, and hardly anyone notices the difference. Except for that last point - in C and C++, the order of declarations is inverted. The private functions come first, the public ones last, because lookup is dependent on the lexical order. D code is written with the public ones first, private ones last.
I have my setup so that you can create a shell environment specific to the project associated with the working directory. For example, I can invoke

edit-env -ds dump-data.sh

and it will open a script for editing which will only be available to run in the project's directory. It would be callable as the bash function `dump-data`. I've got lots of useful little things like that now that I wouldn't necessarily want to be stored in the project's VC but that I find useful.
There is no evidence of the link between sleeping sickness, EL, and Spanish flu.

> Since encephalitis lethargica’s (EL) prevalence in the 1920s, epidemiological and clinical debate has persisted over whether EL was caused by, potentiated by, or merely coincident with the Spanish influenza pandemic. Epidemiologic analyses generally suggest that the disorders were coincidental.

https://en.m.wikipedia.org/wiki/Encephalitis_lethargica
https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2778472/
> They drive about 18 miles a day on average

The LLVs don't drive for an hour a day and sit in the parking lot turned off for 23 hours a day. Many routes might be 6 hours or more. You need vehicles that have AC or heat and the ability to run for an entire day. The differential cost for such a vehicle is not the cost of a battery. I'm not saying the current purchasing process is waste-free, but you need to use realistic numbers.

The longest route is about 185 miles in Phillipsburg, KS. There are averages, medians, and modes, none of which are the right numbers. The average isn't as important as probable mileage.

For example, say a bus carries a maximum of 80 people. When 10 people get on your bus, your costs aren't 12%.
Not to mention the huge amount of cumulative energy consumption on those wasted cycles.
Yes, that is indeed what I said.

edit: everyone has a threat matrix they have to deal with.
I wish they could extend these protections to local software. Imagine if all of your devices had a single "disable telemetry" button.
What is vertical scaling?
Everyone has a test environment. The lucky ones have a different environment for prod.
That is not within the CA Attorney General's control. The statute (CCPA) specifies opt-out, not opt-in, for most consumers. (The exception is for children under 16, who get an opt-in process.)
Docker is like MongoDB. It was cool for a while, until everybody realized you don't actually need it.
Docker isn't as hard to learn as the author makes it out to be. You can learn it in less than 5 hours (take a 10 hour course at 2x the speed). Golang takes significantly longer to learn. This may sound obvious, but the speed of learning depends on what you already know.

A docker container is instantiated from a docker image, it's similar to object oriented programming: an object is instantiated from a class. Want to manipulate containers? Use 'docker container ...'. Want to manipulate docker images? Use 'docker image ...'.

There's also a differentiation from production vs. development environments. How do you onboard new developers? If you use docker, you can put a docker-compose.yml file in the repo and when you onboard a new developer, it's as simple as 'git clone ${the_repo} && docker-compose up'. If you want to use docker in production, you're probably using Kubernetes, and I would agree that there's an increased cost in complexity. Want to scale the docker containers across multiple servers? The logical choice is to use Kubernetes to orchestrate the containers. If you're scaling vertically, sure, use your current method. Golang is fast.

As your company grows & scales, I think you'll run into deployment issues using scp for deployments. What happens if two developers deploy at the same time? Ideally you put every deployment through a single "pipe" where if two people deploy at the same time, one deployment/testing process would run after the other in a serial manner, causing the second deployment to fail if there were a conflict.

Arguing about tech turns into a religious debate at a certain point. Use docker/Kubernetes if you need to, and if you can get by without using them, don't use them. Docker is awesome for solving versioning problems and onboarding new employees. Kubernetes is awesome at scaling and deployments. If your employees all agree to use the same version of software, there's no need to use docker or Kubernetes.

But hey, at least docker/Kubernetes give you the choice to think freely and if you see some cool library that you want to use written in some obscure language or version, it's easy peasy.
I think this is particularly dangerous with python. Some of the things it installs will compile c dependencies for the architecture you are on, I thought?
The press release is specific and limited too:

"The newly-approved regulations ban so-called “dark patterns” that delay or obscure the process for opting out of the sale of personal information. Specifically, it prohibits companies from burdening consumers with confusing language or unnecessary steps such as forcing them to click through multiple screens or listen to reasons why they shouldn’t opt out."

https://oag.ca.gov/news/press-releases/attorney-general-bece...
Do you have an article that explains this approach in just a little more detail?
I understand that, but an infinite loop is not a valid response to a program's preconditions being unfulfilled.

The infinite loop is a landmine left in the field.

Handling the negative -1 with a log error and an assert, would be better than an infinite loop.

Infinite loops can damage even other programs by hogging the cpu. They are far worse than an exception or an std::exit.

I think in the authors example, having sway fail to parse JSON would have been a better fallback than having the entire system lock up.

I don't want to be over dramatic but leaving that infinite loop in there is the type of mindset that leads to horrendous code bases decades from now.

Sway and Wayland was created to get away from the warts of X11. This infinite loop is bringing the new effort closer in line with its ugly older cousin.
Yes, and when winter schedule starts, children will stay in a bed an hour longer, and in springtime, children will have to get up an hour earlier again. What have you gained? Nothing.

You've actually made things worse, because now some people get up earlier/later than others, creating confusion amongst people that need to align their schedules.
What's crazy is that apparently there's a "fallback" Azure AD authentication endpoint that is a delayed read-only replica of the production endpoint with a subset of the features. During the last global AAD outage, they claimed that they learned their lesson and improved the failover to the fallback endpoint. That didn't seem to happen...

What is more crazy is that low level service-to-service authentication in Azure is primarily based on Azure AD. This includes Key Vault and Storage Accounts. Both were mentioned in the Microsoft notification page as affected by this outage.

How can anyone build a reliable service on top of Azure if what is essentially the failure of the "Office 365 login" also breaks your VM's access to its SSL certificates (or whatever)?
Huh, WebRTC for the Web 2.0 2010 era. Nice.
Interesting. Stack Exchange has a truly awful dark pattern in their GDPR banner experience:

You click to customize tracking cookies and get presented with a list of checkboxes, but primary button on the right is "Accept all cookies", whereas the left side (where you'd usually find a "Cancel") is a secondary-looking button that says "Accept changes".

If you don't take the time to actually read the buttons, you end up unchecking a bunch of boxes just to inadvertently accept them all. Real scumbag stuff. From the above, it sounds like tricks like that may not even be covered.
When it provides benefits which either can't be solved by or clearly don't belong to any other layer.
Just putting this out there.."Adapting a lamp post into a charging point for electric vehicles can cost as little as £2,000"
Seems like a good infrastructure project ...
That's not in any way surprising. When you have more parameters than data, this is trivial.
"Yes. There's nothing special about a mobile phone number when it comes to SMS delivery."

This is false.

"Mobile" numbers - numbers that are classified as belonging to an actual mobile carrier - are indeed different than non-mobile numbers.

For instance, you cannot send SMS from a short-code to a non-mobile number. Which means, your twilio number (which is not a mobile number) cannot receive 2FA (or any other SMS) from the 5-digit "short code" numbers that gmail (and most banks, etc.) use for new account verification, etc.

Non mobile numbers are, in many ways, second class citizens in the mobile-operator ecosystem.
Again, Manusmriti is not a vedic source. Mentioning it will only serve as a distraction and weaken your argument. The paper by Dipankar Gupta is junk. It does not cite the specific verse numbers of specific vedas. Apparently, Gupta has a lot to say, but gives the impression that he is simply making up stuff as he goes along.

The Wikipedia article is better. But you will notice the article citing the book I mentioned earlier: 'Stephanie Jamison and Joel Brereton state, "there is no evidence in the Rigveda for an elaborate, much-subdivided and overarching caste system", and "the varna system seems to be embryonic in the Rigveda and, both then and later, a social ideal rather than a social reality"'.

If there is really a "large body of evidence", I am still waiting for something concrete that you would cite, so that I can go look it up, in the Vedas.
Docker Swarm usage here in production. Mainly a regulatory and compliance constraint, but it is relatively simple compared to other container orchestration platforms.
I'm not sure why systemD is needed for restarting a process what about a simple loop with an if statement? Process isolation to run a go binary on a presumably dedicated web server? Privileged sockets, not even sure what those might be.

The point of this post is to not complicate things, but what I hear is even more complicated be it via a docker alternative.
Yeah the Docker step isn't strictly speaking necessary for the deployment, it's more for devs with diverse OS's to be able to isolate dependencies on the OS. At JVM shops, the same .jar unfortunately doesn't reliably and reproducibly run the same way across machines. The JVM can only isolate dependencies within itself - if your app requires eg certain /etc/host values, that's something that can and probably should go into a Docker file that isolates dependencies on that, and make that explicit.

As for the AMIs the benefit of always making new ones and storing them (tagging them with the git commit hash) vs mutating a running ec2 is it makes it incredibly simple to roll back - if a release goes wrong, just spin up new EC2s using the previous AMI and viola.

In general we prefer immutability of all things. State is the devil, especially when it comes to "what's running in prod?"
Not really, CPU is still "of-the-shelf". SoC is custom. That's just because you can't buy Neoverse and drop it into the motherboard, so making a custom SoC is the only way to obtain it.

Donut has a good video about LLV: https://www.youtube.com/watch?v=RE5FGyq12ds
Standards are written with precision and with a minimal number of words (i.e. no redundancy). This is great for implementers, as wishy-washy rules make for incompatible implementations. People really don't want to argue about interpretations of a rule.

A tutorial it ain't. Neither is it a guide, an overview, a textbook, a nutshell, or a marketing document.

Just the facts, Ma'am.
I am going to put a different spin on this: If you use a service like google photos, wouldn't you want to uplift all your photos, albums and metadata into the service?

Viewed from the "be maximally useful" perspective, it makes sense. I have 150,000 photos (maybe) -I don't want to approve each one. Even at the album granularity, I have thousands of albums. We all do.

Yes, its a giant, egregious privacy breach. That is pretty much definitional for a cloud based Photo archive/album service.
> the only real UNIX systems available these days are illumos and xv6

I do wonder how you are defining "real UNIX system" in that statement.
Well, except those groups don't particularly need dynamic or static linking, respectively, either.

Distro maintainers definitely loved dynamic linking 25 years ago, when they relied on a machine under someone's desk at e.g. Pixar for infrastructure and on the kindness of random universities for file hosting. It isn't really as true of distro maintainers today. You can update a library to fix a security issue and let a build farm handle the upgrade for pretty cheap (either using $your_favorite_public_cloud, or using a handful of relatively cheap physical servers if you prefer that). You can then upload the results to a CDN for free / cheap, who can get the modified binaries to your users quickly, without you being, as they used to say, "slashdotted." (There's also better technical tooling for things like binary diffs these days.) The cost of storage is also much cheaper, so you can save the intermediate build products if you want - generally you just need to rebuild one .o file and one .a file in a library and you can continue all the downstream builds from the linking step onwards, without recompiling anything else.

Software houses, meanwhile, are quite capable of shipping trees of compiled binaries. You can rebuild a bunch of shared libraries if you want, and ship them all together (Facebook, for instance, has a wonderfully terrifying system where they deploy a squashfs image and they have a FUSE filesystem to mount it: https://engineering.fb.com/2018/07/13/data-infrastructure/xa...). You don't actually need to statically link things to avoid OS dependencies; you've got $ORIGIN-relative rpaths and other means of finding dependencies relative from a binary. Or you can use a system like Nix where each version of a dependency has its own unique path, so you can co-install all sorts of things "systemwide" without them actually conflicting with each other, and the final binary was built against the paths to the specific exact dependencies you told it to use.

To be clear, I agree that this is a silly tooling turf war - I just want to encourage people to explore more tooling options and not feel like they're constrained by which "side" they fall on. There's a lot of options out there!
Four Highlights in Huawei Analytics Kit 5.2.0 That Unlock the Power of Data
There's quite a bit more charging overhead for 110 vs 220.

Also, there are 30,000 post offices. I'd imagine it will be a long process, even if they just put in 110. one evse requires large amounts of continuous current, let alone with a parking lot full of vehicles.
Advanced function resolution technology is one of the main reasons I use C++. The combination of being statically typed yet allowing users to create elaborate function dispatch hierarchies is unmatched.
Utilizing Channel Analysis to Facilitate Precise Operations-Huawei Developers
This is done for a very good reason. Some languages have chosen to base the standard on a particular reference implementation rather than a specification. In practice, this has led to any alternative implementations of those languages having to recreate any quirks of the original implementation to prevent inconsistencies. That makes later implementations brittle and tougher to optimize. Also, specs always have a formal grammar for language syntax, and may provide a test suite that covers aspects of the language semantics.
> , it should at least be possible to implicitly convert each argument to its corresponding parameter type.

Oh no! You just got burned (maybe). Make sure you turn on your compiler's warnings to find bogus-but-legal implicit conversions.
How to Quickly Collect the Data You Need from Huge Amounts of Data
It's usually pre-compiled but yes. Go binaries are also architecture-specific, so it's equivalent there. I'm fairly sure my whole venv is pure python though so it should be even more portable if you factor out the interpreter.
A simulation from the economist gives ~2% chance of being hospitalized if you get COVID as a 29 yr old male with no comorbidities.

https://www.economist.com/graphic-detail/covid-pandemic-mort...
Yes, he needs to fill the pool with a dilatant fluid not a thixotropic fluid.
I have M.S.. My question is can remyelination from Lion’s Mane outpace the demyelination from M.S.
I suspect that the only people who've actually read the entire Standard are compiler writers :-)

Note to anyone trying to implement a language - don't bother reading tutorials or textbooks on a language. Just the Standard. Otherwise you'll be sorry.
I've found that when writing something like this which iterates over and over many millions of times a helpful test can be to place a simple counter in your loop. If you have an algorithm which you expect to loop only one million times and it loops ten million times, that is something you want to investigate.
Oddly, most of this brittle nature helps build a more robust product.

That is, yes, it will break often in small ways. However, most of the breaks will be from version upgrades or machine changes. The sooner you find those, the better.
C++ is really the one language where I suggest reading the manual, repeatedly. Sometimes I go and read the docs at cppreference for practically every expression I write.