skysight-inc/HackerNews huggingface dataset:
When I have encountered DRY in the wild, it has always been DRY zealotry. Repeated code was absolutely never allowed, and everything had to be modularized such that if anyone could ever imagine a future where something might get used again, it needed to be structured like that from the first merge.

What it led to was an inscrutable codebase where unless you had been working with it for years, finding out where a thing was actually done was an exercise not unlike an archaeological dig.

Like most things, it’s a matter of something which is a good idea, but the reasons it is a good idea are lost in its most common application which is at the exteme.
What Jeffrey Epstein Did to Earn $158M from Leon Black
Repetition also makes it harder to replace one thing in all instances but I agree that too much DRY can make a codebase a headache to wrap your head around: lots of different overloads for constructors and lots of branching inside the common code makes it hard and unpleasant to work with or ramp up as a new hire.
Front running is simplistically placing your own orders in front of your customers orders based on the knowledge that the customers orders will be executed.

Buying at better than requested rates and reselling to a customer based on a request from that customer to buy at a specific point is not front-running the customers order, it's literally just carrying out the customers order, but pocketing the difference between what you can find buy the asset at and what the customer decided to pay.

Think of this, you pay someone a fixed amount to buy you a PS5. When he gets to the shop there is a sale, so he pays less than he expected and less than you expected, but he's fulfilling your order at the agreed price so he pockets the difference. That's not front-running. He is making money fulfilling your order, but it's not front-running.

Now second scenario imagine you again pay a fixed amount for him to get you a PS5. He comes back saying "sorry, but they didn't have any left ... but I just happen to have bought 4 myself before I could fulfill your order, I'm willing to sell you one at an elevated price".
That's front-running. He executed his own order, in front of the one he was carrying out for you, with the knowledge that he would be able to make money because of your order.

Note that the illegal part is not "making money by buying and selling something". It's perfectly legal for someone to buy the last PS5 and resell it at a higher price to make money. The illegal part carrying out such an order based on the inside knowledge of your pending order and front-running your order with their own.

Naturally this is rather fuzzy explanation, take it with a grain of salt.
That's interesting, I'll try it out (I have Android Studio installed so I should be good to build), thanks!
> Every laptop, home computer and all-in-one computer and many PCs use exactly a single PCB.

That's only the case if the memory is soldered to the motherboard; otherwise, it's on a separate PCB. The storage also has to be soldered in (not M.2 or a traditional HD). The WiFi has to be on the motherboard too. And so on.

The laptop I'm using to type this comment has at least five PCBs: the motherboard, two memory boards, a storage board, and a WiFi board. It might have more that I missed.
A cone surface is topologically equivalent to a disk. You don't have to cut it at all in order to flatten it, if you allow as much stretching and bending as you want.
So, 0 holes.

If you want to consider a more restrictive collection of modifications, like, say you want to preserve angles or something inside the shape, then that would be a different question.
Uh, I guess if you had a surface which was generally smooth but possibly has some boundaries and/or corner edge things, and/or corner point things (e.g. sticking two cones together), you could also ask about how many cuts combined with conformal maps [edit : I think conformal maps isn't the thing I'm looking for. Yeah, I think I'm looking for something related to developable surfaces maybe] would be needed to flatten such a thing out? (so this could maybe produce a similar question for which the one or half or whatever cut between the edge of the cone and the center, could be an answer?)
IoT devices are starting to use hardcoded DNS servers instead of using the one provided by DHCP, which negates the benefits of Pi-Hole on those devices.

For now, I've configured my router to force all UDP port 53 traffic to my Pi-Hole which overrides what I mentioned above.

But, in the future we may start to see IoT Devices hard-code DoH servers which will be harder to force over to the Pi-Hole.
The initial result of the gastrulation and neurulation. e.g., what would've made that process 'useful' so that it persisted in an evolutionary sense. Would intestinal processes work as well if they weren't contained (from mouth to anus), or if brain/spine/nerve channels weren't separated from other parts of the body.
We tried getting visibility with bunnyPAPR.org and now with the $15 Hoodie Viral Helmet (slimmer).

The mass market appeal of these is quite low. People are tired.

Hospital market was a no go (they need certifications).

Airports... maybe. But we found it tough trying to break in to that market. Airlines aren't really supportive.

I track this stuff here:
https://www.reddit.com/r/viralHelmets/
I really don't see how WSB posts about how GME is overshortted is any different from any of the other analysts DD.
Discovered AnonAddy (which my friends and I call AnonDaddy) last week and I'm in love. The reply function works perfectly. I cannot stop suggesting it to people.

Unfortunately HackMD rejects the anonaddy.com TLD, so I've had to use my "real" address there, but so far everywhere else it works fine. A clever friend realized you can register a new github account with an anonaddy address and use that to connect to HackMD. Smart.

Great service. Free tier is great. Will probably end up paying and adding my own domain for the odd site that rejects theirs.

The only feature I'd like is greater bandwidth allowance per month on the lite plan. Current limits are 10MB per month free tier, 50MB on $1/mo lite tier, and unlimited on Pro. But fair enough.
I just read the original article my self before seeing your post. The last bit about "sharding" by partitioning your db from the start helped alleviate a lot of my concern I think. All my apps data doesn't actually need to be in the same DB for 90% of my use case (userid in range -> db x).
Awesome, very pleased to hear it! For neilmed, you might try one of the higher flow crevices temporarily to dislodge stuff: https://www.amazon.com/Multi-Purpose-Saline-Spray-ounces/dp/...

For the breathe right, I can tell you my early experience:

1. I actually got hypocapnia: pins and needles in arms from excess ventilation. This just showed how unused my body was to proper airflow. My pulse o2 went up a couple percentage points and the hypocapnia went away fairly quickly.

2. My nose clogged up a bit temporarily, almost like it wasn’t used to the airflow. This went away. After a couple days

3. My nostrils started staying further apart when I didn’t have the strips on. I basically just resisted them collapsing inwards.

So you may find after a few days use they lead to some improvements when not wearing them. I use them most when sleeping.

You might also consider a sleep study, in case thus blockage has led to apnea or anything similar.

Final thing: there is a device called a pulmonica, used to train the lungs. Believe I read reports from some people saying it improved congestion via vibration of the sinuses. I have not tried one extensively, but am currently evaluating. I’d consider my sinus congestion mostly managed now so can’t give feedback there. But as you seem to have a severe case it might be worth tracking down this lead.
That is not a great measurement. Transistors can be of different types, each with different value in terms of making products work. Other things matter too: metal, pads, die separation saw cuts, e-fuses, diodes, resistors, and capacitors. Nobody cares about transistors that can't be hooked up to anything.
I had no idea W. E. B. Du Bois was a data and info graphic guru. Wow.
It's a fairly common thing in our industry to take ideas to extremes where the initial benefit becomes a liability. Then comes the next thing and the same zealotry kills the next thing as well. The next thing is very welcome because it allows people to start as a blank slate and escape the corners they painted themselves in.
Ooh, that's interesting. The way it was described made me think that you needed some JS to check if the data was in cache or not.

I guess it's probably a bad idea to let the browser send this type of potentially unique info to the server by default, but I understand how it makes sense from a performance perspective.

As far as I'm concerned privacy should always trump performance, but I realize that not everybody shares this point of view.
> cut the sock to flatten it

From the topological standpoint, you do not need to cut the sock for this - it is already “the same as” (homeomorphic to) a piece of the plane surface.
Have they finally axed True Ups?
Wow, interesting.

So, to access 3rd party cookies I need to access a document DOM object that has that 3rd party origin? But such a document is not always available, is it...

Looks like the use cases targeted by that proposal are limited to an embedded iframe that wants to access its own domain cookies. I was thinking also about arbitrary doman.

Like requestStorageAccess(targetOrigin, keys...)
You speak as if there is just one entity making these things. There isn’t, there are hundreds of labs all over the world working on this. If one of them comes out with a treatment alternative like this it may gain some traction but if they came out with a cure they would dominate the global market
> Autism spectrum disorder (ASD) is characterized by social and behavioral impairments, along with restricted interests and repetitive behaviors.

This seems like a very negative view of autism.
That was simply SEO talking. There was no other way to shoehorn a link to their Starlink webpage into the article.
Always thought this should've been open sourced as soon as google acquired it. The mechanic was copied in other VR games and it would've been a good reference/learning point for other VR devs. It seemed odd for google to charge for something like this when it could've been used to share and inspire new ideas. Glad they got around to it.
I have been using evcxr for the last 2-3 weeks and I'm loving it. There are two things that bother me: (a) fancy UI components seem to only work with Python and C++ kernel (not theoretically, but with available packages), (b) while you can redefine values and functions when you're iterating, you cannot do so with structs (yes, big structs go to a local package that I depend on, but sometimes I have ad-hoc utility structs).
Tether bank answers to “The Bit Short inside crypto's dommsday machine”
It's called AddressSanitizer. You enable it with the compiler flag -fsanitize=address. It's supported by clang, gcc and lately MSVC.
Precisely that!
Astronomers, both amateur and professional, have a legit issue with starlink. SpaceX are even trying to mitigate the issue - because of astronomers pointing it out. So I can see nothing wrong in a magazine for hobby astronomers taking a jab at starlink.
-90°C got transcribed wrong (the degree symbol as another zero)
I got a GPD mini laptop it was a huge waste of money because I hate working with it and the resale value has dropped a lot.
How about the “are all basically the same disease and they will be resolved in what will be known as the "metabolic revolution" in medicine” part?

If that’s not snake oil I don’t know what is.
> If your site is 10KB and you rely on 2MB of javascript libraries and fonts,

... then you're doin' it wrong.
An example Rust Jupyter Notebook for data visualization using this tool: https://plotters-rs.github.io/plotters-doc-data/evcxr-jupyte...

Rust hold interesting promise for data analysis and visualization at scale, especially as someone who hits use cases where Python/R start to bottleneck. The ecosystem is not there yet, though.
That is a great bit of self awareness. “This of how I changed my mind” is a narrative we all need to see more and experience more ourselves.
Depends on your archival needs. Consensus seems to be that tapes have a longer unpowered shelf life. In terms of speed it really is cold storage though. You can't just bring the tape over to a user's system and copy a file. And seek times for retrieval of arbitrary files are very slow compared to HDD.

If you really need it to last and re-writability isn't an issue, M Disc claims 1,000 years.
An honest question: is there a Positive or even neutral one-line summary of ASD?
tldr: It's on loan from NASA
"According to an Ifop opinion poll in October, 57 per cent of French Muslims under 25 think sharia law is more important than the law of the French republic"

https://www.ft.com/content/b6c0681f-3a0a-40fa-8b90-86997925f...
Workers and Resources: Soviet Republic –
It was an expensive lesson for me.
One of the little Chromebooks which will take a standard Linux distribution is a good option.

A tablet running Debian, and a wireless keyboard, is my choice these days though.
I just came across a Flash video, on a Mozilla page on less…
Webassembly is about to become as necessary for browsing the modern web as Javascript is today. For much of the same reasons: you must keep it on to be tracked, so it will be "made necessary" on as much of the commercial web as possible.
Apple and Amazon are unsurprisingly absent:
For Apple the web is a nuisance at best, and Amazon just never contributes back.
"When saftey is paramount"

(From the ad)
I didn't get the reference, if there is one here. :( Can you or someone else explain?
I think one key problem is whey people attempt to DRY the code before actually understanding what they're building. I like to let the code "tell me what to do"; I'm building something, and I repeat the pattern a few times, so I keep an eye on it. Eventually, I'll have a few repeated patterns I can look at. A lot of times, they're similar, but not the same. Waiting gives me the opportunity to review several similar patterns and find a more elegant solution that can accommodate all of the use cases, rather than forcing a sub-optimal abstraction for the sake of being DRY alone.
TRS80. I was in high school, and I was taking a FORTRAN class. We dropped off a card deck to the teacher, who went twice a week to a mainframe somewhere. So you'd put in your code, get the results half a week later, make a fix, and put in the change a week after you put in the first program.

Then the school got five TRS80s. You could make a change in a minute instead of in a week. That changes some things...
There is no rational reason to ever short this. The funds that are shorting this deserve to be liquidated for being so foolish. At best you can only double your money with thirsting , unless you keep adding to your short. Losses however are unlimited. Too many people think that they can make a fortune shorting, like in 2008. But the reason why a movie was made about those guys is because success at shorting is so rare and difficult that when someone does it successfully , it is big deal. No one makes movies about people who buy and hold stocks.
Polkit-exec (pkexec) already exists, has much better security, and integrates with your DE instead of expecting passwords on the terminal.
I'm not usually one to poke fun at these things but my friends who study formal logic/model theory/category theory/homotopy type theory/etc. will be excited to learn that they are not in fact doing mathematics.
Yeah, I'm persuaded by the Julia Marcus school of thought that simply ordering people to stay home is important but not nearly enough. You have to provide ways for people to reduce their risk in case they decide not to listen to your orders.

I personally stay home as much as I can, but I have certain privileges many others don't.
The Adder WS has a 4K OLED display, although it's temporarily sold out:

https://system76.com/laptops/adder

The Bonobo WS has a 4K display option at a higher price point:

https://system76.com/laptops/bonobo
You've been getting downvoted by a large number of established HN users, and from a quick look it seems to me that the fault lies with your comments. Maybe there are exceptions, but the ones I saw in that ended up with negative points were unsubstantive and often inflammatory. Please stop posting like that to HN, and make more of an effort to stick to the intended use of the site—thoughtful, informative conversation on topics of intellectual curiosity, avoiding flamebait. Do that and the downvote issue should go away. If it doesn't, you can email us at that point: hn@ycombinator.com. But please don't compound the guidelines breakage by posting like you did here.

https://news.ycombinator.com/newsguidelines.html
> I would expect an automatic process - disable and remove failed drive completely from a tome, add SOME free reserve drive at SOME rack in the datacenter to the tome

We have spec'ed this EXACT project a couple different ways but haven't built it yet. In one design, there would be a bank of spare blank drives plugged into a computer or pod somewhere, let's pretend that is on a workbench in the datacenter (it wouldn't be, but it helps the description). The code would auto-select a spare drive from the workbench and begin the rebuild in the middle of the night. At whatever time the datacenter technician arrives back in the datacenter they can move the drive from the workbench and insert it in place of the failed drive in the vault. It doesn't even matter if it is half way through the rebuild, the software as written today already handles that just fine. It would just continue from where the rebuild left off when it was pulled from the workbench.

The reason we don't really want to leave the drive in a random location across the datacenter in the long run is we prefer to isolate the network chatter that goes on INSIDE of one vault to be on one network switch (although a few vaults span two switches to not waste ports on the switches). Pods inside the vault rebuild the drive by talking with the OTHER 19 members of the vault, and we don't want that "network chatter" expanding across more and more switches. I'm certain the first few months of that would be FINE, maybe even for years. But we just don't want to worry about some random choke point getting created that throttles the rebuilds in some corner case without us in control of it. Each pod has a 10 Gbit/sec network port, and (I think) a 40 Gbit/sec uplink to the next level of switches upstream. The switches have some amount of spare capacity in every direction, but my gut feeling is in some corner case the capacity could choke out. We try to save money by barely provisioning everything to what it needs without much spare overhead.

Plus the time to walk a drive across the datacenter isn't that big of a deal. Some of the rebuilds of the largest drives can take a couple days ANYWAY. That 5 extra minutes isn't adding much durability.
>helps that a 10kloc c program getting riir'd probably won't be a 10kloc rust program, because c doesn't have libraries and rust does.

What? Rust has so few libraries of significance that it still depends on C for security-critical areas like SSL.

>it is literally impossible to write "a small codebase focused on its key value-adds without distractions" in a language that doesn't have strings and requires you to build a dictionary from scratch

Strings are misunderstood, I'm not going to get into it here. My dictionaries in C usually clock in at about two dozen lines of code. The complexity doesn't go away because your language does it for you.
Forgot about the most important way I make the web fast, rule #1. Eliminate DNS lookups. I gather the DNS data in bulk before I start reading and add it to custom zones file that are served from localhost authoritative servers. For example, I gather all the DNS data for all sites posted to HN before I start reading. One way to do this, if encryption is desired, is to use DoH+HTTP/1.1 pipelining. I wrote some custom programs to speed up the Base64URL encoding.

This way, there is no DNS traffic leaving the network. The only lookups preceding a TCP connection to a website are to the loopback.

That is the number one way I "make the web fast". If retrieving a web page were a chemical reaction, DNS is the "slow step". In most cases, I eliminate it.
It sounds like you'd find great pleasure in writing harnesses for oss-fuzz. Google has found and reported over 25,000 bugs in 375 projects, but they need people like you to help wire up new projects.

You can get started here: https://google.github.io/oss-fuzz/
Seconding the performance issues. This is obviously amplified when screen sharing, which makes certain types of collaboration difficult. (Remote grooming sessions, for instance.) I also find recent UI changes have made the product harder to use, at least for our version and processes, and have added nothing of value in return.

As far as how useful Jira is, a huge percentage of that is going to be your team's processes external to Jira. I have found it to be a very good mirror. If your team's processes are a mess, your Jira instance will quickly become one as well. But if your team is organized and is bringing an existing, functional system to Jira, I have found that it's a good enough value add to be worth it.

It's definitely an enabler, though, rather than a tool that will funnel you into good practices. (The same can be said for Confluence but it's even more true there IMO.)
I imagine in theory Snakemake, which handles dependency graph resolution , could be used to compute dependencies, and its flexible scheduler could then call nq.

OTOH, if just working on one node, skip nq and use Snakemake as the scheduler as well.
The provided script downloads a bunch of binaries from the authors blog, with --no-check-certificate no less. No thanks.
Except that Rust is also a much much more expressive language. Even ignoring things like solid module support and libraries you'll find your Rust programs to be much fewer LoC (assuming bug/LoC is the right metric) for equivalent functionality.

I agree that rewrites have the serious potential to introduce new bugs and the cost is rarely worth it if the codebase is actually that stable and low througput, but the reality is that most aren't. A one time high cost in exchange for introducing 70% less bugs over a period of N years starts to look like a good trade off.

Yes, complexity is the root of all evil. I can get onboard with the whole statement except the "no matter what language you use". If you have the ability to use any language that enforces memory safety, we should use it.