skysight-inc/HackerNews huggingface dataset:
I learned Haskell a few years ago, enough to read it, but not fluent enough to comfortably write it. Haskell scratches a real intellectual itch, related to how it formally captures certain concepts (types, purity, etc). But my opinion is that Haskell collapses under the weight of its terseness and academic complexity. Can it be extremely elegant? Yes, in contrived examples[0]. Is it able to maintain this elegance when dealing with common problems? No.

0. https://wiki.haskell.org/Introduction#Quicksort_in_Haskell
"Sony panicked and bought a company that has one franchise (Destiny)."

If you think Sony turned around and bought Bungie in the 2 weeks since the Acti-Blizz acquisition was announced, I dunno what to tell you.
Sounds like you ignore that YT has a subscription business model along side the ad-based one..
> Still, even without capitalism, you'll have to contend with the issue of how to cover operational expenses

You're still thinking in the framework of capitalism.

Let me be clear that I think that doing anything but capitalism is bound to fail while we're living in a resource restricted reality.

Nonetheless, if we want to think about it for arguments sake: there are no costs associated without capitalism, only necessary work and resources. It's really hard to think without the restrictions of capitalism for me, because that's the only way I've ever experienced and it's so effective at prioritizing resources and productivity. Anything else has historically always fallen short.

Though it's still a pretty fucked up and heartless system
I am referring to the early 2000s when half the Hollywood celebs were driving Prius [1]. Prius carried the hype about hybrid cars back then the same way Tesla is doing now for EVs.

[1] https://www.autoweek.com/news/a2082556/starring-role-hollywo...
What is AB?
All perfectly valid points. May I ask what you mean by #1? Interest rates are historically low and a fixed mortgage will only change based on property taxes and insurance.

#2 is something I thought about a lot as I was buying my first home, but I couldn't see how a drop in wage would change anything, since my mortgage is now less than what I paid in rent for just a modest apartment.
Me neither. I am even in Quebec, but on an English device.
I'm a big fan of one to ones, but only if both parties are into it.

If it is a status report, it should be an email.

It should be a place for you to discuss topics that are stymieing you and/or build rapport and trust.

I've had direct reports tell me they wanted to have a 1:1 less often, so I know my style of 1:1 doesn't work for everyone. It's a big world.

I wrote more about 1:1s here, esp managing them from the perspective of a new developer/employee: https://letterstoanewdeveloper.com/2020/03/16/how-to-manage-...
standard text format for legal pleadings feels like it has more of a value prop

- for litigants, standardizes the production of documents

- for legal researchers, makes it easier to discover / extract what they need (vs current PDF workflow)

- for hosting tools like PACER, makes it easier to index references and preview docs. for courts who have to accept e-file, lets them do more auto linting / checking on filings

- for people in the judge's office, makes it possible to build summarization tools that simplify reading memos etc
GET with "Query" header + "Vary: Query" header, might be a thing to get escape from the cache dungeon
I live on London where we have "good" public transport.

Yes a bus or the tube "solves" these problems of not having a crap UI, but they also introduce so many more and worse problems that don't make up for it. Expensive, inconvenient, dirty, late and/or slow, uncomfortable. And at least a car with crap Aircon controls actually has Aircon at all!
The supplies that just flew off the shelves and were sold at a fair price are more than incentivized for being restocked or even served by pop up wholesale resellers.

It's not like the anti-gouging laws lock in a price under profitablity; the stores wouldn't have the items even before the anti-gouging kicks in if that were the case.
Tunicates evolved long before animals that you would recognize as typical vertebrates. In their free-swimming larval state, tunicates do have a "notochord", or nerve chord, running along their head-tail axis. This structure is a kind of proto-spine. The evolution of true vertebrates proceeded from this condition by neoteny, the retention of larval traits in the adult body plan. Pyrosomes look so bizarre compared to a layman's notion of what a chordate should look like because they are colonial aggregations of lots of individual adult tunicates that have resorbed their notochords (I'm pretty sure that's the case, despite what the photo description says).
That's assuming it ever leaves my github aka my code graveyard (where sideprojects go to die).
My theory with the XC60 refresh with its huge, high, flat-top, snub-nosed bonnet compared to the old sloping one is that all that extra volume is for the fancy double/hybrid engines and so on.

Or maybe people just like to feel like their car is a rhino, but the same refresh also slightly lowered the roofline and the driving position feels lower too.

The other down side is that my wife always shouts that I'm going to crash when parking nose-in because the bonnet feels twice as long as it really is.
The New York Times buys Wordle
I can find value in understanding why some people felt they were useless and why others felt they were productive. Most of it probably won't be great, but it helps consider things I did not know I did not know.
Please don't, unless you can replace the dumb driver. Dumb cars usually involved in dumb accidents because dumb driver drives dumb.
Fascinating if one person is interviewing for many roles then sending in proxies to do the jobs in return for a kickback.
One reason we believe this is that we can typically detect virus quantities way too small to reliably replicate in culture, and believe that in vivo infection is even harder than in culture (because of innate immune response and the body not being composed just of the most susceptible cells).

You generally can't measure infectious dose directly without a highly unethical challenge study. You can sometimes know concentrations that did or didn't result in infection in various real world scenarios, and sometimes you have circumstantial evidence (e.g. you can know how much virus a person sheds, and what proportion of a room with certain ventilation quantities got infected).
> I find it intriguing that only in the digital age have we sort of decided that the creator of something doesn't get to dictate the terms of its use.

Except that's not true. Mark Twain and Shakespeare cannot tell you you're interpreting their works incorrectly. JK Rowlings cannot stop you from making paper mache out of her books. I can timeshift and spaceshift content with tape recorders, VCRs, TiVo and more.
> This specification defines the HTTP QUERY request method as a means of making a safe, idempotent request that contains content.

I’m already seeing implementors failing at following the spec here – they will equate the QUERY method to querying a mutable database, which won’t give reproducible results, and to give reproducible results the server would need to save it. Now to make it idempotent, will be an ad-hoc decision of each server. It seems contradictory. At this point it’s indistinguishable from a PUT on a resource that represents the query itself.

I’m not seeing the point of the new method.
But Youtube does have a subscription business model? You can pay for Youtube Premium ( https://www.youtube.com/premium ) and see it without ads, with downloads for offline viewing and listening, and so on. Almost exactly like Spotify.

People just ignore the ads instead.
Should I max out my PS Plus subscription because it's about to get converted to something else at a favorable value ratio?
> don't fully support the 7 existing http verbs

9 to be precise (RFC 7231 defines GET, HEAD, POST, PUT, DELETE, CONNECT, OPTIONS, TRACE, RFC 5789 defines PATCH).

Some of those are not commonly used because of various security vulnerabilities that have been discovered over the years (see https://www.kb.cert.org/vuls/id/867593, https://www.kb.cert.org/vuls/id/288308, https://www.kb.cert.org/vuls/id/150227) for some examples.

Some tooling goes as far as defining some of those methods as "forbidden", like what the standard for JavaScript Fetch does.
It's not rude and uncalled for to point out a very valid point.

Your comment on the other hand is completely rude and uncalled for as it gives zero value and the only thing we learn is that 'it hurt your feelings', probably because you too dislike 1:1s
It is not abuse. You are using the platform, the platform is monetized through ads. You requested it when you agreed to view any content on their platform.
> When dressed for the weather riding in the cold weather can be quite enjoyable

Not as enjoyable as sitting on my heated leather seat, sipping coffee, listning to an audiobook and moving my right foot back and forth between the the accelerator and brake while my wipers and heater keep the sleet off the windshield.
I'm honestly appalled by the price for YouTube Premium. It's $15/month. That's the same as HBO Max, almost twice of Disney+ and more expensive than F1TV or Showtime which come in around $10. Per month this is 50% more than Prime! Only my UltraHD Netflix plan is more expensive. This price to me is outrageous, given that Google, unlike everyone else listed here, doesn't provide any of the content and their services is known to be awful/non-existent. All they do is in essence provide the platform.
2000s priuses were very cool amongst the aging boomer-hippy population. When they first came out it was a big deal to be in the school pickup line with your prius. You probably also shopped at organic grocery stores like whole foods (before the AMZN purchase), and just transitioned from pilates to yoga. Southpark even made an episode about the phenomenon.
It’s hard to recommend a tech stack without requirements and conditions. Maybe you can extend your question a little bit?
The short version is that it's perfectly fine. This doesn't modify the HTTP spec, and it uses established extension mechanisms.

The long version:

RFC 7231 defines the standard HTTP methods in section 4.1. [1] Looking at it, the only methods that are required are GET and HEAD. All others are optional, and the spec explicitly calls out that additional methods may be created and registered with the IANA.

Looking closely at this RFC reveals two things:

1. It doesn't modify any of the HTTP RFCs. (There's no "Obsoletes" or "Updates" header.)

2. In section 6 of the QUERY RFC, it requests that the IANA add the new method to its registry. That follows the guidelines in RFC 7231 section 4.1.

[1] https://datatracker.ietf.org/doc/html/rfc7231#section-4.1
"Literally never have I walked out of a 1x1 and thought "wow that was unreasonably effective"."

? Nobody would ever suggest that you should feel that way, or that an individual 1x1 would be singularly effective.

When you go Heli-skiing, you ski with a partner, and you're constantly shouting out to your partner to let the know where you are. Primarily, you do this because of the various kinds of danger, especially avalanches. That those things are unlikely does not abnegate the need for communication.

One thing never made obvious in films or popular culture is the amount of communication in the military. 1/2 of the game is communicating. It's information, which is the basis of coordination, which is the basis of management of force. A 'radio' is as important as one's 'rifle'. A rifle can defend you against one person; a radio connects you with the totality of the power of the system you are in.

The point is it's a form of systematic communication which I would overwhelmingly support.

Especially the bit about 'open ended' - my gosh there are so many details lost in the normal operative aspects it's almost scary.

'Status Updates' are generally not meaningless, it's one of the means that people use to coordinate, though they can be cumbersome.

Wasted time in meetings is definitely endemic, at the same time, a lot of complaint is sometimes rooted in the lack of understanding of the nature of one unit within the larger system.

As developers, we feel that our 'code' is our productivity, but it's like the 'rifle' - it's just the obvious thing. The 'radio' is the other key thing.

Also - the 'performance' bits are probably overdone. It's extremely hard to change habits. You can definitely get people to do things like adjust to a coding style, but it gets hard past that. I'm more of the view of just trying to leverage what people are already good at because most people are good at 'something'. But merely as 'coordination', these things are important.

Especially with direct managers, there needs to be fairly consistent communication, which is different FYI from large team meetings of which there are probably too many.
I don't disagree, but my point was that they shouldn't. Clarence Thomas famously wrote about believing that his own success was tainted by affirmative action, and later he was indeed appointed to the Supreme Court primarily because he was a black conservative. That doesn't mean he was unqualified or less fit for the court than previous appointees, no matter what his own insecurities were, and it also doesn't mean that he or our society would have somehow been better served by Clarence Thomas not being given any of the opportunities affirmative action programs may have afforded him.

The deeper problem is that there isn't really a solution here. The old system wasn't neutral and instead actively discriminated against huge swathes of the population. That the beneficiaries of that system never doubted their worthiness doesn't make the old system better, and any change that impacts them will suffer from the same aspersions about a lack of "merit" that we are seeing now.
I agree, my guess is it's caused by the lack of white space.

The margins are too narrow which makes it unclear what belongs to what and where the boundaries are. That can feel messy as it all sort of blends together visually. To compensate they used lots of borders, but those tend add more density without enough white space.

I don't think the actual layout is that messy, it's a nice column layout, seems decently structured, nice sections. It's just really hard to see atm.

I think if they use this exact layout, but just give everything some "breathing room" it would be much better.

The other thing is the images. They use screenshots of UI without making it into a graphic; meaning it doesn't look like a graphic, easy to fix, would improve things a lot.

The second thing that stands out to me is the text in the images. Beyond bad practice it's messy as now there are two titles that are competing for my attention. I think just the text on the graphic (as actual text) or just a graphic + text as it is now, would be much better!

Anyway, I agree, it's a bit messy. That said, I think it could be quite nice without too much effort.

I would love to play around with this, I think it has a lot of potential.
Good point! I should update this site and mention that.
While we are at it, please make dumb TVs too.
It surely does, calls go both ways, and Closure doesn't understand everything introduced on the JVM since Java 8.

Poor students, at least Blue/J.

By the way, I already used Clojure in projects.

Usually I only critic stuff I actually know.
> Perhaps it is easier to roll out a new request method, rather than increase the scope of an existing request method.

It’s easier to define semantics for a new method than to expect everyone to change how an existing methods is handled by all existing software.
How about old-school mailing lists? They seem to be still used by OSS teams.
I remember one time I was talking about web ads with a few friends and said something along the lines of 'you have to be stupid as fuck not to use an adblocker on the internet these days' and literally 3 out of 5 people immediately popped up and said they don't use them. All were using one within a week, lol.
Note that deb packages are not usually signed unless something major changed in the last 5 years or so. The repository metadata is signed and contains a checksum of all packages. It’s all safe as long as you install from a repo, but installing a deb package directly doesn’t usually do signature checks. See https://www.debian.org/doc/manuals/securing-debian-manual/de...

AFAIR there are options to sign packages themselves, but there’s at least two competing incompatible signing schemes.

rpm packages carry a signature in the package itself.
Toyota are doing fine because of their reliability. Can the same be said about Tesla?
If IoT was done responsibly, then we'd be more willing to try. The example was wifi connecting something that gave no benefit, and introduced significant risk (having a bad actor inside your wifi network). It doesn't take a scientist.

IoT could be done so much better. First, give some benefit (E.g. give you a service call when something went wrong).

And Why not use a simple VPN to the host? Encrypt the link some other way? Hell, require a password?

I've programmed IoT device firmware for clients. I put in security - they want it removed. Because it makes installation harder for their staff. No profit in it.

I'd run from any IoT device today. Until we have some legislation or accountability or even UL rating for security, there will be no security at all.
how is that Tesla even legal?
It depends on your risk appetite. You can test exhaustively, and that's safe but probably slow.

I think a lot of shops employ some kind of heuristics to figure out what combinations to focus on e.g. "most of my most serious rendering problems happen with language/font combinations that usually take up a lot of space and use non-latin characters at smaller screen sizes" and so might lead someone to test those combinations more than ones that are seen as less risky.

Totally made up example, or course, you need to build up these kinds of insights from experience (or buy them from someone - but not me, I'm not a frontend guy).

You could potentially test 'diagonal' slices of your test cases - i.e. you might not test every combination of {Edge, Firefox, Chrome} and {English, Chinese, Spanish} - so your test combinations might be something like {{Edge, English}, {Firefox, Chinese}, {Chrome, Spanish}} - then you don't test every combination, but you get a kind of cross-section that tests every one of your test arguments in at least one scenario. Where there are many parameters and dimensions, you can test a few of these 'diagonals' by cutting the test data in different ways to get pretty-good coverage without suffering so much from combinatorial explosion, and pick carefully which dimension combinations you wish to create test scenarios out of.
Wordle Is Joining the New York Times
Ultimately they must persist in memory to be useful. Beyond bootstrapping, sometimes API keys, etc must be read continuously. Env is as good a place as any if you need it continuously.

If you mount a tmpfs and copy it into the container env at runtime, is this much worse than mounting a secret object in the k8s Deployment/pod definition in api server?

You could argue that the k8s API server wouldn’t learn it if it was runtime discovered, but this increases complexity. Are ephemeral secret mounts that much better than the built k8s secret objects? I would say no.
This reminds me of the Trump ‘Four Seasons’ media event.
Compared to average is what matters, not compared to other "fringe" ideologies. I think to equate "fringe" with dumb in general is foolish.
All the manners in which the vaccine could have been tested, were employed before deployment. The only thing that wasn't done, as you note, is to wait for XX number of years to see long-term side effects. So in fact, we don't know what the effects of this vaccine will be in 10 years -- because the only way to know that is to wait 10 years. But... there is also no indication, from similar vaccines, that "something terrible" happens in 10 years.

A lot of people out there are just imagining, out of nowhere, than in 10 or 20 years, everyone who got the vaccine is gonna get autism or sprout a third nipple or keel over dead. But they're just imagining this. I can imagine a lot of things too... like, who here can prove to me that the new Doritos flavor introduced last year won't trigger brain cancer in 20 years? Anyone??
> fishing a single item out

This is the challenge. Allow for partial unload without displaying "ready for dirty dish load."

Ultimately I think it has to be performed by a manually operated sign, which can easily get out of sync with the dishwasher state.

https://www.amazon.com/Dishwasher-Indicator-Dishwashers-Home...
For some bizarre reason, at one particular health care provider my blood pressure always read high. At my current and previous primary care doctor, as well as with my personal BP monitoring deice, my BP was always in the "normal" range. But at the one doctor (a cardiologist) it was always, consistently, very high, regardless of who did the measurement or which machine they used. I felt no particular stress or discomfort there (no more so than at any other doctor), but it was like that for years.
yes, ironically the word choice is to avoid bike shedding, if I said it was the ultimate issue there would be all sorts but but no, this issue, where as if it's the 2nd everyone can have their pet issue be most important and we can reach agreement on it and move forward while tabling the discussion of what is the ultimate issue.

Whenever you have one of these bike shed issues in a meeting, do this:
Give everyone 5 minutes to say their piece, give everyone an opportunity to ask 2 follow up questions to anyone, and a 2 minute response. Go through everyones opinion, take a vote and move on. Then set a date 1 year in the future to review/change the policy.
Sometimes reality beats fiction: http://rupy.se/doc/

I chose Query.java as the class name for my combined GET/POST container back in 2008:

https://github.com/tinspin/rupy/blob/master/src/se/rupy/http...

Back then it was hosted on google code.
Just compressing PDFs is not informative enough to tell the user what it is doing under the hood. Is it subsetting fonts? That's usually harmless. Is it rasterizing the vector graphics? That's generally not fine by me. Is it downscaling the raster graphics? It's probably fine but would depend on the intended audience of the PDF and the DPI. Is it merely optimizing the compression used for compressing the content stream? That's also fine. Is it using some thresholding to reduce grayscale to black-and-white? That's only fine if the document is scanned. Etc, etc.

I can never trust this kind of "simple tool" that magically reduces file sizes without telling me what it's doing. Personally, I think PDF is too complicated a format to have this kind of simple file-size-reduction tool.
Congrats to Josh for a 7 figure payout - I just hope it remains as barrier-free as it does now.
The GNU Name System
> And besides being non-functional, these interfaces are even ugly! The type, the layouts, and animations scream “designed by committee and approved by someone who doesn’t have to use it.”

The main problem is that the car manufacturer has a monopoly on selling you features and updates after you have bought the car.