skysight-inc/HackerNews huggingface dataset:
> And the community is tired of people asking for help with their homework

I don't think anyone objects to closing those questions. That's not really what this is about. My questions are very clearly not asking for help with homework and trivial "how do I write a for loop" or "it doesn't work" questions. Still get downvoted/closed frequently. Most often:

* It gets closed as duplicate because there's a vaguely similar - but different - question. Or sometimes there's a completely different question with an answer that incidentally also answers my question.

* It gets closed as too vague or not clear because it's simply outside the domain of expertise of the voter. It's clear to people that know what I'm talking about.

To be clear when I say "mods" I don't exclusively mean people with official mod power. It's also people that moderate for fun - those that trawl the new questions. Let me know if you have a better name for those people.

You can tell it's them because you very often get a couple of downvotes immediately and then if you check back a month or two later it will have been upvoted by many more people that actually had the same question and arrived there via Google.
Now you can write Telegram bots in CSS
My first (and only) IT role in an EDA shop (both mech and electrical), one of my first asks was to get an SVN server running. I was like what? You sure? Yes, they were sure.
The thing I often think about is while the demands for an orbital class vehicle quickly become untenable, ICBM's stay viable for a lot longer. I don't know if MAD is more or less stable without the prospect of space exploration.
Of course a country’s capital will always be relatively developed. But Addis Ababa contains less than 5% of Ethiopia’s population…the majority live in horrible conditions.
There is nothing that is safe against physical attacks practically. You can always find a point where you can do a MITM attack as the communication channels between the TPM and anything else is almost always insecure.
But then you'd just get fake reviews, and networks of fake actors boosting each others fake articles.
In all fairness, postgres still works for their workload even if RDS didn't. You can get a lot of workloads out of postgres with the right hardware, the right replication, and the right extensions (eg Citus has a columnar extension that probably would have been a pretty good fit for that).
The Price I Have to Pay (To Be a YouTuber)
Lawyers and fraudelent claims are a big part of the problem. My wife rear-ended someone at a slow speed and the other party declined ambulance coverage. They were able to drive home no problem. A week later they hired a lawyer and my wife caused the woman to have a miscarriage. Of course they were unable to provide any medical documents confirming even the most basic details yet the insurance company still gave them a payout probably because it was cheaper than paying attorneys to right it. A very similar scenario exists with condo property insurance. The lawyers make millions and the consumers premiums keep going up.
This is mitigated by a Trusted Computing Group feature - at boot, the OS sets a non-volatile flag, and clears it again on clean shutdown after wiping any sensitive material from RAM. If the system boots with the flag set then the firmware wipes the RAM before booting anything. This doesn't protect you against someone pulling the RAM out of the system and dumping it there, but that's a much harder attack.
Maximum deductible is taking on more of the risk yourself.

The first dollar in any claim is always paid, the last dollar hardly ever, so the first dollar is worth more. Maximum deductible also reduces the chance you’ll involve insurance at all. Why report a $200 fix when your deductible is $1000?

Comprehensive insurance is for when you CANNOT afford to lose the car. If it would be painful but you’d survive, you probably don’t need it.
Space debris could weaken Earth's magnetic field
Slow Down, Do Less
I mentioned this in another thread, but why can't we regulate headlight height? Why do SUVs and pickups trucks have to have headlights that are higher than buses and real trucks?
You're creating so many assumptions that nothing you've stated could be concluded to be an honest reflection of reality.

Nobody has to know the rate of leaks, it's irrelevant. Gross negligence is not necessary, how would you even know? Leaks by definition are rarely exposed, we only see some of them.

A "highly sensitive" key doesn't mean anything. Assigning more words to it doesn't somehow change the nature of it. Humans are bad at securing things, that's why the best security is to not have a system that requires it.

Whatever hypothetical solution you have would be crushed under the weight of government committees and office politics until your security measures are bogus.
I wonder if air breathing rockets would change this much.
And what has little snitch told you? Has anyone’s fears about their IDEs stealing code been realized?
Please don't take this as rude, but speaking more plain and directly than the previous person you replied to: I think they were politely telling you to come up with more substance in your comment.

The culture on Hacker News has historically been along the lines of, "if your comment is not more insightful than providing an upvote on the post, withhold it and leave an upvote instead." This was on the "welcome" page when signing up for a Hacker News account, and can be found here: https://news.ycombinator.com/newswelcome.html

See:

> The most important principle on HN, though, is to make thoughtful comments. Thoughtful in both senses: civil and substantial. ... The test for substance is a lot like it is for links. Does your comment teach us anything?

I think Hacker News comments tend to miss the mark on this test more often than not, to be fair. But it's perhaps worth at least politely pointing out when the substance test falls as far as, "this was essentially my approval of the more substantial parts of the post."

The irony of my comment is that I'm adding nothing to the discussion, myself. But hopefully there's some small value in reinforcing Hacker News' social ideals.
Came here to say this. If you use a hammer to fasten a screw, it's probably not going to work
Yeah that would work, minimalism and artificial constraints are ways to help manage ADHD. The other thing to think about it is that your mental solution is probably wrong and won't survive implementation. Consider that a challenge to focus on.
The batch request just eliminated io. It doesn't change the speed of the database overall. It would make that e2e test I mentioned harder to measure as how would you profile the specific query related to the request within that batch? I can imagine an improvement in overall speed, but I don't think this is a common pattern and the time spent in the db will still be slower than the web app for all processing related to the request.

Also for the Cache... Its a hard thing to measure and define right? Because it can live anywhere. It can live in the web app or on another third party app and depending on where it is, there's another io rt cost.

Because of this Usually I don't classify the cache as part of the db for these types of benchmarking. I just classify actual hits to the fs as the db bottleneck.

I mean if everything just hits an in memory cache that's more of bottleneck bypass in my opinion. Definitely important to have cache but measuring time spent in the cache is not equivalent to measuring where the bottleneck of your application lives.
I used to do competitive debate. I don't recommend learning anything about that world, or using their recommendations. Competitive debate overlaps with real-world speaking, in the same way that competitive programming overlaps with actual software development. That is to say, there is very little overlap, and some actively harmful habits one will pick up from the former. It took me years to unwind all those "lessons" from debate club.

I've found the Socratic method to be an effective way to persuade people. Ask questions, figure out why a person believes what they believe. Do your best to "steelman" their point of view, and then share yours. A lot of the time, people just want to be heard.
It’s not Android per se that’s the problem, it’s that Android uses Gradle as a build system and Gradle uses Java.

The Gradle compatibility matrix is pretty complicated: https://docs.gradle.org/current/userguide/compatibility.html...

I’ve also used Facebook’s Buck build system, as an attempt to get away from Gradle, and it’s also fussy about JDK versions.
What I like about this post is that it provides a good attack against the function coloring philosophy, which always rubbed me the wrong way. Function coloring essentially implies that there's no good reason for async and sync to be different, and it's being used as an argument that we should try to sweep the distinction between the two under the rug as much as possible, and that's just not a good idea.

I also like the point that maybe(async) isn't terribly compelling. Recently, I've been looking at building an async parser, and the sync version of the interface is pretty simple: fn parse(r: &mut dyn Read) -> Result<ParsedObj> [1]. In theory, I could slap an async on it, change Read to AsyncRead, and now I have an async version. Except it's not usefully async: the consumer of the data can't do anything until everything has been fully read in. So what you want in the asynchronous version of the API is something that looks like a stream of parse events. But that API is way too much faff for anyone trying to use the API synchronously. Or is it? If you have a high-level method that distilled the stream of output events into a simple, easy-to-use answer, then you end up with something that looks maybe(async)-able [2].

Where I think the author gets it wrong, though, is in asserting that it's statefulness that causes maybe(async) to break down. State per se isn't the problem: our underlying parser above is statefully turning a stream of input data into a stream of parse events, and this could sometimes work well with maybe(async). The problem arises when you're multiplexing many streams at once. In synchronous code, there's just no way to do that kind of multiplexing (as pointed out earlier in the blog post), while it's a pretty key design feature of async code. The trouble really comes in when you have a system whose outer interface is a 1:1 stream interface, but which internally needs to go through a 1:N piece and an N:1 piece. It looks like it could be maybe(async)-able from the outside, but its implementation is hopelessly not maybe(async)-able.

[1] Honestly, a lot of parsers go a step further and just read in the input buffer as a &[u8] and rely on zero-copy, but that interface turns out to be even less useful in an async context.

[2] But the faff remains if you can't resort to one of the pre-canned methods. How much of an issue that ends up being is left to the reader to decide.
I'm sure I could've worded it better, but the bottom line is we are an org that uses Microsoft - Azure, C#, etc.

Other options had no shot
Sure, but we were talking about the US, which is so developed that it doesn’t even have 3G anymore. Americans own over one personal motor vehicle per household, they could charge their phone with their car if they really had to. Less than one hour of the California minimum wage buys you a 30W solar panel or a large spare battery to charge your phone. The risks are minimal.

And I’ve definitely had phone lines go out in the past. All it takes is one tree falling. The lines are on the same poles as the electric service. Sure, they were more reliable, but not by any measure that makes them worth keeping around (especially since the vast majority of lines sit completely inactive).
This is what building to code should address. If a house is built to a specific hurricane code, and is destroyed due to other reasons (a hypercane, for instance), then let insurance cover this and mandate rebuilding to an even higher standard.

https://www.nbcnews.com/news/us-news/hurricane-idalias-destr...

: Dozens of modest homes along the Big Bend coast were heavily damaged in the floodwaters, but interspersed among the debris were residences left relatively unscathed, all because they were built elevated on stilts.
Well, yeah, but building something tall enough to reach the synchronous orbit is impossible even on Earth, there’s no material with even a thousandth of the compressive strength required. Space elevators are only possible because they’re tensile structures and the “bottom” that supports the weight of the entire structure is up there in a low gee environment.

Remember that just getting outside the atmosphere is the almost trivial part of rocketry compared to the problem of having to then accelerate to >= orbital speed fast enough to not fall down!

And anyway you’d have to dismantle the planet to build your launch tower, which I guess would solve your problem, in a fashion. Though – whatever you turned your planet into would just have an annoying tendency to rapidly collapse back into a ball.
I could see the state requiring new parts because of unscrupulous insurance companies insisting that shitty used parts were fine: but it’s nice you had the option of taking the cash. Best of both worlds, really.
TPM can always store the (root) private key inside the TPM, but where will the other side of the channel (CPU, HD etc.) store their private key?
Man Group and Bloomberg partner to develop open-source ArcticDB Database
It's not a "big tech" product. It's an infrastructure product. A public utility. With (if they don't mess up) life-long subscription customers. With essentially zero risk (aside from infrastructure risk: earthquakes, upgrade cycles.)
Try to manage a single day having given up all the elements of advanced civilization yielded by an Ethiopian mind. We'll see if you make it to lunch.

E.g. - ABS (Applied Bottle Sciences) - https://www.youtube.com/watch?v=3e-IMCcWdcM
Try contacting the CTO in a company of 100k+ people. Your email probably goes to their junk folder. I worked in a similarly sized company and I didn't even know the name of the CTO, nor if there even was one.
Are their losses greater or less than pre purchase. I know revenue is down, but I wonder how the cost cuts affected margin.
> And that’s how Google search will be overtaken by GPT with ease.

Yes if the LLMs are designed to give you the best results. Right now, it’s a honey moon phase for consumers, when there’s a fierce competitive race. But just like any other tech its deployment and realization is governed by incentives. If we get an entrenched LLM monopolist I don’t think it’ll be any different from a search monopolist. Perhaps worse.
Funny they split read and write instances out late. That should be done by default.
Put wolves at charge of solving the problem. They seem to be immune to the prion and are extremely good keeping deer populations healthy. Is what they do.

This is the result of having crowded game farms, basically breeding deer like rabbits and accumulating them on small areas so people can come and have fun shooting.
Working from home has been pretty difficult for me as a person with ADHD, everything is just so distracting that I actually went from 3 monitors to 2 monitors to now only just the laptop screen so that way I can force myself to focus. I can't imagine being productive with Vision Pro and it's "infinite" screens and infinite browser tabs. It would be productivity hell for me.

Tho, I have been trying a few different techniques to get myself more focused such as deleting TikTok and forcing myself to keep my phone on Do Not Disturb., etc.

I've even recently built an desktop app around the techniques described in this other HN Post here: https://news.ycombinator.com/item?id=38274782 and using some techniques in Cal Newport's book "Deep Work" which has significantly helped me stay focused and get into a flow state much easier. I'm going to be launching this app soon in the App Store in the coming weeks. Would love to share my app with fellow HN'ers and get some feedback.

Email in my bio if any one wants to give it a try.
in 1986 and 1987 ... yikes

https://www.linkedin.com/pulse/18th-december-day-perl-progra...

Obfuscation coding contests, Perl golf tournaments to create the shortest feasible code for a specified function, and Perl-language poetry collections have all grown up as a result of Perl's versatility.

Your takeaway may well be that perl is not the kind of thing that your boss would like. My takeaway is that perl (and raku) is versatile and engenders a sense of -Ofun.
By the same token, a space faring civilization based from the Moon or Mars is much more feasible, and a large argument for colonizing either imo, also rarely discussed nowadays.
>It’s not difficult so much as it just takes so much time and challenging-yourself

What's the difference?
Also impressive: Jonas Deichmann's circumnavigation by triathlon. 450km swimming in the sea, 21000 km cycling and 5060 km running.

https://jonasdeichmann.com/triathlon-360-degree/

https://en.wikipedia.org/wiki/Jonas_Deichmann
> especially if you're a very small company

Probably better not on AWS
qw/one two three/;

in raku is

<one two three>
People think it's hard to get to AWS people. It isn't. Ask your rep and they'll try and get you to an architect.

You might have to ask support who your rep is.
> The mystery of how dinosaurs had sex (2022)

The perfect problem AI can solve.
I love these people's work.

At the same time I don't think any of this really addresses the root causes of the problems, which are career, university administrative, and field (i.e., recognition and attention) incentives. The whole paradigm we use, and the way we treat scientists and fund research, is broken. It feels a little bit like bailing water out of your boat with teacup on one side while ignoring the gaping hole letting rushing water in on the other side.
The only one I know of is Kuru which passes from person to person in Papua New Guinea due to cannibalism.
I will break it down:

1. You argue cashless is annoying because you have to remember your card/phone in addition to cash.

2. I countered that you could equally say that cash is bad because I have to remember cash in addition to my card/phone. Which makes them at worst equal. You just have to remember whichever one is accepted.

3. Except - as I stated and you highlighted - that is not really the case. Almost everywhere accepts card - more than accept cash, so not only is cashless equal to cash, it is better.

(From a "having to remember things" point of view anyway.)
> three weeks of spotty or delayed attendance can lose one a job

Under what conditions will a person have a job that they are expected to be at, but not have car insurance to get there? I'm sure this exists (for instance for someone whose policy is revoked for DUI or accident or whatever), but in many cases I assume public transit or a three week wait to start is acceptable.
If nothing else, gorgeous youtube video: Makes the point, brilliantly edited, funny, actually illustrates what the reviewer sees. Best Apple Vision Pro review I've seen. Bravo.

(And yes, Marques Brownlee's is very good too: https://www.youtube.com/watch?v=dtp6b76pMak )
Yeah fair enough. The login screen should still provide good protection in a TPM-only scenario. (Although it had some vulnerabilities in the past: https://secret.club/2021/01/15/bitlocker-bypass.html)
Unless the time-series was only for simple monitoring or querying, I would stay away from key-value databases like Prometheus or InfluxDB which have limited joins and limited analytics capabilities.

A fully relational time-series database like Timescale (a plugin db built on Postgres) gives you full SQL analytics, including aggregations and full relational joins with other data, which is where a lot of the value-add usually is. This also opens up the field to building multivariate machine learning models.
But even that isn't so simple, because there are at least three types of people who use coupons.

The first are the ones coupons nominally target -- not people who go out of their way to find coupons. Just ordinary new customers who need an incentive to try the product once and then might become repeat customers. These are actually great when you can get them, but they're not that big a percentage of coupon users.

The second is the, let's say, analysts. Smart retirees who now have lots of free time and can use it to find a good deal. Tech savvy customers who know how to use advanced search features to find the best deal or are willing to set up a scraper to send them an alert. These customers are great too -- you don't make much margin from them, but you make a little, and then they immediately go away and leave you to keep their money in peace. And when you offer a good deal, they will come to you, so your margin is lower but so is your marketing expense.

The real problem is Karens. They don't know how to read but own a fanny pack that says "the customer is always right" and want to spend two hours arguing with you to try to get you to accept an expired coupon for the wrong product over something that has a $0.17 margin.
>There is nothing that is safe against physical attacks practically.

This! If security is your prime directive in your line of work(government, highly sensitive data, etc), then as long as your device has been outside your physical possession and in the hands of an untrusted third party, then it's automatically considered compromised and gets wiped or discarded by your IT department.

Because no amount of marketing security fluff from Microsoft, Apple, Google can stand against targeted attacks of state actors or knowledgeable motivated well funded actors with freshly acquired zero days.

The security they provide is only good enough against the average thief off the street, which I guess covers 98% of Average Joe's threats.

Even CC security certifications never judge a device whether it's hackable or not, but only on how long it takes for it to be hacked by an accredited lab, because nothing with outside physical access is ever unbackable. With enough time and six figure equipment off the publicly available commercial market, everything reveals its secrets eventually. And that's without zero days off the black market.
And 20m rows isn't a lot. Maybe they forgot to put in an index?
Well yeah, of course. I can't understand why people reach for a bunch of bespoke databases where you need a whole other ecosystem of tooling and libraries to use and monitor, can't have transactions across them, another single point of failure, your ORMs don't mix if you use one of those.

The amount of work you need to do to make it not worth it is quite high assuming it can be done which they seem to have accomplished pretty easily by DIYing their own provisioned iops rds (not sure why they didn't try that).
This is technically wrong. Increase in gravity does affect buoyancy because air density changes with gravity. The reason is that the column of air above you is compressed by gravity. With very large gravity, all the atmosphere could be compressed down to possibly a few km.
https://www.timescale.com/blog/how-we-scaled-postgresql-to-3...

Staring at a >trillion rows in a TimescaleDB hypertable on PostgreSQL.
> As long as the government can keep a private key secure...

Which government? Software crosses borders.

You can bet that if the US mandated a back door to be inserted into software that was being exported to another country, that country would want to either have the master key for that back door, or a different version of the software with a different back door or without the back door. A software user could choose the version of the software that they wanted to use according to which country (if any) could snoop on them. It's unworkable.
Lots of the manufacturer’s rebates have become instant rebates because of pressure from places like Walmart (who really, really dislikes having to advertise a higher price than possible).