skysight-inc/HackerNews huggingface dataset:
I've always wondered certain vehicles were chosen for fleets. However the original mail truck always made sense to me. It was small, durable, and simple with it's OHV engine and solid rear axle. But what about other civil service cars? When I was growing up the de-facto Police vehicle and taxi cab was the Panther platform Ford Crown Victoria. A rear wheel drive, V8, large, lumbering, expensive, complex luxury sedan that mostly lives in cities such as Boston and NYC where it snowed half the year and rarely could ever go faster than 50mph. Yet almost unanimously everyone decided to go with the 12mpg option that had almost twice the moving pieces in it's engine as the competition with smaller engines.
The web client doesn't seem to support it, or at least I can't find it -- it's definitely not in the contact/profile screen like in the Android app.
It should work with Brave too.
Is it also accurate to say the rest of the universe is wandering though space with respect to the black hole?
As an Emacs user, I just have no use for this, and I get the feeling most Emacs users won’t either.
I think bad actors are the only problem worth talking about. Remove bad actors, and social media becomes a lot more tolerable/positive.

The other problems with social media are either not important to most people, or solved by other services already.
There are probably a lot of reasons. You are assuming there is no good reason, but obviously there is.
Was about to write this.

Here's also an easy summary of it's effect and recommendation If one consider buying supplements:

https://www.reddit.com/r/MushroomSupplements/comments/h090ry...

Bought some myself and tried to track its effect by playing 3DS Devilish Brain Training game and track performance.
Suspending vaccinations for side effects that happen in 1 in 300000 cases is not medically reasonable. Even if all these cases are due to the vaccine, not vaccinating gives a worse result than vaccinating so it’s the dumb thing to do.

Which is what WHO and EMA are saying. But now that there’s panic, they’re not relevant anymore.
Damn that's not an easy feature to find, I just went looking for it from the directions in the article and it was still hard to find.

Admittedly Safari is my default browser, but still.
"Hey John, can you mute yourself? Thanks!"
Actually think the whole thing was totally reasonable along with the few hours it took them to get back to you.

My only qualm would be if instead of removing your extension entirely, maybe it would be better to say "App is currently being reviewed and will be made available soon."
NYPD uses Impalas
Bronner fan for life - they got me hooked when I found myself spending 15 minutes in the grocery store reading the entire label.

IF CAP CLOGS, POKE IT! OKAY!!
Who actually runs Docker directly in production? Doesn't everyone just use managed solutions like ECS?
Yup, when you have one production server or maybe two for good measure, you don’t need a big layer of abstraction on top.

“We don’t need to do very much so we don’t do very much” is a good place to be, what is hard is deciding what and when for building out abstractions. Almost everywhere does it way too early or way too late.
Banning is not a solution to anything. And as far as the value is concerned, it will definitely go down initially when legitimate people will pull out. But in the long run, it will rise because of the alternative illegal use of the currency.

Another thought is that there are ~200 countries. Some of them survive only on illegal funds. Will it be possible to ban this thing completely?
NL? Natural Language?
Rural USPS mail carriers will sometimes use right hand drive SUVs and minivans. There is also a bigger "ice cream truck" for packages.
What Holds Up a North Pole of Dust?
it's OK if you don't get it
I never had any issues with andOTP. It worked even when some websites specifically asked for a different app.
That's how I and many others felt with Digg over a decade ago. People like to use what they are familiar, but if you push hard enough people will abandon the platform. I guess reddit isn't pushing hard enough yet, although I suppose I would be gone if the old version wasn't available.
No, software engineering is also bound by the laws of physics. The worlds do have existence in reality, which you will find out as soon as anything you create starts hitting the physical limits of CPU, memory, latency, which are all pretty much governed by c, the cosmic speed limit.

> And in today’s world, software engineering is essential to make physical engineering a reality.

It is literally quite the exact opposite.
Everything you actually need to know: “ It’s con men with a new variety of magic beans to feed the bubble machine — and artists are their excuse this time.”

For the longer version: https://davidgerard.co.uk/blockchain/2021/03/11/nfts-crypto-...

(jwz did a blog post about them a few days back, but you can’t get there from here. Go find his blog without using a hn referer if you wanna read it...)
I don't like this one bit. Good luck to the author and team, but I despise attempts to bring emacs "into the future."
Would that not be a front and over exertion of states rights? The state said the federal government is overreaching. If they ignore them, would that not lead to the state to fight against the federal government in court?
Yes, there are probably very few outlets where mail trucks currently park. These things are parked in the middle of parking lots, not in garages. And you need more than one outlet, you need one for every truck that parks there. And I am sure no current USPS office has power service hooked up for several hundred amps of draw that was never anticipated to be used.

There's no way to do a project this big without phasing it in. The USPS has many tens of thousands of buildings.
did you know that the internet was invented by this guy and not Tim Berners-Lee? https://en.wikipedia.org/wiki/Robert_Cailliau
To curb your urge, cloth insulation was common until the 60s in GB and if you are a very unlucky contractor you dig up paper insulated wires and nope out.
This is a good corner cut, but in addition to other comments, there's two huge accessibility concerns, and one usability/design principle problem:

1. The color spaces available in CSS are not perceptually uniform. You may achieve some a11y checkbox with the inversion of luminosity/hue, but that doesn't mean it's actually readable.

2. Not all, but many, dark mode users prefer lower contrast in some areas to reduce brightness over all. This approach can tailor in the opposite direction.

3. In general with dark themes, it's still generally preferable for darker-in-light-mode things to be darker in dark mode. This does the opposite and can lead to confusing design structure.
the same can be said for the JVM; all I have is a jar for my product, and setting up a new machine is as easy as spinning up a VM, installing the JVM, then running a jar. It's great!
There is nothing to play down. More than a year into the pandemic are there is still no evidence of long-term damage except in rare cases. Evidence of inflammation in monkeys does not qualify, before you ask.
How long will it take to recharge these hundreds of vehicles, and who will be around to take them out of their charging stations and move in a new vehicle?

Electric vehicles are great but at scale, the issues around charging them daily are very real. It works for a single homeowner, but if a post office has 100(?) trucks, and it takes 2 hours to charge, someone needs to be there to keep track of them, unless you expect 100 charging stations.
Why do you trust Telegram more than Signal?
Just to clarify my point: The bug was a screwup. We’ve all done screwups. My worst bug was an amateur hour royal screwup that resulted in DDOS. Nobody should be shamed for bugs, including serious ones that get to production.

Not fixing a serious, visible, known bug for six years is what’s shameful. There is nothing positive about neglect like that. It’s kind of admirable that they actually rewarded the guy but it shouldn’t have even got to that point.

Totally agree you should not shame for bugs. The shame is for ignoring this bug until one of your customers finally had enough and fixed it by patching the binary. If it was my company I would feel ashamed.
"in the end can you really say it’s simpler than what we’ve got for free built in to golang?"

In this cherry picked example with a golang binary, sure. At my job, docker has saved us probably hundreds of man-hours. We don't have to worry about complications like systemd, because I can tell a container exactly how to run. Etcetera.

You can copy the golang binary into an alpine container and instead of having to maintain a server, you now have ephemeral containers that can be destroyed, spun up, scaled...

There is a difference of keeping things minimal and refusing to use industry tools. There is nothing scary about docker or even kubernetes. But they do take time to learn and understand, and yes, the benefits of containerization outweigh using bespoke server setups.

edit: s/systemd init scripts/systemd. We use s6-overlay instead of systemd to manage processes in containers.
Do you have a database, a queue service, a caching layer (or 3), a session store? If all your app needs is an http server then sure, why bother with docker... But if it's more complicated than that, it's great to have standard recipes for alignment in local development, a problem docker solves very well
Are you an Investor? We would love to speak with you
Oh dang...you're right

$ csc -optimize-level 5 fib.scm
$ time ./fib

real 0m5.506s
user 0m5.489s
sys 0m0.010s

I could get a few fractions of a second better playing with the stack size (4 MB was the best, 8 MB or above would segfault)

$ csc -optimize-level 5 -stack-size 4m fib.scm
$ time ./fib

real 0m5.295s
user 0m5.277s
sys 0m0.011s

Everything else was negligible or extremely varied.
If they looked too good, the sad fact is that they might be targeted for being stolen.
Google Photos circumvents iOS 14 photos privacy features
The same can be said for static c++ binaries. Setting up a machine is as easy as scping the bin to the host and running it. docker isn't necessary, it's just nice for repeatable builds.
That's slightly better, but they have used Crown Victoria's in the past. Kind of hard to continue using them when they've long been discontinued.

But still, why the Impala? Why an 18mpg, FWD, 300hp transversely mounted engine design? Why kneecap yourself with a shit car? When do they use the full potential of the Impala, or the Crown Vic, or the EcoBoost Explorer? Even in the 90s and 2000s. Why not solicit contracts for custom vehicles? We could have had a 4d, 4WD Mitsubishi 3000GT Sedan Interceptor Edition. Instead there are enough Panther platforms cubed up in junkyards for every man woman and child in America.

It goes to show that the requirements for police vehicles are crafted by the police themselves. "We need a high performance, 2WD luxury car with... ahhh... three, NO four... yeah FOUR hundred horsepower!"
Interesting! As I recall, that was the same one that motivated my advice above. Maybe something about the tea tree oil, I thought, but I was strongly disinclined to further experiment.
I think most standard readers are compiler writers.
It seems like you are comparing a theoretical modern EV to the terrible efficiency of the old LLV. They didn’t choose to continue buying the old LLV, they are buying a vehicle with a new ICE. So the comparison makes little sense.
States don't have the right, under the current US legal system, to nullify federal laws.
> No, the reason we went with go was because golang’s packaging is so much better than node. Or java. Or C#. We get a single binary. Building is as easy as: `go build`

This is only true insofar as you have an extended group of collaborators committed to observing the fundamental tenets[1] that make this work. Not hard to run into (popular!) software written in Go that is as bereft of this simplicity as the other ecosystems the author compares to. (Interestingly, Docker itself is the product of minds that were exposed to Go, and yet these principles didn't "take" in that case...)

1. http://blogs.perl.org/users/leon_timmermans/2020/08/perl7-is...
Some recent experience going over the pros and cons for the most well known API Gateway out there (e.g. AWS API Gateway, HAProxy, and Kong) had us go back and forth between those.

Although I have no experience with any in particular, the experts I know are leaning towards the apparently most complete, mature and robust solution which we concluded to be AWS API Gateway, which in my view has an extremely high fidelity that's hard to reason against (though I'm looking forward to be proved wrong).

AWS API Gateway might probably have its own complexities and depending on what you're solving for specifically, might be way too much to take. But make no mistake, the knowledge you and your team will acquire is likely to payoff in the long run since I think it'll likely span across decades and continue to develop faster than most of its competitors. Though to be clear, I'm also for giving smaller businesses a fair shot.
If you instantly "escalate" your problem to your teammate without having made an effort it gives the impression that you don't respect their time or concentration.

So make an effort first so that when you go to your colleague you can tell them a few things that you have already tried. You may find an answer before you need to go to them. And if you don't find the answer the list of things that you have already tried can help set the context and help your colleague to help you better.

This is particularly important if the problem is easily google-able. If you keep going to your colleagues for help and they search a few keywords on google, go to the first result and show you the answer right there that's the sign that you are not making and effort to solve it yourself first.
I don't know about how hermetically sealed go's packaging is, but the main advantage of docker is that when Ubuntu 26.04 and python4.3 comes out your docker image containing nodejs, python3, and tensorflow 2.3 code should theoretically still just work out of the box. Really good for "set and forget" deployments that might be forced onto new hardware or OS at some point but when you don't want to ever touch the code again except for bugfixes.
You're right about it being a tricky attempt at faking an apology.

But the below isn't correct:

> Right, so the company is saying "I will never acknowledge our mistakes because if I do we might have to fix them."

I probably didn't word it perfectly in my original comment, but the company did acknowledge mistakes quite often after assessments of the claimed faulty/broken/whatever product (roughly 30% of faulty claims were approved and either repaired or reimbursed from memory). The rejected claims were often taken to court (like 15%) due to the value of products.

I was mostly commenting on the deception of only allowing pseudo-apologies.
What do you see in the parent comment that says they _shouldn't_ do this? It's just laying out that they _are_ doing it, in direct response to a comment wondering why their site is so terrible.
Try BigInt in JS https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...
Australia did the same thing.
And this is a significant difference to how mail is delivered in most of Europe, where the vast majority of last-mile delivery is done on foot or on bike, and relatively little is done by vehicle. Density undoubtedly plays a fair role here.
Can you imagine a marketing company ever approving a label like that? And it's so distinct, effective, and memorable.
I worked a on a couple teams where there was a constant crush to reduce complexity, remove code, streamline, remove corner cases. What is even better, is when engineers can be product designers and simplify features or cut them entirely. My best example of this when the spec called for a continuous value for a predicate, I arbitrarily changed it to small, medium and large. But it brought in the schedule and the schedule by 10 days.

Shared simplicity is a superpower.
> as is usually seen with other vaccines

Is this really true? I can't recall having any vaccine in my life that's ever knocked me out like I often hear reported for the sars-cov-2 vaccine.
I imagine they will keep a few gas powered vehicles for very hot climates.
No, enforcing lockdowns is an action.
Judge rules Google to face lawsuit claiming it tracks users in Incognito mode
This was a hilarious clip. Brought me back to 15 years ago, messing around with people on Ventrilo while playing World of Warcraft. Many, many lost nights and days playing that addictive game. Comic relief thru Ventrilo harassment was necessary...
Eh, I'm not sure about that. People don't steal cars because they look good. And the people who do, probably don't think box trucks are that attractive. Stolen vehicles are usually crimes of opportunity.
Yes. I do k8s all day and this solution wins every time for simplicity where possible. I get it -- service discovery, healthchecks, no downtime deployments, the rest of the k8s goodies -- doing all that in a generic way is hard!

So just orchestrate your business logic. There's no shame in that. And you might well come away with a cleaner system than if you tried to wedge everything into Kubernetes or some other orchestrator.

I've come full circle -- started with Mesos, moved to Kubernetes, dabbled with Nomad/Consul. I love what Kubernetes offers. Avoid the complexity if you can. If you don't NEED to pay the price. Just don't.
It is impossible to study the long-term effects of any vaccine within a year. Impossible. Unless you are elderly or immunocompromised you are almost certainly exposing yourself to more personal risk by being vaccinated.
Wouldn't it be funny if they did? I can imagine perhaps USPS contracting out some low volume routes to Amazon.
Thank you for a comment. It's relief to find someone who has a perspective that lines up with modern research on intelligence. There is so much denial as so many of these people seem to think everyone is more or less like the people they work with and don't understand how even the dumbest person at the office is probably 2 standard deviations above the norm of intelligence. Even higher probably if they work at a really desirable company.

I've scored as low as 112 and as high as 127 on officially given IQ tests with the average being around 118. I'd be interested to know if you have any advice for someone with that level of ability.
> Using "buffer" as a name for text being edited is hardly worthy of the title weird, vim does it too. Lots of other text editors as well. "Buffer" != "file", the first exists in the memory of the text editor process, the second exists on the file system. Their contents may differ, and one may exist without the other.

It doesn't matter. When people talk of editing documents in Word, they speak of opening a file, not a buffer. That's the metaphor people are used to. It may not make sense, but saying "well, ackshually, files refer to the copies on disk while buffers refer to the copies in memory" just confuses people more. Have we learned nothing since Macintosh 1984? Actually, we haven't; we've gone backwards. The spatial Finder was based on very deep psychological notions of how humans relate to the world: through spatial orientation and object manipulation. Meaning that there is only one place on the screen where a given file appears, and it appears at the same place every time unless the user moves it. In short, it works like an actual desktop with real physical pieces of paper. And Apple brushed it aside in favor of NeXT's Unixoid "file manager".

> Likewise, calling the subdivisions of the screen "windows" is something which vim does too, and likely other editors also. For a text mode editor, it makes perfect sense. When you then port such an editor to a GUI, you end up with "windows" which are subdivisions of the GUI "window" – vim has that too, not just emacs.

Again, it doesn't matter. The ordinary user's concept of a "window" maps directly to a GUI window, so if you expect your program to be used in a graphical environment without confusing the shit out of people, you need to adopt that environment's terms and concepts.

Meet. Your. Users. Where. They. Are.
It’s entirely possible we just have very different skin/hair/body chemistry and react very differently to it! Let this be a disclaimer to anyone reading the thread above: it might affect you differently!
I have most of those things. I just use hosted versions of those things.
There's a throwaway line in there:

> Note, we did get a little more complicated and create a SystemD script to launch it at startup.

There's a good chance that most of what you want is in Systemd.

Restart a process if it fails health checks? Systemd. Do you want to isolate a process in a container? Systemd. Open privileged sockets? Systemd. You can do a lot with Systemd.
You don’t need a “charging station,” you just need an outlet. And you don’t need someone to “charge” them except the person who parked it. It charges at night after use. An exterior outlet costs almost nothing compared to the fully burdened cost of a parking space.

Of all the “very real” problems with electric vehicles, you picked two or three things that aren’t.
They've been using Impalas since at least 1996, but I guess they have a mixed fleet that also includes some Crown Vics:

https://en.wikipedia.org/wiki/Police_vehicles_in_New_York_Ci...
Interesting. I can't get it to give me any options like that personally. (Maybe because I have a security key active?)
I'm guessing they wouldn't be strictly street legal for general use?
It’s just funny to use three separate encapsulating technologies inside each other... when do we add another layer?
Yeah, I agree. Avoiding apologies is probably a good idea for the company. The part that stuck with me was the "acceptable" pseudo-apology.

Not apologised at all comes off better than a backhanded apology IMO.
Along with this, vertical scaling is severely underrated. You can do a lot and possibly everything ever for your company with vertical scaling. It would apply to 99% of the companies or even more.

Edit:
Since people are confused, here is how StackOverflow handles of all of its web operations. If SO can run with this, so can your 0.33 req/minute app which is mostly doomed for failure. I am only half joking.

StackOverflow architecture, current load (it will surprise you): https://stackexchange.com/performance

Everytime you go to SO, it hits one of these 9 web servers and all data on SO sits on those 2 massive SQL servers. That's pretty amazing.

I want to be clear though, Horizontal scaling has a place in companies that has a team of corporate lawyers. Big. And in many many other scenarios for ETL and backend microservices.
How do you know if you're getting the actual mushroom vs. the substrate?
Good point about timing: it really is easy to spend your wheels and waste time early in the app lifecycle on things that don’t matter and never will. But it’s also true that if you stay focused on cranking out product and don’t worry about long-term architecture, you just might end up with a large, successful ball of mud that’s no fun to maintain or work on. Finding the inflection point between those modes isn’t easy.
That's pretty much me, I told my wife if I put up the finger to wait and try again in 15 minutes, unless it's my son's daiper or whatever, then I'll happily take the loss of context.

I also found that functional programming, types or type annotations, and writing very small functions glued together by longer functions helps to reduce cognitive load when solving problems. Then I can add comments to literally bracket the area I am searching for the problem or solution and slowly move them closer together as I rule out functions and stuff.
Go's packaging is about as hermetically sealed as it gets--deployment is a single executable binary. No external runtime, no support files.